Cookie Policy

This Cookie Policy explains what Civlso stores in your browser, why, and what your options are. It's part of our Privacy Policy, not a replacement for it.

What we mean by "cookies"

Civlso does not set any cookies of its own. It uses your browser's local storage, session storage (cleared when the tab closes) and IndexedDB instead. These are small pieces of data saved on your device so the Service can remember who you are and how you left things. Most of them hold your own study work and never leave your device. Keys marked "per account" include your account ID, so two people sharing a browser keep separate copies.

Essential storage

Required for the Service to function. Blocking these will break sign-in and core features.

• sb-…-auth-token (local storage, set by Supabase): your signed-in session, so you don't have to log in on every page load. Sign-in may briefly store related Supabase keys.
• civlso_age_gate_ok_v1 (session storage): remembers that the age check was passed in this tab.
• civlso_age_gate_block_v1 (local storage): if the age check fails, blocks new sign-ups from this browser for 24 hours.
• civlso_plugin_session_v48:<plugin> (session storage): the ID of a metered plugin session, so reloading the page does not charge you twice.

Preference storage

Remembers choices you've made so you don't have to re-set them every visit.

• civlso-theme: your theme (Dark, Light, or Deep Space), shared by the website, app and these policy pages.
• civlso_lite_mode: Lite mode on or off.
• civlso_coach_everywhere_v21 and civlso_coach_nudge_v1: whether the floating Coach is shown and how often it nudges.
• civlso_intents_v1 (per account): your first-run answers to "What brings you to Civlso?".
• civlso.graphics.v1 and civlso.hydrocontrol.theme: graphics quality and theme in the games.
• civlso_research_v5_tour_seen and civlso_atlas_visibility_v2: Research Studio tour seen, and the Research Atlas view settings.

Your study work on this device

Not needed for sign-in, but this is where these tools keep your work. Clearing it deletes that work for good unless it is also on your account.

• FE Exam Studio: civlso_fe_history_v2 (your last 25 attempts), civlso_fe_exam_date_v1 (exam date), civlso_fe_handbook_v1 (handbook drill runs), civlso_fe_plan_v1 (today's plan and ticked blocks), civlso_fe_log_v1 (study log), civlso_fe_debrief_v1 (saved debriefs, up to 20). Nothing here is sent to Civlso.
• Learning: civlso_tracking_v16 (a copy of your learning activity, also synced to your account), civlso_read_progress_v17 (Read progress), civlso_coach_log_v1 (recent Coach sessions, which you can download), civlso_homework_v2 (homework), civlso_mistake_review_v1 (Mistake Library review state).
• Labs, games and videos: civlso_lab_workspace_v1, civlso_lab_thumbs_v2, civlso_lab_videos_v1, civlso_cad_survey_v2 (per account), civlso_game_progress_v1, each game's own progress key (for example civlso.loadpath.v1), civlso_video_progress_v1 and civlso_sightline_saved_v1 (per account).
• Research and reference: civlso_research_workspace_v5 (Research Studio workspaces, including imported CSV data; older civlso_research_workspaces_v17 is migrated), civlso_datum_v1 (Datum reading list, per account).
• Plugin OS: civlso_plugin_os_installed_v48, civlso_plugin_os_coach_note_v48, civlso_plugin_os_layout_v2 and civlso_plugin_os_workspaces_v2 (per account), civlso_plugin_state_v48 (per account and plugin), and the IndexedDB database civlso-plugin-store, which holds plugin documents, decks and workbooks. Some plugins also keep a recovery copy of unsaved work.
• Collaborate: civlso_collab_seat_v1 (the room you were last in, with its board, last 60 chat messages and the names of others, for up to 7 days), civlso_collab_recent_v1 (recent room codes), civlso_collab_removed_v1 (people a host removed, for 24 hours), civlso_collab_inbox_v1 (a deck passed from Deckspan, for one day).

Campaign attribution

• civlso_marketing_attribution_v1 and civlso_marketing_signup_pending_v1 (session storage): only if you arrive from a recognised Civlso campaign link. They keep the approved campaign, source, medium and creative identifier for up to 2 hours, so a sign-up can be credited to that campaign in our analytics. Not essential.

Analytics

We use Vercel Web Analytics on the website and in the app to understand overall traffic and usage patterns. It's designed to be cookieless: it doesn't set persistent tracking identifiers, doesn't build a profile of you individually, and doesn't track you across other websites. It's used to see aggregate numbers like how many people visited a page, and the campaign events described above.

Third parties

• Stripe: when you pay, you go to Stripe's checkout page, which sets its own cookies on Stripe's domain (for example for fraud prevention) under Stripe's policies.
• Google: if you choose "Continue with Google", Google's sign-in page uses its own cookies.
• Code hosts: jsDelivr, unpkg and cdnjs deliver code libraries. They receive your IP address but do not set storage in Civlso.
• Cloudflare Turnstile: built in but not switched on today. If we switch it on, it may use its own storage to tell people from bots, and we will update this policy.

What we don't use

Civlso does not use third-party advertising cookies, cross-site tracking pixels, ad-retargeting scripts or session recording. We don't sell or share browsing data with advertisers.

Managing storage in your browser

Most browsers let you view, block, or delete local storage and cookies through their settings. Because essential storage is required for sign-in, blocking it will prevent you from using most of the Service. Clearing your browser's storage will sign you out and delete the device-only work listed above, including your FE study plan, log, debriefs and history. To keep a copy first, use "Download my data" in Profile, then "Profile & privacy": it includes the local storage keys on that device that begin with "civlso". Plugin documents in civlso-plugin-store are not included, so download those from the plugin itself.

Changes

We may update this policy as the tools we use change. We'll revise the date above when we do.