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
CodeRunner sets four first-party cookies on its own domain, all HttpOnly. `cr_access_token` and `cr_refresh_token` keep you signed in. `cr_oauth_state` and `cr_oauth_redirect` protect sign-in with Google and last 10 minutes.
Your browser also keeps, in session storage, the progress of a checkout (`coderunner_checkout_open`, `coderunner_checkout_needs_abandon`, `coderunner_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 sets its own cookies only on Google's pages, when you choose to sign in with Google.
- Google Sign-In. Sign in with Google (OAuth). Data: Google account ID, email address, name, IP address, browser user agent. Location: United States. Agreement: https://business.safety.google/processorterms/
Functional
InsForge, OpenRouter and Vercel work on our servers and set nothing on your device through our site.
- InsForge. Database, transactional email (verification and reset codes) and the compute worker that verifies submitted runs. Data: Account, profile, sign-in logs (IP, user agent), runs, prompts, code, replays, billing customer ID and status, email address. Location: United States. Agreement: https://insforge.dev/dpa
- OpenRouter. AI gateway for the in-run coding agent, routing to Google Gemini 2.5 Flash-Lite. Data: Prompts (up to 2,000 characters), the run's chat history and the current code. Location: United States. Agreement: https://openrouter.ai/data-processing-agreement
- Vercel. Hosting the web app and running its server routes. Data: IP address, browser details, URLs and the content of requests to the app. Location: United States. Agreement: https://vercel.com/legal/dpa
Performance and analytics
PostHog counts page views on public pages such as the home page 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 the public home page. Data: Page URL, a random session ID kept in session storage, IP address and browser details. Location: United States. Agreement: https://posthog.com/dpa
- Sentry. Error and performance monitoring for the web app and its server routes. Data: IP address, request URL path and query string, request bodies, browser details, error traces. Location: United States. Agreement: https://sentry.io/legal/dpa/
The screen recording of a run (the replay) is made by CodeRunner itself during the run and sent to our own servers. It 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.