Privacy policy

1. Overview

Reelocal respects your privacy. This policy explains what data may be processed when you use the service.

2. Videos and temporary files

Your video is uploaded only after your action and is used for speech recognition, SRT preparation, translation when selected, and creation of localized MP4 files. Source and output files are stored temporarily in private object storage and deleted automatically.

Abandoned uploads are deleted within approximately two hours. Files associated with a render job are normally deleted approximately one hour after completion or failure. The service does not provide permanent file storage or a media library.

3. Speech recognition, translation, and generated voice

Extracted audio is sent to OpenAI for speech recognition. When you request another language, the reviewed text is sent for translation. If you separately request a voiced version, the reviewed translation is sent to ElevenLabs to generate an artificial voice. According to the selected mode, the original audio track is either fully replaced or kept quietly under the generated voice. Temporary text and voice-script files are deleted with the render job.

4. Access, orders, and quotas

Telegram Login may be used to provide a signed session, free MP4 creations, and purchased credits. The server verifies the Telegram signature and sets an HttpOnly cookie. Anonymous access is limited by a server-side hash of the client address. Telegram login payload is not stored in browser localStorage.

For a manual purchase, Reelocal stores an individual order number, its status, the number of credits, and a pseudonymous account key. The direct Telegram ID is not stored in Redis. Reelocal does not collect or store bank-card details; payment is made using the instructions shown by the bot and is verified manually from the actual bank receipt.

5. Technical data

Redis stores temporary upload sessions, queue state, progress, free-access counters, permanent credit balances, orders, and a ledger of credit additions and deductions. The ledger uses a pseudonymous account key and does not include video, audio, subtitle text, bank details, Telegram username, or IP address. Closed-beta metrics are aggregated and do not include video, audio, subtitle text, access codes, or IP addresses.

6. Website analytics

Reelocal uses Cloudflare Web Analytics and its own server-side aggregate counters to measure visits, completed processing stages, created MP4 files, Telegram registrations, and completed credit purchases. A random browser identifier is converted to a pseudonymous value before it is stored in Redis; raw IP addresses and direct Telegram IDs are not included in the analytics report. This information is used to understand whether the service is being used and improve its reliability, not to identify individual visitors.

7. Contact form

Messages sent through the contact form and an optional Telegram contact are delivered through the Telegram Bot API. Do not submit files, passwords, tokens, or other sensitive information.