reasoning-translator privacy policy
Last updated November 3, 2026 · service in development
reasoning-translator is run by Hocine B. For any questions or requests about your data, contact [email protected].
The data we use
To create and protect your account, we use your email address, username, a hash of your password, and the technical details needed for sessions. Your password is never stored as plain text. If you choose Google, we receive your Google ID and confirmed email address. We do not request access to your documents, contacts, or messages.
Your optional choice to receive updates is saved with its date. It is off by default. No marketing campaigns are currently being sent. Your private projects, their context, and the files you upload are stored for your account. Original files and their versions are stored in a private OVHcloud S3 bucket in the GRA region, with server-side encryption. Automatic translation, scoring, and public sharing are not enabled. Checking uploaded file formats does not replace a virus scan.
Why we use it
Account data is used to provide the sign-up and sign-in service you request. Projects and files are used for the private storage and downloads you request in the app. They are not sent to marketing or notification tools. Technical data helps prevent abuse and keep this service safe. Any marketing messages depend on your consent, which you can withdraw by contacting us.
The public homepage translator
Text submitted to the homepage demo is sent to DeepInfra and OpenAI to prepare and improve a translation. The demo accepts up to 800 characters. Use non-confidential sample text. Our team may review completed submissions: the final source text or an excerpt, its destination language, and API cost information can be sent to our private admin WhatsApp group through our notification service. Recognizable credential patterns are redacted, but this is not a guarantee that sensitive information will be detected.
Operational source snippets are cleared after the alert is dispatched or within 24 hours. Usage, cost records, and protected network-address hashes used to prevent abuse are kept for up to 30 days. Copies already sent to WhatsApp remain in that private group until deleted there. The public demo does not use your app session or account cookies. OpenAI response storage is turned off; the providers' separate abuse-prevention and retention policies still apply.
The desktop agent and your local files
The desktop app accesses the folder you choose to carry out the tasks you request. The whole folder is not synced. Your messages, file names and paths, text read from files, and any tool results needed may be sent to our server and then to the OpenAI API to plan the next step. Local history and results stay on your computer. The sign-in token is encrypted using secure system storage when available.
Document translation and correction currently use a demo service: the file sent to our server is copied without changes, with a name starting with DEMO_UNPROCESSED_. This service does not translate or correct any text. Connecting a real document service will require an update to this notice.
On our server, the agent context expires after one hour of inactivity. Files and results from document tasks expire after 30 minutes. They are deleted during the next cleanup. These time limits do not delete files saved in your local folder, local history, or any backups managed separately. The OpenAI API is called with response storage turned off. This does not exclude abuse prevention logs, kept for up to 30 days by default, or the other exceptions described in the OpenAI API data policy. We do not promise zero data retention or processing only within Europe.
Cookies and technical logs
The Mac app separately asks in Account and settings whether you allow Google Analytics to measure button and screen categories. This measurement is off until you agree. It uses a random identifier that changes when the app restarts, and excludes your account, messages, documents, file names and paths. Advertising features are disabled. Your dated choice and the notice version are saved on your Mac for 180 days. You can refuse or withdraw your permission in those settings. Accepting website cookies does not enable desktop measurement.
The public homepage does not load the account API or create a session cookie. The app runs separately on app.reasoning-translator.com. Its account cookies are limited to that host and are not shared with the public site. These cookies are needed for sessions, form protection, temporary desktop app approval, and Google sign-in if you choose it. On the sign-up and sign-in screens, we count steps and error types without storing field values, email addresses, IP addresses, or visitor IDs in these counts. These combined statistics are kept for 90 days. The browser respects Do Not Track and Global Privacy Control signals for this optional tracking. Technical logs may contain IP addresses and page paths, but not your passwords, cookies, or confirmation details. Log size is limited.
When protection is set up, Cloudflare Turnstile checks sign-ups, sign-ins, and email resend requests using technical browser details. This protection is separate from marketing consent and does not receive your passwords or documents. Abuse prevention counters keep protected hashes of network addresses, email addresses, or accounts. They expire within 48 hours and are cleaned up during later requests.
Site analytics
With your permission, we use Google Analytics 4 to measure public pages, calls to action, pricing choices, completed public demos and account registration steps. The Google tag and analytics cookies stay off until you accept audience measurement. These cookies help associate visits, sessions and events in the same browser across reasoning-translator.com and app.reasoning-translator.com. They are configured to expire after 180 days. Advertising storage, advertising user data and advertising personalization remain disabled.
After a successful Google sign-in, and only if you have allowed Analytics, a cookie lasting at most 60 seconds passes the account-creation or sign-in result to the browser. It contains only the result category, without an account identifier or token. The browser removes it before measuring that result, and discards it if you have withdrawn consent.
When you allow audience measurement, Google receives technical request information and the limited event data described here. We normalize private page paths and exclude account identifiers, names, email addresses, tokens, document content, uploaded filenames and free-text fields from event parameters. Only approved campaign labels are retained from campaign URLs. Google Signals and advertising personalization are disabled. Audience measurement follows your saved cookie choice independently of browser privacy signals. You can change or withdraw your choice using the cookie preferences button on our public website.
A necessary cookie remembers your choice across this site and its application for 180 days. It contains a random consent reference, the notice version, the time and your analytics choice. Our consent register records a random event reference, the consent reference, the version, your choice, its source site and the server time. This register does not contain your account, email, page history, IP address or browser signature. If a request fails, the same consent event can be retried without creating another record. These records are separate from newsletter permissions.
You have allowed Google Analytics. You can withdraw your permission at any time. Your cookie preferences are remembered for 180 days.
GA4 event data is retained for two months; aggregate reports follow Google Analytics retention rules. Browser settings, tracking protection and opt-outs can limit visitor and session reporting. Security logs, account operations and newsletter preferences are separate from analytics. Matomo collection has been retired.
How long we keep data and how to delete it
Your account is kept for as long as you want to use it or until you request deletion. Sessions expire within 7 days, confirmation links within 24 hours, and Google and desktop sign-in requests within 10 minutes. Desktop return codes can be used once within 60 seconds. Expired hashes are cleaned up during later requests. Account data is not sold. Archiving a project does not delete its files. Original files and their versions are not yet deleted automatically. Send deletion requests to the contact above. Deleting stored files requires an authorized administrator. The document retention policy will be clarified before the commercial launch.
Service providers
OVHcloud hosts the app and its database. Resend receives your email address and email content to send a confirmation, using a sending domain set up in the Europe region. Loops receives your email address, account ID, and account creation or sign-in events only if you have agreed to marketing messages and confirmed your email address. Incomplete form entries, passwords, and tokens are never sent to Loops. Pending events are kept on our servers for up to 30 days. Signing in again does not reverse an unsubscribe request in Loops. You can unsubscribe using email links or contact us to withdraw consent and request removal of your contact details. A technical account creation alert is also sent to an admin WhatsApp group through an intermediary service. It contains a masked email hint, never your full address, password, token, or document. Google is involved if you choose that sign-in method. OpenAI receives the details needed for the desktop agent tasks described above. Some processing by these providers may take place outside the European Economic Area. Their own policies and safeguards apply to their services.
Cloudflare privacy policy · Loops privacy policy · Resend privacy policy · Google privacy policy · OVHcloud data protection
Your rights and requests
You can ask to access, correct, or delete your data, withdraw marketing consent, and exercise your other applicable rights (to object, restrict processing, and transfer your data) by using the contact above. We may check your identity before acting to protect your account. You can also contact your data protection authority.
This notice describes the service in development: accounts, private projects, original file storage, and the desktop agent with simulated document processing. It will need to be reviewed before the commercial launch and before connecting a real translation or correction provider.