PricingConsole

Data protection

Last updated 12 November 2026

View .md

Tonbo encrypts the connection between your program and Tonbo, and encrypts your databases, streams, Volumes and account records where it stores them, with keys Tonbo manages. This page says what is encrypted and with what, who holds the keys, and what that does not protect against. How it works for Machines and Volumes, down to each key and what a deletion destroys, is on Security internals.

On the network

Every endpoint you reach is an HTTPS URL: the console and sign-in at tonbo.dev, the Management API at api.tonbo.dev, each region’s database and streams origins (see Origins) and each Machine’s HTTPS name. Each refuses any TLS version older than 1.2. An SSH session to a Machine is encrypted by SSH itself.

TLS ends where Tonbo first receives the request: at the network edge in front of tonbo.dev, api.tonbo.dev and streams.tonbo.dev, and at the region’s load balancer for every other name. Past a region’s load balancer, the request travels on Tonbo’s private network in that region. Some of Tonbo’s services call another region’s over a private link between the two regions’ networks, and each such link accepts TLS 1.3 only. Tonbo’s services connect over TLS to the databases that hold accounts and billing, which are set to refuse any connection without it.

Where it is stored

Databases and streams

A database or a stream is kept in Amazon S3 in its region, where every object is encrypted with S3’s server-side encryption (SSE-S3, AES-256), and its newest writes are on its replicas’ disks, which are encrypted Amazon EBS volumes (see Tonbo’s S3 settings). Tonbo adds no encryption of its own on top, and Tonbo’s servers read the data in the clear to serve your reads.

Reads through streams.tonbo.dev may also be kept for a while in the cache of the network edge in front of it. A database’s local copy on your own machine is a SQLite file that Tonbo does not encrypt; protect it as you protect that machine’s disk.

Machines

A Machine’s root and scratch disks are on its host’s local drives and last for one wake: every wake starts on fresh ones, and no other Machine can read them (see Isolation guarantees). Each secret you give a Machine is stored encrypted with AES-256-GCM under a data key of its own, made from a key Tonbo keeps in AWS Key Management Service (KMS) for the region, and the Machine’s host holds it only in memory.

Volumes

Tonbo encrypts a Volume’s data itself before storing it. What goes to object storage is compressed and then encrypted with AES-256-GCM, and the copy on the Machine’s host is encrypted with AES-256-XTS sector by sector, each sector checked against an HMAC-SHA-256 code when it is read. These keys are derived from the Volume’s own data key, which is made in KMS and stored only wrapped by the region’s Volume key, a KMS key that only the service running Machines may use. Deleting a Volume, or the account that owns it, destroys the stored copy of its data key before its data is deleted, and the database backups that still hold that wrapped copy expire within 14 days (see Volumes).

Accounts and billing

Tonbo’s records of accounts, members, API keys, balances and billing are kept in Amazon Aurora databases whose storage is encrypted with a KMS key Tonbo keeps for that database alone; so are their automated backups, kept for 14 days. Billing records of products Tonbo has retired are archived for seven years in S3 under a KMS key of their own, which only the role that reads the archive may decrypt with. Sign-in itself is handled by Tonbo’s sign-in provider, which this page does not cover.

Keys

Tonbo manages every key, in its own AWS account: a KMS key for each purpose above, and the default keys of S3 and EBS encryption. Customer-managed keys are not offered: you cannot bring, hold or revoke a key of your own. AWS rotates each of Tonbo’s KMS keys automatically once a year and keeps the older key material for what it already protects; rotation does not re-encrypt stored data or change the data keys made under the key.

What this does not protect against

  • Tonbo itself. Tonbo holds the keys and runs the servers that decrypt your data to serve it, so this is not end-to-end encryption. What keeps Tonbo out of your data is policy, not cryptography: Tonbo processes your content only to run the service for you and does not read it for its own purposes (see the Privacy Policy, section 1).
  • Anyone with a key of your account, or with the URL of a public database or stream (see Public and private).
  • Copies on your own machines: a database’s local copy, and anything your program writes.
  • Deleted data, for a while: S3 keeps the replaced and deleted versions of a database’s or stream’s objects for 30 days before it erases them, and backups of the account and billing databases expire after 14.