Security & privacy
The trust contract.
Snaben sits between professionals and their colleagues, their networks, and their employers. The trust we ask for is non-trivial. Here is what we do — and what we deliberately can’t do — to earn it.
Admin trust contract
Company admins see aggregate engagement only — seat utilisation, anonymised cross-office connection counts, office-level participation rates. They have no SELECT permission on individual users, trips, drops, or messages. Enforced at the database level via Postgres RLS.
Bilateral disclosure
Sensitive intent fields (open to work, fundraising, exploring acquisition) are visible only to viewers who've flagged the matching intent. Detail columns are REVOKED from authenticated reads; access is via a SECURITY DEFINER RPC that enforces the bilateral gate.
Verified identity
Every member is verified through LinkedIn OIDC. Company-tier members get a second verification via work-email domain or SSO (Okta, Azure AD, Google Workspace via WorkOS).
Audit & accountability
Every company-admin action is logged to an immutable audit table. Admins see what's recorded about them. Members can request a full data export under GDPR.
Data residency
EU customers can opt into a Supabase EU region. All data in transit and at rest is encrypted (TLS 1.3, AES-256).
Authentication
LinkedIn OIDC, work-email SSO (SAML/OIDC via WorkOS), and SCIM provisioning for enterprise customers. We do not store passwords ourselves.
What we deliberately do not build
- · Org-chart visualisation (your HRIS already has this)
- · Performance review tools
- · Manager dashboards showing individual employee activity
- · Any surface where an admin can read a single employee’s trips, profile, or DMs
- · Surveillance features of any kind
Reach security inquiries to security@snaben.com. Responsible disclosure rewarded.
SOC 2 Type I in progress (target Q3). Type II evidence accumulating.