Your traffic goes through your proxy. Your keys can't be read back. Live video is never saved.

01 · Transport

Everything between you and us travels encrypted.

All connections to us are encrypted (HTTPS only).

02 · Proxies

Sessions use your own proxy or VPN.

Per-profile SOCKS5 on any plan, OpenVPN or WireGuard on paid plans; the Test button shows what to expect from a proxy before you launch.

A profile can attach a SOCKS5 proxy at a public address as its exit to the internet (egress), or an OpenVPN file (.ovpn) or WireGuard file (.conf) — VPN exits are on paid plans — so websites see that address instead of ours. Before the session starts we check the proxy details and that a SOCKS5 proxy can be reached with a real connection through it, and website address lookups go through the proxy too, so they do not reveal your real location. A VPN file is checked before it is accepted: Driftstack does not run scripts from VPN configs. An OpenVPN file that carries a script directive is refused with the line named; from a WireGuard file only the keys, addresses, endpoint, allowed IPs, DNS and MTU are read — its PostUp/PreUp hooks are never used. Proxies on private or local addresses (for example localhost or a home network address) are not accepted. A VPN tunnel carries everything the profile does, including WebRTC and HTTP/3. On a SOCKS5 proxy, whether WebRTC and HTTP/3 traffic can use the proxy depends on your proxy's UDP support: the Test button shows what to expect before you launch, and a running session shows whether HTTP/3 is actually in use. On a proxy that cannot carry HTTP/3, it is switched off. Your session's traffic leaves only through your proxy or VPN, never around it. The desktop app launches a profile only through the proxy or VPN you chose for it and never picks one for you (a profile with none chosen does not launch), and every agent session names one of your saved proxies when it is created. Driftstack does not route your traffic through a shared exit of its own. Steps are stored without page text (a step held for your approval keeps the words of the control it would press): an AI session's transcript keeps your messages and the AI's replies as written (a reply can quote a page), with card numbers, secret parameters in web addresses and the passwords and codes of four or more characters a step typed into a recognised password or code field masked, and each step with the site it was on, stored encrypted (not end-to-end) and shown on no staff screen. See /trust/security-overview for the full picture.

03 · API keys

We couldn't read your keys if we tried.

Stored only as one-way scrypt hashes — never readable.

API keys are scrambled one-way with scrypt — a deliberately slow algorithm that makes guessing impractical — before they ever touch the database. The readable key is shown exactly once, when you create it; after that nobody at Driftstack — admin, support or operations — can recover it. A database breach would expose scrambled values, not keys. Keys can be rotated with a 24-hour overlap and revoked at any time. The desktop app signs in with a short code you approve in the dashboard, so it receives its own restricted sign-in credential without a key being copied by hand.

04 · Webhooks

Every webhook proves it came from us.

Signed (HMAC-SHA256) · stale messages rejected.

A webhook is a message we send to your systems when something happens — say, a session finishing. Webhooks are signed, so you can check they came from us. Your code checks it with one SDK helper, verifyWebhookSignature (a constant-time compare, built to resist timing tricks). Messages older than the default 5-minute timestamp tolerance are rejected, so an intercepted copy can't be re-sent later ("replay"); secrets rotate per-endpoint without touching the rest of your account.

05 · Team roles (RBAC)

Your whole team can look. Only admins can change.

Admin and member roles; only admins can make changes.

Invite teammates by email from the desktop app or the dashboard; each invitation link works for seven days. Members can view the owner's profiles, past browser sessions, audit log and settings, but only admins can change anything or work in a live session (role-based access control). Sessions, profiles, webhooks, API keys, email preferences — every change is permission-checked before it runs. Audit entries record who acted (the member) separately from whose account it was (the owner). Owners can review recorded activity in the dashboard's audit log, or download it as a CSV export.