Trust centre
How Eeklin Ops keeps your data safe.
What we do today, who processes data for us, where it lives, and what we're working towards. Updated 18 November 2026.
Separation between organisations
Every row an organisation creates carries its id, and the database refuses to show it to anyone else (row-level security on every table, checked by a test suite that tries to cross between organisations). Files sit in private storage with links that expire in minutes. Viewing Ops as another member is read-only, enforced by the database.
Identity and access
- Sign in with an email link, a passkey, Google or Microsoft, or your company’s own single sign-on (OpenID Connect: Entra ID, Okta, Google Workspace).
- Provisioning from your directory (SCIM 2.0): people are added, paused and removed as they are there.
- Access policies per organisation: passkeys only or for admins, short sessions, allowed networks and countries, and a fresh passkey for sensitive actions.
- Roles from a permission matrix, admin for a while (asked, approved, ended automatically) and access reviews.
- Every sign-in logged with method, device and place; a new device or country is emailed to the person.
Audit
One audit log for every change that matters: records, files downloaded, exports, settings, roles, security. Each entry has who, when, from where and what, never the value of a sensitive field. Organisations search and download it, and can stream it to their own security tools through a signed webhook. The finance books keep their own trail.
Data protection
- Secrets and keys encrypted with AES-256-GCM under a key ring with rotation.
- Uploads checked: programs, scripts and macro files are refused; every file is scanned before anyone else can open it.
- Sensitivity labels on files: Restricted files get no share links and stay out of AI search.
- Sensitive fields on records, readable only by the roles you choose and never sent to AI.
- Privacy requests: find, export or erase one person’s data across Ops.
- AI never receives your members’ sign-in emails, personal phones or account secrets, and providers don’t train on your data.
Data regions
Each organisation chooses the United States or the European Union when it starts; its database, files and calls stay there.
Sub-processors
| Service | What for | Where |
|---|---|---|
| Neon | The database (Postgres) | United States or European Union, by the organisation's region |
| Vercel | Hosting the application | Global edge; functions in the organisation's region |
| Cloudflare (R2, Workers) | File storage, background jobs, inbound email, Office links | United States or European Union buckets, by region |
| Resend | Sending email | United States |
| LiveKit Cloud | Calls, meetings, recordings in transit | Nearest region to the call |
| Groq | AI: meeting transcripts and fast answers | United States |
| NVIDIA | AI: drafting and summaries | United States |
| Cloudflare Workers AI | AI: embeddings for search, backup answers | Global |
| Hunter | Finding public company contact addresses (sales agent) | European Union |
Policies
- Privacy policy and terms.
- Reporting a security issue (also in security.txt).
- A data processing agreement on request: hello@eeklin.com.
Certifications
We’re working towards SOC 2 Type II and ISO 27001, with an independent penetration test first. Until then, we answer security questionnaires and share this page and our controls on request.

