Privacy notice
Updated 8 November 2026
Who is responsible?
SYBEEL GAMES UNIP LDA, represented by Amin Rezaee, is responsible for ReadOff account and service processing. Contact support@readoff.app about personal data. Our registered address and tax number are on the company details page. Stripe/Link processes payment information under its own privacy terms and merchant-of-record responsibilities.
Information we process
| Information | Purpose |
|---|---|
| Email, password hash, sign-in session | Create and secure accounts. Passwords are stored as salted hashes, not readable passwords. |
| Images and extracted or pasted text; generated audio | Recognize text, generate your chosen voice, and deliver playback or a download. |
| Character balances, usage events, purchase references | Supply purchased credits, enforce allowances, resolve billing issues, and prevent duplicate crediting. |
| Marketing choice and its audit record | Remember whether you agreed to optional news and promotional messages. |
| IP address, browser/request information, service logs, trial identifier | Operate the website, diagnose failures, protect accounts, and limit abuse. |
| Support correspondence | Respond to questions, complaints, privacy requests, and cancellation requests. |
When your content is sent
Selected images stay in the browser until you choose Extract text. The service then sends the image for recognition. Choosing Read aloud sends the reviewed or pasted text for voice generation. ReadOff does not provide a permanent document or audio library. Content is processed through server memory and the browser for the active reading; third-party processing and technical logs have their own retention arrangements.
Service providers
- Google Cloud: website/server hosting, infrastructure logs, and Document AI image recognition. Recognition currently uses a US processor and online processing. Google describes online Document AI content as processed in memory without persisting document data to disk; request metadata may be logged.
- Inworld: receives submitted reading text to generate audio. Its retention depends on the applicable account and service arrangements; ReadOff does not promise zero retention by this provider.
- Supabase: hosts account records, password hashes, balances, usage and purchase references, and marketing preferences. When a social sign-in provider is connected, Supabase also handles that sign-in and its provider identity records. Google is currently the only offered social sign-in provider. It processes your login and shares the identity and email details needed to authenticate you; your Google password is not sent to ReadOff.
- Resend: delivers account verification and password-reset emails, including the recipient address and the secure account-action link. Verification status and hashed, expiring action tokens are stored with your account.
- Stripe/Link: hosts checkout and processes payment, billing, fraud checks, receipts, and transaction support. ReadOff receives payment status and purchase references; it does not receive full card numbers.
- Cloudflare and Google email services: route and receive messages sent to our support address. Website font files may also be requested from Google Fonts when using the app.
Provider processing may take place outside Portugal or the EEA, including the United States. Applicable provider agreements and international-transfer arrangements govern that processing. Contact us for information about the arrangements relevant to your data.
Why processing is permitted
Account creation, recognition, audio delivery, and credit administration are necessary to perform the requested service or take steps at your request before purchase. Security and abuse prevention are based on legitimate interests in operating a reliable service. Accounting and other required records are processed to meet legal obligations. Optional promotional messages rely on consent.
Cookies and browser storage
ReadOff uses account-session cookies (up to 7 days), a free-trial identifier cookie (up to one year, linked to the account when signed in so sign-in does not renew the allowance), and, during private testing, a preview-access cookie (up to 8 hours). Your chosen voice is stored locally until cleared. A selected pack may be stored in the current tab while you sign in, with an application validity of 30 minutes. These support sign-in, allowances, preferences, and the purchase journey. Checkout providers use their own storage under their notices. ReadOff currently has no advertising trackers or audience-analytics integration.
Retention
The Google Cloud default service-log bucket retains records for 30 days. Encrypted local database backups are rotated after 30 days when the backup job next completes successfully. They are protected by a key encrypted for the operator’s Windows account. Encrypted copies are also uploaded to private Google Cloud Storage in the US, with the recovery key stored separately in Google Secret Manager under access controls. Cloud copies become eligible for lifecycle deletion after 30 days and have an additional seven-day soft-deletion recovery period; actual removal depends on cloud lifecycle execution. Backup copies may retain an earlier account record during these periods; restored data must have subsequent completed deletions reapplied before service resumes.
Account, balance, and usage records are kept while needed to provide the account and resolve service or purchase issues. We retain financial records and other information where required by law or necessary for legal claims. Trial records and service logs support allowance enforcement and security. Closing your reading does not delete account, financial, support, or provider records. You can request a deletion confirmation email from your account page. The link expires after 30 minutes and requires a separate confirmation. Confirming closes access, revokes sessions, removes sign-in credentials and marketing preferences, and replaces the ReadOff profile email/password with a closed-account marker. Retained payment references may still be linked to transactions by authorised support. A linked Supabase sign-in identity is also removed. This does not delete your Google account. Purchase/refund references and a minimal closure record are retained as needed for accounting, resolving disputes, preventing duplicate credits and applying deletion again after restoration. Ask support about purchase or refund issues before closing; statutory rights remain unaffected.
Optional news and promotions
The marketing box is optional and unchecked by default. You can change it in your account or email support. Withdrawing consent does not affect your purchases or necessary service messages. Marketing-preference records are retained where needed to respect your choice and demonstrate consent.
Your rights
Subject to applicable conditions, you can request access, correction, deletion, restriction, portability, and objection to processing, and withdraw consent. Contact support@readoff.app; we may need to verify your identity securely. You can complain to the Portuguese data protection authority (CNPD) or another competent supervisory authority. We do not use ReadOff account or reading data to make automated decisions with legal or similarly significant effects.
What you choose to share
Only upload content you are entitled to process. Avoid submitting sensitive personal information you do not need to read, and consider whether you have permission to submit information about other people. Sharing content for reading does not make it public to other ReadOff users.
Updates
This notice will be updated when processing changes. Contact support for questions or a copy of the current information.