Security
Last updated 10 November 2026.
Subtext is used to sketch subsurface interpretations. Those can be commercially sensitive. This page explains how we protect them, what we have not built yet, and how to reach us.
Questions or a security questionnaire: security@subtext.software.
You can try Subtext without sending us anything
You can use the app without an account. A board made without an account stays in your browser, on your device. We do not receive it, and we do not save it to our database.
That means your team can evaluate Subtext before any of its data reaches us.
Signing in is how a board is saved to our servers and shared. We ask before moving boards from your browser into an account.
Your company owns its boards
Signed-in boards live in workspaces, and workspaces belong to your organisation, not to the employee who made them.
- Roles. Each person on a board is an owner, editor or viewer.
- Workspace visibility. Admins choose whether other members can see a workspace’s boards, view them, or edit them. New workspaces start private.
- External sharing. Workspace admins can turn off sharing outside the company. Turning it off removes everyone outside the workspace from its boards and revokes every share link. An organisation can keep it off across all of its workspaces.
- Invites. A workspace invite works only for the email address it was sent to, and it expires.
- Revoked links. A share link stops working if the person who made it can no longer manage the board.
How we handle your data
- Where it is stored. Boards saved to an account, and the sign-in email address, are stored in the United States, in AWS us-east-2 (Ohio). On Enterprise boards with live editing, changes are relayed through Cloudflare, which also keeps the live state of each board while people edit.
- Encryption. All traffic uses HTTPS, and browsers are told to always use it (HSTS). Stored data is encrypted at rest by our database provider, Neon. See Neon’s security page.
- No direct database access. Your browser never talks to our database. Every read and write goes through our own server, which checks who you are and what that board allows you to do.
- Separate environments. Test and preview builds use a separate database and a separate sign-in system, with their own credentials. Development work cannot reach production data.
- Version history. We keep earlier versions of each saved board for 30 days. We keep more of the recent ones: one every 10 minutes for the last hour, one an hour for the last day, then one a day.
- Deletion. Deleting a board deletes its history too. If you ask us to delete your account, we delete the email address and the boards saved to it.
- No AI training. We do not use your boards or files to train AI models.
- No advertising. We do not sell personal information. We do not run advertising cookies or ad tracking.
Signing in
There are no passwords. You sign in with a 6-digit code, sent to your email address by our sign-in provider, WorkOS. Repeated wrong codes are rate-limited.
Single sign-on through your company’s identity provider is on our roadmap (see below).
In the browser
The app sends strict security headers on every page:
- a Content Security Policy that limits where scripts and data can load from
- a ban on showing the app inside other sites, to stop clickjacking
- camera, microphone, location, payment and USB access turned off
Who runs it
We use a small number of well-known providers. Every provider that handles your data is SOC 2 certified, and each one publishes its own security and compliance information.
| Provider | What it does | Where | Security |
|---|---|---|---|
| Vercel | Hosts the app and its server | United States | SOC 2 · Vercel compliance |
| Neon (on AWS) | Database and file storage for saved boards | United States (Ohio) | SOC 2 · neon.com/security |
| WorkOS | Sign-in, including sending sign-in codes | See WorkOS | SOC 2 · workos.com/security |
| Resend | Sends workspace invites and feedback emails | United States (Virginia) | SOC 2 · resend.com/security |
| Cloudflare | Sits in front of the app, relays live editing on Enterprise boards, and measures app traffic without cookies | Global network | SOC 2 · Cloudflare compliance |
How we work
- Company accounts for code, hosting and the database are owned by the company and protected with two-factor authentication.
- Changes go through pull requests and run on a separate preview environment before they reach production.
- Automated tests check who can see and edit each board.
- Dependabot watches our dependencies for known vulnerabilities and opens updates automatically. We review and merge security updates promptly.
What we are working on
We would rather tell you now than have you find out in a review. These are not built yet:
- Single sign-on (SAML/OIDC, such as Okta and Microsoft Entra ID)
- Automatic user provisioning (SCIM)
- Audit log with export
- Reassigning a departed employee’s boards
- SOC 2
- Third-party penetration test
If one of these blocks a trial, tell us. It helps us decide what to build first.
Reporting a security issue
Email security@subtext.software. Please give us a reasonable time to fix the issue before you publish it. We will reply within 2 business days.
For security and procurement teams
We are happy to fill in your security questionnaire, take your team through how the app works, or run a pilot with external sharing turned off. Email security@subtext.software.