Privacy policy
Effective 4 October 2026
How DemoBro handles information when you visit demobro.com, use the service, or connect the DemoBro Browser & Recorder extension to an application tab.
Contact us about your data1. Who is responsible
DemoBro provides the service at demobro.com and is responsible for the account, website and service information described here. Contact support@demobro.com about this policy or your personal data.
If your employer or another organization chooses the content of a demo, that organization is responsible for its decision to capture and share that content. Its instructions and any applicable data-processing agreement also govern our processing on its behalf. This policy does not replace the privacy terms of the application you demonstrate or the coding agent you choose.
2. Information we handle
Selected page content may contain names, contact details, personal messages, financial information, health information or locations. We do not request browser geolocation or read the browser’s general history database, but such information can appear inside a page you select. Use sample data and only capture information you are authorized to share.
- Account and service information: your name, email, sign-in and authorization information, team membership, preferences, support messages, subscription and credit usage, and payment references. Stripe processes checkout and payment details.
- Demo content: the prompts, scripts, files and media you provide; generated projects and videos; and any presenter photos, voice samples or other assets you choose to use.
- Connected-tab information: the selected application’s origin and observed URL path, page titles and visible text, descriptions and positions of controls, screenshots, manual clicks and steps, action results, and connection, pause and approval status. Automatic page observations remove URL query strings and fragments; content you explicitly provide or capture can still contain URLs.
- Connection authentication: a pairing code and scoped DemoBro connection token. These authorize DemoBro access; they are separate from your application’s passwords and session cookies.
- Technical and usage information: browser/device details, IP addresses and request logs, identifiers, visited DemoBro pages, feature interactions, errors and performance events. DemoBro’s own analytics disables automatic content capture and session replay; creator-configured analytics on shared pages can behave differently.
3. Browser access and local sign-in
Automatic browser access begins when you select a tab, review the connection disclosure and grant permission. The extension runs packaged code to observe the selected application and perform supported demo actions. It does not require access to your application’s source code. The DemoBro application also uses a small extension bridge to pair a project and show connection status.
Vibe the demo opens the website you enter in a new tab and explores its pages after you start it. Page observations are sent to DemoBro to prepare a private demo draft. Detected sign-in screens or problems pause exploration. The extension uses browser notifications to ask for your help; the same request remains visible in DemoBro if notifications are unavailable. Clicking a notification opens the relevant tab. You complete sign-in yourself and choose when to resume or stop.
The extension remembers validation for your DemoBro website address. It uses your existing browser session cookies to check your account and renew expired access, including when no DemoBro tab is open. Only the validated website address is kept in extension storage; account profiles, passwords and sign-in tokens are not copied there. Reconnect lets you sign in again when your session ends.
The extension requests access to all sites when you install it or approve an update. This enables screenshots and recording across websites in the tab you select. Recording starts only when you choose to start it, follows navigation in that tab, and can be paused or finished at any time, including before the first step. The DemoBro Studio shows recording status and captured steps live; saving or publishing uploads the recording to DemoBro. You can restrict or revoke site access in your browser’s extension settings.
Enter application passwords and verification codes directly in your application. The extension does not read its cookies or browser storage. Detected authentication screens and sensitive actions pause automation so you can act locally and choose Continue. Detection is not a guarantee that every sensitive page or action will be recognized.
Input fields and marked private areas are masked in captured images. Masking does not remove all sensitive information visible elsewhere on a page. Keep the application tab visible during capture, review the resulting content, and use Stop and disconnect to end automatic access. You can also revoke site access in your browser’s extension settings or uninstall the extension.
4. Why we use information
We use information to provide your account, connect your selected application, prepare and run the requested demo, generate and edit content, render and share outputs you choose, process payments, provide support, prevent abuse and maintain the service’s reliability.
Where European data-protection law applies, providing the service you request is based on performing our contract with you; security and essential operational work rely on our legitimate interests; legally required records rely on legal obligations; and processing that requires your consent relies on that consent. You may withdraw consent for future processing. Browser permission is a technical control and does not by itself establish a legal basis to capture another person’s data.
5. Who receives information
Data is shared as needed for these functions, at your direction, or when required by law or necessary to address fraud or security threats. A chosen integration or AI provider may process information outside your country, including outside the European Economic Area. Contact us for the providers and applicable transfer arrangements for your workspace; we do not promise that every connected provider processes data exclusively in the EU.
- DemoBro’s hosting and storage infrastructure, including Microsoft Azure, processes account and demo data to operate the service.
- Your authorized MCP client or coding agent can receive browser observations, screenshots and action results. The agent and its model provider process this information under the terms you have with them.
- AI-generation providers receive the prompts and relevant context needed for the feature you request. The configured route can use self-hosted models, OpenAI, Azure OpenAI or Mistral. Depending on the feature and configuration, voice, image and presenter generation can use self-hosted models, OpenRouter and its selected providers (including HeyGen, ByteDance Seedream and Fish Audio), ElevenLabs, Hedra, Sync Labs or D-ID. Photos and audio you supply serve as references for the generation you request. Only use these features with the required rights and consent.
- Stripe processes payments. OVH handles configured account email delivery; Resend may handle configured email campaigns and their delivery, open and click events. These services process the addresses and messages needed for those communications. PostHog processes operational and product-usage analytics when enabled.
- People you invite to a project and recipients of links or outputs you share can access the content made available to them. A creator may enable Google Analytics, Google Tag Manager or Microsoft Clarity on a shared demo page; those tools then process visitor information under that creator’s settings and notices.
6. Chrome extension data-use commitments
DemoBro’s use of data obtained through the browser extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. This applies to the captured data and to information derived from it.
- We use extension data only to provide or improve its disclosed purpose: creating product demonstrations, including the operations needed to maintain, secure and measure the reliability of that feature.
- We do not sell extension data, transfer it to advertising platforms, data brokers or other information resellers, or use or transfer it for personalized advertising, unrelated purposes, creditworthiness decisions or lending.
- Transfers are limited to providing or improving that purpose, complying with law, addressing fraud or security threats, or a business transfer with the user’s prior explicit consent, as allowed by the Limited Use policy.
- Human access to extension data is limited to your explicit consent for specific content, security investigations, legal requirements, or aggregated and anonymized information used for permitted internal operations.
- We do not use captured demo content to train general-purpose AI models. Processing your content to generate the demo you request is part of providing the service.
7. Storage, retention and deletion
Manual recordings remain in the extension’s local storage until you discard them or remove the extension, and can be transferred to DemoBro when you choose. The live connection token, connection state and recent command receipts are held in extension session storage; Stop and disconnect clears that connection state.
Uploaded information is handled separately. Command parameters and successfully consumed results are cleared as the browser workflow progresses. Pending or unconsumed results can remain on the server; disconnecting is not an immediate deletion of every server-side record.
We retain accounts, projects, generated content and associated records as needed to provide the service and respond to your requests. Retention depends on whether the account or project remains in use, a deletion request, legal record-keeping duties, and operational, security or backup-recovery needs. We do not apply one universal expiry period to all data.
You can discard local recordings and use available project controls. Contact support@demobro.com to request account or content deletion, or an export. We assess the records involved, any required retention, and remaining copies in storage or backups; removing a project from the interface does not guarantee immediate erasure of every stored copy. Stopping capture or uninstalling the extension does not delete previously uploaded projects or shared copies.
9. Your choices and rights
You can stop the browser connection, revoke extension permissions, choose what to capture, and control how you share a demo. Contact us to request access, correction, erasure, restriction, portability or to object to processing where those rights apply. We may need information to verify that the request concerns your data. If your organization controls the demo content, we may direct the request to it or assist it in responding.
You may also raise a concern with your local data-protection authority. In France, this is the CNIL. This page is updated when our handling of information changes; the effective date appears at the top.
10. Contact DemoBro
For privacy questions, provider details, access, export or deletion requests, email support@demobro.com. Describe the account or project concerned without sending application passwords, verification codes or other secrets. Report security vulnerabilities to security@demobro.com.