TAC Security ESOF, verified by ADA CASA Assessor
Zenpa is verified and secured under TAC Security ESOF by an ADA CASA Assessor. That independent assessment backs the security claims of our private, local-first AI for Mac: encrypted local storage, careful OAuth handling, and work content that stays on your device.
Notarized by Apple
The Zenpa Mac app is Developer ID signed and notarized by Apple. That means Apple has scanned the build for known malware before it reaches your Mac, so Gatekeeper can open it without a warning about an unidentified developer.
What stays on your device
Messages, files, project context, and the memory Zenpa builds from them are stored and processed locally. The AI model runs entirely on your device, so your work content is not sent to a cloud AI provider for processing.
How connected tools are handled
When you link Slack, Gmail, Jira, or another service, the OAuth access and refresh tokens are saved on your device in an encrypted local store. Our database keeps only connection metadata: which service is linked, granted scopes, and profile identifiers from that provider.
- Tokens stay off our database. Connector access and refresh tokens are not written to our servers.
- One-time OAuth handoff. During sign-in to a tool, tokens pass through our server once, encrypted, inside a single-use token that expires immediately after your device claims it.
- Local encrypted storage. On your device, credentials are stored in an app-encrypted local store, isolated per account.
What is in our database
No raw work data. No memory contents. No AI answers. What we do store is limited to what running the product requires: your account credentials, connection metadata for linked tools, and optional usage telemetry if you have it turned on.
Telemetry is controlled by the Help us improve Zenpa toggle in Settings. It is on by default, and you can turn it off at any time. When enabled, we receive limited signals such as your questions and technical diagnostics to improve the product. We never receive your answers or raw memory.
You control the memory
Pause memory, exclude specific tools, or clear anything Zenpa has learned, at any time from the app. Connected services only run while you keep them enabled.
You can also delete your account whenever you want. After an email confirmation, we delete or anonymize eligible server-side records about you, including logs and feedback, and request deletion of your billing profile from our payment provider. We and our payment provider may retain limited records where required for legal, tax, fraud prevention, dispute, or regulatory purposes, and if you hold a Lifetime license we keep what is needed to preserve and restore that entitlement.
What touches the network
Zenpa uses a secure connection for account sign-in, connecting your tools via OAuth, usage telemetry (if enabled), and feedback you choose to send. Your memory, files, and answers are never part of any of these. After sign-in, AI processing, search, and memory work offline.
Built with compliance in mind
Because your work content is processed and stored on your device, it never becomes data we hold on your behalf. There is no server-side copy of your messages, files, or memory to audit, and data minimization is built into the architecture rather than added on top. For teams subject to the GDPR, the Swiss FADP, or similar rules, this design can simplify your compliance work, though every organization remains responsible for its own assessment.
Report a vulnerability
Found a security issue? Contact security@zenpa.ai. We also publish a security.txt file at the standard location. It is a short reference for security researchers with our contact details and a link to this page.
For the full picture on data handling, see our Privacy Policy.