This policy covers the LocalePilot app, the purchase of a license and the website localepilot.app. The data controller is the publisher of LocalePilot: Ramah GUEDEGBE, sole trader (entrepreneur individuel) registered in France under SIREN 523 501 765, 235 rue Saint-Honoré, 75001 Paris, France, who publishes software under the GLabs325 brand (glabs325.com). Contact: localepilot@glabs325.com.
1. Summary
LocalePilot is local-first. It reads localization files from locations you select on your computer and writes exports back locally, under your control.
LocalePilot has no account and no publisher-operated server. The app includes no analytics, no cloud telemetry and no cloud crash reporting. This website sets no cookies; it measures its audience in aggregate, without cookies, with Cloudflare Web Analytics (section 9).
2. Data stored on your computer
LocalePilot may store local settings such as:
- references to recent projects;
- AI provider endpoints and model identifiers;
- AI API keys, kept in the secure storage of the operating system;
- the license state and validation dates;
- the date of the last update check;
- an opt-in, local-only counter of unsupported file formats (see section 8), off by default.
License keys and API keys are stored in the secure storage of the operating system. Non-secret license data is signed locally to detect tampering.
Export backups (copies of your localization files as they were before an export replaced them), the export journal, project settings and the project glossary are kept in LocalePilot's own storage on your Mac, never inside your project. Export backups and the export journal are never sent anywhere. The project's translation context, which is part of its settings, and approved glossary terms can be sent to a translation provider, as described in section 3. Settings > Project > Backups > Show backups in Finder opens the backups. Older backups are deleted automatically, and you can delete them yourself from the same screen.
LocalePilot keeps a local diagnostics journal separate from the export journal: timestamps, actions, error messages and technical traces. Error messages may contain paths or text. Entries older than 14 days are purged at startup and on writes; a size limit can remove older entries sooner. Nothing is sent automatically: review a problem report before sending it yourself.
3. Localization files and translation providers
LocalePilot processes the localization files you select. Their content stays on your computer unless text is sent to an AI or machine translation provider that you configured. This happens when you start a translation, when you add a language with Translate automatically checked (it is checked by default once a provider is configured), when you run an AI audit of existing translations, and when you adapt an App Store or Google Play listing with AI. Testing the connection to a provider also contacts it; for Microsoft Translator, Google Cloud Translation and LibreTranslate, the test translates the word “Hello”.
When you use an AI model (OpenAI, Anthropic, Gemini, DeepSeek, Ollama or LM Studio), the request may contain, for each text to translate, the source text, the key name, its description and group, the current translation in the target language, up to 6 neighboring keys of the same group and up to 2 translations of the same key in other languages. It may also contain the approved glossary terms and the project's translation context (domain, audience, tone and style guide), which is sent whenever it is filled in. An AI audit, which works only with these AI models, sends the same items for each existing translation it checks. Machine translation services receive less: Microsoft Translator, Google Cloud Translation and LibreTranslate receive only the source text; DeepL also receives the key name, its description and group and, if the glossary option is on, the approved glossary terms. For a store listing, the non-empty source fields are sent, after your project name and web addresses have been replaced with neutral markers. LocalePilot never adds file names, file paths or the project name to a request.
To apply the glossary with DeepL, LocalePilot creates a glossary in your DeepL account whose name starts with LocalePilot-, one per language pair, and replaces it when your approved terms change. It stays in your DeepL account, including after you uninstall LocalePilot. LocalePilot creates nothing in your accounts with other providers. You are responsible for the provider account, the API key and the provider's terms.
Ollama, LM Studio and LibreTranslate run on your computer with their default address, and the text then does not leave it. If you enter the address of another machine, the text is sent to that machine. A cloud model used through Ollama or LM Studio receives the text, even at the default address. The Before you launch panel of a batch translation or an AI audit shows where the text goes.
The What is sent page of the Help section details what each provider receives.
4. License activation
LocalePilot uses the license key API of Polar (polar.sh) for Pro features. Polar is the Merchant of Record for purchases.
Activation sends the license key, LocalePilot's public Polar organization identifier and a device label of the form LocalePilot Desktop <timestamp>. Validation and deactivation send the license key, the same organization identifier and the activation identifier that Polar returned for this device.
The app keeps the license key in secure storage, with signed local data such as the activation identifier and validation dates. No publisher-operated server takes part in license validation.
5. Purchases
Polar sells LocalePilot licenses as Merchant of Record. It collects the information needed for payment, invoicing and taxes (such as your name, email address, billing country and payment details) and processes it under its own privacy policy (polar.sh/legal). GLabs325 never receives your card details. Polar shares with us the information needed to manage your order, such as your email address, country and order details, which we use for support, refunds and our accounting obligations.
6. Update checks
On macOS, LocalePilot uses the open-source Sparkle updater. At most once every 24 hours (automatic checks can be turned off in Settings), and whenever you choose Check for Updates, the app downloads a static update feed (appcast.xml) hosted on GitHub. The request carries no account, license key, project data or system profile. GitHub only receives what any download reveals: your IP address and the updater's user agent, which includes the app version.
When a newer version is listed, Sparkle shows it with its release notes. The update is downloaded only after you click to install it, then verified (signature of the archive and Apple Developer ID signature) before it replaces the app. LocalePilot never installs an update without that click.
On Windows, LocalePilot may check a static latest.json file attached to GitHub Releases, at most once every 24 hours and when you use the check button in Settings. It does not download or install updates: the download button opens the release in your browser.
7. No analytics or cloud crash reporting
LocalePilot includes no product analytics, session replay, cloud crash reporting, cloud sync or marketing tracking.
8. Unsupported format counter (opt-in, local only)
LocalePilot can count how many times each unsupported file format (a file extension such as xml or csv) is seen during a project scan. The counts help decide which import format to build next.
- The counter is off by default. It only runs once you turn on Unsupported format signal in Settings.
- It stores only a file extension and a count, for example
{"xml": 3, "csv": 1}, in the app's local settings on your computer. It never stores a file path, file name, key name or file content. - It is never sent anywhere. You can read or export it yourself from Settings.
- Settings also offers a one-off report of the unsupported formats seen during the last scan, copied to the clipboard. That report is kept in memory for the current session only.
- Turning the counter off stops counting. It does not erase counts already collected; the report table in Settings shows what is stored.
9. This website
Hosting
localepilot.app is a static site hosted by Cloudflare. To deliver pages and protect the site against abuse, Cloudflare processes technical data such as your IP address, browser user agent, the requested address and the time of the request, under its own privacy policy (cloudflare.com/privacypolicy). We do not use these logs to profile visitors.
Cookie-free analytics
To know which pages are read, the site uses Cloudflare Web Analytics, the analytics tool of Cloudflare, our host. It sets no cookies, stores nothing in your browser and does not fingerprint your device. A small script sends Cloudflare the page viewed, the site you came from, your browser and device type, your country and page load timings; we only see aggregated statistics, never an individual visitor. The site uses no advertising tools. The free online tools run in your browser: the files you drop into them are not uploaded.
Waitlist
If you join the waitlist, we collect:
- your email address;
- the language of the page you used (for example
fr); - the source of the signup, a short code that tells us which page or link you came from (for example
tool_arb_keys); - your stack (for example Flutter or React Native), if you choose to tell us;
- the version of the consent text you accepted.
We use your address for one thing: a single email, in your language, when LocalePilot launches. The legal basis is your consent. We send nothing else and delete the address once that email is sent. Until then, you can withdraw your consent and have the address deleted at any time by writing to localepilot@glabs325.com.
The form is delivered by Web3Forms (web3forms.com), which acts as our processor: it receives the form and forwards it to us by email.
Cloudflare and Web3Forms may process data outside the European Union, under the safeguards described in their own policies.
10. Support emails
If you write to us, for example with a diagnostics report that you choose to send, we receive the content of your message and your email address. We use them only to answer you and delete them once the request is closed, unless the law requires us to keep them longer.
11. Your rights and data deletion
Because LocalePilot is local-first, almost all of its data lives on your computer. You can:
- remove recent project references from the app;
- delete local data (settings, signed license data, key kept in secure storage) by uninstalling the app or deleting its application support folder, for example
~/Library/Containers/com.glabs325.localepiloton macOS; - deactivate a license from Settings, or contact Polar for data related to your purchase.
The publisher operates no server or database that holds your projects or localization files, so there is no such data to delete on our side. The data we receive directly is limited to waitlist signups, order information shared by Polar and the messages you send to support.
Under the GDPR, you can ask to access, correct or delete that data, object to its use or withdraw your consent, by writing to localepilot@glabs325.com. You can also lodge a complaint with the French data protection authority (CNIL, cnil.fr) or the authority of your country.
12. Contact
Questions about this policy, or a request to delete a support exchange: localepilot@glabs325.com.