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 these first-party cookies on our own domain. You cannot switch them off in the service, but you can block them in your browser, and the service may then not work.
- sx_at and sx_rt (HttpOnly): keep you signed in.
- sx_csrf: protects your requests against cross-site forgery while you are signed in.
- sx_mfa (HttpOnly): holds a sign-in that is waiting for your second factor, for a few minutes.
- sx_oauth (HttpOnly): protects a Google or GitHub sign-in, for up to 10 minutes.
- sx_saml (HttpOnly): protects a single sign-on request, only on the sign-in path.
- sidebar_state: remembers whether the app's sidebar is open, for 7 days.
Your browser also keeps these on your device only: synlex-marketing-theme (your site theme) and synlex.project.(workspace) (the last project you opened) in local storage, and synlex.signup.draft and synlex.verify.unsent (an unfinished sign-up) in session storage.
4. Cookies and tools from other providers
We group the providers by what their cookies do:
- Strictly necessary: These are needed to run the service and keep it secure, for example to keep you signed in or to complete a payment. They do not need your consent.
- Functional: These remember your choices or supply a feature you asked for.
- Performance and analytics: These show us how the service is used and where it fails, so that we can improve it.
Strictly necessary
- Vercel Inc. hosts the site and serves it through its CDN. It sets no cookies on your device.
- InsForge stores our data on its servers and sets nothing on your device.
- Google Sign-In and GitHub: when you choose to sign in with them, they set their own cookies on their own sign-in pages, under their own policies. GitHub also reads connected repositories for scans, from our servers.
Functional
- No provider sets functional cookies. Our own sidebar_state cookie is listed in section 3.
Performance and analytics
- PostHog counts page views on our public marketing pages with a random ID kept in session storage (ssl-marketing-distinct-id), which is cleared when you close the tab. It sets no cookies.
- Sentry reports errors and performance problems and uses no cookies.
Our other providers, OpenRouter and Resend, work on our servers and set nothing on your device. Google Fonts serves the icon font our pages load; it receives your IP address and browser details and sets no cookies.
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.