L'auxiliaire
Privacy policy
The short version: this extension has no server, and nothing you read or save is sent anywhere.
Last updated 2 September 2026.
What is collected
Nothing. There is no account, no sign-in, no analytics, no telemetry, no crash reporting, no advertising and no third-party SDK. The developer has no server and receives no data about you or your use of the extension — there is no mechanism by which they could.
What is stored, and where
Everything the extension remembers is written to Chrome's local extension storage
on this computer (chrome.storage.local). It is not synced to your
Google account and it is not uploaded anywhere. It holds:
- Saved words — the word, its translation, the sentence you met it in, and the address and title of the page or the name of the PDF it came from.
- Your collections and workbook names, including any lists you created or renamed yourself, and the order you dragged them into.
- Saved conjugation tables you chose to keep.
- Settings — hover mode, slower speech, light/dark choice, and your reading-aid colours.
- A translation cache, so a phrase you look at twice isn't translated twice. Entries expire after seven days and the cache is capped.
- Tutorial progress — which parts of the tour you have seen.
- PDF handoff records — when you open a PDF, its bytes are held briefly in this browser's IndexedDB so the viewer tab can read them. These are swept automatically after 30 minutes.
Uninstalling the extension deletes all of it. Export your words first if you want to keep them — the workbook's Export button produces a CSV file or an Anki deck.
What leaves your computer
There are exactly three cases, and none of them involve the developer.
1. Translation
Translation runs on your machine, through Chrome's built-in
Translator API. The text you translate is not sent over the network.
The first time you translate, Chrome downloads a French → English language pack from Google. That is a Chrome download, made by the browser, and it happens once. Afterwards translation works with no network connection at all.
2. Speaking practice
Practice sessions are the one part of this extension that is not on-device. Speech recognition is provided by Chrome's Web Speech API, which transcribes your speech using a Google service — so audio captured during a practice turn may be sent to Google's servers and is handled under Google's privacy policy, not this one.
The microphone is only ever opened while a practice turn is running, after you have granted permission and pressed to start. The extension does not record, store or transmit audio itself, and nothing from a practice session is saved — session state lives in memory and is gone when you close the panel. If you would rather nothing left the machine, don't use the Practice tab; every other feature works without it.
3. Reopening a PDF from a website
The popup's "reopen this PDF" button fetches that PDF from the site you are already on, so the extension can display it. That request goes to that site and nowhere else, and only when you press the button.
Permissions, and why each one exists
- storage — to keep your words and settings, as above.
- activeTab — to act on the tab you are looking at when you use the extension. It grants no standing access to your browsing.
- sidePanel — to open the workbook beside the page.
- alarms — to sweep the expired translation cache and old PDF handoff records on a timer.
- offscreen — Chrome's translation API needs a real document to run in, which a background service worker isn't. This creates a hidden one.
The extension deliberately requests no host permissions — it never asks for standing access to read the sites you visit. Its content script runs in the page to make click-to-translate work, and reads only the text you click, select or hover.
Children
The extension is not directed at children and collects no personal information from anyone, of any age.
Changes
If this policy ever changes, the updated version will ship with the extension and carry a new date at the top of this page.
Contact
Questions, or something here that looks wrong? Open an issue on the GitHub repository. The source is public — every claim on this page can be checked against it.