Version 1.0.0, effective 20 November 2026. Signature verified with key synlex-1.
Cookie Consent and Tracking Preferences
1. Who this policy is from
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
Fortress sets only the cookies and browser storage it needs to sign you in, keep your account secure and finish checkout. Our Cookie Policy lists them. It sets no analytics or advertising cookies, so there is no consent banner.
You can block or delete cookies in your browser.
3. Cookies we set without a choice
`ft_access`, `ft_refresh`, `ft_mfa_pending` and `ft_oauth_state`: first-party, HttpOnly cookies that sign you in and keep your account secure.
The `fortress_checkout_` entries in session storage, which bring you back to the right screen after checkout.
Google Sign-In: Google sets its own cookies on Google's pages, only when you choose to sign in with Google.
4. Cookies that depend on your choice
None. PostHog counts page views on our public pages with a random ID kept in session storage, and sets no cookies. Sentry error reports use no cookies. Our other providers (Apify, Google, InsForge, OpenRouter and Vercel) set no analytics or advertising cookies 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:16:08 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.