Readspresso · Legal documents

Cookie and browser storage policy

What Readspresso stores on your device, for what purpose, and when it asks your consent.

Język: wersja polska (wiążąca)

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 short version

  1. Until you click “Sure” on the analytics question, no cookie is placed on your device and the Google Analytics script is not loaded at all.
  2. Everything Readspresso stores in order to work at all - your library, progress, settings - goes into browser storage (IndexedDB), not into cookies, and needs no consent, because without it the app could not do its job.
  3. The only cookies that can appear come from Google Analytics, and only with your consent, which you can withdraw at any time in Settings - we then delete them straight away.
  4. There are no advertising, tracking or profiling cookies. We do not run ads.

1. Legal basis

  1. Storing information on, and gaining access to information stored in, a user's terminal equipment is governed by art. 399 of the Polish Electronic Communications Law of 12 July 2024 (Prawo komunikacji elektronicznej), in force since 10 November 2024.
  2. That provision replaced the repealed art. 173 of the Telecommunications Law. References to the old provision, still found in many cookie policies, are out of date.
  3. Under art. 399(1), storing information on a user's device or accessing it is permitted subject to the user's prior consent, given after they have been fully informed.
  4. Consent is not required, however, where the storage or access is necessary to transmit a communication or is necessary to provide the electronically supplied service requested by the user (art. 399(3)). That exception covers the storage described in section 3.
  5. The processing of personal data that accompanies this has a separate basis under the GDPR - see the Privacy Policy.

2. Two different mechanisms: cookies and IndexedDB

  1. Cookies are small text files a site stores on your device, which the browser then attaches automatically to every subsequent request to that server. That is precisely what makes them suitable for tracking.
  2. IndexedDB is a database built into the browser. Data stored in it is never sent to a server automatically - only application code running in your own browser can read it. It is not suitable for tracking and does not leave your device.
  3. Readspresso keeps your data in IndexedDB; it also stores a few small technical items in localStorage and sessionStorage, and - if you turn on reminders - registers a service worker script to handle push notifications (see section 3). The distinction matters in practice: data in IndexedDB is entirely under your control and does not reach us - except the training statistics the app synchronises with your account on our server while the device is signed in and you have not switched off keeping progress in your account (see section 3 of the Privacy Policy).
  4. Art. 399 nonetheless applies to any storage of information on a device, whatever the technique - including IndexedDB. That is why we describe it below and explain why consent is not required for it.

3. Strictly necessary storage - no consent required

  1. Readspresso is a reading-training application that runs entirely in the browser. Without storing data on your device it could not perform its basic function: it would not remember the text you loaded, could not restore where you stopped reading, could not show progress and could not keep your settings. Closing the tab would mean losing everything.
  2. This storage is therefore necessary to provide the service requested by the user within the meaning of art. 399(3). No consent is required for it, and for that reason we display no consent banner for necessary storage. A banner asking permission for something the app cannot run without would be a sham - the user would have no real choice.
  3. Scope of necessary storage:
Information stored without consent under art. 399(3) of the Electronic Communications Law
Name Mechanism Purpose Retention
documents IndexedDB your text library, together with where you stopped reading until you delete it
exerciseResults, exerciseProgress IndexedDB exercise results and levels - without them the training could not adapt to your progress until you delete it
benchmarks, sessions IndexedDB history of measurements and reading sessions - the statistics shown in the app until you delete it
settings IndexedDB your settings (including your first name, if you give one) and your recorded analytics-consent decision, so we don't ask on every visit until you delete it
entitlement IndexedDB the sign-in token confirming your email address and any Readspresso Pro access - without it you would have to confirm your address by email code on every launch token valid 72 hours, renewed automatically - for at most 90 days after the address was last verified with an email code
readspresso.signedOutEmail localStorage your email address, saved only when your sign-in has expired - so the app can offer to sign you back in with the same address until you sign in again or delete the data in this browser
readspresso.pendingUnsubscribe localStorage a marker that switching off reminders has not yet reached the server (for example, because you were offline) - the app retries on the next launch until reminders are successfully switched off
readspresso.lastRoute localStorage the app screen you were last on (for example the document being read or the exercise - named by its identifier, without any content), with the time it was saved - so that when you come back to a browser that closed the tab in the meantime, you return to the same place rather than the start screen overwritten on every screen change; the app uses it for at most 30 minutes after saving
readspresso:checkoutEmail sessionStorage the email address given at purchase - kept for the trip to the payment page (Stripe, Link) and back, so you need not type it again deleted right after returning from the payment page, at the latest when the tab closes
/sw.js service worker registration of the script that displays push notifications with practice reminders - created only when you turn reminders on; it stores no content or data about you and does not act as a cache until you delete the data in this browser or clear the site's data
  1. None of this information is a cookie, and none of it is attached to requests by the browser automatically. The app itself sends our server only the sign-in token (to confirm your address and access) and - unless you switch off keeping progress in your account - a copy of your training statistics (exerciseResults, exerciseProgress, benchmarks), as described in section 3 of the Privacy Policy.
  2. Remembering that you declined analytics also falls within the art. 399(3) exception - it is information necessary to respect your choice.

