Cookie Policy
This policy explains how IDLING uses cookies and similar technologies on the marketing and waitlist site (idlingapp.com and related domains). It supplements our Privacy Policy.
What are cookies?
Cookies are small text files stored on your device when you visit a website. We also use similar technologies (such as browser local storage) for equivalent purposes. Where relevant for transparency, this policy describes that local storage alongside HTTP cookies.
Who is responsible?
Pedro Jesús Parada Avendaño (data controller). Contact: hello@idlingapp.com.
Cookie and similar-technology inventory
The tables below identify each cookie or technology by name, provider, type, purpose, duration, and legal basis. Analytics and measurement cookies are only placed if you accept them in the banner or preference centre.
Strictly necessary (always on)
| Name | Provider | Type | Purpose | Duration | Legal basis |
|---|---|---|---|---|---|
NEXT_LOCALE | IDLING (first-party; managed with next-intl) | HTTP cookie | Remember your selected language (English or Spanish) between visits | 1 year from last update | Legitimate interest / technical necessity for the service you request |
kairos_cookie_consent_v2 | IDLING (first-party) | Local storage | Store your cookie choices (necessary and analytics) and notice version | Until you change your choice in the preference centre or clear site data in your browser (no fixed automatic expiry in our code) | Technical necessity / legitimate interest |
kairos_cookie_consent_v1 | IDLING (first-party) | Local storage | Previous consent record (only if it already existed in your browser before a notice update) | Same as kairos_cookie_consent_v2 | Technical necessity |
They do not require additional consent.
Analytics and measurement (optional; consent only)
We use Amplitude (Amplitude, Inc.; processing with EU data residency). The SDK is initialised only after you consent. Amplitude cookie names include a variable suffix made up of the first 10 characters of the project API key (for example, AMP_a2dbce0e18).
| Name | Provider | Type | Purpose | Duration | Legal basis |
|---|---|---|---|---|---|
AMP_ + project suffix | Amplitude, Inc. (EU) | HTTP cookie | Device and session identifiers (deviceId, sessionId, etc.) to count visits and measure site performance in aggregate | 365 days (provider default; not customised on our site) | Consent (GDPR Art. 6(1)(a)), withdrawable at any time |
AMP_MKTG_ + project suffix | Amplitude, Inc. (EU) | HTTP cookie | UTM parameters, referrer, and click IDs for campaign attribution | 365 days (provider default) | Consent |
AMP_TEST_ + timestamp / AMP_TLDTEST_ + timestamp | Amplitude, Inc. (EU) | HTTP cookie | Technical check that the browser supports cookies; removed after initialisation | Session / deleted when the test completes | Consent (when the SDK is activated) |
| Amplitude local storage keys (e.g. unsent event queue, session replay data) | Amplitude, Inc. (EU) | Local storage | Explicit event measurement and, for a sampled fraction of sessions, session replay with masking of sensitive fields (waitlist form, inputs, etc.) | Aligned with the provider session cookie (365 days by default) unless manually deleted | Consent |
Information collected through these technologies is used in aggregate form for marketing-site usage statistics.
Advertising cookies
We do not use advertising cookies or third-party advertising trackers on this marketing site.
Purpose and legal basis (summary)
- Necessary: legitimate interest and/or technical necessity to provide the service you request (language, consent record).
- Analytics: your consent (GDPR Art. 6(1)(a)), withdrawable at any time via the banner, preference centre, or footer “Cookie settings” link.
Retention
The periods in the tables apply specifically to each cookie or technology.
IDLING first-party cookies and storage
NEXT_LOCALE: 1 year from last update, unless you delete it earlier in your browser.kairos_cookie_consent_v2and, where present,kairos_cookie_consent_v1: until you change your choice or clear site data; we do not set a separate automatic expiry in our code.
Amplitude cookies and storage (only if you accepted analytics)
- Default HTTP cookie expiry: 365 days, per Amplitude’s cookie documentation.
- If you withdraw consent, we stop initialising the SDK and opt out; you may also delete Amplitude cookies in your browser.
General criterion
Cookies are kept for as long as strictly necessary to fulfil their purpose and, in any case, in line with the retention periods set by each cookie provider.
How to control cookies
- Banner and preference centre on the site (Customize / Accept all / Reject all).
- “Cookie settings” link in the footer to change your choice.
- Browser settings: you can block or delete cookies and local storage; blocking necessary cookies may affect site functionality.
Changes
We may update this policy and the inventory when we add cookies or providers. If a change is material, we will ask for your consent again where required.