This policy explains how DigiSim Technology Ltd uses cookies and similar storage/access technologies on digisim.io, the DigiSim Museum and the DigiSim web application.
It covers browser cookies, localStorage, sessionStorage and IndexedDB. These technologies are regulated even where a stored value does not directly identify you.
We use necessary technologies to provide features you request. Google Analytics is our only current optional analytics purpose and is loaded only after consent. We do not use advertising cookies or pixels and do not sell personal information.
Technologies Covered
A cookie is a small value a website asks a browser to store and return. localStorage keeps key-value preferences, sessionStorage normally lasts for one browser tab, and IndexedDB stores structured data such as local circuits or Firebase sign-in state. In this policy, "storage technologies" covers all of them.
Why We Use Them
Necessary storage remembers your language and privacy choice, keeps you signed in, protects sessions, restores local projects, displays the correct plan, and preserves settings you request. With consent, Google Analytics helps us understand aggregate audience and feature use so we can improve the Service. Analytics consent is not required to use DigiSim's core features.
Necessary, Preference and Analytics
Necessary technologies support security, authentication, billing state and requested local features. Preference technologies remember choices such as language, theme or sound. Analytics technologies measure use and are optional. Because analytics is the only current non-essential purpose, the banner offers equally accessible "Accept analytics" and "Reject analytics" choices rather than presenting artificial categories.
Providers and External Sites
Google supplies Firebase Authentication and Google Identity Services for sign-in, including the official Google button and One Tap on selected pages. Firebase App Check and reCAPTCHA Enterprise help protect requests against automated abuse and can run on public pages before you sign in or make an analytics choice. They are separate from Google Analytics, which loads only after analytics consent. Cloudflare delivers pages and assets and processes network-security and request information. Google-hosted fonts receive the connection information needed to serve fonts; this is not Google Analytics. Stripe may store security and checkout values on Stripe-hosted pages when you choose to purchase or manage billing. Our contact form opens Google Forms. The Privacy Policy identifies these recipients and links to provider notices. DigiSim does not currently deploy Meta/Facebook Pixel, advertising-network cookies, session recording, Hotjar or Microsoft Clarity.
Current Storage Inventory
Names generated by a browser SDK can vary by project or version. The entries below describe the values DigiSim code currently creates or asks the listed provider to create.
| Name / storage | Purpose | Duration | Category |
|---|---|---|---|
| digisim_lang (cookie) | Remembers the selected language across DigiSim pages. | 1 year | Preference |
| digisim_theme (cookie) | Remembers the selected light or dark theme across DigiSim pages. | 1 year | Preference |
| digisim_cookie_consent + timestamp (localStorage) | Records whether analytics was accepted or rejected and when the choice was made, so the banner and scripts respect it. | Until changed or browser data is cleared | Necessary |
| Firebase Authentication records (IndexedDB; SDK-generated names) | Restores and protects the signed-in state and authentication tokens on the device. | Until sign-out, account deletion or browser-data clearing | Necessary |
| _grecaptcha (localStorage) and Firebase App Check records (SDK-managed browser storage) | Supports automated-abuse detection and request verification. Security code can run on public pages independently of analytics consent. | Local values remain until the provider updates or removes them, you clear site data, or the browser evicts them; verification tokens have provider-managed expiry and refresh. | Security — separate from optional analytics |
| Local circuit databases and draft keys (IndexedDB/localStorage) | Autosaves projects and drafts on the device so a lab can restore work without uploading it. | Until you delete the project, clear site data or the browser evicts it | Requested feature |
| planInfo, userState and entitlement/profile caches (localStorage) | Displays the current account and plan while the authoritative account state is refreshed. | Until refreshed, sign-out or browser-data clearing | Necessary |
| Language, theme, sound and simulator preferences (localStorage) | Restores interface and lab choices made on the device. | Until reset or browser data is cleared | Preference |
| Temporary navigation/workspace values (sessionStorage) | Carries requested navigation or unsaved workspace state within the current tab. | Browser-tab session | Necessary / requested feature |
| _ga (cookie; Google Analytics) | Distinguishes browsers for consent-based audience and usage measurement. | Up to 2 years | Analytics — consent required |
| _ga_<container-id> (cookie) and digisim_analytics_purchase_ids (localStorage) | Maintains consent-based Google Analytics session state. The localStorage entry prevents repeated reporting of a verified purchase and contains at most 100 order references and expiry times, without checkout session IDs, payment details or circuit content. | Google Analytics cookie: up to 2 years, subject to provider/browser controls. Local order references: used for up to 30 days; removed on the next consented purchase after expiry, when consent is withdrawn, or when site data is cleared. | Analytics — consent required |
| Stripe-hosted checkout and billing storage (on stripe.com) | Payment security, fraud prevention, checkout, invoices and customer-portal operation after you choose a billing action. | Set by Stripe for the stated security or billing purpose | Third-party necessary on Stripe pages |
Your Choices
The first DigiSim visit presents equally prominent options to accept or reject analytics. Necessary storage is used without analytics consent only where it is required to deliver a requested feature, secure the Service or remember the privacy choice. Use "Cookie Settings" in the footer at any time to change the analytics choice; withdrawing consent stops future analytics loading and may reload the page to remove an already loaded script.
Browser controls can delete or block cookies and site storage. Clearing Firebase storage signs you out; clearing local project databases or drafts can permanently remove work that was never cloud-saved or exported. Blocking all storage may prevent authentication, local autosave and preferences from working. You can also use Google's browser controls or opt-out tools, but DigiSim's own Reject choice is sufficient for DigiSim analytics.
Personal Information and International Transfers
Some identifiers in authentication, analytics or Stripe-hosted checkout can be personal information. Our Privacy Policy explains the lawful bases, recipients, retention criteria and rights that apply to that processing.
Providers may process information outside the United Kingdom. The destination and lawful transfer mechanism depend on the provider and service. Our Privacy Policy explains the possible mechanisms and how to ask about the safeguard relevant to your information. Acceptance of this policy is not consent to an international transfer.
Changes to This Inventory
We update this policy when a storage purpose, provider or duration materially changes. A new non-essential purpose will not be enabled under an old analytics choice unless that choice fairly covers it; where required, we will ask again. The revision date above identifies the current inventory.
Contact Us
Contact us if a technology appears that is not described here or if you have a question about your choice.
DigiSim Technology Ltd · Company no. 16962306 · Registered in England and Wales
Office 16555, 182–184 High Street North, East Ham, London, E6 2JA, United Kingdom