Your sequences stay yours.
Security is extremely important to you. And it should be.
What we hold today, and what we're working toward.
-
SOC 2 Type I
In progressAn independent audit of our security controls. The auditor is engaged and the audit is underway.
SOC 2 -
HIPAA
Roadmap 2026–27A HIPAA-ready architecture, with a business associate agreement for qualified accounts.
HIPAA -
ISO 27001
Roadmap 2027+A certified information security management system, once international customers need it.
ISO -
Security questionnaires
TodayWe answer SIG, SIG Lite and CAIQ under NDA while the SOC 2 report is in progress.
SIG
No training on your research
We don't train, fine-tune or evaluate any model on your sequences, conversations or notebook entries.
Analysis without a model
Deterministic analysis runs on our servers.
Encrypted end to end
TLS 1.2+ in transit and AES-256 at rest, and every subprocessor encrypts on its side.
Share only what you choose
Share a selected record or project with a collaborator without granting access to the rest of your lab.
Your workspace stays separate
Research is compartmentalized by workspace, with access checked on every request.
Biosecurity checks built in
We flag known biosafety concerns in text and construct annotations. Serious findings prompt an acknowledgement and are recorded for review.
The details
How data moves: AI, BLAST and chat tools
Models. Anthropic is our primary model provider. OpenAI receives the same context when Anthropic is unavailable or rate-limited, or when you choose an OpenAI model. Both state that they don't train on data sent through their APIs, and each keeps inputs and outputs for a limited abuse-monitoring window under its own policy.
When a model sees your data. When you use the assistant, and in two features when you ask for AI: the cloning designer drafts the wet-lab protocol, and marking a notebook entry done sends the entry for an outcome summary. A recording you make with a microphone button, in the assistant or in a notebook entry, goes to OpenAI to be transcribed. Uploading a sequence doesn't send it to a model.
Memory. Lab memory is scoped to its workspace, and your personal assistant preferences follow your account. General biological knowledge lives in a separate store.
BLAST and chat tools. Remote BLAST sends your query sequence to NCBI. Through the MCP connector, the chat client you connect (Claude, ChatGPT or Codex) receives what it asks for and what Plasmole returns, under its provider's terms.
Access, roles and sign-in
Sign-in is with email and password or with Google, through Supabase. Access tokens are short-lived and renew with a refresh token.
Projects are the boundary. Every plasmid, primer, entry, document and analysis belongs to a project, and every project to a personal workspace or a lab. A personal project is private to its owner; a lab project is open to everyone in that lab. Leads and admins manage the lab. Members edit every lab project and its records, while moving someone else's record to Trash, sharing it or moving it elsewhere stays with its owner and the lab's leads and admins. Alumni keep read access without editing.
Checked on every request. Access is checked at the data layer against your account, your lab role and what has been shared with you. Each browser tab works in one workspace at a time. Share links use opaque, revocable tokens, so the link itself doesn't reveal the record's id. Plasmole staff can reach a workspace for support and security investigations.
Roadmap: multi-factor authentication, company single sign-on (SAML and OIDC), and customer-controlled audit-log export.
Where data is stored and how it's encrypted
Location. By default in the United States: the database in Supabase (US East) and the application on Render (US East). For an enterprise contract we can run a dedicated deployment in another region, and the contract sets where data is stored and processed. Our model providers process in the US, so the contract also sets whether AI features run there.
Encryption. TLS 1.2+ on every public endpoint, and AES-256 at rest in Supabase. Traffic to every subprocessor runs over TLS. Provider credentials stay on our servers and never reach the browser. Customer-managed keys aren't offered yet.
Subprocessors
| Provider | Purpose | Region | Data |
|---|---|---|---|
| Supabase | Database, authentication | US East | All customer data at rest |
| Render | Application hosting | US East | Request metadata, application logs |
| Anthropic | Assistant model; host for the Claude connector | US | Prompts, which may include sequence and project context, and responses |
| OpenAI | Failover model, or the model you choose; host for the ChatGPT connector; memory search embeddings; voice transcription | US | Tool arguments and responses; on failover, the same context Anthropic would get; memory text; voice recordings, which we don't store |
| NCBI | Entrez lookups and remote BLAST | US | The accession or search term, and the query sequence for BLAST. No account id. |
| UniProt | Protein record lookup, when you or the assistant look up a protein | UK | The accession or search term supplied. No account id. |
| Sentry | Error tracking | US | Stack traces, request metadata and your account id. A browser error can include data from the screen where it happened. |
| PostHog | Product analytics | US | Usage events by account id, with the page's route. No sequences, record names or entry content, and no text from what you click. |
| Stripe | Payments | US | Billing email and tokenized payment method |
| Resend | Email delivery | US | The recipient's address and the email's content, which can include record names and a note someone wrote: sign-up and password-reset emails, invitations, review requests and decisions, and access and storage notices |
Cookies and analytics. Sign-in tokens are kept in your browser's local storage, and PostHog sets an analytics cookie. PostHog records which features are used, keyed to your account id, never the text of what you click. Sentry records a sampled replay of some sessions with on-screen text masked. Our servers strip credentials and email addresses from their error reports and shorten long sequences, but an error in the browser can include data from the screen. To turn analytics off for your account, email us. Transactional email (sign-up and password-reset emails, invitations, review requests and decisions, and access and storage notices) is delivered by Resend.
Backup and deletion
Backups. The database is backed up daily, and any of the last seven daily backups can be restored. Uploaded files aren't in those backups. We don't run point-in-time recovery and haven't timed a full restore, so we don't publish a recovery-time target.
Deletion. Deleting a plasmid, entry or project moves it to a trash, where it stays until you restore it or delete it for good. To remove your account and its data, email us and we'll confirm when it's done; an erase removes data from every copy, backups included, within 30 days.
Everything we have, and what's on the roadmap
| Item | Status |
|---|---|
| Access checks at the data layer, not just the interface | Today |
| Versioned entries and plasmids | Today |
| TLS 1.2+ in transit, AES-256 at rest | Today |
| Responsible disclosure policy | Today |
| SOC 2 Type I audit (auditor engaged) | In progress |
| Multi-factor authentication | 2026–2027 |
| SAML SSO and OIDC | 2026–2027 |
| Self-serve account deletion and data export | 2026–2027 |
| Customer-controlled audit-log export | 2026–2027 |
| HIPAA-ready architecture; BAA for qualified accounts | 2026–2027 |
| ISO 27001, pending international demand | 2027+ |
| 21 CFR Part 11 readiness assessment | On request |
Questionnaires and contracts
We answer SIG, SIG Lite and CAIQ questionnaires under NDA. The contracting party is Plasmole, Inc., a Delaware corporation. Email [email protected].
Report a vulnerability
Email [email protected]; we acknowledge reports within 5 business days. In scope: all *.plasmole.com domains and our public API. Out of scope: denial-of-service, social engineering, physical attacks, and third-party services we don't operate. Researchers acting in good faith within this scope will not face legal action from Plasmole.
