Legal
Cookie Policy
Every cookie NamiDB Cloud sets. Only strictly necessary and user-requested preference cookies; no analytics or advertising cookies.
- Last updated
- Version
- 2026-11-01
- Questions
- info@namidb.com
Contents
01What we use and why there is no cookie banner
This policy covers app.namidb.com and auth.namidb.com. NamiDB Cloud uses a small number of first-party cookies, all of them either strictly necessary to provide the service you asked for (signing you in and keeping your account secure) or preferences that you set yourself (which organization to open, a collapsed sidebar). We do not use analytics, advertising, social-media or other third-party cookies, and we do not use similar technologies such as tracking pixels, fingerprinting or local storage for tracking.
Under Article 5(3) of the EU ePrivacy Directive (2002/58/EC), as implemented across the EEA, the UK’s PECR (regulation 6) and similar laws, storing information on your device requires consent unless it is strictly necessary to provide a service you explicitly requested. Authentication and security cookies fall within that exemption, and so do user-interface preferences set by your own action and limited to that purpose (Article 29 Working Party Opinion 04/2012). That is why NamiDB Cloud shows no cookie consent banner. If we ever add a cookie that needs consent, we will ask for it before setting it.
02Cookies we set
| Name | Purpose | Type | Duration | Attributes |
|---|---|---|---|---|
sb-namidb-auth-token (and sb-namidb-auth-token.0, .1, … when split) | Keeps you signed in: holds your session's access and refresh tokens. Set when you sign in. | Strictly necessary | Up to 400 days, renewed while you use the console; deleted when you sign out | HttpOnly, Secure, SameSite=Lax |
sb-namidb-auth-token-code-verifier (and per-flow …-flow-<id>-code-verifier) | Protects GitHub or Google sign-in and email sign-in links against interception (PKCE). Only set while such a sign-in is in progress. | Strictly necessary | Deleted when the sign-in completes | HttpOnly, Secure, SameSite=Lax |
nami_pending_email | Remembers, signed and server-side only, which address is waiting for its verification code, so it never appears in a URL. | Strictly necessary | 30 minutes | HttpOnly, Secure, SameSite=Lax |
nami_recovery | Proves, for 15 minutes, that you opened a valid password-reset link, which is what allows a new password to be set. | Strictly necessary | 15 minutes | HttpOnly, Secure, SameSite=Lax |
nami_last_org | Opens the console on the organization you used last. Set only when you create or switch to an organization. | Preference | 1 year | HttpOnly, SameSite=Lax |
sidebar_state | Remembers whether you collapsed the console sidebar. Set only when you toggle it. | Preference | 7 days | SameSite=Lax (default) |
“Secure” cookies are sent only over HTTPS. “HttpOnly” cookies cannot be read by JavaScript in the page, which protects your session against cross-site scripting. Cookie values are opaque: session tokens, or values signed with a server-side key so they cannot be forged. None of them identifies you to anyone but NamiDB, and none is shared with third parties.
03Where we set no cookies
- The data plane at db.namidb.com (HTTPS API, MCP and Bolt) authenticates every request with an API key and sets no cookies.
- The legal pages you are reading set no cookies of their own.
- Payment pages (Checkout and the billing portal) are hosted by Stripe on its own domain. Stripe may set cookies there for fraud prevention and to run the payment flow, under the Stripe Cookie Policy.
- If you sign in with GitHub or Google, their sign-in pages set their own cookies under their policies. If you signed in with them, the console shows your profile picture by loading it from the provider.
04Controlling cookies
You can see and delete cookies in your browser’s settings and block them for app.namidb.com. If you block the strictly necessary cookies you will not be able to sign in. Deleting the preference cookies just resets the console to its defaults. Signing out deletes the session cookies.
05Changes and contact
We update this list whenever the console starts or stops setting a cookie; the version date at the top changes with it. Questions: info@namidb.com. How we handle personal data in general is in the Privacy Policy.