This policy is from SwiftSoft Labs LLC ("we", "us"). It explains which cookies and similar tools need a choice from you, and how you change that choice.
Our Cookie Policy lists the same providers and what each one does.
2. The choices this policy covers
Continuum sets only the cookies and browser storage it needs to keep you signed in and to finish checkout. Our Cookie Policy lists them. PostHog counts page views with a random ID in your browser's session storage, not a cookie. We set no analytics or advertising cookies, so there is no consent banner.
You can block or delete cookies and browser storage in your browser.
3. Cookies we set without a choice
`continuum_at`, `continuum_rt` and `continuum_oauth_state`: first-party, HttpOnly cookies that keep you signed in and protect sign-in with Google.
The checkout keys in session and local storage listed in our Cookie Policy.
Google Sign-In: Google sets its own cookies on Google's pages, under Google's policy, only when you choose to sign in with Google.
4. Cookies that depend on your choice
None. We set no analytics or advertising cookies.
PostHog counts page views with a random ID kept in your browser's session storage, which is cleared when you close the tab. It sets no cookies.
Sentry sends error reports without cookies.
InsForge, OpenRouter and Vercel work on our servers and set nothing on your device through our site.
5. How to change your choice
You can block or delete cookies in your browser settings. Blocking a cookie the service needs may stop that part of the service from working.
Each browser explains how to delete cookies in its help pages.
6. Changes and contact
We may update this policy. Questions go to legal@swiftsoftlabs.com. Our address is 312 W 2nd St, PO Box 5309, Casper, WY 82601.
Check these documents
Checking the signature in your browser…
Your browser computes the SHA-256 of each document on this page and compares it with the hash in the signed release manifest.
DigiCert, Inc. timestamped the manifest hash at Fri, 20 Nov 2026 12:13:43 GMT. Synlex checked the authority's signature, the hash, and its certificate chain to DigiCert Trusted Root G4, a root pinned in Synlex. To check the token yourself, download it from the footer and run:
The JSON API publishes the signed manifest bytes and the signature; the keys file publishes synlex-1's public key and its window. Then check that the manifest's signedAt falls inside that window and that its document hashes match the documents.