Ezra

Privacy

VERSION 2026-07-24 · LAST UPDATED 2026-07-24

DRAFT — pending legal review. This page scaffolds Ezra's existing in-product consent language at version 2026-07-24. The binding terms are being finalized and this is not a substitute for the signed pilot agreement / DPA.

What we store

Each workspace gets an isolated instance with its own database. Where you connect Google, the OAuth refresh token is encrypted at rest. We keep an audit log of connections and approval-gated actions, and — at sign-up — the intake you provide on the consent screen (how you found Ezra, your role, your focus, and your IP address for the acceptance record).

What we don't do

No pooling across workspaces, and no training on your data. Ezra reads only what it's invited to, and nothing leaves your workspace without your click.

Processing

Documents you share are sent to the inference API for processing only. A zero-data-retention inference tier is available on request.

Export & deletion

A full export of your workspace's data is available on request. When you remove Ezra (by uninstalling it from Slack), we revoke its access, disconnect your connected tools, shut down your instance, and schedule deletion of our copy.

This DRAFT describes how Ezra handles data today; the binding wording is pending legal review. See also our Pilot Terms.