Project isolation
Each active project has its own database and its own roles. The Data API will not serve a project that is not active. Pools used for ordinary requests refuse the provisioning login and refuse the metadata database.
The key and the token do different jobs
Send the publishable key in the apikey header. It is meant to live with the client because it does not authorize rows. Treat it as a project credential anyway: revoke it if it leaks, and do not confuse it with a secret.
Send the user’s JWT as a bearer token. CubiBase Auth issues HS256 tokens signed with the project’s signing secret when your users sign up or sign in through /auth/v1. Alternatively, CubiBase accepts RS256 when you set a JWKS URL, issuer, and audience for your own identity provider. The verified subject is written to cubibase.user_id for that transaction.
For tokens that carry a session id, every request also checks that the session is still live and the user is not banned. A revoked session fails on the next call, even if the access token has not expired. A development issuer can still mint a token for a user id you choose while you are building.
The control API can also create a secret key with the prefix cb_sec_. That secret is returned once and stored as a hash. The Data API does not authenticate with it. Do not send it from a client in the expectation that it will return rows.
Row Level Security
Tables created through CubiBase have Row Level Security enabled and forced. If you pass a text column as the user column, CubiBase creates a policy for the API role: a row is visible and writable only when that column equals cubibase.current_user_id(). If you skip the user column, the API role has no isolation policy of its own.
The SQL role, used by the Console, has a separate policy so the project developer can work with rows. Forcing RLS does not mean the Console is limited to a single end user.
Your Console session
Developer passwords are hashed with Argon2id. The Console keeps the access and refresh tokens in HTTP-only cookies, so page scripts cannot read them. A CSRF cookie is readable by the Console’s own requests. Email verification and password reset use single-use tokens. Refresh tokens rotate.
What this page does not claim
CubiBase has not published a compliance certification, a residency guarantee, or an uptime SLA. Encryption in transit is what you should expect from the public HTTPS endpoints. Encryption at rest is an infrastructure fact to confirm in the legal review, not a claim on this page. You still choose the user column, the exposure flags, and how your app signs tokens.
Questions
Can I rely on the publishable key as the only protection?
No. The Data API rejects a call that has a valid key and no end-user token. You also need a row policy that matches the way your table stores the user id.
Where are developer passwords stored?
Only as Argon2id hashes in the metadata database. The marketing site never sees your password. The Console posts credentials to its own backend, which talks to the engine.