Cookie Policy
How BuildBase uses cookies and similar technologies. Last updated: August 2026
What are cookies
Cookies are small text files stored on your device when you visit a website. They are used to remember preferences, analyze traffic, and provide a better experience. BuildBase also uses related technologies including local storage, server-side sessions, and tracking pixels for similar purposes.
How BuildBase uses cookies
BuildBase uses cookies and similar tracking technologies provided by both first-party and third-party services. These fall into three categories: essential, analytics and functional. The analytics ones are only loaded after you provide consent, and so are the functional ones here and in the documentation. Live chat in the signed-in console is the one exception: it loads on every page there, because that is the support channel for the product you are paying for rather than a tracker. Partner referral tracking sits in the essential group: it stores an ID that identifies the partner who sent you rather than anything about you, and it is what lets us pay that partner, so it is not something you are asked to opt into. Error monitoring (New Relic) is deliberately configured cookie-less: it stores nothing on your device, so it does not appear in the categories below — what it processes is described in the privacy policy.
Essential cookies
Required for core functionality, or for us to meet an obligation we have taken on. These cannot be disabled without breaking the service or a commitment we have made to someone else.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| Server-side session | BuildBase | Authentication and session management. Stores session ID, user ID, organization context, and role. | 30 days |
| cookie-consent-v2 | BuildBase | Stores your cookie consent preferences (which categories you accepted or declined). Set on buildbase.app so your choice applies across our site, documentation and console. | 1 year |
| cf_clearance | Cloudflare Turnstile | Bot protection and spam prevention on forms | 30 minutes |
| endorsely_referral | Endorsely | Stores one referral ID when you arrive through a partner link (a URL containing ?via=), so the partner who referred you is paid if you later subscribe. The ID identifies the partner, not you, and the cookie holds nothing else; it is read when you subscribe. What Endorsely records on its own side is listed in our privacy policy. Set on buildbase.app so the referral survives moving between our site, documentation and console, and mirrored to browser local storage because Safari shortens the life of cookies set this way. | Up to 30 days |
Analytics cookies
Help understand how visitors interact with the website. Used to improve the user experience. Only loaded after consent.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| _ga, _ga_* | Google Analytics | Distinguish unique visitors, track page views and sessions | Up to 2 years |
| _clck, _clsk | Microsoft Clarity | Session recording, heatmaps, and user behavior analysis | Up to 1 year |
| ahrefs_* | Ahrefs | SEO performance tracking and visitor metrics | Up to 1 year |
Functional cookies
Enable additional features like live chat and visitor preferences. On this site and in the documentation they are only loaded after consent. Live chat is the exception in the console at console.buildbase.app: once you are signed in it loads on every page, because it is how you reach support in the product you are paying for, and support you have to opt into is support that is missing on the day you need it.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| crisp-client/* | Crisp | Live chat state, conversation history, and visitor identification. Set on this site, the documentation and the console. When you are signed in to the console, the name and email on your account are attached to the conversation so we know who is writing; signing out clears the chat session in your browser. | Up to 6 months |
Local storage
BuildBase uses browser local storage (similar to cookies but stored differently) for the following purposes. Local storage data remains until explicitly cleared.
| Key | Purpose | Context |
|---|---|---|
| token | JWT authentication token for maintaining your logged-in session | Console and auth pages |
| state | Temporary OAuth state ID used during the login flow | Auth pages |
| dt-pref:* | Table display preferences (column visibility, sizing, density). Also synced to your account. | Console |
Email tracking pixels
Emails sent through BuildBase may include tracking technologies to measure campaign performance.
| Type | How it works | Data collected | Opt out |
|---|---|---|---|
| Email open tracking | Transparent 1x1 pixel image embedded in emails | IP address, device/browser info, timestamp of email open | Disable image loading in your email client, or unsubscribe |
| Email click tracking | Links in emails route through our server before redirecting to the destination | Which link was clicked, IP address, device/browser info, timestamp | Unsubscribe from emails using the link in each email |
Third-party privacy policies
Third-party services used on this website operate under their own privacy policies:
Managing cookies
Most web browsers allow you to control cookies through settings. You can:
- Use the cookie consent banner on this site to accept or decline non-essential cookies
- View and delete existing cookies in your browser settings
- Block all or specific cookies
- Clear local storage through your browser's developer tools
- Opt out of Google Analytics using the Google Analytics Opt-out Browser Add-on
- Opt out of Microsoft Clarity tracking at Microsoft Privacy Dashboard
- Disable email open tracking by blocking image loading in your email client
Disabling essential cookies or clearing local storage may log you out or affect core functionality.
Changes to this policy
This Cookie Policy may be updated when new services are added or removed. Check this page periodically for changes. See our Privacy Policy for full details on data handling practices.
Contact
Questions about cookies or tracking can be directed to:
Email: [email protected]