Security
Last updated 15 October 2026
Tissue runs code from lots of customers on shared machines, so keeping each customer's code and data away from everyone else's was the first thing the design had to get right. This page follows the order security questionnaires ask things in, so you can use it as the answer. Where we don't do something, it says so.
1. Who we are
Tissue Systems, Inc. is a Delaware corporation based in Washington State, and one named person runs the platform. We don't have a SOC 2 report or an ISO 27001 certificate. We'd rather tell you that here than send back a questionnaire with half the boxes empty. Everything below is something you can check yourself or ask us to show you.
2. Where your data is
Everything runs on bare-metal and virtual servers we run ourselves, at the providers listed in section 3 of the Privacy Policy. Nothing is stored in a hyperscaler's account: the two Amazon Web Services machines that run Mast probe checks hold no data, only the result of the check they just made.
- Cells, c3 databases and account data are in the United States, in Los Angeles and Kansas City. Each c3 database has its home server in Los Angeles and a replica in Kansas City that's updated continuously.
- g7 objects are stored as three copies in Los Angeles, Kansas City and Quebec. A write is acknowledged once two of the three have it.
- Mast pages, keys and delivery records live on a separate cluster in Chicago and Virginia, with a third replica and quorum witness in Germany. Pages are handed to Apple's and Google's push services from those hosts and nowhere else.
- Monitoring and staging run in Germany. Staging holds no customer data, and monitoring holds request counts and error rates, not request content.
We don't offer region pinning, so you can't keep an account's data in just one of those places.
3. Encryption
In transit: everything to tissue.systems and to your Cells is served over TLS, with certificates issued automatically by Let's Encrypt. Traffic between our own servers goes over a WireGuard mesh, and the internal services behind the edge can only be reached over that mesh or from the host itself.
At rest: vault bindings (type = "vault") are encrypted with a key that's only ever held in memory on the serving hosts, and they're injected into a Cell when it runs, so plaintext secrets are never in your deployed bundle or in a backup. API tokens are stored as SHA-256 hashes and passwords as salted hashes. Databases, objects and deployed code sit on unencrypted disks. We don't use full-disk encryption because the threat it answers, a stolen drive, is one the providers handle physically, and they already control the hardware. If your data needs to be unreadable on disk, encrypt it in your Cell before you store it.
4. Workload isolation
Every Cell runs in its own V8 isolate, a lightweight per-request sandbox with no filesystem, network or process access of its own. A Cell can only reach the platform services it's explicitly bound to (c3 databases, g7 buckets, vault secrets), and only its own account's resources. Cells never talk to the storage backends directly; our internal services broker every request, and outbound connections from a Cell to our own infrastructure addresses are refused.
5. Authentication and access control
Passwords are hashed with salted PBKDF2-SHA256 at 600,000 iterations. You can also sign in with an emailed link, a passkey, or your Google or GitHub account. Sessions use short-lived signed JWTs. API tokens (tok_…) carry an explicit allow-list drawn from 25 scopes, so you can issue a token that can read Cells but can't delete databases, for example. You can revoke a token from the dashboard at any time.
You can turn on two-factor authentication with an authenticator app, with single-use recovery codes as the fallback. Signing out every other session and CLI login is one action, and the API stops accepting them within fifteen seconds instead of waiting for them to expire. We email you when a recovery code is used and, unless you turn the notice off, when your account signs in from a device and network we haven't seen in the last 30 days.
An account can have more than one person on it. Each membership has a role (owner, admin or developer), and the role caps what that person's sessions and tokens can do, so nobody can mint a token with a scope they don't hold themselves. Removing someone ends their sessions and deletes the API tokens they issued on that account, and moving someone to a narrower role cuts their tokens down to what the new role allows. Every change like this goes into the account's activity record, which you can read in the dashboard or export.
As for our own access: production is reached over an operator-only overlay network, with SSH keyed to one named person. There's no password login, and the one break-glass host that still answers on a public port accepts only that key. Nobody at a hosting provider has a login to our systems. We don't look at customer content except to investigate abuse or a support request you've opened.
6. Backups and recovery
- The registry that holds accounts, Cell metadata, tokens and Mast records is a replicated cluster, snapshotted every hour into replicated object storage. Snapshots are kept on a tiered schedule for about a year.
- Every c3 database is backed up hourly into the same object storage, thinned to one copy a day and kept for 30 days. That's on top of the live replica described in section 2.
- Objects in g7 aren't backed up separately. The three copies at three sites are what keeps them safe, and a deleted object is gone.
- Deployed Cell code is kept on every serving edge, so losing one edge doesn't lose a deployment.
Restores are scripted, and we've run them against real snapshots. One serving edge failing doesn't take the platform down. If the Los Angeles site is lost, each database's replica is promoted automatically once the nameservers agree the site is down.
7. Data retention and deletion
The full schedule is in section 5 of the Privacy Policy. The short version: your content stays until you delete it or close the account. Per-request access logs and the account activity record are kept for 30 days, Mast page history for your plan's history window, and traffic statistics for 90 days at hourly resolution and 400 days at daily. Closing an account starts a seven-day grace period. After that, every table and bucket the account owns is deleted, on both the platform and the Mast cluster, with the auth record going last. Backups age out on their own schedule, and we never restore part of one.
8. Monitoring and incident response
The fleet is monitored from a separate site. We alert on availability, error rates, certificate expiry, replication lag and DNS reachability, and an independent check makes a round trip through each serving edge every minute. Alerts page the operator directly. Status is published at tissue.systems/status.
If we find out your data was exposed to someone who shouldn't have seen it, we'll email the account's owners within 72 hours of confirming it, with what we know, what we've done and what you should do. Incidents that affect availability are written up on the status page.
9. Change management
- Infrastructure is managed as code, and changes are reviewed before they're applied.
- Releases are built on a dedicated build server, then signed on the operator's own machine with a key the build server has never held. The signature is checked before anything reaches a server.
- The runtime, its dependencies and the operating systems are updated on a regular schedule to pick up security fixes.
10. Sub-processors
The companies that handle your data for us, and what each one sees, are listed in section 3 of the Privacy Policy. We'll update that list before adding one. On Colony, Sovereign and the top Mast plan, we'll sign our standard data processing agreement on request.
11. Your responsibilities
Some of this is on you. Keep your account credentials, API tokens and Mast channel keys secret, give tokens only the scopes they need, put secrets in vault bindings rather than in code, and keep your Cell's dependencies up to date.
12. Reporting a vulnerability
If you think you've found a security problem, email security@tissue.systems with the details and steps to reproduce it. We're glad to hear from good-faith researchers. We'll write back to say we've got your report, and we ask that you give us reasonable time to fix it before you publish.