Privacy Policy

• Account details: your email address, name and profile photo if you sign in with Google, or your email and a password you create (stored only as a secure hash by our authentication provider). If you turn on two-step verification, the authenticator secret is stored by our authentication provider.
• Your sites: the content, images, settings and drafts you create in the editor, and the deployments you make.
• Business details you give to AI: when you use AI features, the business name, description, location and the text of the sections you ask AI to work on.
• Payments: the plan or credit pack you buy, the amount and the payment status. Card details are entered on Stripe’s page and never reach our servers. For manual payments (EasyPaisa, UPI) we keep the transaction id and the screenshot you upload so we can verify it.
• Usage and technical data: basic analytics (pages visited, device and browser type), and security logs such as IP address used to detect abuse and limit requests.

To run the service (sign you in, save and deploy your sites, unlock passes and credits), to write AI content you ask for, to answer support requests, to prevent fraud and abuse, and to improve the product. We use your email to send account, payment and service messages; you can unsubscribe from non-essential emails.

Only with providers that help us run Brovo, and only what they need:

• Hosting, database and authentication (our backend provider).
• AI providers: the text and business details you ask AI to work with are sent to third-party AI models to generate the result. Do not put passwords, payment card numbers or other secrets into AI prompts.
• Stripe for card payments.
• Deployment targets you choose (Netlify, Vercel, GitHub): your site files are sent there when you deploy.
• Image and email services used to fetch photos, deliver form messages and send our emails.

We may also disclose information if the law requires it.

When you connect GitHub, Vercel or Netlify, we receive an access token to act on your behalf only when you press deploy or manage a domain. Tokens are kept in your browser’s local storage so you stay connected, and, to let you redeploy and attach domains later, a copy is stored with your site’s settings in our backend. Local storage can be read by scripts running on the same page, so only connect accounts on a device you trust, and disconnect (or revoke the app in the provider’s settings) whenever you like.

We use cookies and local storage to keep you signed in, remember your drafts and preferences, and measure usage. You can clear them in your browser settings; some parts of the editor will then not remember your work on that device.

The sites you build are yours. You are responsible for the privacy policy and consent notices of your own site. Brovo can write a general starting-point Privacy and Terms page for your site, but it is not legal advice. Messages sent through forms on your published site go to the email address you set, via the form service you enabled.

We keep your account and sites while your account is active. You can delete a site at any time. If you ask us to delete your account we remove your personal data and sites, except records we must keep by law, such as payment records.

You can ask to access, correct, export or delete the personal data we hold about you, and to object to certain uses. Email us from your account address and we will respond as soon as we can.

We use encrypted connections, access controls and optional two-step verification, and limit who can reach data. No system is perfectly secure, so please use a strong, unique password and keep your devices updated.

Brovo is not meant for children under 13, and we do not knowingly collect their data.

We will update the date above when this policy changes. Questions? Email contact@brovo.tech. See also our Terms and Refund Policy.