Security · Seven21
Security, built in
The controls Finance and IT ask about first (identity, encryption, audit history, and tenant isolation) in the same workspace as the ledger. Seven21 is not SOC 2 or ISO 27001 certified.
Access and identity
Who can sign in, how they prove it, and what each role is allowed to touch.
- Domains
Work email and verified domains
Sign-up expects a work email. Companies can verify a domain so SSO and directory-backed sign-in rules apply to that domain.
- MFA
Authenticator MFA
Owners, admins, and Seven21 staff enroll an authenticator. Google and Microsoft sign-in do not skip it. Company SSO can satisfy the factor at your identity provider. Owners and admins may see a limited enrollment reminder before setup is required.
- SSO
Sign-in options
Email and password, Google, Microsoft, and a per-company OIDC or SAML provider when a domain is verified. Business includes SSO. Enterprise adds a security review and invoice by purchase order.
- 4 roles
Roles for Finance and IT
Invite people as Owner, Admin, Manager, or Viewer. Admins manage settings, billing, and integrations. Managers edit the ledger. Viewers read it. That lets Finance and IT share one workspace with different write rights.
- Sessions
Session controls
Sessions use a signed JWT with a bounded lifetime. People can sign out of all sessions from Account. Password reset, role changes, member removal, and authenticator reset also revoke sessions.
Data protection
How secrets are stored, how traffic is protected, and what happens when a company leaves.
- AES-256-GCM
Encrypted secrets at rest
Directory tokens, vendor tokens, identity-provider secrets, authenticator secrets, and AI provider API keys are encrypted with AES-256-GCM before they are stored. After save, the product shows a hint or last four characters, not the full secret.
- HTTPS
HTTPS in transit
The app is served over HTTPS. Production responses also send upgrade-insecure-requests as part of the content security policy.
- Isolation
Tenant isolation
Each company has its data scoped by company id in the application data layer. Reads and writes that would cross companies are refused.
- Retention
Company delete and retention
An owner can delete the company from Settings after name and authenticator confirmation. Company data is removed with that delete. An anonymized audit tombstone can remain until scheduled retention removes older rows.
Visibility and change control
Every important change is recorded, and the risky ones are surfaced before they cost you.
- Audit log
Append-only audit log
Creates, edits, invites, connector syncs, reminder runs, and related admin actions are recorded with who and when. The database blocks routine updates and deletes on that log.
- Templates
Security policies and templates
Start from templates with plain-language guidance (including shadow apps, approved AI tools, and offboarding access), then choose who gets notified.
- Alerts
Admin change alerts
When a subscription connection or directory sync is disconnected or a subscription is retired, Seven21 surfaces a dashboard alert and can post to Slack when that notification is enabled.
- Flagged
Deactivated people still holding access
Directory sync flags former or deactivated people who still hold licenses so Finance and IT can review access that outlived employment.
Integrations posture
Connections read; they do not reach into your vendors and change things.
- Read-oriented
Read-oriented directory sync
Google Workspace, Microsoft 365, Rippling, and Okta connect with read-oriented scopes to import people and licenses. License sync lists access to review. It does not remove someone in a vendor admin console. Optional account provisioning is a separate admin-enabled path.
- Opt-in
Okta app discovery is opt-in
Okta sync refreshes a discovered app list for review. Nothing is added to your ledger automatically until an admin chooses to import or ignore it.
- Off by default
AI Spend and Shadow AI
AI Spend connects providers one at a time for usage visibility. Shadow AI discovery uses directory scopes your company grants. Per-app OAuth autofetch for vendor seats is off by default.
Hosting, status, and incidents
Where Seven21 runs, how status is reported, and what happens when something goes wrong.
- Vercel · Supabase
Hosting and database
The web app runs on Vercel. Application data is stored in Postgres hosted with Supabase. Email delivery and other helpers are sub-processors. A current list is available on request through Contact.
- No SLA
Status page
Published incidents appear on the Status page. That page is maintained by hand. It is not a live automated uptime monitor, and it does not promise an SLA.
- Per DPA
Incidents
If Seven21 learns of a personal data breach affecting customer data, it notifies the affected company without undue delay, as described in the data processing addendum.
See the Status page for published incidents.
Disclosure and review
Report a vulnerability or request our security review through Contact, and read the documents that govern how your data is handled.
