Cookie & Storage Notice
Everything BuildAPI keeps in your browser, and why. Last updated 15 October 2026.
The short version
We set one cookie, and it is strictly necessary. We also keep two of your own preferences in your browser. We run no advertising or analytics trackers and load no third-party tracking scripts, so there is nothing to consent to and no banner to click through.
Nothing described here follows you to other sites or builds a profile of you.
Cookies we set
| Cookie | Purpose | Lasts |
|---|---|---|
| Session | Keeps you signed in as you move between pages, and lets us check that a form you submit came from
our own page (the anti-forgery token for that is kept on our server, inside the session, not in a
cookie of its own). Holds only a random session identifier — no personal data is stored in the
cookie itself. Marked HttpOnly and SameSite=Lax, and Secure
in production. |
Until you close your browser or sign out |
It is what the law calls strictly necessary: the site cannot do what you came for without it, which is exactly the category that does not require consent.
Browser storage we use
Your browser’s local storage holds two small preferences so the interface behaves the way you left
it: whether you chose light, dark or your system’s theme (bapi-theme), and which billing
period you last viewed on the pricing and billing pages (planInterval).
These are conveniences, kept on your own device. They are never sent to us, never shared, and clearing your browser storage removes them with no effect beyond forgetting the preference.
The snippet you install on your own site keeps the last authorisation answer in your visitors’ local
storage, so your site keeps working for a bounded window if we are briefly unreachable; with bot protection on,
it also keeps a visitor’s pass in session storage (__buildapi_bot, gone when the tab
closes) so they are not challenged on every page. That runs on your site under your privacy notice, not this
one; it is described in the developer documentation.
Why there is no banner
Consent banners exist for cookies that are not strictly necessary — advertising, analytics, cross-site tracking. Under the EU/UK ePrivacy rules and laws like the CCPA, strictly-necessary cookies are exempt, and a banner that asks you to consent to something there is no way to decline is theatre, not compliance.
We would rather not set the trackers than ask you to wave them through. If that ever changes, a banner will appear before any non-essential cookie is set, and this notice will change with it.
Third parties
Our public pages load no third-party tracking or advertising scripts. When you make a payment, that happens on the payment processor’s own secure checkout, which sets its own cookies under its own policy — we do not control those and they apply only during payment.
Controlling them
You can clear or block cookies and local storage in your browser settings at any time. Blocking the cookie above will stop you signing in or submitting forms, because it is what makes those work — but nothing here tracks you, so there is nothing to turn off for privacy’s sake.
Contact
BuildApi
2999 Brown Street
Pleasanton, CA 94566
support@buildapi.app
See also our Privacy Policy and Terms of Service.