Schemas only
We keep the shape of your tables: names, columns, types and relationships. Never the rows in them.
Security
You’re trusting JillionDB with how your database is built. Here’s exactly how we look after it, and what we don’t do yet.
What we hold, and what we never do
No connection to your database
JillionDB never connects to your database and never asks for its password. Your own tools apply the SQL it writes.
Private to your account
Every project, version and proposal belongs to one account. Our tests check that another account can’t see or change them.
Signing in
Passwords are never stored
We keep a scrambled form made with scrypt and a unique salt, so the password itself can’t be read back, even by us.
Sessions and links
Your sign-in lives in a cookie scripts can’t read, sent over HTTPS only. Email links work once and expire: 24 hours to confirm an address, 1 hour to reset a password.
Changing your password signs out your other devices
And repeated wrong guesses are slowed down, by address and by network.
Agents
Keys are shown once
Agent keys are stored scrambled, like passwords. Settings shows when each was last used, and revoking one takes effect immediately.
Only a person can approve
An agent can read schemas and propose changes. Approving happens in JillionDB, signed in as you. There’s no way for an agent to approve its own proposal.
Limits on every key
Each key can make up to 240 requests a minute, and a project holds at most 50 waiting proposals.
The site itself
HTTPS everywhere
Every page and request is encrypted, and browsers are told to never use an unencrypted connection.
Only our own code runs
No ads, trackers or third-party scripts. A strict content policy stops anything else from running on our pages, and the site can’t be embedded in another one.
Changes come from JillionDB only
Any request that changes your account or projects must come from jilliondb.com itself, so another site can’t act on your behalf.
Deleting
Deleting your account in Settings removes your account, projects, versions, proposals and keys straight away. Demo workspaces are deleted when you leave them, or after 24 hours.
More on what we keep, and why, in our Privacy notice.
Not yet
- Two-step sign-in
- Single sign-on for teams
- An independent security audit or certification
We’d rather say so than imply otherwise. These are on our list.
Found a problem?
Tell us at security@jilliondb.com. Include what you found and how to reproduce it, and we’ll reply as soon as we can. Please test only with your own account or a demo, and give us time to fix things before sharing details.