Verified against the LocalePilot source code on 30/10/2026 (commit b84b323). Cloud AI providers require LocalePilot Pro.
What is sent
Each request holds fixed instructions for the model and, for each text of the batch:
- the key name and the source text, with its placeholders as they are;
- the current translation in the target language, if it is not empty;
- the description of the key, if your file has one (for example the
descriptionof an ARB entry or the comment of a String Catalog entry), and its group, the parent path of a nested key; - up to 6 neighboring keys of the same group, with their key name and source text. They can be keys you did not select;
- up to 2 existing translations of the same key in other languages of the project;
- the plural categories expected in the target language, for plural messages.
For the whole request:
- the source and target language codes, and the Model behavior chosen in the settings;
- the approved glossary terms that apply to the target language, with their scope and notes, if Use approved glossary is on (Pro);
- the project's Translation context (Business domain, Audience, Tone, Style guide), if you filled it in.
With Adapt with AI on the Store listings screen, the request holds the source fields of the listing instead, with your project's name, the glossary terms that stay the same in every language and web addresses replaced by neutral markers. See Store listings.
With the AI audit, the request has the same content, for already translated cells of the audited language only. The current translation is always sent, and so are the approved glossary terms: the audit has no option to leave them out. See AI audit.
What is never sent
- Your files, their names and their paths.
- The name of your project, except where it appears inside a text you translate.
- Forbidden glossary terms and glossary terms that are not approved.
- Keys of the project other than those of the batch and their neighbors.
What stays with the provider
LocalePilot creates nothing in your account with the provider: no file, no glossary, no saved setting. How long the provider keeps requests and answers depends on its terms and on the settings of your account with it.
API key and address
Add your key in Settings, AI provider, with Add a key. It is stored in the macOS Keychain, never in LocalePilot's settings file. The Base URL can be changed: the text and the key are then sent to that address, as the Before you launch panel shows.
| Provider | Default address | How the key is sent |
|---|---|---|
| OpenAI | https://api.openai.com/v1 | Authorization: Bearer header |
| Anthropic | https://api.anthropic.com | x-api-key header |
| Gemini | https://generativelanguage.googleapis.com | x-goog-api-key header, never in the address |
| DeepSeek | https://api.deepseek.com | Authorization: Bearer header |
DeepSeek is called in the OpenAI-compatible format. Test only asks for the list of models available with your key, without any of your text.
Options that change what is sent
- Use approved glossary (Pro): off, no glossary term is sent.
- The project's Translation context: sent with every request as long as it is filled in.
- Batch size: how many texts each request holds.
- Translate automatically with …, in Add a language: checked by default, it translates a new language as soon as you add it, with the approved glossary.
The comparison with the other providers is on What is sent.