Cookie Policy
v2026.07 · July 3, 2026
OneRealSet only uses cookies and browser storage that are strictly necessary for the application to work: one language cookie and a handful of local storage items. We do not use analytics, advertising, profiling or third-party cookies, which is why you will not see a cookie banner — the law does not require one for these technical items. This policy explains in plain language exactly what we use, what it is for, how long it lasts and how you can manage it from your browser.
1. Who is responsible
The OneRealSet website and application (an online personal training platform with an AI coach available via web chat and WhatsApp) are operated from Spain by: - Owner: [RELLENAR: nombre y apellidos del titular] - Tax ID (NIF): [RELLENAR: NIF] - Address: [RELLENAR: domicilio] - Email: [RELLENAR: email de contacto] This cookie policy is provided in compliance with Article 22.2 of Spanish Law 34/2002 on Information Society Services and Electronic Commerce (LSSI-CE), and complements our Privacy Policy, which explains in detail how we process your personal data.
3. Exactly what we use
OneRealSet uses only the following items, all of them technical and first-party. There is nothing else: - NEXT_LOCALE — Type: first-party technical cookie, set with the SameSite=Lax attribute. Purpose: to remember your language preference (Spanish or English) so the application is shown in your language on every visit. Duration: 1 year (365 days) from when it is set or renewed. - one-realset-store — Type: first-party local storage (localStorage). Purpose: to keep the application state in your browser (for example, your dashboard data and interface preferences) so the app runs smoothly and you do not lose context between visits. Duration: no automatic expiry; it remains until the application updates it or you clear the site data. - one-realset-auth-v2 — Type: first-party local storage (localStorage); while you sign in, one-realset-auth-v2-code-verifier is stored as well. Purpose: to keep your Supabase session securely signed in (authentication). Without them you would have to enter your password constantly. Duration: for as long as the session is active; they are renewed automatically and removed when you sign out. - one-realset-chat — Type: first-party local storage (localStorage). Purpose: to keep your conversations with the AI coach in this browser so you can pick them up again. It holds what you tell the coach, including any training and health data you share in the chat. Duration: removed when you sign out; until then it remains unless you clear the site data. - streak_alert_last_date — Type: first-party local storage (localStorage). Purpose: to remember, in this browser, when the last training streak alert was shown to you, so the same notice is not repeated on the same day. Duration: no automatic expiry; it remains until you clear the site data. - app-sidebar-collapsed — Type: first-party local storage (localStorage). Purpose: to remember whether you left the sidebar collapsed. Duration: no automatic expiry; it remains until you clear the site data. - session-planner-mobile-divider-height-pct — Type: first-party local storage (localStorage). Purpose: to remember the height you chose for the session planner divider on mobile. Duration: no automatic expiry; it remains until you clear the site data. - rdg-views:<table> — Type: first-party local storage (localStorage), one entry per table. Purpose: to remember the views you save in the history and progress tables (columns, filters and sorting). Duration: no automatic expiry; it remains until you clear the site data. - one-realset-sw — Type: first-party IndexedDB database, managed by the application's service worker. Purpose: to keep the changes you make while offline until they can be sent, together with the session credential needed to send them. Duration: each change is deleted as soon as it is sent, and any of yours still pending are discarded when you sign out. - one-realset-static, one-realset-dynamic and one-realset-api — Type: first-party service worker caches (Cache Storage); their names also carry the application version. Purpose: to store the application's resources, its pages and the latest data responses so it loads quickly and works offline. Duration: replaced with every application version, and the data response cache (one-realset-api) is emptied when you sign out. We do not use any analytics, advertising, tracking or profiling cookies or storage, and we do not place third-party cookies on our domain.
4. Why we do not ask for consent (no banner)
The law only requires consent for cookies that are not necessary to provide the service. Article 22.2 of the LSSI-CE exempts from consent those storage devices that are strictly necessary to provide a service expressly requested by the user, and the cookie guidance issued by the Spanish Data Protection Authority (AEPD) confirms that technical cookies — such as session or authentication cookies, and personalisation chosen by the user, for example the language — fall within that exemption. Every item listed in section 3 fits that category: they are essential to, or directly instrumental for, the service you yourself request when using the app, or they remember an interface preference you choose. That is why we do not show a cookie banner: not because we have chosen to skip it, but because it is not required when only exempt cookies are used. Being honest also means not asking you for unnecessary clicks.
6. How to manage or delete cookies and local storage
You can view, block and delete both cookies and local storage from your browser settings. The exact steps vary by browser and version, but in general: - Chrome and Edge: settings menu, privacy and security section, cookie and site data options (or clear browsing data). - Firefox: settings, privacy and security section, cookies and site data. - Safari: preferences or settings, privacy section, manage website data. - In most browsers you can also click the padlock or settings icon next to the address bar to manage the data for this site only. From those options you can delete OneRealSet's data specifically or all sites' data, and set default blocking rules. Bear in mind that clearing the site data will sign you out and reset your language preference; your account and training data are not lost, because they are stored on our servers, not in your browser, except for changes you made offline that have not been sent yet.
7. What happens if you block them
Because OneRealSet only uses technical items, blocking them directly affects how the application works: - Without the Supabase session tokens it is not possible to stay signed in: you will not be able to use any feature that requires an account. - Without one-realset-store the application cannot keep its state in the browser and may behave erratically or more slowly. - Without the NEXT_LOCALE cookie the application will not remember your language and will revert to the default language on every visit. - Without streak_alert_last_date you may see the same streak alert repeated several times on the same day. Public informational pages may remain readable, but the application as a service needs these items to function. There is no signed-in version of OneRealSet that works with storage completely blocked.
8. Changes to this policy
If in the future we add cookies or technologies that are not exempt — for example, analytics tools — we will do two things before activating them: ask for your prior consent through a cookie banner as required by law, and update this policy to describe, in the same level of detail, what is being added, for what purpose and for how long. Any relevant change will be reflected in the version number and the last-updated date shown at the top of this policy. We recommend reviewing it from time to time. The current version is v2026.07, updated on July 3, 2026.
9. Legal framework
This policy is governed by the applicable Spanish and European Union legislation, in particular: - Spanish Law 34/2002, of 11 July, on Information Society Services and Electronic Commerce (LSSI-CE), especially Article 22.2. - Regulation (EU) 2016/679, the General Data Protection Regulation (GDPR). - Spanish Organic Law 3/2018 on the Protection of Personal Data and guarantee of digital rights (LOPDGDD). - The AEPD's cookie guidance, as interpretative criteria. The details of how we process your personal data — including the health data in your training profile, the legal bases, our processors and your GDPR rights — are set out in our Privacy Policy, which is the reference document for those matters. The governing law and jurisdiction are those of Spain, without prejudice to the rights you may have as a consumer under the law of your place of residence.
10. Contact
If you have any questions about this cookie policy or about how OneRealSet uses your browser storage, you can write to us at [RELLENAR: email de contacto]. To exercise your data protection rights (access, rectification, erasure, objection, restriction, portability or withdrawal of consent), please see the Privacy Policy and the Settings > Privacy section of the application, where many of these actions are available directly. If you believe our processing does not comply with the law, you have the right to lodge a complaint with the Spanish Data Protection Authority, AEPD (www.aepd.es).