Version 2.0.0, effective 19 November 2026. Signature verified with key synlex-1.
Cookie Policy
1. What cookies are
Cookies are small files that a website stores on your device. Similar technologies, such as local storage and pixels, do the same job. This policy covers all of them.
A first-party cookie is set by us. A third-party cookie is set by a provider that supplies a tool to us.
2. Who sets them
SwiftSoft Labs LLC ("we", "us") sets the cookies that run the service. The providers listed in section 4 may also set cookies or read data from your device when they supply their tool to us.
3. Cookies we need
We use cookies and similar technologies that the service needs to work and to stay secure, for example to keep you signed in. You cannot switch these off in the service, but you can block them in your browser, and the service may then not work.
4. Cookies and tools from other providers
PostHog (product analytics): no cookies unless you accept analytics; see our Cookie Consent policy.
Vercel Speed Insights and Sentry: measure performance and errors without cookies.
Our other providers (Google, InsForge, OpenRouter, Hetzner) work on our servers and set nothing on your device. Google sets its own cookies only on Google's pages, when you choose to sign in with Google.
5. Your choices
You can block or delete cookies in your browser settings. Blocking them may stop parts of the service from working. Each browser explains how in its help pages.
6. How long cookies last
A session cookie is deleted when you close your browser. A persistent cookie stays on your device until it expires or you delete it. The lifetime of a provider's cookie is set by that provider and is described in its own policy.
7. Changes and contact
We may update this policy. Questions go to info@swiftsoftlabs.com.
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 Thu, 19 Nov 2026 10:24:21 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.