Cookies Policy
Cookies Policy
How Reads uses cookies and local storage, in accordance with art. 22 of Spain's LSSI-CE.
1. What are cookies?
A cookie is a small piece of data stored by your browser. Reads also uses browser local storage, which works the same way but is not sent back to our server on every request. Both are covered by this policy.
2. Cookies we use
Reads only sets strictly-necessary cookies. Under art. 22.2 of Spain's LSSI-CE these do not require your consent, but we still list them:
| Name | Type | Purpose | Duration |
|---|---|---|---|
| access_token | First-party, HTTP | Keeps you signed in during a session. | Session (deleted on sign-out) |
| refresh_token | First-party, HTTP-only | Refreshes your session so you don't have to log in every day. | 7 days |
| reads_lang | First-party, localStorage | Remembers your language choice. | Until cleared by the user |
3. Third-party cookies
Reads uses a small number of third-party cookies from the services below. None of them are shared with social-media platforms.
- Google AdSense — free users who have reached the monthly limit (10 books or 50 recommendations) are served banner ads by Google. Google sets cookies such as
__gads,__gpi, andNIDto serve ads, cap ad frequency, and prevent click fraud. Cookies persist up to 13 months. These are not set for Reads+ subscribers or free users under the cap. Personalised (behavioural) ads require your consent; by default Reads requests non-personalised ads. Governed by Google's cookie policy. Opt out at Google Ads Settings. - Stripe may set its own cookies on the Stripe-hosted checkout page during payment — governed by Stripe's own policy, only applies on stripe.com.
- Cloudflare Turnstile — the “I'm not a robot” check on our sign-up form loads a script from challenges.cloudflare.com. Cloudflare may set a short-lived cookie (
cf_clearance, expires in minutes) to remember that your browser passed the challenge. It contains no personal data and is not used for tracking or advertising. See Cloudflare's Turnstile cookie reference. - RevenueCat — powers Reads+ subscription management across web and mobile. The web SDK stores a pseudonymous customer ID in your browser's
localStorage(keyrc_*) so we can recognise your subscription across sessions and devices. It does not set advertising or tracking cookies. RevenueCat only ever receives your pseudonymous ID, subscription product ID, purchase receipts, and basic device info — never your reading activity. Governed by RevenueCat's privacy policy.
4. How to control cookies
You can block or delete cookies from your browser settings at any time. Because Reads's first-party cookies are strictly-necessary, disabling them will sign you out and prevent parts of the app from working. AdSense cookies can be blocked without affecting Reads itself. To manage personalised-ad settings across every Google-served site, visit Google Ads Settings.
5. Changes to this policy
If we start using non-essential cookies in the future, we will publish an updated policy and ask for your prior consent through a banner, as required by law.
6. Contact
Questions about cookies? Write to readscoteam@gmail.com or use the Contact page.
Last updated: 26 August 2026.