Cookies Policy
Effective Date: 24 March 2026
Controller: SVX BETA LTD, 3 Hill Street, Edinburgh, EH2 3JP, United Kingdom
1. Overview
This Policy explains how SoapVox uses browser-based storage technologies during the Open Beta. It applies only to the SoapVox platform.
Our separate public website may use standard cookies; these operate independently and never receive Platform data.
SoapVox does not use cookies or LocalStorage for tracking, analytics, profiling, or advertising.
2. What Technologies We Use
SoapVox does not set traditional tracking cookies in the Platform.
The Platform uses:
• LocalStorage - persistent key–value storage used only for short-lived technical data required for session continuity
• SessionStorage - temporary memory used for real-time UI state
• Strictly necessary authentication cookies (for example, secure HttpOnly session tokens) used to maintain an active login session
LocalStorage may hold limited non-sensitive values for access gating and basic UI behaviour.
For example:
• beta access gating values (for example, an access flag and timestamp), and
• simple UI counters (for example, skip count).
These values:
• contain no stance, country, or political-opinion data,
• contain no real-world identifiers such as emails or handles,
• do not create user profiles,
• are not shared with third parties, and
• may be cleared automatically by the Platform when temporary access expires or when a new session begins.
SessionStorage may temporarily hold identifiers used by the interface to maintain the active session state.
We do not use:
• analytics cookies,
• advertising cookies,
• fingerprinting,
• cross-site identifiers, or
• behavioural tracking tools.
Storage Controls
LocalStorage is never used to store stance, country, or political-opinion data. SessionStorage may temporarily hold stance or the currently displayed topic solely as transient in-session UI state and is cleared when the session ends. No real-world identifiers are stored in browser storage.
3. What May Be Stored
The following values may be stored on your device to support the Platform interface during the beta.
• access gating values (for example, an access flag and timestamp), and
• basic UI state and counters required for navigation and live interface operation (for example, skip count)
These values:
• do not include stance, country, or political-opinion data,
• do not include any emails, handles, or real-world identifiers,
• do not connect to moderation or server logs,
• do not track behaviour or build cross-session history, and
• expire when the login session ends, or the browser session ends
4. SessionStorage (Short-Lived State)
SessionStorage may temporarily hold:
• temporary pseudonymised session identifiers
• the currently displayed discussion topic required for live UI rendering,
• temporary identifiers used for navigation and real-time interface updates, and
• display assets needed for the live preview interface.
SessionStorage:
• is cleared automatically when the tab closes or the browser session ends,
• is never written to LocalStorage for long-term storage,
• does not include country or real-world identifiers, and
• is used only to operate the live interface.
5. What We Never Store
• stance (political label) beyond transient in-session UI state
• country
• topic–session associations beyond transient in-session UI state on the user’s device
• real-world identifiers (emails, handles, usernames)
• long-term or cross-session identifiers
• preferences revealing political data
• any authentication credentials that would allow access to a user’s external accounts or third-party services
This section applies only to data stored on the user’s device (for example via cookies, LocalStorage, or SessionStorage) and does not describe server-side processing or logging, which is covered in the Privacy Policy and Terms of Use.
Political-opinion data is never stored persistently on the user’s device and exists only as transient in-session UI state.
6. Why These Technologies Are Used
LocalStorage and SessionStorage are used solely to support the operation of the interface by:
• maintaining temporary session data required to keep your session active
• preserving UI state if a tab refreshes
• enabling temporary preview-card display
• supporting essential real-time interface functions
None of this creates profiles, tracks behaviour, or builds history.
7. Information Site Cookies (Separate Website)
Our public website (separate from the Platform) may use:
• basic site-function cookies
• performance/load-balancing cookies
• form/session cookies
These website cookies:
• never receive stance, topic, country, snapshots, or login data
• never interact with Platform processing
The Platform does not use cookies for tracking, advertising, or analytics. Any storage used is strictly necessary for the operation of the service.
8. Managing Storage
You may clear LocalStorage, SessionStorage, and cookies at any time through your browser settings.
Clearing storage will:
• remove temporary Platform data
• reset interface/UI state
• may require re-authentication if your login session has expired or if temporary storage is cleared
This does not affect your rights under the Privacy Policy or the short-term server logs used for safety (e.g., IP/session logs retained for 28 days).
9. Updates
We may update this Policy to reflect changes in the Platform or legal requirements.
Latest versions are published at: info.soapvox.live/legal/cookies-policy
10. Contact
For questions about this Policy or other data-protection matters: privacy@soapvox.live