← Flux

Privacy Policy

Last updated: 20 November 2026

This policy explains what personal data Flux handles, why, and what you can do about it. It covers the Flux web app at readingflux.com and the Flux Chrome extension.

The short version

1. Who is responsible

Flux is run by Stanley Morales, Germany, who is the controller of your data under the EU General Data Protection Regulation (GDPR).
Contact for anything privacy related: support@readingflux.com.

2. What we collect and why

Your account

Email address, username, your password (stored only as a one-way bcrypt hash, never in readable form), whether your email is verified, and your settings such as languages and theme. We need these to give you an account and keep it secure (GDPR Art. 6(1)(b), performance of a contract).

Your learning content

Texts and books you import (title, text, chapters and the translations made while reading), words and phrases you save with their translation, the sentence they came from and, when saved from the extension, the address and title of the page. Also your flashcard decks and review progress, and your conversations with the AI tutor. This is the core of the service, stored so you can use it on any device (Art. 6(1)(b)). You can delete words and texts yourself at any time.

Usage counters

For each account we count AI requests, translations and story generations per day, and the AI tokens used. We use this to apply the free plan's daily limits and to keep costs under control (Art. 6(1)(b) and (f)).

Payments

Premium is paid through Stripe. You enter your card details on Stripe's own checkout page; they never reach our server. We keep your Stripe customer and subscription IDs, your plan, billing period, invoice IDs, amounts and payment status for as long as you have an account (Art. 6(1)(b)). Stripe keeps the invoices themselves as long as tax law requires, up to 10 years (Art. 6(1)(c)).

Emails and feedback

We send you emails to verify your address and to reset your password. If you use the feedback form, your email address, the category and your message are sent to us by email so we can reply (Art. 6(1)(b) and (f)).

Server logs, error monitoring and abuse protection

Like most websites, our servers log requests: IP address, time, the requested address and your browser's identification. We use these logs only to run the service and investigate errors or attacks. They are overwritten automatically after a short time. To stop abuse, the number of requests per IP address is counted in memory for one minute and never stored (Art. 6(1)(f), our interest in a secure, working service).

To find and fix bugs quickly, Flux also records technical error reports (status code, endpoint or page, error message, stack trace, and when signed in, your account ID and email address) in our own database (capped at the latest 1,000 entries) and via Sentry (hosted in the EU). In the web app, Sentry also records sampled performance traces (10% of requests) and Session Replays (10% of sessions, plus sessions where an error occurs, with text inputs and sensitive elements masked by default) (Art. 6(1)(f), our interest in keeping the app reliable). The Chrome extension does not load Sentry.

Analytics

The web app uses Umami, which we host ourselves, to count page views and a few events (for example "a word was saved" or "a free limit was reached"). It sets no cookies, does not store your IP address, does not follow you across websites, and the events carry only categories and numbers, never your texts, words or user ID. The data stays on our own server (Art. 6(1)(f), our interest in understanding how Flux is used). The Chrome extension sends no analytics at all.

3. Translation and AI

To translate or explain something, Flux has to send that text somewhere. Which service gets it depends on the mode you choose:

Read-aloud uses your browser's or operating system's built-in speech voices. Some voices (for example some of Chrome's) are provided online by the browser maker, which then receives the text being read.

4. The Chrome extension

Data the extension handles is used only to provide its features. It is not sold, not used for advertising, not used to decide on credit or lending, and not shared with anyone beyond the services listed in this policy.

5. Data stored on your device

Flux uses no tracking cookies, so it shows no cookie banner. The web app keeps your sign-in token, your settings and the text you are reading in your browser's local storage, and caches the app's own files for offline use. This is technically necessary for the app to work (§ 25(2) TDDDG). Signing out removes your sign-in token. Clearing your browser's site data removes everything else.

6. Service providers

We use these providers to run Flux. They receive only the data they need for their task.

ProviderWhat forLocation
Hosting providerServer hosting and databaseEuropean Union
Google (Gemini API, Google Translate)AI features, free translationsEU / USA
StripePaymentsIreland / USA
ResendAccount emails and feedback emailsUSA
Sentry (Functional Software, Inc.)Error monitoring, tracing, and session replay (web app)European Union (Germany)

When data goes to the USA, the transfer is covered by the EU-U.S. Data Privacy Framework or by the European Commission's Standard Contractual Clauses.

7. How long we keep data

8. Your rights

Under the GDPR you have the right to access your data, to have it corrected or deleted, to restrict how it is used, to receive it in a portable format, and to object to processing based on our legitimate interests. You can delete your account yourself in Flux under Profile → Delete account: this ends any subscription and removes all your data at once. For anything else, write to support@readingflux.com from the email address of your account. We will answer within one month.

You also have the right to complain to a data protection supervisory authority, for example the one where you live.

9. Security

All connections use HTTPS. Passwords are stored only as hashes. Access to the servers is limited to the operator.

10. Children

Flux is not meant for children under 16, and we don't knowingly collect their data. If you believe a child has given us data, contact us and we will delete it.

11. Changes

If Flux starts handling data differently, we will update this page and change the date at the top. For important changes, we will also tell you in the app or by email.