Security & Trust
Read-only by design. Ephemeral by default.
Questions: hello@anku.app
Read-only access, scoped tight
Anku requests read-only access to Events, Persons, and Insights in your PostHog project. It never asks for write permissions and never installs tracking scripts in your app.
Your key, encrypted
A stored Personal API Key is encrypted at rest with AES-256-GCM whether or not you opt into weekly scans; without the opt-in you can also run a one-off analysis without storing the key at all, and it is never written to disk.
Ephemeral processing
Event and session queries are processed in memory during a diagnosis run. Raw telemetry is not persisted after the run completes.
PII scrubbing before synthesis
Automated scrubbing strips passwords, tokens, full names, and sensitive parameters from event payloads before anything reaches our synthesis models.
What we store
Only the deliverables Anku produces for you: computed metrics, classifications, prescribed changes, and outreach drafts keyed to hashed, non-reversible identifiers. Zero end-user PII is persisted.
Your controls
Disconnect in Settings and your encrypted key and the briefs and email logs for that connection are deleted immediately. For full account deletion, open Settings and type DELETE; for an export of the data we hold about you, use the Export button in Settings — or email hello@anku.app from your registered address and we'll do it for you.