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

Fareburn sets these first-party cookies on its own domain. They are Secure and HttpOnly, so scripts on the page cannot read them.

  • fb_access_token and fb_refresh_token keep you signed in. They are removed when you sign out.
  • fb_oauth_state and fb_oauth_redirect are set when you sign in with Google. They protect that sign-in, return you to the page you came from, and last 10 minutes.

Fareburn also keeps these items in your browser's local storage, on your device:

  • fareburn:intent:plan remembers the plan you picked before signing up, so checkout can open after you sign in.
  • fareburn:settings:phone, fareburn:settings:notifications and fareburn:settings:loyalty, each followed by your user ID, keep the phone number, notification choices and loyalty programs you enter in Settings on this device only. Deleting your account clears them.

You cannot switch these off in the service, but you can block or delete 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.

Strictly necessary

  • Google Sign-In: when you choose Continue with Google, Google sets its own cookies on Google's pages, under Google's policy.

Functional

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

Performance and analytics

  • PostHog: counts page views on our public pages with a random ID kept in your browser's session storage under ssl-marketing-distinct-id, which is cleared when you close the tab. It sets no cookies.
  • Sentry: sends error and performance reports without 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.

Legal Center · Questions? See Legal Contact.