Cookie Policy
Which cookies and similar technologies Busabase Cloud uses, what each one does, and how to control them.
Effective Date: August 12, 2026
Last Updated: November 3, 2026
This Cookie Policy explains how AI Organizer Company ("Busabase," "we," "us," or "our") uses cookies, local storage, and similar technologies on Busabase Cloud (the "Service"). It supplements our Privacy Policy.
1. What Cookies Are
A cookie is a small text file that a website stores on your device. It lets the site recognise your browser between requests — for example, to keep you signed in. We also use local storage, a related browser mechanism that keeps small preferences on your device without sending them to our servers on every request.
2. Cookies We Set
These are set by Busabase itself and are required for the Service to work or to remember your choices.
| Name | Type | Purpose | Retention |
|---|---|---|---|
better-auth.session_token | Essential | Keeps you signed in and identifies your session. Without it you cannot access a workspace. | 7 days |
better-auth.csrf_token | Essential | Protects sign-in and account forms against cross-site request forgery. | Session |
webpage_lang | Preference | Remembers whether you chose English, 简体中文, or 日本語, so you land on the right language next visit. | 1 year |
busabase_attr | Analytics | Remembers how you first arrived: a format version, capture time, normalized UTM source, medium, campaign and content labels, the path of the first page you visited, the name of an ad click parameter, and the external referring hostname. Never full referring URLs, query strings, or click parameter values. Shared across busabase.com subdomains. At signup we keep a channel label and these details on your new account to understand which channels work. Later sign-ins do not change it. Blocking it does not affect signup. It follows your choice in Cookie settings: where we ask first, it is not written unless you accept, and declining removes it. | Up to 30 days from first capture; later visits do not extend it |
busabase_signup_conversion | Advertising | Set once, on the response that completes your signup (a verified email address, or an account created through a sign-in provider such as Google or GitHub). Holds a one-way hash of your new account's id, used only as a de-duplication id so the advertising partners in Section 4 count your signup once. It contains no email address or account id. Shared across busabase.com subdomains. Our ad tags read it on the next page and delete it. Not set if you declined analytics and advertising, or, where we ask first, before you accept. | Until it is read; at most 1 day |
theme (local storage) | Preference | Remembers light or dark mode. Stored on your device only; never sent to our servers. | Until cleared |
Essential cookies do not require consent because the Service cannot be provided without them. If you block them, you will not be able to sign in.
3. Third-Party Analytics
We use two analytics providers to understand, in aggregate, which pages people use and where the product is confusing. They set their own cookies on our domain.
| Provider | Cookies | Purpose | Retention |
|---|---|---|---|
| Google Analytics (Google LLC) | _ga, _ga_* | Distinguishes visitors and sessions to produce aggregate traffic and page reports. | Up to 2 years |
| Microsoft Clarity (Microsoft Corporation) | _clck, _clsk, CLID | Aggregate usage metrics and heatmaps showing which parts of a page people interact with. | Up to 1 year |
We do not sell the data they collect. Their own handling of this data is governed by Google's privacy policy and Microsoft's privacy statement.
Visitors in the EEA, the UK, and Switzerland choose first. We work out your country from the network request, and if you are in one of those places, or we cannot tell, we show a banner and load neither these providers nor the advertising tags in Section 4 unless you accept. Visitors elsewhere are counted by default and can opt out. Either way, you can change your mind at any time with Cookie settings in the site footer. Your choice is stored in your browser, plus one small cookie that records only this choice so you are not asked again on each workspace address. Declining stops the tags from loading; it does not delete cookies they already set, which you can clear in your browser settings.
4. Advertising
We advertise Busabase on the platforms below. Their tags measure which ads lead to sign-ups, and let those partners show our ads to people likely to find Busabase useful. They set their own cookies on our domain.
| Provider | Cookies | Purpose | Retention |
|---|---|---|---|
| Google Ads (Google LLC) | _gcl_au, _gcl_aw | Connects a sign-up to the Google ad that led to it, and supports ad measurement and audiences. | Up to 90 days |
| Reddit Ads (Reddit, Inc.) | _rdt_uuid, _rdt_cid | Connects a sign-up to the Reddit ad that led to it, and supports ad measurement and audiences. | Up to 90 days |
| X Ads (X Corp.) | muc_ads, personalization_id, _twclid | Connects a sign-up to the X ad that led to it, and supports ad measurement and audiences. | Up to 2 years |
| Meta Ads (Meta Platforms, Inc.), when enabled | _fbp, _fbc | Connects a sign-up to the Facebook or Instagram ad that led to it, and supports ad measurement and audiences. | Up to 90 days |
Google, Reddit, and Meta tags load on Busabase Cloud pages under the same choice as the analytics providers above: where we ask first, nothing loads until you accept, and Cookie settings in the site footer withdraws it at any time. When a signup succeeds (a verified email address, or an account created through a sign-in provider such as Google or GitHub, not a submitted form), the tags report one sign-up event to each partner, identified only by the de-duplication id in busabase_signup_conversion. X's tag is not loaded on ordinary page views. Loading it is the sign-up event itself, so it is requested only on the page that reports that completed signup. When you arrive from an X ad, the page keeps that ad click's id in the _twclid cookie on our own domain, without contacting X; the id goes to X only with that sign-up event, so the sign-up can be credited to the ad. We do not send your email address, name, account id, or workspace content to these partners ourselves. Some partners' tags, X's among them, can also read an email address typed into a form on the page where the tag runs and send a one-way hashed (SHA-256) version of it to their platform to match the sign-up to an account there.
Each partner handles this data under its own policy: Google, Reddit, X, and Meta.
5. What We Do Not Use
Beyond the advertising partners in Section 4, we do not use other ad networks, retargeting pixels, or social media widgets that track you across sites. We do not sell cookie data, and we do not share it with data brokers.
Your workspace content — records, files, change requests, and review history — is never stored in cookies. It lives in your Space and is governed by our Privacy Policy.
6. How to Control Cookies
- Cookie settings: use the link in the site footer to accept or reject analytics and advertising together.
- Browser settings: every major browser lets you block or delete cookies. See the help pages for Chrome, Safari, Firefox, or Edge.
- Google Analytics opt-out: install the official browser add-on.
- Do Not Track / Global Privacy Control: we honour browser-level tracking-protection signals where our providers support them.
Blocking essential cookies will prevent you from signing in. Blocking preference cookies means the site will forget your language and theme. Blocking analytics or advertising cookies has no effect on how the Service works for you.
7. Changes to This Policy
We may update this Cookie Policy as the Service changes. Material changes will be posted here with an updated "Last Updated" date.
8. Contact Us
Questions about this Cookie Policy:
Customer Support: support@busabase.com
Company: AI Organizer Company
Registered Address: 8 The Green, STE R, Dover, DE 19901, USA