Cookie Preferences
Last updated: September 13, 2026. This revision is effective immediately.
About cookies on this website
Cookies are small text files a website stores on your device to remember preferences or measure how the site is used. On brilliant.design we keep our cookie usage to a minimum, and we group what we do use into two categories so you can decide what to allow.
For context on how this fits into our broader data practices, see our Privacy Policy.
Strictly necessary
Required for the Website to function: for example, to remember the cookie preferences you set on this page. These are always on and can't be switched off.
Analytics
Help us understand how visitors use the Website in aggregate: which pages are read, how navigation flows, where people drop off. We use Google Analytics 4. No advertising or cross-site tracking.
Cookies we actually set
The table below lists every cookie placed by us on this Website and the Platform when the relevant category is enabled. Cookies that are not in this list are not placed by us; third-party services loaded on specific pages (listed further down) may place their own.
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
| brilliant_cookie_consent | brilliant.design | Stores your cookie preferences so this banner doesn't reappear on every visit. Saved in your browser's localStorage. | Until cleared | Strictly necessary |
| brilliant_session | brilliant.design | Keeps you signed in to the Platform. Set only when you sign in. Contains a random identifier (we store only a hash of it), is not readable by scripts (HttpOnly), and is sent only over HTTPS. Deleted when you sign out. | 30 days | Strictly necessary |
| Error & reliability monitoring | brilliant.design | Reports uncaught errors, the path patterns of failed requests, a small set of reliability signals (whether checkout opened or failed, whether a plan upgrade activated, whether your browser can run the editor, and which upgrade prompts were shown), and anonymous page views so we can fix a broken page or purchase and see which pages get used. Tagged with the random brilliant.installId identifier (listed below), the app version, the platform, a route class, and coarse context: the referring site's domain only (never the full address), any campaign tags in the link you arrived from, and a coarse device profile (window size and operating-system family). It never sends page content, design content or full URLs, is rate-limited, and runs regardless of your cookie choice. | No cookie set | Strictly necessary |
| _ga | Google (Google Analytics) | Assigns a pseudonymous client ID used to distinguish unique visitors. | 2 years | Analytics |
| _ga_BB78EDH424 | Google (Google Analytics) | Persists session state for our specific GA4 property. | 2 years | Analytics |
Google Analytics is loaded only after you opt in on this page (or via the banner). If you opt out, it is not loaded and no analytics cookies are set.
Third-party services on specific pages
A small number of pages load third-party services that may set their own cookies, under their own privacy policies: the pages where a purchase can start (the pricing pages, your account and team settings, the new-team page and the in-app checkout) load Paddle's checkout script when you reach for checkout (Paddle is our merchant of record; the script is required to start a purchase, so it is strictly necessary at the point of use), and the demo-booking page embeds Cal.com's scheduler (required for the booking function of that page). They load only where they are needed, not at page load. Paddle's script can also load ProfitWell, a Paddle retention-analytics service. That side-load is not required for checkout, and we gate it behind the Analytics consent category: ProfitWell is loaded only if you have accepted analytics cookies here or via the banner. Paddle checkout itself works either way.
Browser storage we use (not cookies)
Beyond cookies, the Website and the web editor keep some data in your browser's local storage. This data stays on your device, is not sent to us as tracking, and you can clear it at any time via your browser's site-data settings. The notable entries:
- brilliant_cookie_consent stores your cookie choice (see above).
- brilliant.installId is a random identifier for this browser. It is used for anonymous error and usage reporting, and it also identifies this installation for the purposes of the anonymous Brilliant AI allowance you can use before signing in. If you use that allowance before signing in and then sign in, the allowance granted to this installation is merged into your account once, and from that point the identifier relates to you. It is not used for advertising or cross-site tracking.
- com.brilliant.credentials:* holds the AI provider API keys you add in the web editor (your own AI). Your keys stay in your browser and are sent only to the provider you connected, never to our servers. Brilliant AI uses no key of yours.
- bn.* entries cache pages you visited (your profile, explore, project snapshots) so they load instantly next time. They are cleared when you sign out.
- com.brilliant.config:* and flutter.AppThemeMode store web editor preferences such as theme.
- A few short-lived sessionStorage entries carry state across a page navigation (for example, a new-project seed or a Figma import draft) and are cleared when read or when the tab closes.
You haven't set your preferences yet. to clear your stored choice and bring the banner back.
You can also disable cookies via your browser's settings at any time. For more detail on how we process personal information overall, see our Privacy Policy.