Localewright: Privacy Policy
Quietcog collects as little personal data as it can. This page explains what Localewright handles. The operator is Quietcog (a sole-proprietor business name). Contact: gb1@mail.grokbot.com.
Summary
Your files are read in your own browser: only the translatable text strings (with placeholders replaced by tokens) are sent to our Worker, and nothing is retained after processing. We do not store file contents, translations or your DeepL key, and we do not put them in logs. We do not use cookies for tracking, we have no accounts, and we do not sell data.
Files and translations
- When you choose a file, your browser reads and parses it on your device. Only the text strings to be translated are sent to the Worker, in small requests, with a fingerprint (SHA-256 hash) of the file, the string count and the character total. The Worker passes the strings to the translation engine and returns the translations, which your browser assembles into the translated file. The strings are not written to a database, file storage, cache or log, and are discarded when each request ends.
- Larger files are sent as a series of short requests. Your browser keeps the file and the translated strings in the browser tab (session storage on your device) until your download is complete, and carries a signed job token that contains no file content and no keys. The Service stores none of this.
- We keep no translation memory and do not use your content to train or improve any model.
- For paid purchases, your browser holds the file while you complete checkout and sends it to us again afterwards. We record only a SHA-256 fingerprint of the file (not the contents), the number of characters, the file format and the language codes in the Stripe checkout record, so the payment can be matched to the file you were quoted.
- Nothing about the file is used for any purpose other than producing your result.
Text sent to translation engines (sub-processors)
- Cloudflare, Inc. (Workers AI and Workers hosting). The free engine is Cloudflare Workers AI (model M2M-100). Your text is sent to Cloudflare to be translated, and Cloudflare also hosts the Service. Cloudflare's Workers AI data usage page states that Workers AI does not retain inputs or outputs of standard inference requests after they are needed to deliver the response, and does not use them to train models; it may keep operational metadata (such as timestamps, sizes and neuron counts). Cloudflare's Privacy Policy applies to Cloudflare's own processing, including normal network metadata such as IP addresses.
- DeepL SE, only if you supply your own key (an option that is currently switched off). If you send a DeepL API key with a request, your text is sent to DeepL under your own key and account. DeepL's terms and privacy policy apply to that processing, and DeepL may store content as its terms for your plan describe. We never store or log your key; it is used only to make that one request.
- Stripe, Inc. (payments). See below.
We do not send your text to any other service.
Payments and Stripe
Payments are processed by Stripe. For applicable purchases Stripe is merchant of record and reseller under Stripe Managed Payments and collects the payment and tax information it needs under its own privacy policy. We receive your email address, the product purchased and the order status. We never see your full card number. The Stripe checkout record also holds the file fingerprint, character count, format and language codes described above.
Usage limits and network addresses
To enforce free limits and a daily capacity cap we keep short-lived counters: a daily total for the whole Service, and a per-day count per network address. We store the address only as a salted one-way hash with a salt that changes every day, and delete counters after the day ends. We keep a record of redeemed Stripe checkout session identifiers so a purchase cannot be used twice, and a monthly character counter per Pro subscription; these contain no file content. We keep no analytics and request logging is turned off for the Worker. Cloudflare may still process network metadata as part of operating the network.
Cookies and analytics
The Service does not set tracking cookies and uses no advertising trackers. The upload page may use your browser's session storage to hold your file during checkout; it stays on your device and is cleared when the tab closes or the download completes.
How we use data
To deliver translations, process orders and refunds, enforce limits, prevent abuse, and answer support messages. We do not sell personal data.
Do not send personal or sensitive data
Localization files should contain interface text, not personal data. Please do not include personal data, health or payment data, or secrets. If you use DeepL under your own key, check DeepL's rules for your plan, which can restrict personal data.
Retention and your choices
Order records are kept as long as needed for accounting and legal purposes (held by Stripe and by us). Other data is deleted as described above. You can ask us to access or delete data we hold about you by emailing gb1@mail.grokbot.com.
Children
The Service is not directed to children under 13.
Changes
We will update this page if our practices change; the date above shows the latest version.