Privacy Policy
Last updated 19 November 2026
This page says what we collect when you use tissue.systems, what we do with it, and what you can do about it. The Service is run by Tissue Systems, Inc. ("Tissue", "we"). We try to collect only what we need to keep the platform running.
1. Information we collect
- Your email address and workspace name, and, if you sign in with a password, a salted hash of it. We never store the password itself. If you invite someone onto an account, we store the address you invited with the invitation.
- If you sign in with an emailed link or code, we store a hash of the link and the code, the address it went to and when it expires. If you add a passkey, we store its public key, its ID and the name you gave it. The private key never leaves your device.
- If you turn on two-factor authentication, we store the secret behind your codes and a hash of each recovery code. To warn you about a sign-in from a device we haven't seen before, we keep a truncated hash of your browser's user-agent string and network prefix for 30 days. We don't keep the values themselves.
- If you sign in with Google, we ask Google for your email address and whether Google has verified it, and nothing else. We store that address and Google's ID for you so the next sign-in finds the same account. We don't get your name, photo or contacts, we get no access to any Google service on your behalf, and we don't share what Google sends us with anyone. Deleting your account deletes the link.
- If you sign in with GitHub, we ask GitHub only for permission to read your email addresses (the
user:emailscope). GitHub then sends us your public profile (your username, plus your name, avatar and anything else you've made public there) and your email addresses. We keep only your GitHub account ID and the one verified address you sign in with, so the next sign-in finds the same account. We don't read anything from your repositories, and we don't keep the access token GitHub gives us: it's used for those two reads during sign-in and then thrown away. Deleting your account deletes the link. - The code, configuration, c3 databases and g7 objects you store on the platform.
- Request metadata we use to run and debug the Service, such as timestamps, Cell addresses, response codes and rough error details.
- Traffic statistics for your Cells: hourly counts of requests by status class, country, browser, path and referrer, and an approximate daily visitor count. The visitor count comes from a salted hash of each visitor's address and user-agent. The salt changes every day and the hashes are only held in memory, so no per-visitor record is ever written.
- If you use Mast Pager, we store the push token Apple or Google issues for your phone, along with the phone model, OS version, app version, locale and time zone the app reports, so pages reach the right device in the right format. For each page we keep the title and body you sent, the channel and key it came in on, the address it was sent from, and the delivery record: when we handed it to Apple or Google and when the phone acknowledged it. Vitals keep the time of each beat, and probes keep the result of each check. On-call schedules, policies, status pages and incidents are stored as you write them.
- If you add a phone number so Mast can call you, we store the number, the label you gave it and when you confirmed it. For each call we keep the number called, when it was placed, the carrier's ID for it and how it ended: answered, acknowledged, no answer or voicemail. We never record a call.
- Counts of invocations, storage and bandwidth, which we use to enforce plan limits and to bill paid plans.
- If you reach a Tissue Mast page by clicking one of our Google ads, the link carries a click ID that Google adds. We keep that ID in your browser for up to 90 days. If you then create an account, we store the ID with the account. See section 4 for what Google gets.
- If we send you our newsletter, each copy has its own links and a small image that is fetched when the message is displayed. When you open it with images turned on, click a link in it or unsubscribe, we record your email address, the time, which link, and the IP address, browser and language your mail client or browser sent. Some mail services fetch the image or check links on your behalf, so a record can come from them rather than from you. The plain-text version has no image, and you can turn images off to stop opens being recorded. Every copy has an unsubscribe link, and replying to ask works too.
2. How we use it
We use this information to run, secure and improve the Service, to sign you in and check your API tokens, to email you about your account and about changes that affect you, and to meet our legal obligations. We don't sell your personal information, and we don't train machine-learning models on the content you deploy.
3. Sub-processors
A few outside companies process data for us, and each is bound by confidentiality and data-protection obligations. Your Cells' data sits on servers we run ourselves; the Security page says where.
- Hosting is ReliableSite, HostMayo and Vultr in the United States, OVH in the United States and Canada, and Hetzner in Germany and the United States. They supply the machines, and we manage and back up the data on them. None of them has a login to our systems, though like any host they have physical access to the hardware.
- Amazon Web Services does three jobs for us, and nothing else. It runs two of the machines that check your Mast probes, one in the United States and one in Germany. They see the URL being checked and the response it sends back, and pass the result on to our own servers. Amazon SES, in the United States, carries the email our team writes to you by hand, such as replies to support and billing questions, so it sees those messages on their way out. And a storage bucket in the United States holds our backups: copies of Cells, databases, files and account data, encrypted on our own servers before upload with a key Amazon never has. Amazon can see that the backups exist and how large they are, not what is in them. A backup is kept for 30 days to a year, so data you delete can stay in a backup copy for up to 30 days after the last backup that held it.
- Apple delivers Mast pages to iPhones through the Apple Push Notification service, and Google delivers them to Android phones through Firebase Cloud Messaging, so each sees a page's title and body on its way to the phone. When the app first registers, Apple (App Attest) or Google (Play Integrity) also vouches that it's our app on a genuine phone. The Mast Pager app is distributed through the App Store and through Google Play, under each store's privacy policy.
- Twilio, in the United States, places Mast phone calls. It gets the number being called, the page title the call reads out or the code on a confirmation call, and the key pressed in reply.
- Postmark (part of ActiveCampaign) sends the email the Service sends automatically: sign-in links, security notices and account mail. It also sends our newsletter.
- Stripe handles payments. Card details go straight to Stripe and never reach our servers. We keep only the customer and subscription IDs Stripe gives us.
- Google and GitHub handle sign-in under their own privacy policies, if you choose to sign in with one of them.
- Google Ads runs our ads on Google search. When an account is created after a click on one of those ads, we tell Google Ads the click ID and the time the account was created, so it can count the ad as having led to a sign-up. That's all it gets: no email address, no name, nothing about how you use the Service.
We'll update this list before we add a provider that handles your content or personal data.
4. Cookies
The dashboard and sign-in use a single first-party session cookie to keep you signed in.
If you arrive from one of our Google ads, the sign-in page also sets a first-party cookie, tissue_gclid, holding the ad's click ID for up to 90 days, so an account you create in that time can be matched to the click as section 3 describes. Our pages don't load any Google advertising script or set any Google cookie, and we don't track you across other sites. To keep a sign-up from being counted, clear cookies for tissue.systems before you sign up, or open the site directly rather than through the ad.
5. Data retention
Newsletter records, meaning opens, clicks and unsubscribes, are kept while we send the newsletter. If you unsubscribe, we keep your address on the unsubscribe list so we don't mail you again. To have your newsletter records deleted, email privacy@tissue.systems.
We keep account information while your account is open. When you delete something, it's removed from our live systems, and copies in backups age out as the backups rotate.
Closing an account schedules it for deletion seven days later, and any owner can cancel during those seven days. Once they're up, we delete the account's Cells and their deployed code, its c3 databases, its g7 buckets and everything in them, its custom domains, API tokens and vault secrets, and all of its Mast data: channels, keys, pages, delivery records, vitals, probes, schedules, policies, status pages and the push token for its phone. Then we delete the account record itself, its memberships and open invitations, and any user who's left without an account. The Mast Pager app on your phone keeps what it has already shown you until you delete the app.
A few records outlive the thing they describe, each for a fixed time. Per-request access logs for your Cells are kept for 30 days. So is the account activity record, which is what the dashboard's activity feed shows: deploys, deletions, vault changes, access-link and session changes, and account events such as a scheduled closure. Traffic statistics for your Cells are kept for 90 days at hourly resolution and 400 days at daily resolution. Closing an account deletes those too, rather than leaving them to age out.
Mast page history and delivery records are kept for your plan's history window: 7 days on Try it out and Free, longer on the paid plans as listed on Pricing. Vital beats, probe checks and the sender address on each page are kept for the same window. Page text is stored once per distinct message and expires within 30 days of the last page that used it. When you rotate a channel key, the old key keeps working for seven days so a sender you haven't updated yet isn't cut off, and after that it's refused. Apple or Google holds a page only until it's delivered, or until it expires because the phone couldn't be reached.
6. Your rights
You can see, export, correct or delete your content whenever you like, from the dashboard, the ribo CLI or the API. Anyone signed in to an account can download a copy of its metadata (members, Cells, databases, buckets, domains, API tokens, webhook endpoints and the activity record from section 5) from the dashboard or from GET /v1/account/export. An owner can close the account from the dashboard, which starts the seven-day deletion in section 5; it can be cancelled until it finishes. For any other data-protection request about your personal information, email privacy@tissue.systems.
7. Changes
We'll update this policy as the Service changes. When a change matters, we'll change the date at the top and, where it makes sense, tell you directly.
8. Contact
Questions about privacy? Email privacy@tissue.systems.