Version 2 · Last updated: 11 August 2026
Cookies are small files stored by your browser; similar technologies (such as localStorage) store information on your device with equivalent functions. This policy describes what crankpal.com uses and why. Controller: CrankPal S.r.l. — privacy [at] crankpal.com (see the Privacy Policy).
The site uses no profiling cookies and no third-party tracking tools. We only use first-party elements:
| Name | Type | Purpose | Duration |
|---|---|---|---|
| crankpal_region | Technical cookie | Stores your selected region/language to show the correct site version | 12 months |
| Plan preference cookie | Technical cookie | Remembers the plan selected during workshop signup | Session / short term |
| crankpal_ref | Technical cookie (referral) | Remembers the code or invitation you arrived with, to attribute the referral — and the related credits — at signup | 30 days |
| crankpal_invite | Technical cookie (referral) | Remembers the personal invitation received by email, to apply its conditions at signup | 30 days |
| cp_cid | Cookie + localStorage (measurement) | Random first-party identifier for site usage statistics and signup-funnel reconstruction. Created on your first visit, valid on subdomains too (blog, documentation); if you choose "Reject" on the banner it is removed and no longer written | 12 months |
| cp_sess | localStorage (measurement) | Session identifier for statistics; absent if you rejected | 30 minutes of inactivity |
| cp_consent | Cookie + localStorage (technical) | Stores the choice made on the banner, valid on subdomains too | 12 months |
| cp_ref_* | localStorage (technical) | Attribution of invite/referral codes | Until manually cleared |
Measurement is performed with a first-party system (no external products). If you arrive from a campaign, we record the parameters present in the page address (utm and click identifiers, e.g. gclid, fbclid) associated with the visit.
Session recording (session replay). With your consent to the "Session recording" option of the banner, the public pages of the site, blog and documentation may record navigation with a first-party tool hosted on our own infrastructure, in masked form (typed text, emails and numbers are obscured; passwords are never captured). Within the management system's private area, recording is used for support and diagnostics and can be disabled for an individual workshop on request to Customer Support.
Some data is not stored on your device but collected by the server that serves the pages, even without consent: your IP address and the browser's technical signature (user agent), retained together with session data for up to 24 months; a stable technical identifier derived in encrypted form (hash) from IP and user agent, which lets us recognise repeat visits even without cookies; the campaign parameters described in § 2; the reading context of the page (time spent, maximum scroll percentage, section in view), reported without any device identifier if you rejected the banner.
We also count served pages server-side, in aggregate form and without any identifier. Measurement events are retained for up to 24 months; the per-identifier visit log for up to 3 years.
Technical and preference cookies do not require consent and are always active. Measurement identifiers (cp_cid, cp_sess) are written on your first visit; if you choose "Reject" on the banner (Accept and Reject have equal prominence) they are removed and no longer written, and your choice is remembered for 180 days. Session recording on public pages is activated only with consent to the dedicated option of the panel.
The processing described in § 3 uses no identifiers stored on your device and is based on the controller's legitimate interest in measuring the site's audience and the effectiveness of its own campaigns; you can object at any time by writing to [email protected]. Details on rights and retention are in the Privacy Policy.
You can change your choice at any time here: Manage cookies. You can also delete or block cookies and localStorage from your browser settings (region and preference storage will be lost).
We will update this policy if the tools we use change; the current version is always published on this page.