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 set three first-party cookies on our own domain. All are Secure and HttpOnly.
- `liteai_access_token` and `liteai_refresh_token` keep you signed in.
- `liteai_oauth_state` protects sign-in with Google or GitHub. It lasts 10 minutes.
Your browser also keeps:
- In local storage: `liteai_theme`, `liteai_ghost_mode`, `liteai_onboarding_completed`, `liteai_heavy_mode`, `liteai_heavy_model_id` and `liteai_install_dismissed`, which remember your theme, Ghost Mode, onboarding, model choice and whether you closed the install prompt.
- In session storage: `liteai_pending_send:` followed by a chat id, which holds a message while it is being sent, and `kelviq_checkout_session_id` while a checkout is in progress. Both are cleared when you close the tab.
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
We group the providers by what they do on your device:
- Advertising: Google AdSense and Google Ads. AdSense and the Google Ads tag load only when advertising is switched on. The Google Ads tag starts with Google consent mode denying ad storage, ad user data, ad personalisation and analytics storage, and we ask AdSense for non-personalised ads. If you are signed in and choose Accept when the app asks whether ads may be personalised, ad storage, ad user data and ad personalisation are granted. Analytics storage stays denied. Google may set its own cookies under its policy.
- Performance and analytics: PostHog counts page views on our public marketing pages with a random ID kept in session storage (`ssl-marketing-distinct-id`), and sets no cookies. Sentry sends error reports and sets no cookies.
- Sign-in: Google Sign-In and GitHub OAuth set their own cookies only on Google's and GitHub's pages, when you choose to sign in with them. Our own `liteai_oauth_state` cookie, listed under "Cookies we need", protects that sign-in.
- On our servers: InsForge, OpenRouter and Vercel work on our servers and set nothing on your device through our site.
Our Privacy Policy lists what each provider receives, where it is, and its data processing agreement.
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 legal@swiftsoftlabs.com.