Privacy policy
Last updated: 6 October 2026.
Who we are
Private Assistant is a personal project of Louis Basseto, who decides how its data is used: the "controller" under the GDPR. "We" means Louis and the software he runs. To reach him, write to the support address that Google shows on this app's sign-in screen.
Louis is its only user. This page is for him, and for the people whose mail and invitations will pass through it: those who write to him, and the guests on his calendar.
Where things stand
The assistant is being built. For a check of up to 14 days of whether Google keeps the app's access, it holds one encrypted Google sign-in token; it reads no Google data, and the check then revokes and deletes the token. This page describes what it will do, and marks what isn't in use yet. We update it before the app uses data in a new way.
In short
- Nothing is sent from Louis's Gmail and no event changes until he approves it on his iPhone with Face ID.
- We keep no copy of his mailbox or calendar. The assistant fetches what a request needs, when it needs it.
- Chat history is kept 90 days, then deleted.
- No ads, no analytics, no selling. Google data never trains AI models.
- We don't call this service anonymous. The people who run the server could technically reach its data. We don't read it, except in the cases listed under "Google user data".
What we'll do with the Google account
| Permission | What it's for | In use |
|---|---|---|
Read Gmail (gmail.readonly) | Search and read mail when Louis asks, for example "What needs my attention?" | Not yet |
Compose Gmail (gmail.compose) | Save drafts, and send the emails Louis approved with Face ID. Each is sent once. | Not yet |
Calendar events (calendar.events) | Read events and free time; create or move the events Louis approved with Face ID. Only the start, end, title, location and description change. | Not yet |
Drive, app files only (drive.file) | Create and update three memory notes (Profile, People, Open loops) in an "Assistant memory" folder in Louis's Drive. It can't see his other files. | Not yet |
It never deletes, archives or forwards mail, deletes events or changes attendees.
What we keep, and for how long
As each feature arrives:
| What | Where | Kept for |
|---|---|---|
| The Google connection: the sign-in token (encrypted), the permissions granted, the account's email address | Our server | Until Louis disconnects Google. The check's token: until the check ends, 14 days at most, when it is revoked at Google and deleted |
| The Google check's results: for each day, the date and time, ok or failed, and an error code; never a token or any content | Our server, and public on its status page | 30 days |
| Louis's messages and the assistant's replies, which can quote or summarize mail and events | Our server | 90 days |
| What the assistant fetched to answer a request, such as an email it read | Our server | 7 days |
| An email or event change waiting for approval, with its full text | Our server | Until Louis decides, or 24 hours |
| Actions taken: what, to whom (recipients or event title), when, and the result; never email bodies | Our server | 90 days |
| Settings: time zone, language, budget, brief time | Our server | Until Louis deletes them |
| Paired phones: their public keys and push token | Our server | Until the phone is removed |
| Cost counters, with no content | Our server | 13 months |
| Technical logs, never message content | Our server | 14 days |
| Encrypted backups of the data above that's on our server, logs excepted | Scaleway Object Storage, Paris | 7 days, rolling |
| Memory notes | Louis's Google Drive | As long as he keeps them |
A daily job deletes what has passed its time.
Who else processes it
- Scaleway SAS (Paris, France): our server, its disks and the backups.
- The AI model: it processes the text a request needs (the message, recent history, and any mail or events the assistant read) to write the reply, on an EU endpoint, with zero data retention and no training. While Louis compares models, chat uses GPT-6.1 sol, run by Microsoft Azure in the EU. When it still fails after one retry, the backup, Mistral Medium 3.5, run by Mistral AI in the EU, writes the reply instead, on the same terms, and the app marks that reply.
- OpenRouter, Inc. (USA), only while we develop: it relays chat messages to the model's EU endpoint, and its relay runs in the US. With logging off it doesn't keep the messages. It keeps request details such as token counts and timing, and its terms let it categorize a small sample of prompts, in what it calls anonymized form. Transfers to the US are covered by the EU's standard contractual clauses in its data processing agreement. Google data never goes through OpenRouter.
- Let's Encrypt: issues this site's HTTPS certificates. It sees the site's names, never any user data.
- Google: the mail, calendar and Drive stay at Google. We send the emails and events Louis approves through Google's APIs.
Google user data: Limited Use
Private Assistant's use and transfer of information received from Google APIs, including Google Workspace APIs, will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- We use it only for features Louis sees in the app: answering him, and the emails, events and memory notes he approves.
- We share it only with the processors above, and only to answer his requests.
- We don't sell it, use it for ads or to judge credit, or pass it to data brokers.
- Neither we nor anyone else uses data from Google Workspace APIs, or anything derived from it, to develop, improve or train generalized or non-personalized AI or machine-learning models.
- Nobody reads it except Louis, unless he asks us to look at a specific message, security requires it (for example, to investigate abuse), or the law does.
How we protect it
- Every connection is encrypted (HTTPS).
- Only the web port is open to the internet. There's no admin panel.
- Logs never hold message content.
- The server's data disk is encrypted. Its key is never stored in plain form: Scaleway Key Manager unwraps it for our server, from the server's own address, and otherwise only for our own administrator and deployment accounts.
- Backups are encrypted on the server before upload.
- The Google sign-in token is encrypted with a key of its own, which a key in Scaleway Key Manager wraps. It is decrypted only in memory, for the moment the daily check uses it.
- Planned with email: the server, not the AI, enforces the Face ID rule, so an email or invitation can't trigger an action on its own.
Rights and choices
- Disconnect Google in the app, once Google is connected, or remove access in the Google Account at myaccount.google.com/connections.
- See, correct, delete, export or restrict the data, or object to its use: write to the contact above. We answer within one month. Backups roll off within 7 days.
- If you wrote to Louis or are on his calendar: once email and calendar are in use, your name, address and message can pass through the assistant when he asks about them, and are kept as listed above. You have the same rights.
- You can complain to a data protection authority where you live or work. In France, that's the CNIL: cnil.fr/fr/plaintes.
Legal basis
To be confirmed by a legal review. For Louis's data: providing the service he asked for (GDPR Article 6(1)(b)). For the people in his mail and calendar: our legitimate interest in helping him handle his own mail and schedule (Article 6(1)(f)). No decision with legal or similarly significant effect is made automatically: the assistant suggests, and Louis decides.
This website
These pages set no cookies and load nothing from other sites. Our server logs which page was served, when, and whether it worked, and keeps that for 14 days. It never records your IP address.