Audit logging
In placeEvery change staff make in our operator tools is recorded in an admin audit log.
Every change staff make in our operator tools is recorded in an admin audit log.
Audit logs are kept live for 90 days and then archived until your account closes.
Source: DPA, Annex 2
Data security
In placeServer-side checks decide who may read, run or change each of your resources.
Your resources are protected by server-side access checks that decide who may read, run or change each one.
Every record is tied to the customer it belongs to.
Source: DPA, Annex 2
Integrations
In placeConnected accounts use OAuth only. Their tokens are encrypted with AES-256-GCM, and you can disconnect them at any time.
We reach Google, Microsoft, GitHub and Slack accounts only through OAuth, with your consent, and use them only to run what you start.
OAuth tokens are encrypted at rest with AES-256-GCM. You can disconnect an account in the Dashboard under Settings › Connections.
Source: Privacy Policy, Section 7.1
Sign-in and SSO
In placeSign in with an email code, a passkey, Google or Microsoft, or your organization’s single sign-on.
You can sign in with an email code, a passkey, a provider such as Google or Microsoft, or your organization’s single sign-on.
Sign-in records hold the time, the method, the IP address and the device, so you can view and end your sessions.
Source: Privacy Policy, Section 3.1
Two-step sign-in
In placeYou can turn on two-step sign-in and passkeys to protect your account.
You can turn on two-step sign-in and passkeys to protect your account.
Source: Privacy Policy, Section 12.1
Role-based access
In placeEach person has a role in each company account, and access checks follow that role.
Each person holds a role in each company account they belong to, and the products they may use are set per person.
In Consulting, roles also limit what each person sees inside a client: only the sponsor sees all amounts.
Source: Privacy Policy, Section 3.1
API keys
In placeAPI keys are stored only as SHA-256 hashes. The full key is shown once and cannot be read back.
We store only a SHA-256 hash of each API key. The full key is shown once, when you create it. We keep its first characters and last four so you can recognise it.
You can revoke a key in the Dashboard. We may revoke a key we believe is exposed, and tell you by email.
Source: Security, Keys and credentials