Auditing & Traceability

Cookie & Tracking Technologies Policy

Document Version: 2.1 | Effective Since: March 2026

This document governs the use of cookies and local storage technologies on the SecureZZ SaaS platform. In compliance with the General Data Protection Regulation (GDPR) and the ePrivacy Directive (Directive 2002/58/EC), we transparently detail the nature, purpose, and technology of identifiers stored in your browser.

Non-Commercialization & Non-Profiling Commitment

In alignment with our security policy, SecureZZ prohibits the use of cookies for advertising profiling or commercial targeting. We do not build behavioral user profiles nor cross-reference your data with third-party companies for marketing or targeted advertising.

1. Categories of Technologies Used

Our infrastructure deploys two exclusive categories of trackers, distinguishing technically between HTTP header cookies and client-side persistence (LocalStorage):

A. Strictly Necessary Technologies

Pursuant to Article 22.2 of the LSSI / ePrivacy Directive, these technologies are exempt from prior informed consent requirements as they are strictly necessary to provide a service expressly requested by the user. Without these identifiers, platform functionality and technical security cannot operate properly.

IdentifierTechnologyProviderPurpose / Technical JustificationExpiration
tokenCookie (HTTP)SecureZZ (First-party)Authenticated session (JWT). Configured with HttpOnly and Secure flags to mitigate session hijacking (XSS) and prevent script access.72 Hours
sz_localeCookie (HTTP)SecureZZ (First-party)Remembers the selected language when opening the homepage.1 year
sz_sys_stateLocalStorageSecureZZ (First-party)Stores the user's legal preference regarding trackers (cookie acceptance/rejection).1 Year
securezz_tour_seenLocalStorageSecureZZ (First-party)UX control: remembers whether the user has completed the welcome virtual tour to prevent intrusive repetition.Persistent
job_notified_ / securezz_job_seen_LocalStorageSecureZZ (First-party)Technical scan management: tracks notifications for completed scans and malware analyses so the user is alerted accurately.Persistent
pendingVerificationEmailLocalStorageSecureZZ (First-party)Registration flow: retains the email awaiting 2FA verification code so validation can resume if the page is refreshed.Deleted upon verification or expiry
forgotCooldownUntilLocalStorageSecureZZ (First-party)Anti-abuse security: stores the timestamp until which a password reset email cannot be resent (60-second cooldown). Contains no personal data.60 seconds (auto-deleted)
g_stateCookie (HTTP)Google IdentityFederated authentication state management (SSO) to facilitate sign-in expressly requested by the user.1 Year
__stripe_mid / __stripe_sidCookie (HTTP)Stripe, Inc.Technical security and transactional fraud prevention (Stripe Radar) to protect against fraudulent charges.1 Year / Session

B. Analytics & Performance Technologies

In compliance with data protection authority guidelines (AEPD/CNIL), these cookies require your prior informed consent. GA4 telemetry processing is strictly conditional upon your express acceptance before injection.

IdentifierTechnologyProviderAnalytical Purpose (Telemetry)Expiration
_ga / _ga_<id>Cookie (HTTP)Google Analytics 4Generates aggregated, anonymous metrics to monitor platform stability and navigation flows.2 Years

2. Consent Control & Self-Determination

In compliance with Article 7.3 of the GDPR, SecureZZ guarantees easy revocation of consent at any time. The Company informs you that:

  • Proof Retention: An anonymized technical record of granted consent is retained to ensure traceability for legal audits.
  • Validity Period: Your analytics consent preferences expire 24 months after your last update, at which point a new choice will be requested.

For further information on the legal and technical use of trackers, you may consult the AEPD Guidelines & Tools.

You may revoke or modify your consent at any time using the configuration button below:

Absence of Automated Decision-Making

We inform you that SecureZZ does not use cookies or tracking technologies to build user profiles or for automated decision-making producing legal effects (Art. 22 GDPR).

Infrastructure Warning: If the Client forcibly blocks strictly necessary cookies, authentication and technical security mechanisms may not function properly, compromising access to services.

Technical documentation for client-side cookie management in major browsers:

  • Manage cookie policies in Google Chrome (Enterprise)
  • Strict tracking & cookie management in Mozilla Firefox
  • Cookie administration in Microsoft Edge