Privacy Policy
Last updated 12 September 2026 · Applies to brovoice.dev and the brovoice command line tool
Summary
The brovoice command line tool sends us nothing. It has no telemetry, no analytics and no phone-home. Used with your own API key, or with the offline voice, we never see you at all and you never create an account.
If you sign in for the hosted voice, we collect your email address, hold the text you ask us to speak only for as long as it takes to speak it, and keep a running count of characters used so we can enforce your plan limit.
Who we are
brovoice operates brovoice.dev and is the data controller for the information described here. You can reach us at admin@brovoice.dev about anything on this page, including deletion requests.
Google user data
Signing in uses Google OAuth. We request only these scopes, and nothing else:
| Scope | What it gives us | Why we ask |
|---|---|---|
| userinfo.email | Your email address | Identifies your account, and is the address we reply to about billing or deletion |
| userinfo.profile | Your basic profile: name and picture | Shown to you on the account page so you can tell which account you are signed in as |
We do not request access to Gmail, Drive, Contacts, Calendar or any other Google service, and we cannot read them.
Limited Use. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we do not transfer Google user data to third parties except as needed to run the service, we do not use it for advertising, we do not sell it, and no human reads it except where required to resolve a support request you have raised or to comply with the law.
What we store
| Data | Purpose | Retained |
|---|---|---|
| Email address | Identifies your account; sent by Google at sign-in | Until you delete the account |
| API key hashes | Authenticating the command line tool | Until you revoke the key |
| Character counts and timestamps | Enforcing the monthly limit on your plan | 13 months, then deleted automatically |
| Subscription status | Knowing whether your plan is active | Until you delete the account |
API keys are stored only as a SHA-256 hash together with a short display prefix. The key itself is shown to you once, at creation, and is never written to our database — a copy of our data would contain no usable credentials.
What we do not store
- The text you have spoken. It is passed to Google Cloud Text-to-Speech, converted to audio, returned to you, and not written to our database. We record only how many characters it contained.
- Audio. Generated on demand and never retained by us.
- Your code. The tool summarises an agent's output on your own machine before anything is sent. Filenames, repository names, prompts and source code are not transmitted to us.
- Payment details. Razorpay collects and holds these directly. Card numbers never reach our servers.
- Passwords. There are none — Google sign-in only.
- Advertising or tracking identifiers. The site sets no advertising cookies and runs no third-party analytics.
Cookies
The only cookies we set are the session cookies that keep you signed in after Google authentication. They are strictly necessary for the account pages to work, and there are no advertising or analytics cookies.
Who else processes your data
- Google Cloud — receives the text to be spoken and returns audio, under Google's terms. Also provides the sign-in.
- Supabase — hosts the database and authentication.
- Razorpay — processes payments and holds billing details.
- Vercel — serves this website.
We do not sell your data, and we do not share it for advertising or any purpose beyond operating the service.
Security
Data is encrypted in transit. Database access is restricted by row level security so one account cannot read another's rows, and the credentials used by our backend are held as managed secrets rather than in source code.
Your rights and choices
- Revoke a key from your account page at any time. It stops working immediately.
- Delete your account and all associated data. Email admin@brovoice.dev from the address on the account. We action it within 30 days and confirm when it is done.
- Request a copy of what we hold about you, at the same address.
- Revoke our Google access yourself at myaccount.google.com/permissions.
- Avoid us entirely. Use the tool with your own API key, or the offline voice, and never create an account.
Children
The service is not directed at anyone under 16, and we do not knowingly collect their data. If you believe a child has given us information, email us and we will delete it.
International transfers
Our processors operate globally, so your data may be processed outside your country of residence, under the contractual protections those providers offer.
Changes to this policy
Material changes will be announced by email to account holders before they take effect, and the date at the top of this page will be updated.