Trust & privacy
Your content stays yours. You stay in control.
Mindy is built around a simple principle: each site's knowledge is isolated, the plugin sends only what it's told to, and you can stop the flow instantly. Here's how that works in practice — no hand-waving, just the mechanisms.
The foundations
Per-tenant isolation
Every connected site gets its own vector collection and its own Postgres schema. Your content is never pooled with another customer's — isolation is structural, not a filter applied after the fact.
HMAC-signed webhooks
Every payload the plugin sends is signed with your site's secret and delivered with an X-Mindy-Signature header. Mindy verifies the signature before accepting anything, so only your paired plugin can write to your knowledge base.
Data minimization
The plugin sends only the published content it's told to — and on a change it captures just an id, never extra page state. Drafts and unpublished work stay on your site.
The instant kill switch
Two independent off-switches stop all sync the moment you flip either one — no claim, no SQL, no network. Turning Mindy off is immediate and entirely yours to do.
You stay in control
A note on what we don't claim
We'd rather be precise than impressive. This page describes the isolation and control mechanisms that actually exist in the product today. If you have specific security, compliance, or data-handling requirements for your organization, reach out at hello@mindy.help and we'll talk through your needs directly.