4. Analytics cookies - with consent

  1. The service uses Google Analytics 4 to establish which exercises are actually used and completed. A detailed description, with the full list of events sent, is in the Privacy Policy.
  2. Google Analytics cookies are stored only after you consent. Before you answer the consent question, and after you decline, the Google Analytics script is not loaded at all - so no cookie is stored and no data reaches Google. We load the script only after you consent, using Google Consent Mode v2 with the advertising consent signals permanently set to “denied” (see section 7).
  3. Cookies stored after consent is given:
Cookies stored only after consent
Name Set by Purpose Retention
_ga Google distinguishing users - tells whether two visits come from the same browser up to 2 years; deleted immediately when you withdraw consent
_ga_<identifier> Google maintaining measurement session state in Google Analytics 4 up to 2 years; deleted immediately when you withdraw consent
  1. Two years is Google's default. The actual retention is shorter if you clear your browser data or withdraw consent earlier: when you withdraw consent, the app immediately deletes the _ga and _ga_… cookies (and _gid, if present).
  2. Retention on Google's side and the rules for transfers to the United States are described in the Privacy Policy.

5. Giving and withdrawing consent

  1. On your first visit we show a one-time analytics consent question. It has two equally weighted buttons: “No thanks” (decline) and “Sure” (accept). Declining takes exactly one click - the same as accepting.
  2. We use no dark patterns: we do not hide the decline button, do not visually favour acceptance over refusal, do not force you through extra settings screens, and do not re-ask after a refusal.
  3. Declining does not limit the service. All features remain available unchanged. We do not operate a “consent or pay” model.
  4. You can withdraw consent at any time using the toggle in the app's Settings. Withdrawing is as easy as giving consent and takes effect immediately: the app stops sending events, Google Analytics is disabled for the open page, the _ga, _ga_… (and _gid, if present) cookies are deleted, and on later visits the Google Analytics script is no longer loaded. You can equally change your mind the other way and enable analytics after having declined.
  5. Under art. 7(3) GDPR, withdrawing consent does not affect the lawfulness of processing carried out on its basis before withdrawal.
  6. You can also delete stored cookies in your browser settings - see section 8.

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.

6. Third-party cookies

  1. Stripe and Link. When you go to pay, you leave our service for Stripe's payment page, where Link (Sold through Link, LLC, a Stripe company) takes the payment on our behalf. Stripe and Link set their own cookies there, including those necessary to process payment and prevent fraud and, if you save your payment details in a Link account, to recognise your device on later purchases. On that page Stripe and Link are separate data controllers under their own privacy policies, available at stripe.com/privacy and link.com/privacy. We have no influence over these cookies and do not read them.
  2. Google Analytics. The cookies described in section 4 are third-party cookies set by Google. Their use is described in Google's cookie information.
  3. Typefaces - hosted by us. Interface fonts are served from our own server, not from Google Fonts. No cookie is created and no connection is made to fonts.googleapis.com or fonts.gstatic.com, so Google does not learn your IP address merely because you opened the page.

7. What we do not use

  1. No advertising or remarketing cookies. The advertising consent signals in Google Consent Mode are permanently set to “denied” in our configuration, regardless of your choice. We run no ads and build no advertising audiences.
  2. No fingerprinting - no recognising a device by its configuration, and no other technique intended to replace cookies as a persistent identifier.
  3. No embedded social plugins, “like” buttons, maps, videos or other elements that set third-party cookies.
  4. No analytics tool other than the Google Analytics described above - no Plausible, PostHog, Matomo, Sentry, Hotjar or Meta Pixel.
  5. We do not sell or share cookie data with data brokers or advertising networks.

8. Clearing the data yourself

  1. Every browser lets you delete site data for readspresso.com and block cookies. The relevant options are usually under “Privacy and security” or “Site settings”.
  2. Vendor instructions:
    1. Google Chrome
    2. Mozilla Firefox
    3. Safari
    4. Microsoft Edge

Careful - this also deletes your library and progress

Clearing site data for readspresso.com erases everything in IndexedDB described in section 3: your library, exercise results, measurement history and settings. We hold no copy of your library or settings on any server, so they cannot be recovered. A copy of your training statistics is kept in your account (unless you switched that off) - it returns once you verify your address again. Your Readspresso Pro purchase remains valid - you can restore access with a code sent to the email address used for the purchase.

  1. Blocking site data in your browser will stop Readspresso remembering anything between visits. The app will still start, but every time as if for the first time.

9. Changes to this policy

  1. We update this policy when the information stored on your device, the list of providers, or the law changes.
  2. If we introduce a new category of cookie requiring consent, we will say so before we start using it and ask for your consent - existing consent does not extend to new purposes.
  3. Each version carries a number and effective date. Archived versions are available on request.
  4. Version 1.5 (2 October 2026) - first published version of this policy.