Security and compliance
Steel runs each session in its own browser, encrypts the credentials that you store, and offers a HIPAA-ready BAA on Scale and Enterprise. A session can hold the logins and data of the sites that it visits, so control who can reach it.
Session isolation
Each session is its own browser in Steel's cloud, with its own cookies, storage and proxy. A new session starts with no cookies and no login, unless you load a profile or a session context into it. Sessions do not share state with each other.
Files that you upload to a session, and files that its browser downloads, stay after the session ends. You reach them through the Files API.
You connect to a session over wss://connect.steel.dev, and you call the API at https://api.steel.dev. Both connections are encrypted. The connection URL holds a token that controls the session until it ends, so treat it as a secret, and do not log it.
Access to a running session is access to every account that it is signed in to. Give the live view only to people who may act for those accounts.
Data handling
A session can leave data behind after it ends:
| Data | What it holds |
|---|---|
| Recording | A video of the session. On by default. Set recording to false to turn it off. |
| Logs and agent traces | What happened in the session |
| Session files | Uploads and downloads |
| Profile | Cookies, storage and other browser state |
| Credentials | Usernames, passwords and TOTP secrets for sites |
Steel keeps recordings, logs and files for your plan's data retention period, and it deletes a profile that you stop using. A credential stays until you delete it. Data retention gives each period. Release a session when its work ends, and download what you need before the period ends.
Steel encrypts stored credentials with AES-256-GCM. Each project has its own data key for credentials, and a key management service encrypts that data key with a key that belongs to your organization. Each encrypted value is bound to its organization, project, credential and version, so it does not decrypt anywhere else. Steel fills the sign-in form inside the session, so the values do not pass through your code or your agent's model. A filled field holds the value, though, and code that reads the page, such as a script over CDP, can read it. By default, Steel blurs the username and password fields after it fills them, so a model that reads screenshots does not see those values. See Credentials.
Access control
An API key gives access to your organization's resources. A project key reaches one project, and an organization key reaches every project. Choose a scope compares them. Keep keys on your server, and give each environment its own key so that you can revoke one without the others.
Members of an organization sign in to the dashboard. Only an organization admin can create an organization key, create a project or manage billing. An organization can require two-step verification for its members, and Enterprise adds SSO. See Organizations and members.
Compliance
| Feature | Plans | Details |
|---|---|---|
| HIPAA-ready BAA | Scale, Enterprise | A business associate agreement for health data |
| Enterprise SSO | Enterprise | Sign-in through your identity provider |
Steel's servers are in the United States. The Privacy Policy explains how Steel handles your account's personal information under the GDPR and the UK GDPR. The Data Processing Agreement holds the Standard Contractual Clauses for transfers from the EEA and the UK.
For the HIPAA-ready BAA or Enterprise SSO, contact sales. To ask about your personal data, write to compliance@nenlabs.xyz.
The Terms of Service and the Privacy Policy are the legal terms. Steel is a product of Nen Labs, Inc.