Privacy

Last updated October 21, 2026. Have counsel review this notice before launch. It describes the MVP as built.

What we keep

We store the email you enter at checkout, a hash of the API key issued for that email, a sealed copy of that key so the receipt can show it, the credit balance, and the payment record: amount, rail, processor id, and status. We do not keep the localization file after the response is sent. Server logs may briefly contain an error message from a failed request.

Who else sees a string

When a live model is configured, the masked strings are sent to that provider (an OpenAI-compatible chat API) so they can be translated. Placeholder tokens are sent with the text. We do not use your files to train a model of our own. The model provider’s terms apply to that request. In mock mode, translation stays on the machine and uses a built-in glossary.

Payments

Card and USDC checkout are handled by Stripe. Stripe receives the email, the amount, and the card or wallet details. LocaleDrop never sees a card number. Bitcoin checkout is handled by the operator’s BTCPay Server, which sees the invoice amount and order id. We do not send the file to Stripe or BTCPay.

Keys and cookies

The browser stores the API key in local storage if you paste it into the translator. That is so you do not have to type it on every file. The site does not use advertising cookies. Payment processors may set their own cookies on their hosted pages.

To ask for a copy of the checkout record, or for deletion of an unused key, write to hello@localedrop.dev. Deleting a key deletes the credits on it.