Swvle Cookie and Browser Storage Policy
Effective November 6, 2026
The names, lifetimes, and write timing below are taken from the application. Cookies are host-only: the application does not set a Domain attribute, so each cookie applies only to the host that set it. localStorage and sessionStorage follow the origin of the document that writes them. There is no separate cookie-preference center.
1. About this policy
Swvle, Inc. (Swvle) uses, or may use depending on the active service configuration, cookies and related technologies to operate its website, account portal, and hosted SuperFan AI services. A cookie is a small piece of data a website stores in a browser. Similar technologies include localStorage, sessionStorage, pixels, SDK identifiers, and other browser or device identifiers. These technologies differ in duration, scope, and purpose.
This policy supplements our Privacy Policy. It distinguishes Swvle-operated properties from Customer-deployed SuperFan experiences because the Customer generally controls the privacy and consent requirements of its own website, while Swvle provides the underlying hosted technology.
2. Categories of browser technologies
| Category | Illustrative purpose | Consent considerations |
|---|---|---|
| Strictly necessary | Sign-in state, security, load balancing, checkout, session integrity and requested service operation | Often exempt from consent where the applicable legal test is met; notice may still be required |
| Functional / preferences | Language, display preferences, or remembering a selected experience | Depends on the specific functionality, duration and jurisdiction |
| Analytics and performance | Measuring visits, errors, feature use and service performance | May require consent or another legally permitted mechanism depending on implementation and location |
| Marketing and advertising | Attribution, advertising pixels, retargeting, cross-site measurement | Frequently subject to prior consent or opt-out requirements, depending on applicable law |
Cookie categories alone do not establish the lawful basis for a given technology. A first-party cookie is not necessarily exempt, and storage set by an embedded third-party script can still be subject to a website operator's notice and consent duties.
3. Our website and dashboard
The marketing site, account pages, and administrative dashboard use the cookies and storage in section 5 for sign-in, language, theme, navigation, billing, and measurement.
Google Analytics loads on Swvle pages, including the marketing site and embedded chat documents, when a measurement ID is configured. The script is Google's gtag.js. It writes first-party _ga and _ga_<measurement id> cookies on the Swvle host when the page loads. The application does not wait for a consent choice before loading that script.
Stripe.js loads on the workspace billing payment form. Stripe Checkout runs on Stripe's site. Stripe sets its own fraud-prevention cookies; Swvle application code does not name them. Stripe documents __stripe_mid (about one year) and __stripe_sid (about 30 minutes).
4. Customer-embedded SuperFan experiences
Bubble and Inline both insert an iframe as soon as the host page runs the embed script. That iframe is a Swvle document. On that load, before the visitor opens a Bubble panel or sends a message, the iframe writes the swvle: visitor ids in section 5 (anonymous-id and visit-id) in localStorage on the Swvle origin. A standalone SuperFan page writes the same keys when the page loads. The marketing homepage writes them when a live SuperFan is mounted in the hero.
The embed script writes one key on the customer's origin, and only when auto-open is enabled: sessionStorage key swvle:embed:auto-opened:<channel id>. The script reads it on load. It writes 1 when that auto-open actually opens the panel. The value lasts for the browser tab.
The deploying Customer is responsible for the privacy notice and any consent mechanism on its own website. Storage inside the Swvle iframe is on Swvle's origin. Swvle does not provide a consent signal that delays the iframe or Google Analytics.
5. Inventory
| Key | Where | Purpose | Lifetime | When it is written |
|---|---|---|---|---|
swvle.* | Cookie on the Swvle host. Path /, SameSite Lax. Some are HttpOnly. | Language, sidebar layout, a signup access code, and a consumer referral | 10 minutes, 7 days, 1 year, or the browser session, depending on the cookie | When that preference, signup, or invite step happens |
_ga, _ga_<measurement id> | Cookies on the Swvle host, written by Google Analytics | Distinguish browsers and measure visits | 2 years | On load, when a measurement ID is configured, before any click |
__Secure-better-auth.session_token | Cookie on the Swvle host. HttpOnly, Secure, SameSite Lax, Path /. On a non-HTTPS host the name is better-auth.session_token and Secure is off. | Signed-in session | 7 days | After a successful sign-in |
swvle:* | localStorage on the Swvle origin | Theme, last sign-in method, dismissed prompts, sign-up handoff, and SuperFan visitor continuity (anonymous-id, visit-id) | Until the visitor clears site data. The visit id changes after 30 minutes without activity. | Visitor ids when a SuperFan mounts, including when an embed loads before the panel opens. Other keys when the visitor sets a preference, dismisses a prompt, or starts sign-up. |
swvle:* | sessionStorage on the Swvle origin | Embed sign-in token, a dismissed legal notice or billing banner, and an email held during invite sign-up | Browser tab | When that sign-in, dismissal, or sign-up step happens |
swvle:embed:auto-opened:<channel id> | sessionStorage on the customer website | Avoid auto-opening the Bubble again in the same tab | Browser tab | When auto-open is enabled and the panel opens |
__stripe_mid, __stripe_sid | Stripe.js on the billing payment form, and Stripe Checkout on Stripe's site | Payment fraud prevention | About 1 year and about 30 minutes, as documented by Stripe | When the payment form or Checkout is used |
Every app-owned cookie starts with swvle.. A cookie name cannot contain :. Every app-owned browser-storage key on the Swvle origin starts with swvle:. A legacy theme key, swvle_theme_preference, is copied once into swvle:theme-preference and removed. Older app cookie names are copied once into the swvle. name and removed.
6. Your choices
Browsers can block or delete cookies and site storage. Blocking the sign-in cookie, the embed sign-in token, or the visitor identifiers can interrupt sign-in or a SuperFan session.
Swvle does not currently offer a cookie-preference control. Google Analytics is not held until a consent choice. To stop analytics cookies, use the browser's controls or a browser extension that blocks Google Analytics.
For a SuperFan on another organization's website, that organization's notice covers its own cookies. The Swvle iframe still uses the Swvle-origin storage in section 5. In applicable U.S. states, advertising or targeted-advertising opt-outs belong to the site operator that engages in those practices. This application does not set advertising or retargeting cookies of its own.
7. Changes and contact
We may update this Policy as the browser technologies, legal requirements, or services change. We will change the effective date and provide additional notice where required.
Swvle, Inc.
privacy@swvle.com