Trust

Your data and privacy

What ChurnWhisper reads, where it lives, and how tenant isolation works.

What we read

ChurnWhisper is read-only. It never creates, edits, or deletes anything in your store.

Where it lives

Data is stored in a Postgres database. Access tokens are encrypted at rest with AES-256-GCM, using a per-store key derived from a server-side secret. A stolen database dump does not yield usable store tokens.

Tenant isolation

Every query is scoped to a store id at the SQL level. There is no "get customer by id" call that works without a store — that shape of query is how cross-tenant leaks happen.

When a request asks for a customer that belongs to another store, the response is an identical 404. The API never confirms whether a record exists in someone else's store.

Uninstall

When you uninstall, the store is marked uninstalled and all subscriptions are cancelled. Customer records are queued for anonymisation.

← Plans, trials and billing Win-back automation →