Cookie & Storage Notice
Everything BuildAPI keeps in your browser, and why. Last updated 8 September 2026.
The short version
We set two cookies, both strictly necessary, and use a little browser storage for your own preferences. 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. Holds only a random session identifier — no
personal data is stored in the cookie itself. Marked HttpOnly, and Secure
in production. |
Until you sign out or it expires |
| CSRF token | Protects the forms you submit against cross-site request forgery. Without it, a form post cannot be trusted. | The session |
Both are what the law calls strictly necessary: the site cannot do what you came for without them, which is exactly the category that does not require consent.
Browser storage we use
Your browser’s local storage holds a few small preferences so the interface behaves the way you left it. For example, which billing period you last viewed on the pricing and billing pages.
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 verification snippet you install on your own site keeps one small item in your visitors’ browsers — the last authorisation answer — so your site keeps working for a bounded window if we are briefly unreachable. 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 two cookies above will stop you signing in or submitting forms, because they are what make 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.