Platform
Security and data ownership
Your designs are your intellectual property, stored encrypted, isolated per project, and reachable only by people and keys you have authorised. Everything that touched them is written down.
Per-project
isolation
Encrypted
at rest and in transit
Scoped
API keys
Yours
design ownership
01
The short version
You own what you design here. Sequences you upload, constructs the platform computes for you, and every export you generate remain your intellectual property. They are not used to train models, they are not folded into the public catalog, and they are not visible to other customers. If you close your account, you take them with you in open formats rather than leaving them behind in a proprietary one.
That statement is only worth as much as the controls underneath it, so the rest of this page describes them: how accounts authenticate, how projects are separated, how data is stored, how machine access is scoped, and what record exists of who did what.
02
The controls
Authentication
Email and password with multi-factor authentication, or a managed identity provider. Sessions are short-lived and individually revocable, so losing a laptop is an inconvenience rather than an incident.
Per-project isolation
A project is the unit of access. Membership is explicit, permissions are per-role, and a user with no membership cannot read a project, list it, or learn that it exists. Sharing is an action someone takes, never a default.
Encrypted at rest and in transit
Everything moves over TLS and is written encrypted. Sequence data, run outputs and export packages are treated as customer content throughout, with the same handling whether a design is a sketch or a lead candidate.
Team-scoped API keys
Keys belong to a workspace and carry explicit scopes, so a key that submits jobs cannot also manage billing or add members. Keys rotate, revoke individually, and report their own usage.
Audit and run history
Every job records who ran it, against which project, with which engine version, and what it returned. Every design revision keeps its predecessor. The history is readable by project members, not only by administrators.
SSO and workspace policy
Single sign-on through your identity provider, centrally managed membership, and workspace-level key and webhook policy. Joiners and leavers are handled where your organisation already handles them.
03
What the record contains
- Actor
- User or API key, named per event
- Scope
- Project identifier, revision number
- Action
- Run, edit, share, export, revoke
- Engine
- Build version of the engine invoked
- Result
- Output reference and run identifier
- Timing
- Submitted, started, completed
- Retention
- Kept for the life of the project
Audit history and scientific reproducibility turn out to be the same requirement wearing different clothes. A reviewer asking how a construct was produced and a security team asking who exported it are both asking for a durable record of actions against a project. One log answers both, which is why run history is a first-class part of the product rather than an administrative add-on.
Export events are recorded like any other action. When a package leaves the platform, the manifest inside it and the entry in the history describe the same run, so a file found on someone’s desktop two years later can still be traced to the project and the engine versions that produced it.
04
Ownership, stated plainly
Customer designs belong to the customer. The platform needs a licence to store and process them in order to run the engines you asked for, and that is the extent of it. Your data does not become training material, reference material or anybody else’s starting point. The public catalog of 1,000 constructs is ours and stays separate from your work in both directions.
Portability is part of the same commitment. GenBank, FASTA, SBOL and CSV are open formats, and you can export at any time without asking. A platform worth trusting with a design programme should be one you could leave; building the exit cleanly is the most honest way to say so.
Ready to run it
Try this in the Splice Platform.
CPU engines are free to run. GPU engines run on prepaid credits.
Related