1. Architectural Overview
Under the EU ePrivacy Directive and European data protection law, websites must transparently disclose the nature, purpose, and duration of all client-side storage technologies.
INNOSPHIRE employs minimal, functional-only cookies and local storage tokens designed strictly to deliver user interface settings, interactive campaign simulation state, and secure Stripe checkout flows.
3. LocalStorage & Session Tokens
To ensure high-performance rendering without repetitive server roundtrips, INNOSPHIRE utilizes client-side localStorage and sessionStorage for:
sov_haptics_pref: Stores user audio/haptic feedback toggle preferences (sound ON/OFF);innosphire_simulator_state: Preserves your active creator selection in the interactive GMAX Campaign Simulator;sov_lead_id: Ephemeral lead identifier generated during intake submission to allow instant dossier rendering.
4. Attention Telemetry Engine (sov_beacon.js)
Our frontend employs an in-house Attention Telemetry HUD (sov_beacon.js). This script measures anonymized viewport dwell time, saccadic scroll speed, and creator card engagement to calculate Attention Capture Index (ACI) benchmarks.
Zero PII Association: Telemetry beacons are decoupled from IP addresses and personal identifiers. They are mathematically processed in aggregate to benchmark hook velocity.
5. Managing Preferences & 1-Click Purge
You can purge all INNOSPHIRE client-side tokens from your browser at any time by clicking the button below:
For inquiries regarding cookies or tracking compliance, contact: privacy@innosphire.com.