Binding language
This is a courtesy translation. The Polish version is the legally binding one; in the event of any discrepancy, the Polish text prevails.
The key facts about your data
- Your account is a verified email address - no password. When you first open the app we ask you to verify an email address with a six-digit code; you cannot start using Readspresso without it (section 15). We do not know your surname. Your first name, if you give it, stays in your browser and never reaches our server. We collect no location data.
- What you read never leaves your browser. Your library, the content of your documents, your place in them and your settings stay on the device - we have no access to them and store no copy on any server.
- We store no cookie until you consent. The only cookie that can appear comes from Google Analytics, and only if you click “Sure” on the analytics question. Before you consent - and after you decline - the Google Analytics script is not loaded at all. Declining is as easy as accepting, and you can withdraw consent at any time in Settings, with immediate effect.
- Google never receives what you read - not the text, not the titles, not your answers. Only the fact that some exercise was completed.
- We do not profile you and take no automated decisions. We run no advertising.
- Our server receives your email address (stored in the database as a keyed hash), transaction information if you buy Readspresso Pro (Link, part of Stripe, takes the payment on our behalf - section 8), and your training statistics (exercise levels, round results including accuracy, and reading-speed measurements in WPM), so your progress follows you to another device - you can switch off keeping them in your account at any time in Settings, and we then delete the copy from the server. If you turn on practice reminders, we also store their settings together with your email address in readable form, because that is where we send them. The content of what you read never reaches it.
The detail follows. If anything remains unclear, write to coffee-bits@coffee-bits.pl and we will explain.
1. Controller and contact
- The controller of your personal data is COFFEEBITS spółka z ograniczoną odpowiedzialnością, seated in Rzeszów, ul. Stanisława Stojałowskiego 12 lok. 47, 35-120 Rzeszów, Poland, entered in the KRS register of entrepreneurs under number 0001215852, NIP 8133945689, REGON 543667100.
- For all data protection matters write to coffee-bits@coffee-bits.pl. You may also write to the registered office.
- The controller has not appointed a data protection officer, because none of the conditions in art. 37(1) GDPR is met. Requests are handled directly by the controller at the address in paragraph 2.
- The controller operates no telephone customer service and has no telephone number for data protection matters. The contact channel is email or written correspondence.
2. Data that stays only on your device
-
Readspresso saves your training data in your browser's storage, in an IndexedDB
database named
readspresso. Document content, your reading position, reading sessions and settings are never sent to our server. The three training collections (exerciseProgress,exerciseResults,benchmarks) are the exception: while the device is signed in with a verified email address and you have not switched off keeping progress in your account (section 6), a copy of them is synchronised to our server so your progress follows you to another device - see section 3. For everything else, we have no access to it, make no copy of it, and are unable to read or recover it. - The database contains eight data sets:
| Data set | What it contains |
|---|---|
| documents | the full content of everything you paste, load from a file or import from a URL, with its title, source and the point you stopped reading |
| exerciseResults | individual exercise results: level, accuracy, average reaction time, error count, points, date |
| exerciseProgress | current and best level, session count, streaks of successful and failed rounds |
| benchmarks | history of reading-speed and comprehension measurements |
| sessions | reading sessions: when they started, how long they lasted, how many words, average speed |
| settings |
your preferences: speed, chunk size, typeface, theme, reader mode and others, the
first name the app greets you with on the workout screen (if you give one;
displayName), the device's copy of your choice whether to keep progress in your
account (progressSyncEnabled), plus your analytics consent decision (analyticsConsent:
not decided, granted or denied)
|
| entitlement | the signed sign-in token confirming your email address and any Readspresso Pro entitlement - it contains the verified email address, stored in plain form |
| regressionEvents | left over from a retired feature (a map of where you went back in a text) - the app writes nothing to it, so it is empty; it is kept only because it is part of the database structure |
-
Internal record identifiers are generated with
crypto.randomUUID(). They are random values. We do not use fingerprinting - recognising a device by its configuration - and create no persistent tracking identifiers. - We do not collect your surname, home address, telephone number or location data. Giving a first name is optional - you can leave the field empty or change it in Settings. It is saved only in the settings in your browser and is never sent to our server.
-
You have full control over this data. You can delete it yourself at any time using the
“Delete all data in this browser” button in Settings, or by clearing site data for
readspresso.com in your browser. Deletion is immediate and irreversible - we hold no backup from which
to restore it. Before that button deletes anything, the app turns off any practice reminders set up
from this device (it deletes their entry on our server); if there is no connection at that moment, you
can turn reminders off with the link included in every reminder email. Data on our server is deleted
separately - see section 13(3). Settings also offers “Download my data (JSON)”, which
exports every one of the eight data sets above - for the
entitlementset, only the decoded contents of the token, not the token itself - and, if an email address has been verified on this device, the data held on our server too (see section 13(5)). - Because this data never reaches the controller and is neither stored nor used by it, the controller carries out no processing operations on it to the extent that it remains solely on your device. We describe it here so you know exactly what the application you use writes down.
The flip side of this design
Your library cannot be recovered. Clearing browser data, private mode, or changing browser or device means permanently losing the texts you loaded and your place in them. We cannot recover them, because we never had them. Training statistics are different: we hold a copy of them (section 3), and it returns to a new device once you verify the address again - provided no more than 18 months have passed since the last synchronisation (section 7(2)). There is no copy only of results from a period when the device was not signed in (section 15(3)). Your Readspresso Pro entitlement is unaffected - you restore it with a code sent to your email address.
3. Data processed on our server
- On the server side we store what is necessary to verify your email address, to sell access and confirm that a given device is entitled to it, and a copy of your training statistics. If you turn on practice reminders, we also store what is necessary to deliver them, as well as short-lived technical entries that serve security. We use the Upstash Redis key–value store, running in the European Union (Belgium). “Email hash” in a key name means the keyed hash described in section 4. We write the following kinds of entry:
| Key | Contents | Retention |
|---|---|---|
| entitlement:<email hash> | a record of every purchase linked to the address (Lifetime access or subscription): variant, status (active, payment arrears, expired), end date of the current billing period, Stripe identifiers - customer, subscription or payment - and last update date | indefinitely - until deleted on request (see section 7(1)) |
| stripe-owner:<Stripe identifier> | the link from a Stripe customer, subscription or payment identifier to the hash of the email address the purchase was made under - so that later changing the address in Stripe cannot move a purchase to someone else | no automatic expiry; deleted together with the entitlement entry (see section 7(1)) |
| progress:<email hash> | a copy of your training statistics: current and best level per exercise with the session count and round streaks, individual round results (exercise, level, accuracy, mean reaction time, error count, points, date) and your reading-speed measurements (words per minute - raw and effective - comprehension, date). Capped at the 750 most recent round results and the 250 most recent measurements. It contains none of the content you read and no document titles. Created only after you verify an email address, and not at all if you switch off keeping progress in your account | 18 months from the last synchronisation - every synchronisation restarts the period - then deleted automatically; earlier on request (see section 7(2)) |
| progress-off:<email hash> | created only when you switch off keeping progress in your account: just the date you did so. While it exists, the server accepts no training statistics from any of your devices | 18 months from the last sign-in or sign-in refresh (which happens automatically while you use the app) - each restarts the period; deleted earlier when you switch keeping progress back on or delete your data from the server |
| notification:<email hash> | created only if you turn on practice reminders (after verifying an email address): your push subscription (endpoint and encryption keys, if your browser supports push), your email address in readable form (kept unhashed here because delivering an email reminder requires it - see section 4(4)), the language, reminder time and time zone you chose, and the date a reminder was last sent | 90 days from turning reminders on or from the last use of the app (a synchronisation, sign-in or sign-in refresh), then deleted automatically; earlier when you turn reminders off or delete your data (see section 7(3)) |
| notification:index | the list of email hashes of people with reminders turned on, which the reminder-sending job reads |
a hash is removed from the list together with its notification:… entry, or - once
that entry has expired - on the next run of the sending job (every 15 minutes)
|
| otp:<email hash> | the six-digit verification code | 10 minutes, then deleted automatically; a correctly used code is deleted at once |
| otp-attempts:<email hash> | a counter of attempts to enter the verification code | at most 10 minutes; deleted earlier when the code is used correctly or a new code is sent |
| revoked:<email hash> | created only when you delete your data from the server (section 13(3)): just the time of that deletion, used to reject sign-ins issued before it - so that no device still holding one can restore the deleted data. Contains nothing else | 100 days, then deleted automatically (see section 7(5)) |
| ratelimit:<…> | request counters protecting the ordering of verification codes against abuse: a counter for your IP address (the IP address is part of the key name) and counters for the hash of the email address a code was ordered for | 1 hour or 24 hours from the first request, then deleted automatically |
| stripe-event:<identifier> | the identifier of an event received from Stripe and its processing state - protection against processing the same payment twice; contains no personal data | 60 seconds while being processed, 30 days once processed; then deleted automatically |
-
We store none of the content you read on the server. The server does not know what
texts you loaded or how many you have. We do store a copy of your exercise results (the
progress:…entry above) - so the server does know your training results, including your reading speed (WPM) and your accuracy in exercises - unless you switch off keeping progress in your account (section 6), in which case the results stay only on your device. Results from a period when the device was not signed in stay only on your device until you verify the address again. - Outside the store described in paragraph 1, server functions hold transient request counters in working memory for IP addresses (a 60-second window) and for the hashes of email addresses codes are ordered for (a 1-hour window) - see section 5.
- We store no payment card data. We never see it - it is handled solely by Link and Stripe (see section 8).
4. Email pseudonymisation - an honest explanation
- In the key names of all the entries described in section 3, we do not store your email address in readable form. Instead we store its HMAC-SHA256 cryptographic hash, keyed with a secret known only to our server (not a plain, unkeyed SHA-256 hash). The readable address appears in our database only inside the reminder entry - see paragraph 4(d). A leak of the database contents therefore does not yield a ready-made list of our users' email addresses, and - unlike a bare hash - cannot be checked against a list of candidate addresses without also possessing that secret.
- We do not, however, claim this data is anonymous - because it is not. Whoever holds both the database and that secret can still recover which email addresses are ours by computing the same keyed hash. It remains reversible in principle, just not by anyone holding only a leaked database.
- Consequently this is pseudonymisation within the meaning of art. 4(5) GDPR, not anonymisation. A hashed email address remains personal data and we apply the full GDPR regime to it, including your rights described in section 13.
-
Your email address in readable form also exists:
- in our Stripe account, as the customer address attached to the transaction, and at Link, which takes the payment on our behalf (section 8(3));
- at the email provider Resend, for as long as needed to deliver the verification code message, the confirmation of the contract after you buy Readspresso Pro, the acknowledgement of a notice of withdrawal and, if you turn on practice reminders, the reminder messages;
- in the sign-in token stored in your browser, and transiently in the memory of a server function while your request is handled - it is not written to the database in that form; in the browser also after a sign-in has expired (to offer signing back in with the same address) and for the trip to the payment page - see the Cookie and browser storage policy, section 3;
-
in the
notification:…entry described in section 3, if you turn on practice reminders - delivering an email reminder requires a readable address, so this one entry is a deliberate exception to point 1 above, not an oversight; - in our mailbox, if you write to us.
5. IP address and logs
-
Our server functions read your IP address from the headers passed on by the hosting platform
(
fastly-client-iporx-forwarded-for) solely to limit the number of requests from one address - this protects against bulk ordering of verification codes, code guessing, and abuse of the URL import, data export and data deletion features, account setting changes and the withdrawal form. -
As a rule the IP address is used only in the server function's working memory, for the duration of the
request and a 60-second rate-limiting window; entries for addresses that have stopped sending requests
are removed once that window has passed. The exception is ordering a verification
code: the counter of requests from your IP address is then written to our database (the
ratelimit:…entry in section 3), with the IP address as part of the entry's name. The counter is deleted automatically after 1 hour. We do not link the IP address to your entitlement or transaction. - Separately, Google, as hosting provider (Firebase Hosting and Cloud Functions), keeps server logs containing IP addresses and request metadata (date and time, path, response code, browser information). These logs are generated automatically and are necessary to maintain and secure the infrastructure; server-function logs are kept in Cloud Logging for 30 days. Google processes them as our processor under a data processing agreement.
6. Purposes and legal bases
| Purpose | Data | Legal basis |
|---|---|---|
| Concluding and performing the contract for Readspresso Pro; handling payment and refunds | email address, transaction data, Stripe identifiers, and the order data Link passes to us: name, country and billing address, tax identification number (if you give one) | art. 6(1)(b) GDPR - necessary to perform a contract |
| Concluding and performing the contract for the Readspresso service (including the free version): verifying your email address when you first open the app and signing in on further devices (verification code, token) | email address, email hash, one-time code, entitlement status | art. 6(1)(b) GDPR - necessary to conclude and perform a contract; the verified email address is the identifier of your account (Terms, section 6) |
| Synchronising training statistics between devices | email hash, exercise levels, round results, reading-speed benchmarks | art. 6(1)(b) GDPR - necessary to perform a contract: carrying your progress across devices and protecting it from loss are part of the service described in the Terms (sections 4 and 6). You can switch the feature off at any time in Settings (“Keep progress in your account”) - doing so deletes the copy from the server and stops synchronisation on all devices |
| Practice reminders (push notification or email) - only for people who have turned them on and verified an email address | email address, email hash, push subscription (endpoint and encryption keys), language, reminder time, time zone, date last sent | art. 6(1)(b) GDPR - necessary to provide the service you ask for by turning reminders on; you can turn them off at any time in Settings or with the link in every reminder email |
| Handling complaints, withdrawals and refunds | email address, content of the request, transaction data, full name (if you give it, e.g. in the “Withdraw from contract here” form) | art. 6(1)(b) and art. 6(1)(c) GDPR in conjunction with the Consumer Rights Act |
| Issuing and keeping accounting documents; tax settlement | transaction data, invoice details if provided | art. 6(1)(c) GDPR - Accounting Act, Tax Ordinance, VAT Act |
| Service security, rate limiting, countering abuse | IP address, request metadata, email hash (counters of codes ordered, the sign-in revocation marker after data deletion), Stripe identifiers (linking a purchase to an address) | art. 6(1)(f) GDPR - legitimate interest in protecting the service and its users from abuse |
| Establishing, pursuing or defending claims | transaction data, correspondence | art. 6(1)(f) GDPR - legitimate interest |
| Usage analytics (Google Analytics) - product development and assessing which exercises are actually used | the events listed in section 10, cookie identifier, IP address, browser and device information, approximate location | art. 6(1)(a) GDPR - your consent, and for storing and reading information on your device also art. 399 of the Electronic Communications Law |
Where processing is based on art. 6(1)(f) GDPR you have a right to object - see section 13(6).
Analytics is based on consent alone, not on legitimate interest. If you do not consent, no analytics are collected and you use the full functionality of the Service - declining restricts nothing. You can withdraw consent at any time (see sections 10(6) and 13(7)).
7. Retention periods
-
The entitlement entry (
entitlement:…) is kept indefinitely, for as long as the entitlement can be exercised. This is necessary above all for Lifetime access - deleting the entry would mean permanently losing purchased access. The links from Stripe identifiers to the email hash (stripe-owner:…) are kept for the same period. We delete both at your request (see section 13(3)), subject to the exception described there in point (c). -
Training statistics (
progress:…) are kept for 18 months from the last synchronisation. Every synchronisation restarts the period, so your history does not disappear while you use the app; after 18 months without a synchronisation the entry is deleted automatically. We delete it earlier at your request (see section 13(3)) and immediately when you switch off keeping progress in your account in Settings. The set is bounded by design: we hold the 750 most recent round results and the 250 most recent measurements, and older entries are dropped on the next synchronisation. The marker that keeping progress is switched off (progress-off:…) - 18 months from the last sign-in or sign-in refresh; deleted earlier when you switch keeping progress back on or delete your data from the server. -
Practice reminders (
notification:…) - kept for 90 days from turning reminders on or from the last use of the app - a synchronisation, a sign-in or a sign-in refresh, which happens automatically while you use the app; each restarts the period. After 90 days without activity, reminders stop being sent and the entry - email address included - is deleted automatically. It is deleted earlier when you turn reminders off in Settings, click the unsubscribe link in a reminder email, delete the data in this browser with the button described in section 2(5), or delete your data from the server. The hash then also leaves thenotification:indexlist. -
Verification codes (
otp:…) and attempt counters (otp-attempts:…) - at most 10 minutes; a correctly used code is deleted immediately after verification. -
Data-deletion marker (
revoked:…) - 100 days. That is the longest a sign-in from before the deletion can remain in use: a sign-in expires at the latest 90 days after the email address was last verified with a code, and a token itself is valid for up to 72 hours. -
Request-limit counters - in the database (
ratelimit:…) 1 hour (the IP address counter and the hourly email-hash counter) or 24 hours (the daily email-hash counter); in server-function memory 60 seconds (IP address) or 1 hour (email hash). -
Payment event identifiers (
stripe-event:…) - 60 seconds while being processed, then 30 days. - Accounting and tax records - 5 years from the beginning of the year following the financial year concerned (art. 74(2) of the Polish Accounting Act), and until the limitation period for the tax liability expires (art. 86 § 1 of the Tax Ordinance). We cannot shorten this period on request, because it follows from a legal obligation.
- Data processed to defend claims - until the limitation period for contractual claims expires.
- Correspondence - up to 3 years from the close of the matter, unless a longer period is needed to defend claims.
- Analytics data in Google Analytics - retained by Google for 14 months from the user's last activity, per the GA4 data retention setting. This is the longest period GA4 allows for user- and event-level data; afterwards Google deletes it, leaving only aggregate reports. Withdrawing consent stops further collection immediately, and the Google Analytics cookies stored in your browser are then deleted (see section 10(6)).
- Your analytics consent decision - stored in your browser and kept there until you change it or clear site data. We keep it so as not to ask you the same question on every visit.
- After the retention period the data is deleted. Deleting the entitlement entry at your request means losing the ability to activate Pro on further devices - we warn you of this before carrying out the request, including in the app itself.
- Order data in our Stripe account (including the data Link passes to us) - for as long as the contract is performed, then for the accounting retention period (point 8) and until claims are time-barred (point 9). Link deletes it sooner if you ask Link to (section 13(3)).
8. Recipients and processors
- We do not sell your data, do not share it with data brokers or advertising networks, and do not use it for third-party marketing.
- We use the following providers, who process data on our behalf under processing agreements meeting the requirements of art. 28 GDPR:
| Entity | Role | Data | Location |
|---|---|---|---|
| Stripe Payments Europe, Limited and Stripe, LLC | running our Stripe account: records of customers, orders, payments and subscriptions, and the customer portal for managing a subscription (for taking the payment itself, see point 3) | email address, name, country and billing address, tax identification number (if you give one), transaction history | Ireland, United States |
| Resend | sending emails: verification codes, confirmations of contracts, acknowledgements of notices of withdrawal (and forwarding the notice to our mailbox) and - if you turn them on - practice reminders | email address, message content (a verification code, purchase details with the Terms attached, the content of a notice of withdrawal - with your name if you give it - or a reminder with a personal unsubscribe link) | United States (AWS infrastructure) |
| Google Cloud EMEA Limited (Cloud Functions) and Google Ireland Limited (Firebase Hosting) | hosting the application and server functions, server logs | request metadata, IP address | European Union (server functions: Belgium); app files served from Google's worldwide CDN |
| Upstash, Inc. | key–value database holding the entries described in section 3 | email hash, purchase data and Stripe identifiers, training statistics (including reading speed and accuracy), reminder data (including the email address in readable form and the push subscription), verification codes, request-limit counters (including IP addresses) | European Union (Belgium) - where the data is stored; Upstash, Inc. is based in the United States |
| Google Ireland Limited and Google LLC | Google Analytics 4 - usage analytics; only after you consent | the events listed in section 10, cookie identifier, IP address, browser and device information, approximate location | Ireland, United States |
- Link and Stripe as separate controllers. Payment for Readspresso Pro is taken on our behalf by Sold through Link, LLC (a Stripe company, United States) as merchant of record, through Stripe Managed Payments. For taking the payment, accounting for the tax, issuing the receipt or invoice, supporting you with the order, refunds and disputes, preventing fraud and meeting legal obligations (e.g. anti-money-laundering), Link and other Stripe companies are separate controllers of your data under their own rules: the Sold Through Link Terms and the Link privacy policy. On the payment page Link collects, among other things, your email address, name, billing address and payment details and, if you choose to create a Link account, that account's data. Link passes the order data to us (email address, name, country and billing address, tax identification number if you give one, and order details); we process it as controller for the purposes in section 6. To the extent Stripe runs our account and keeps that data in it on our instructions, it is our processor (table above). When you go to the payment page you leave our service and enter that of Stripe and Link, which uses its own cookies.
- Push notification services - recipients that are not our processors. If you turn on practice reminders and your browser supports push notifications, our server sends the reminder to the push service your browser designated. Depending on the browser, that is a service run by Google (Firebase Cloud Messaging), Mozilla (autopush), Apple (Apple Push Notification service) or Microsoft (Windows Push Notification Services); we accept no other addresses. The service receives the endpoint address - the subscription identifier assigned to your browser - and the encrypted notification content (the reminder's title and text), encrypted with your browser's keys so the push service cannot read it. We do not choose these services and have no processing agreements with them: they are provided by your browser's maker on its own terms, and they process the data on their own account to deliver the notification to your device. If push is not available, we send the reminder by email through Resend.
- Data is also received by our email provider - for correspondence you send to or receive from coffee-bits@coffee-bits.pl (including complaints, withdrawal notices and data protection requests) - and by the person keeping our accounts - for the transaction data needed for bookkeeping and tax settlement.
- Data may be disclosed to competent public authorities where the law so requires.
- A current list of processors is available on request sent to coffee-bits@coffee-bits.pl.
9. Transfers outside the European Economic Area
- Some of our providers are established or have infrastructure in the United States, which means data is transferred outside the EEA.
-
Transfers take place on the basis of the safeguards in Chapter V GDPR, in particular:
- standard contractual clauses adopted by the European Commission (art. 46(2)(c) GDPR), forming part of the processing agreements concluded with providers, and
- the European Commission's adequacy decision of 10 July 2023 on the EU-U.S. Data Privacy Framework - for providers that have joined that programme (art. 45 GDPR).
- For Google Analytics, data goes to Google Ireland Limited and, within the Google group, also to Google LLC in the United States. The basis is the adequacy decision under the EU-U.S. Data Privacy Framework together with the standard contractual clauses forming part of the Google Analytics data processing terms. A transfer occurs only if you consent to analytics.
- The push notification services described in section 8(4) run on their providers' infrastructure (Google, Mozilla, Apple, Microsoft), which may be located outside the EEA. The endpoint address and the encrypted reminder content reach them only if you turn on reminders and your browser supports push notifications.
- Link (Sold through Link, LLC) is based in the United States. It processes the data it collects on the payment page as a separate controller, and the Link privacy policy describes how that data is transferred outside the EEA. Order data kept in our Stripe account may reach Stripe, LLC on the bases described in paragraph 2.
- You can obtain a copy of, or information on where to access, the safeguards applied by writing to coffee-bits@coffee-bits.pl.
- Data that stays solely in your browser (section 2) is not transferred anywhere, because it never leaves your device. Synchronised training statistics go only to the Upstash store described in section 8. Reminder data goes to the same store and, with each send, to Resend or to a push service (paragraph 4).
10. Usage analytics (Google Analytics)
- The Service uses Google Analytics 4, provided by Google Ireland Limited, to establish which exercises are actually used and completed and which are not. This serves product development only.
- Analytics runs only after you consent. On your first visit we show a one-time consent question. Until you answer it - and after you decline - the Google Analytics script is not loaded at all: your browser makes no connection to Google's servers for this purpose, no cookie is stored on your device, and Google receives no data - no identifier, no IP address, no browser information. We load the script only after you consent, using Google Consent Mode v2 (see paragraph 7).
- In the consent question both buttons carry equal weight: declining (“No thanks”) takes exactly the same single click as accepting (“Sure”). We use no patterns that make declining harder, do not repeat the question after a refusal, and do not make the Service conditional on consent - after declining you use every feature just the same.
- If you consent, only structural events reach Google - the fact that something happened, with a few numbers:
| Event | Meaning and attached information |
|---|---|
| app_opened | the application was launched |
| onboarding_completed | onboarding finished; whether the calibration measurement was taken, and whether the last step led to the Readspresso Pro plans or into the app |
| document_imported | a document was added; source type (paste, file, URL) and word count. No title and no content |
| document_progress_50 | half the document was read; source type |
| reading_session_completed | a reading session ended; words read and duration |
| regression_navigated | a backward jump in the text; position expressed as a number |
| exercise_session_completed | an exercise session finished; exercise identifier, level, accuracy and session type (daily workout, self-chosen practice or onboarding) |
| daily_workout_completed | the daily workout was completed; streak length |
| benchmark_recorded | a measurement was saved; reading speed and comprehension |
- Google never receives what you read. Not the text of documents, not their titles, not the URLs you import from, not your answers in exercises and comprehension tests. This rule is enforced in the application code itself, not merely declared. Independently of this, Google collects the data typical for the tool: an identifier stored in a cookie, IP address, browser and device information, and approximate location derived from the IP address. According to Google, Google Analytics 4 does not store IP addresses and uses them only to derive approximate location; the former “IP anonymisation” option has no effect in GA4, so we neither use it nor rely on it. We have disabled automatic page-view reporting.
-
You can withdraw consent at any time using the toggle in the app's Settings.
Withdrawing is as easy as giving consent and requires no contact with us. Under art. 7(3) GDPR,
withdrawal does not affect the lawfulness of processing carried out on its basis beforehand.
Withdrawal takes effect immediately: the app stops sending events, Google Analytics is
disabled for the open page, and the
_ga,_ga_…(and_gid, if present) cookies are deleted from your browser. On later visits the Google Analytics script is no longer loaded. Data already sent to Google will be deleted after the period in section 7(11). If you want Google to delete it sooner, write to coffee-bits@coffee-bits.pl and we will pass on the request. -
We run no advertising or remarketing. The advertising consent signals in Google
Consent Mode (
ad_storage,ad_user_data,ad_personalization) are permanently set to “denied” in our configuration and do not depend on your choice - even after you consent to analytics, the data is not used for advertising purposes on our side.
What happens if you decline - the full picture
After you decline - just as before you answer - the Google Analytics script is not loaded. We store no cookie, and nothing reaches Google in connection with analytics: no identifier, no IP address, no browser information.
- Apart from Google Analytics we use no other analytics or measurement tool: no Plausible, PostHog, Matomo, Sentry, Hotjar, Meta Pixel or similar.
-
We do no direct marketing and send no newsletter. The only messages you will receive
from us concern your transaction, address verification (verification codes), a matter you raised, or
changes to documents we are obliged to notify you about - and, if you turn them on, practice
reminders. Every reminder email contains a personal unsubscribe link and
List-Unsubscribeheaders that let your mail client offer one-click unsubscribe; you can also turn reminders off in Settings. Receipts, invoices and some subscription messages (e.g. a reminder before a yearly renewal) are sent by Link, under its own rules. - We do not profile you and take no decisions based solely on automated processing that would produce legal effects concerning you or similarly significantly affect you, within the meaning of art. 22 GDPR. Analytics serves to assess the product in aggregate, not to evaluate individuals or take decisions about them. Exercise difficulty adapts to your results, but this happens entirely in your browser. The copy of those results on our server serves only to restore your progress on another device - we do not analyse it and build no profile from it.
11. Connections to external servers
- While you use the Service your browser connects primarily to our own server at readspresso.com. Below we describe every exception, so the picture is complete.
- The payment page (Stripe and Link). When you start payment you are redirected to the Stripe Checkout payment page, where Link takes the payment on our behalf. From that moment you are in the service of Stripe and Link, which uses its own cookies and its own privacy policy. You return to us only after payment completes or is cancelled. You can later manage the order at link.com too.
-
Typefaces - no connection to Google. The fonts used in the Service (Fraunces, JetBrains
Mono, Lexend, Atkinson Hyperlegible) are served from our own server, not from Google
Fonts. Your browser therefore makes no connection to
fonts.googleapis.comorfonts.gstatic.com, so Google does not learn your IP address merely because the page was displayed. This is a deliberate decision: fetching a font from Google's server would reveal every visitor's IP address before they clicked anything. -
Google Analytics. Only after you consent is the analytics script fetched from
googletagmanager.comand events sent to Google Analytics domains. Before consent and after refusal your browser does not connect to these domains. Details in section 10. - Push notification services. If you turn on reminders and allow notifications, your browser registers a subscription with its maker's push service, and that service delivers the reminders our server sends - see section 8(4).
- Pages you point us at. When importing an article from a URL it is our server, not your browser, that fetches the indicated page - see section 12. The source site therefore sees our server's IP address, not yours.
- Apart from the cases above, the Service embeds no content from external servers: no advertising, no social plugins, no maps, no videos and no external icon fonts.
12. Importing an article from a URL
- If you use this feature, you send us the URL of a page - in the request body (a POST request), not in the request address. Our server fetches that page, extracts the article text from it and passes it directly to your browser.
- We do not store or archive the fetched content, its title or the URL itself. This data exists only in the server function's memory for the duration of the request and does not reach our database. We build no history of what you import.
- Processing is based on art. 6(1)(b) GDPR - it is necessary to perform the service you asked for.
- The Google server logs referred to in section 5(3) may record that this function was called, together with request metadata. Because the URL of the imported page travels in the request body rather than as a parameter of the request address, it does not reach those logs as part of the request path. We do not store or log it ourselves.
13. Your rights
In connection with the processing of your data you have the following rights. To exercise them, write to coffee-bits@coffee-bits.pl.
- Right of access (art. 15 GDPR) - you can obtain confirmation of whether we process your data and a copy of it, with information on purposes, recipients and retention. You can also download a copy of the data held in this browser and on our server yourself in Settings - see paragraph 5.
- Right to rectification (art. 16 GDPR) - you can request correction of inaccurate data or completion of incomplete data.
-
Right to erasure (art. 17 GDPR) - you can request deletion of your data. You can do
it yourself: Settings contains a “Delete my server-side record” option which, once
confirmed with a code sent to your email address:
-
deletes the copy of your training statistics (
progress:…), the reminder entry (notification:…) - reminders stop - and any marker that keeping progress is switched off (progress-off:…); -
invalidates your sign-in on every device, so none of them can upload the deleted
data again; the device you delete from also forgets its sign-in if it was for the same address.
All that remains afterwards is the time of the deletion (
revoked:…), kept for 100 days (section 7(5)); -
deletes the purchase record (
entitlement:…) together with the Stripe identifier links (stripe-owner:…), ending Pro access - unless a subscription has not been cancelled (it is active or in payment arrears). In that case only the purchase record stays, so the subscription can still be cancelled; once it is, you can delete that record too.
-
deletes the copy of your training statistics (
- Right to restriction of processing (art. 18 GDPR).
- Right to data portability (art. 20 GDPR) - for data processed by automated means on the basis of a contract. We will provide it in a structured, commonly used, machine-readable format. “Download my data (JSON)” in Settings produces exactly such a file immediately. It contains all the data held in this browser and, if an email address has been verified on this device, the data held under that address on our server as well: the purchase record, synchronised training statistics, whether keeping progress in your account is on, and reminder settings. From the reminder settings we omit only the push subscription's encryption keys, which are credentials for the notification channel rather than information about you. The file does not contain the entitlement token itself, only its decoded contents - the token is a credential, and the file is meant to be safe to pass on. If the sign-in on the device has expired, verify the address again and download the file once more. We will provide the order data from our Stripe account on request; your order history and receipts are also at link.com.
- Right to object (art. 21 GDPR) - against processing based on our legitimate interest (art. 6(1)(f) GDPR), on grounds relating to your particular situation. We will stop processing unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms, or grounds for establishing, pursuing or defending claims.
- Right to withdraw consent (art. 7(3) GDPR) - you can withdraw analytics consent at any time using the toggle in the app's Settings, without giving a reason and without contacting us. Withdrawal does not affect the lawfulness of processing carried out beforehand. Details in section 10(6). Analytics consent is the only processing we base on your consent.
- How we verify your identity. Because we use no passwords and your account is your verified email address, we ask you to send your request from that address (or from the address used for the purchase). If you no longer have access to it, we will ask for other information confirming the request comes from the entitled person - for example transaction details. We do not ask for a scan of an identity document.
- Time limit. We reply without undue delay and no later than one month from receiving the request. In complex cases we may extend this by a further two months, informing you with reasons. Handling requests is free of charge.
- Data in your browser. You manage the data described in section 2 yourself - Settings provides both export and deletion, and clearing site data for readspresso.com in your browser also removes it. We have no access to the data that stays only on your device, so we can neither provide nor delete it on your behalf - unlike the data on our server, which we delete on request (see paragraph 3).
14. Complaint to a supervisory authority
- If you believe we process your data unlawfully, you have the right to lodge a complaint with a supervisory authority.
-
In Poland that authority is:
Authority President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych) Address ul. Stawki 2, 00-193 Warsaw, Poland Website uodo.gov.pl - If you live in another EU Member State, you may also complain to the supervisory authority for your habitual residence or place of work.
- Before complaining, consider writing to coffee-bits@coffee-bits.pl - we may be able to resolve the matter faster. This is not a precondition for lodging a complaint.
15. Whether providing data is required
- Providing an email address is voluntary but necessary to conclude the contract for using Readspresso - including the free version. When you first open the app we ask you to verify an address with a six-digit code; without it you cannot go further and start using the app. The verified address is the identifier of your account (with no password): it lets you carry your progress across devices (unless you switch that off), protects it from loss, restores purchased access and - if you turn them on - receives practice reminders.
- The same address is necessary to purchase Readspresso Pro and to confirm the entitlement on further devices later. Without an email address the contract can be neither concluded nor performed, because it is the sole identifier of access.
- If the sign-in on a device expires (section 16) or you delete your data from our server (section 13(3)), the app keeps working on that device, but without synchronisation and reminders until you verify the address again.
- Giving a first name is entirely optional and does not affect how the app works - it is used only to greet you on the workout screen and stays in your browser (section 2(4)).
- Providing invoice details is voluntary and necessary only if you request an invoice.
16. Security
-
We apply technical and organisational measures appropriate to the risk, in particular:
- HTTPS encryption on all connections;
- identifying database entries by a hash of the email address keyed with a server secret (HMAC-SHA256) rather than by the address - the one exception being the reminder entry, which needs the address in readable form (section 4(4)(d));
- signing entitlement tokens with an Ed25519 private key known only to the server - a token modified in the browser will be rejected; a sign-in expires at the latest 90 days after the address was last verified with a code, and deleting your data from the server invalidates all earlier sign-ins;
- a short, ten-minute validity for verification codes and a limit of five entry attempts, preventing code guessing;
- rate limiting on requests to server functions, including the number of codes ordered from one IP address and for one email address;
- signing reminder unsubscribe links, so each link works only for the address the message was sent to, and accepting push subscriptions only for the addresses of known push services;
- verifying the signature of every event received from Stripe and protecting against replay;
- blocking attempts to point the URL import feature at addresses on internal networks;
- a restrictive Content-Security-Policy and headers protecting against framing the Service and against content-type sniffing;
- the minimisation principle - we do not collect data we do not need.
- In the event of a personal data breach resulting in a high risk to your rights or freedoms, we will notify you without undue delay under art. 34 GDPR and report the breach to the President of UODO within 72 hours under art. 33 GDPR.
- No system is entirely immune to threats. We recommend using an up-to-date browser and securing access to the mailbox we send verification codes to - access to that mailbox allows your entitlement to be activated on a new device.
17. Children and minors
- The Service is intended for people aged 16 or over. This threshold matches the age set in art. 8(1) GDPR as applied in Poland.
- We do not direct the Service at children under 16 and do not knowingly collect their data. Before we send the code that verifies an email address, we ask you to tick a statement that you are 16 or over. We do not store the statement itself - it is a condition of opening an account on the device.
- If you are a parent or guardian and believe a child under 16 has given us their data, write to coffee-bits@coffee-bits.pl - we will delete it promptly.
- A paid contract concluded by a person with limited legal capacity requires the consent of their legal representative, on the terms described in section 1(5) of the Terms.
18. Changes to this Policy
- We may change this Policy if the law, the way the Service works, the scope of data processed, or the list of providers changes.
- Each version carries a number and effective date. Archived versions are available on request.
- We will announce material changes - in particular an extension of the data processed, a new purpose or a new recipient - with at least 14 days' notice in the Service and, for people with an active Readspresso Pro, also by email to the address used at purchase. We cannot write to the addresses of free accounts, because as a rule we keep them only as a hash (section 4).
- A change to this Policy cannot deprive you of acquired rights or extend processing retroactively.
| Version | Effective | What changed |
|---|---|---|
| 1.5 | 2 October 2026 | First published version of the Privacy Policy. |