Security & privacy

Security

Last updated September 22, 2026

The safeguards already in place, the certifications still ahead of us, and a direct line if you have questions.

1. Overview

Zenzible is a young company, and we’d rather describe our security posture honestly than oversell it. Everything below is real and already running in production — we don’t hold SOC 2 or GDPR certification yet, and nothing on this page is meant to suggest otherwise. Anything marked as underway is work we’ve started, not a claim we’ve already earned. Our Privacy Policy covers how your data is used; email [email protected] for anything specific to security.

2. Controls we implement today

  • Meta Tech Provider. Instagram, Messenger and WhatsApp connect through Meta’s own login and setup screens, using Meta’s official APIs — no unofficial tools and no shared passwords. You approve exactly what Zenzible can access, and you can remove that access at any time from your Meta or Instagram settings.
  • Access tokens. Encrypted with AES-256-GCM before they reach the database — for every connected Instagram, Messenger, WhatsApp or Google Calendar account. Decrypted only in memory, only when needed to send a reply, check a connection, or book a meeting.
  • Workspace isolation. Conversations, knowledge bases and settings are scoped to your workspace at the database level with row-level security. One customer’s data is never reachable from another’s session.
  • Webhook integrity. Every inbound message is checked against an HMAC-SHA256 signature before it’s parsed or passed to the agent — unsigned or mismatched payloads are rejected outright.
  • Duplicate protection. Every inbound message is recorded by its own message id, so a retried delivery is recognized and skipped instead of triggering a second reply.
  • Model handling. Your knowledge base and conversations are routed through OpenRouter to the model provider you choose — Anthropic, OpenAI or Google — to generate a reply. OpenRouter doesn’t store prompts or replies. We don’t operate a model ourselves, and none of that traffic is used to train one.
  • Data sharing. We don’t sell your data or share it with anyone beyond the model provider above. The one exception is PostHog (EU Cloud), used only on our marketing pages, only if you accept the cookie banner shown there — it is never active on the product itself, and there are no advertising trackers anywhere on this site.
  • Customer control. Take over any conversation with one click, disconnect a channel or calendar at any time, pause the agent entirely, or ask us to delete your workspace outright — we will.

3. GDPR readiness

We’re building GDPR alignment in stages rather than claiming it all at once. Here’s the honest state of each stage:

In place today.

  • Public Privacy Policy and Terms of Service
  • Row-level security isolating every customer’s data
  • Consent-gated analytics, marketing pages only — no advertising trackers

Underway.

  • Records of processing activities
  • A data subject request process
  • A documented retention and deletion schedule
  • Data processing agreements with key vendors

Down the line.

  • Legal review for EEA/UK customers
  • A signed DPA template for business customers

4. SOC 2 readiness

A SOC 2 Type I report checks whether the right controls exist at a single point in time. Type II is the harder version — it confirms those same controls actually held up, in practice, across several months. We’re nowhere near either yet, but here’s the direction we’re headed:

What’s already running.

  • Row-level security and workspace isolation on every table
  • Encrypted access tokens and secrets
  • Signature-verified webhooks before any processing

What comes next.

  • A written security policy
  • Vendor and sub-processor review
  • Incident response and change management procedures

The audit itself.

  • A Type I review once policies and controls are documented
  • Type II after an evidence period with an auditor

5. Your responsibilities as a customer

You decide what goes into your knowledge base and which channels you connect — which also means you’re the one responsible for having the right to message the people who reach you through them. Keep your account credentials to yourself, and stay within Instagram’s, Messenger’s and WhatsApp’s own rules for businesses.

Contact

Email [email protected] with any security concern, data-processing question, or signed DPA request.