Cookie Policy

SwiftSoft Labs LLC · Version 1.0.0, signed November 20, 2026 · Verify the signed release

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

Zenith sets four first-party cookies on its own domain, all HttpOnly. zenith_access_token and zenith_refresh_token keep you signed in. zenith_oauth_state and zenith_oauth_redirect protect sign-in with Google or GitHub and last 10 minutes.

Your browser also keeps, in local storage, your AI model choice (zenith:modelPreference) and your latest prompt (zenith:lastPrompt) until the app opens your project. It keeps, in session storage, the website generated on the home page (zenith:guestScaffold) and the progress of a checkout (zenith_checkout_open, zenith_checkout_needs_abandon, zenith_checkout_activating). Your browser clears session storage 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 for the service. Most of them set no cookies on your device through our site; the note under each group says which do. We set no advertising cookies.

  • 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

Google Sign-In and GitHub sign-in set their own cookies only on Google's and GitHub's pages, when you choose to sign in with them.

Functional

InsForge, OpenRouter and Vercel work on our servers and set nothing on your device through our site.

  • InsForge. Database (accounts, projects, chats, billing records) and sign-in emails. Data: Email address, name, account credentials, sign-in and session records, prompts, generated projects and chat messages, AI credit usage, billing customer ID. Location: United States. Agreement: https://insforge.dev/dpa
  • OpenRouter. AI gateway for chat, embeddings and image generation (routes to Google Gemini, OpenAI GPT or Anthropic Claude models by plan). Data: Prompts, chat history, generated website projects. Location: United States. Agreement: https://openrouter.ai/data-processing-agreement
  • Vercel. Hosting, builds and request logs. Data: IP address, browser user agent, request logs, all data the app serves. Location: United States. Agreement: https://vercel.com/legal/dpa

Performance and analytics

PostHog counts page views on our public marketing pages with a random ID (ssl-marketing-distinct-id) kept in session storage, and sets no cookies. Sentry error reports use no cookies.

  • PostHog. Anonymous page-view analytics on public marketing pages. Data: Usage analytics (page views, anonymous session-storage ID), IP address, browser user agent. Location: Not provided. Agreement: https://posthog.com/dpa
  • Sentry. Error and performance monitoring. Data: ip address, request bodies, request url path and query string. Location: United States. Agreement: https://sentry.io/legal/dpa/

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.