Privacy
Two different sets of people are involved here, and conflating them is how privacy notices become useless. This one keeps them apart: you, the customer with an account, and your users, the people who talk to Vesper inside your app.
1Which of us is responsible
For your account — your name, your company, your billing details — we are the data controller.
For your users — the person who said “what have I missed?” into your app — you are the controller and we are your processor. We only handle what they say because you asked us to answer them. The Data Processing Agreement sets out the terms.
2Your account data
We hold what you type into the console, and nothing you did not give us:
- Your name, work email and the password hash held by Firebase Authentication.
- Company name, trading name, company number and VAT number, if you enter them.
- Your billing address, and your billing, technical and security contacts.
- Details of your application, and how you want Vesper to appear inside it.
- Counts of your API calls, by day, and what they cost.
The lawful basis is performance of a contract: we cannot bill you or support you without it. We do not sell it, and we do not use it for advertising.
3Your users’ words
When your application sends us a message, it travels to our server, to Google’s Gemini API to be answered, and back to you. If you asked for speech, the reply also goes to Google Cloud Text-to-Speech to be spoken.
We do not store the message. It is held in memory for the seconds it takes to answer and is not written to a database. What we keep is a count: one more request today, and what it cost.
We do not use your users’ words to train models, and our provider is contractually barred from doing so with paid API traffic.
Do not send us more than you need to. Vesper answers what somebody said; she does not need their name, their location, their payment details or their health information, and you should not put those in a message.
4The voice cache
Spoken replies are cached so that a phrase said a thousand times is synthesised once. The cache is content-addressed: the file is named after a hash of the text, and there is no way to ask it for anything. You post text, and it either has the audio for exactly that text or it makes it.
That means a cache hit gives the caller nothing they did not already supply, and audio cannot cross between customers by accident. If a reply contains a first name, that name exists in the cache as sound — so, again, keep names out of replies you do not need spoken.
5This website
No analytics, no advertising, no tracking cookies, no third-party scripts that watch you. There is no cookie banner because there is nothing to consent to.
The console stores a sign-in token in your browser so you stay signed in. That is strictly necessary for a service you asked to log in to, and it never leaves your device except to prove who you are to us. Fonts are served by Google Fonts, which will see your IP address as part of delivering them.
6Who else touches it
- Google Firebase — hosting, sign-in and the database that holds your account.
- Google Gemini API — generates the answers.
- Google Cloud Text-to-Speech — gives her the voice.
- Google Fonts — serves the typefaces on these pages.
That is the complete list. We will tell you before adding anyone to it who would handle your users’ data.
7Where it is held
Your account data and usage counters are stored in Google’s
eur3 region — the European Union.
Generation and speech may be processed in other Google regions under
their standard contractual clauses.
8How long we keep it
- Messages from your users — not kept at all.
- Usage counters — while your account is open, then 30 days.
- Account and profile — while your account is open, then 30 days.
- Invoices and tax records — six years, because HMRC requires it.
- Cached audio — indefinitely, since it is text nobody can retrieve without already having.
9Your rights
Under UK GDPR you may ask us for a copy of your data, to correct it, to delete it, to restrict what we do with it, or to receive it in a portable form. Most of it you can see and change yourself in the console under Profile.
Email hello@meetvesper.co.uk and we will answer within 30 days. There is no charge.
If your user asks you to delete their data, you do not need us: we hold nothing about them beyond an anonymous count of requests.
10Security
- Everything travels over TLS. There is no unencrypted route in.
- API keys are stored only as a SHA-256 fingerprint. We could not show you your own key if we wanted to.
- Database rules refuse a signed-in customer any account but their own, and refuse them the fields that decide money even on their own record.
- Revoking a key stops it working immediately, not at the next renewal.
If there is a breach affecting your data, we will tell you and the ICO within 72 hours of becoming aware of it.
11Complaints
Tell us first — hello@meetvesper.co.uk. If we do not put it right, you can complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113.