cookies policy
Cookies Policy
Last updated: [EFFECTIVE DATE]
This Cookies Policy explains the use of cookies on tempus.build (the “Service”), in accordance with Article 22.2 of Law 34/2002 (LSSI-CE) and the AEPD “Guía sobre el uso de las cookies” (updated May 2024), which incorporates the criteria of the European Data Protection Board.
1. What is a cookie
A cookie is a small file that a website stores on your browser or device to enable functions such as keeping you signed in during a session. Similar technologies (local storage, tokens) are treated equivalently.
2. Cookies used by the Service
The Service uses strictly necessary (essential) cookies and, only with your consent, analytics cookies (Google Analytics and Yandex Metrica). It does not use advertising, social-media or third-party profiling cookies.
2.1 Strictly necessary (no consent required)
| Cookie | Provider | Purpose | Type | Duration | Attributes |
|---|---|---|---|---|---|
| Session / authentication cookie | First-party (operator) | Maintains your authenticated session after GitHub OAuth sign-in and provides CSRF/session integrity; without it you cannot use the authenticated Service | First-party, strictly necessary (technical) | Session / short-lived | httpOnly, Secure, SameSite |
The session cookie is httpOnly — it cannot be read by client-side JavaScript — is transmitted only over HTTPS (Secure), and is restricted by SameSite. It contains a session identifier only; it is not used to track you across other websites or for advertising.
2.2 Analytics (set only with your consent)
These cookies are non-essential. They are set only after you accept them via the cookie banner (see §3); if you decline or make no choice, none of them are set. Google Analytics additionally runs in consent mode: before consent it collects only cookieless, aggregated measurement signals (no cookies, no identifiers).
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
_ga, _ga_<container-id> | Google (Google Ireland Ltd / Google LLC) | Google Analytics — distinguishes users and sessions | Up to 2 years |
_ym_uid, _ym_d | Yandex | Yandex Metrica — user identifier and first-visit date | Up to 1 year |
_ym_isad | Yandex | Yandex Metrica — detects ad blockers | ~20 hours |
_ym_visorc | Yandex | Yandex Metrica — session replay (Webvisor) | ~30 minutes |
_ym_metrika_enabled, other _ym_* helpers | Yandex | Yandex Metrica — operation of the tag (request limiting, integrity) | Minutes to 1 year |
International transfers arising from these providers (United States for Google; Russian Federation for Yandex) are described in the Privacy Policy (§§4–5).
2.3 Local storage
The site also stores two items in your browser’s local storage, treated as strictly-necessary equivalents (no consent required): cookie-consent (remembers your analytics choice and its date, so we don’t ask again — this is what makes your “Decline” stick) and lang (remembers your language). Neither is used for tracking or shared with third parties.
3. Consent
Strictly necessary cookies (§2.1). Under Article 22.2 LSSI-CE, cookies strictly necessary to provide a service expressly requested by the user are exempt from the consent requirement. The session/authentication cookie falls squarely within this exemption: it is set only after you actively request to sign in via GitHub OAuth, and it is indispensable to deliver the requested authenticated service. No prior consent is required for it, though the duty to inform still applies — which is the purpose of this policy.
Analytics cookies (§2.2) are non-essential and are therefore not set unless you consent. Before you make a choice, no analytics cookie is placed: Google Analytics runs in consent mode and collects only cookieless, aggregated signals, and Yandex Metrica is not loaded at all.
4. How we obtain consent for analytics cookies
Analytics cookies are handled through a cookie banner designed to meet the AEPD requirements:
- consent is requested before any analytics cookie is set;
- the banner offers a genuine opt-in (“Accept”) and an equally prominent “Decline” — refusing is as easy as accepting, with no pre-ticked options and no cookie wall;
- your choice is remembered on your device, and you can withdraw it at any time as easily as you gave it (see §5);
- the table in §2.2 lists each analytics cookie, its provider, purpose and duration; the related international transfers are described in the Privacy Policy.
Until you accept, analytics cookies are not set, and declining keeps the site fully usable.
5. Managing cookies and withdrawing consent
You can configure your browser to block or delete cookies. Note that blocking the strictly necessary session cookie will prevent you from signing in and using the authenticated Service.
To withdraw or change your analytics choice at any time, use the “Cookie settings” link in the site footer: it reopens the consent banner so you can accept or decline anew — withdrawing is as easy as giving consent. Declining after a previous acceptance also clears the first-party analytics cookies we can reach. Alternatively, you can clear this site’s stored data (cookies and local storage) in your browser.
6. More information
For the processing of personal data associated with the session cookie (e.g. IP, session identifier), see the Privacy Policy. Questions: [CONTACT EMAIL].