Privacy policy
What the AutoIA app does with your data, what it does not do with it, and what is out of its hands. In force as of 10 September 2026.
The essential point in one sentence: AutoIA sends us nothing. The app has no account, no publisher's server, no analytics and no advertising. What you say goes straight from the phone to the artificial intelligence provider you chose, with the key you paid for. We see none of it, and we have no technical means of seeing any of it.
1. Who is responsible for this processing
AutoIA is published by TBNETSYS, a French company, which distributes the app on the Google Play Store.
For any question about this policy, about the app, or about exercising your rights, write to .
2. At a glance
| Data | Where it goes | Who receives it |
|---|---|---|
| The sound of your voice | To your phone's speech recognition engine, which turns it into text | Your device alone if offline recognition is installed on it; otherwise the publisher of that engine — Google on most phones. Never us |
| The text of your questions and of the answers | Straight from the phone to the API of the provider you chose | Anthropic, Google, Mistral, OpenAI, xAI or Groq, depending on your choice. Never us |
| Your location | Optional. Only the name of the town is attached to your question | Your phone's geocoding service receives the coordinates; the AI provider receives only “Perpignan”. Never us |
| Your contacts | Optional. Read on the phone to call someone you name. The turn in which the call is decided never leaves the device | Nobody, unless several people share the name you asked for: their names alone are then attached to your next question. Never the numbers, never us |
| Your API key | Encrypted in the phone's hardware-backed keystore | Only the provider it belongs to, to authenticate it. Never us |
| The journal and trip summaries | In memory, then in a file if you ask for it | You alone, wherever you choose to put it. Never us |
3. What AutoIA does not do
This list can be checked: the server's code is published, and the app contains no third-party library beyond Google's Android components (AndroidX, Jetpack Compose) and the OkHttp network client.
- No user account. AutoIA asks you for no name, no email address, no registration. There exists nowhere a profile about you.
- No analytics, no usage statistics, no crash reporting. No Firebase, no Crashlytics, no Google Analytics, nor any equivalent.
- No advertising, and therefore no advertising identifier.
- No cookies and no trackers: the app is not a web page.
- No publisher's server. In API mode the app contacts six
addresses in all, those of the providers:
api.anthropic.com,api.mistral.ai,api.openai.com,generativelanguage.googleapis.com,api.x.aiandapi.groq.com. No request goes to any server of ours. - No sound recording is kept. AutoIA never writes an audio file: the recognition engine hands it text, and the sound exists only in transit.
4. Your voice
When you press the button, AutoIA opens the microphone and hands the sound to your phone's speech recognition engine. There are two cases, and the app tells you which one applies — the “What becomes of your voice” block, at the top of its settings screen.
If offline recognition is installed
AutoIA then uses your device's built-in engine, and the sound of your voice does not leave the phone.
This is not a supposition: the measurement was made at network level during a real 38-second dictation. The component that performs this recognition sent zero bytes, while the instrument could be seen carrying other applications' traffic at the same moment — which proves it was not simply blind.
If it is not
Android then hands the sound to the system's speech recognition service — Google's on most phones. The sound of your voice therefore leaves the device and is processed by that publisher, under its own privacy policy, over which we have no hold. AutoIA asks for offline recognition, but that is only a preference: the system remains free not to honour it.
To stay offline, install English in your phone's speech recognition settings. The app displays the actual result, not the preference requested.
The voice that answers you
The same question arises in the other direction, and the consequence there is heavier: a remote synthesised voice would send the entire text of the answer out of the phone. AutoIA reads the voice actually obtained and shows it to you. If it is marked “on the device”, nothing leaves; otherwise the text is passed to your system's speech synthesis engine.
5. Your questions and the answers
The text of your question — and the history of the current conversation, which lets the model follow the thread — is sent straight to the API of the provider you chose, from your phone, over an encrypted connection. Its answer comes back the same way.
To that are added a driving instruction (the model must answer briefly, without formatting, in the app's language), the time, and the name of the town if you allowed location.
What becomes of that text at the provider is a matter for its own policy, which we invite you to read before choosing:
- Anthropic — privacy policy
- Mistral AI — terms and privacy
- OpenAI — privacy policy
- Google — Gemini API terms, including data use
- xAI — privacy policy and API terms
- Groq — privacy policy and terms of use
What AutoIA does to limit retention. At Mistral and at
OpenAI, the API offers to keep conversations on the server side — and at
OpenAI that is the default behaviour. AutoIA explicitly sends the
opposite instruction (store: false) on every turn of speech, so
that your exchanges are not kept in your customer account nor readable
afterwards. At Google, the API AutoIA uses keeps no conversation that can be
read back; on the paid tier, Google undertakes not to train its models on
your exchanges, which it does not promise on the free tier. At xAI, AutoIA sends the same
instruction, and also asks that the model's reasoning trace not be kept; xAI
nevertheless keeps every request for thirty days of its own accord, encrypted,
to check for abuse, without using it to train its models — unless you turn on
Zero Data Retention in the team settings of its console, in which
case nothing is written to disk. At Groq, AutoIA sends the same instruction to
store nothing; by default Groq keeps neither the questions nor the answers, and
keeps request logs, for up to thirty days and in the United States, only to
diagnose a failure or investigate abuse — which you can refuse by turning on
Zero Data Retention in the Data Controls of its console.
Providers do however keep billing data and, depending on the case, technical or moderation logs. That is a matter for the contract between you and them, not for us: the key is yours, the account is yours.
6. Your location
Location is optional: refuse it and AutoIA works for everything else, and the model will simply ask you to name the town when it needs to. It can be turned off at any time in the settings.
AutoIA asks for precise location
(ACCESS_FINE_LOCATION), to name the right town: Android's
approximate location can be off by two kilometres. You can choose the
approximate one instead when Android asks. And it is not
the location that is passed to the AI provider, but only the name of the
town — “Perpignan”, never coordinates.
⚠️ A point of honesty about turning coordinates into a town name. AutoIA uses Android's geocoder for this, which carries no database of its own: it delegates to your device's geocoding service — Google Play services on an ordinary phone — and that service receives the latitude and the longitude. That processing is beyond our reach and beyond our knowledge. What we can state is narrower, and it is true: your exact position goes neither to us nor to the AI provider.
Measured weather, if you have enabled it with your own Météo-France key: AutoIA picks the nearest stations on the phone, then asks Météo-France for their latest observations, and for the forecast of its AROME models for the area you are in, or for the town you ask about. Météo-France receives your key, station identifiers and, for the forecast, a square of about twenty kilometres aligned on a fixed 0.1-degree grid: the cell of about ten kilometres you are in, never your exact location, nor your voice. The AI provider receives the measurements, the forecast, the station names and their rounded distance. None of it passes through us.
7. Your contacts
Access to contacts is optional: refused, AutoIA works for everything else. It serves one purpose only — calling someone without letting go of the wheel, by saying their name aloud.
When you say “call Marie”, the application looks that name up in your contacts on the phone, sending nothing. If a single person matches, it opens the dialler; if several match, it reads you their names and waits for your choice. That turn never leaves the device: no AI provider is consulted.
Only the entries whose name matches what you have just said are read — never your whole address book.
⚠️ What may leave the phone, and nothing more. When several people share the name you asked for, their names are attached to your next question, so that the model does not contradict what the application has just done. Phone numbers never leave: they go straight from your address book to the dialler. And none of this ever reaches us, in any form.
The permission can be withdrawn at any time in Android's settings.
8. Your API key
Your key is encrypted on the phone by an encryption key that never leaves Android's hardware-backed keystore and cannot be extracted from it. The app never displays it again after saving.
It is passed only to the provider it belongs to, to authenticate your requests. It is never passed to us, in any form — no backup, no log, no statistic. You can erase it at any time from the settings.
9. The journal and trip summaries
AutoIA keeps a working journal in memory, useful for understanding a fault. It contains the technical traces and the conversation word for word. It is bounded, and what overflows is discarded.
It is written to a file only if you ask for it, with a button, wherever you choose. It is never sent anywhere of its own accord. Closing the app loses it.
The same rule applies to the trip summary: produced only when you ask for it, it is displayed, then saved or shared only by an act of yours. Producing it does however mean sending the conversation to the provider so that it can sum it up — that is a turn of speech like any other, billed as such.
If you share a journal in order to get help, remember that it contains what you said. That is why the app keeps the two files apart: the technical traces on one side, the conversation on the other.
10. If you use Bridge mode
Bridge mode routes your questions through a server that you host yourself, with your own Claude subscription. In that case you are the one responsible for that server and for the data passing through it. We have no access to it.
The code of that server is published and can be checked. What it writes in its log, for each turn of speech, is the number of characters of your question and, where applicable, the name of the town — never the content of what you say, nor that of the answers.
Access to that server is protected by a password, a second factor (TOTP) and a certificate specific to the device.
11. Transfers outside the European Union
Depending on the provider you choose, your conversation may be processed outside the European Union:
| Provider | Processing |
|---|---|
| Mistral AI | French company, processing within the European Union |
| Anthropic | US company, processing likely to take place in the United States |
| OpenAI | US company, processing likely to take place in the United States |
| US company, processing likely to take place in the United States | |
| xAI | US company, processing likely to take place in the United States |
| Groq | US company, processing likely to take place in the United States |
That choice is yours, and it can be changed in the settings at any time. The safeguards framing these transfers are those each provider describes in its own policy, within the contract between you and it.
12. What Google Play passes on to us
The purchase of the app is made from Google, which acts as distributor. We receive from it aggregated sales data — number of purchases, countries, anonymised installation and crash statistics — but neither your name, nor your email address, nor your bank details. Google's processing of that data is a matter for its own privacy policy.
13. Legal bases and retention periods
| Processing | Legal basis | Period |
|---|---|---|
| Conversation with the model | Performance of the contract — it is the very function of the app | On the phone: the length of the session. At the provider: its own policy |
| Location | Your consent, withdrawable at any time | Not kept: read at the moment of the turn of speech, then forgotten |
| API key | Performance of the contract | Until you erase it or uninstall the app |
| Journal and summaries | Your express request | You keep them or delete them; we hold no copy |
14. Deleting your data
AutoIA, published by TBNETSYS, has neither accounts nor a publisher's server: we hold no data about you. What exists is on your phone, or with the AI provider whose key you entered. Here is where each piece of data lives, and how to delete it.
| Data | Where it is | How to delete it |
|---|---|---|
| Your questions and the answers | On the phone, for the length of the session; with the provider, according to its policy | Closing the app clears the current conversation. With the provider, deletion is requested from your account, on its site |
| Your contacts | In your address book and nowhere else: AutoIA keeps no copy of them | Withdraw the permission in Android's settings, under AutoIA's “Permissions” |
| Your API key | In the phone's keystore | Settings, « Answer source » page, « Remove » button |
| The journal and trip notes | The files you asked for, in the folder you chose | Delete them like any other file; « Remove all traces » empties the journal inside the app |
| Bridge mode authentication | A cookie, on the phone | Settings, « Answer source » page, « Remove » button |
| Your location | Nowhere: read at the moment of the question, never recorded | Nothing to delete; the permission is withdrawn in the Android settings |
Uninstalling AutoIA erases all of the above from the phone at once, except for files you saved elsewhere yourself.
Sending us a deletion request. Write to with « AutoIA » in the subject line. We reply within one month. Our reply will state what data we hold about you, and we keep none beyond that — as of today there is none, and we have no technical means of holding any.
15. Your rights
The European General Data Protection Regulation gives you rights of access, rectification, erasure, restriction, objection and portability.
One point that matters: we hold no data about you. We can therefore neither give you any nor erase any — not out of refusal, but because there is none. The data of your conversation is at the AI provider you chose, with your account: it is to that provider that a request for access or erasure must be addressed. The data on your phone is erased by uninstalling the app.
You may nevertheless write to us at the address given at the top of this page with any question. If you consider that your rights are not being respected, you may lodge a complaint with the supervisory authority of your country. Ours, as a French publisher, is the Commission nationale de l'informatique et des libertés (CNIL).
16. Minors
AutoIA is aimed at drivers holding a driving licence and is not intended for minors. No data is knowingly collected from them — the app in fact collecting no data at all for its publisher.
17. Changes to this policy
This page may change along with the app, in particular if a new artificial intelligence provider is added. The date in force appears at the top. We invite you to read it again after an important update.
This policy is about data. The terms of use, the warranties and liability at the wheel are described on a separate page: terms and conditions of use and sale.