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
The Ghost is a mobile app. It sets no cookies and uses no analytics, advertising or tracking tools, so it asks for no consent choice and shows no tracking prompt. It keeps only the on-device items it needs to run, which our Cookie Policy lists.
3. Cookies we set without a choice
The sign-in items in the iOS Keychain or Android Keystore (`ghost_access_token`, `ghost_refresh_token` and `ghost_user`), the setup items in the app's local storage (`@ghost/onboarded` and `@ghost/onboarding_profile`), and cached copies of voice commands. InsForge, OpenRouter and Vercel run on our servers and set nothing on your device. Kelviq's checkout opens in your browser under Kelviq's own policy.
4. Cookies that depend on your choice
None. No provider we use (InsForge, OpenRouter or Vercel) sets optional cookies or tracks you through the app.
5. How to change your choice
There is no optional tracking to change. Deleting the app removes what it keeps on your device. You can delete cookies that Kelviq sets in your browser in your browser settings.
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 14:44:39 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.