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
Vibe sets no cookies and uses no analytics or advertising tracking, so the app has no consent banner. It keeps only the items it needs to run, such as keeping you signed in or completing a payment, and those are set without a separate choice. Our Cookie Policy lists them.
3. Cookies we set without a choice
The sign-in, checkout and app storage items listed in our Cookie Policy, kept on your phone.
Google Sign-In. Data: Google account ID, email address and name (from the Google ID token). Location: United States. Agreement: https://business.safety.google/processorterms/ Google may use its own cookies on its sign-in screen.
4. Cookies that depend on your choice
None. Vibe sets nothing that depends on your choice.
Sentry. Data: Error and crash reports: stack traces, device, OS and app details, request URL and IP address. Location: United States. Agreement: https://sentry.io/legal/dpa/ Sentry receives crash and error reports to keep the app working and sets no cookies.
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 14:49:56 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.