Skip to main content
Buildrok
Legal

Cookie Policy

Last updated June 13, 2026

This Cookie Policy explains how Buildrok ("Buildrok", "we", "us") uses cookies and similar browser-storage technologies when you visit buildrok.com and use our Service. For more information about how we handle your personal data generally, see our Privacy Policy.

What are cookies?

Cookies are small text files that a website stores on your device when you visit. They are widely used to make websites work, improve performance, and provide information to site owners. Similar technologies include browser localStorage and sessionStorage, which store data locally on your device without an expiry transmitted to a server.

What we use and why

Buildrok uses a minimal set of browser storage technologies plus two privacy-respecting, cookieless first-party analytics tools on our own marketing pages, and a first-party record of named product steps on our own pages (all described below). We do not use third-party advertising cookies, tracking pixels, retargeting, or cross-site behavioral advertising of any kind, and we do not use analytics on the websites you publish to your visitors except for the cookieless page-view counter described at the end of this policy.

1. Authentication token (localStorage). Strictly necessary

NameTypePurposeDuration
brk_auth_token localStorage Stores your JSON Web Token (JWT) to keep you signed in to your Buildrok account. Until you log out or clear browser storage
brk_auth_email localStorage Stores your email address to display in the navigation bar while signed in. Until you log out or clear browser storage

These are necessary for the Service to function when you are signed in. Without them, you cannot remain logged in between page loads. This data stays on your device and is not transmitted to any advertising network.

2. Theme preference (localStorage). Functional

NameTypePurposeDuration
theme localStorage Stores your preferred color scheme ("light" or "dark") so the site loads in the correct mode on your next visit without a visible flash. Until you change your preference or clear browser storage

3. OAuth session cookie (Neon Auth). Strictly necessary for sign-in

When you sign in using Google OAuth, our authentication provider (Neon Auth / Neon Inc.) sets a short-lived session cookie on its own authentication domain to support the OAuth PKCE sign-in flow. This cookie:

  • Is set and managed by Neon Auth, not by Buildrok directly
  • Is used only to complete the sign-in process
  • Does not track your browsing activity across other websites
  • Expires shortly after the sign-in flow is complete

This cookie is necessary to use the Google sign-in option. If you sign in using email and password instead, this cookie is not set.

4. Product analytics on our marketing pages (cookieless). Functional

On our own marketing pages at buildrok.com (not on the websites you publish), we use two privacy-respecting analytics tools to understand which pages are viewed and how visitors move through our signup flow so we can improve the product. Neither tool sets an advertising or tracking cookie, and neither is used for cross-site tracking or advertising.

ToolStoragePurposeDuration
PostHog (PostHog, Inc.) localStorage (no cookie) First-party product analytics: page views and interactions on our marketing pages and signup funnel. We configure PostHog to store its identifier in localStorage rather than a cookie and we disable session recording. Until you clear your browser storage
Vercel Web Analytics (Vercel, Inc.) None (cookieless) Aggregate page-view and performance metrics for our marketing pages. Vercel Web Analytics does not use cookies and does not store a persistent identifier on your device. Not stored on your device

Because these tools are cookieless and first-party, there is nothing for an advertising network to read. You can clear the PostHog identifier at any time by clearing your browser's localStorage, and where your browser sends a Global Privacy Control (GPC) signal we treat it as an opt-out. These tools run only on our marketing pages; the websites you publish through Buildrok never load them. The product-step records described in our Privacy Policy are sent from our own pages only, including your dashboard and the site editor, and store nothing on your device.

What we do NOT use

  • Google Analytics, Meta, or any advertising-network analytics
  • Advertising or retargeting cookies
  • Social media tracking pixels (Meta Pixel, etc.)
  • Third-party session-recording or behavioral-replay tools for advertising. (Our error-monitoring provider, Sentry, may capture a fully-masked replay on our editor surfaces solely to diagnose crashes, as described in our Privacy Policy; it is not used on marketing pages or for analytics.)
  • Third-party chat widgets that drop their own cookies

Analytics for published customer sites

Buildrok provides basic page-view analytics to website owners who publish through the Service. This analytics system does not use cookies. Instead, it uses a daily-rotating SHA-256 hash of the visitor's IP address and user agent to count approximate unique daily visitors without storing the raw IP address. No persistent identifier is stored on the visitor's device.

How to control cookies and localStorage

You can clear cookies and localStorage data at any time through your browser settings. Clearing localStorage will sign you out of Buildrok and reset your theme preference. Most browsers offer controls to:

  • Block all cookies or only third-party cookies
  • Delete all cookies and site data
  • Browse in private/incognito mode (most storage is discarded when the window closes)

Note that blocking strictly necessary storage (authentication tokens) will prevent you from staying signed in.

Changes to this policy

We may update this Cookie Policy from time to time. The "Last updated" date at the top of this page will reflect the most recent revision. Material changes will be notified via a notice on the Service or by email.

Contact

Questions about this Cookie Policy?