Ezra

Pilot Terms

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.

How Ezra runs

Your Ezra runs as an isolated instance with its own database — no pooling across workspaces, and no training on your data. Documents go to the inference API for processing only; a zero-data-retention inference tier is available on request.

What Ezra can access

Invitation is the boundary. Ezra reads only what it's invited to — Slack enforces channel membership, not our promises — and it never receives admin rights or the ability to act as you.

Nothing without your click

Nothing gets sent, shared, or written outside your workspace without your approval. Every send and share waits for your click, and every action is logged.

Ending the pilot

Either side can end the pilot anytime. You can remove Ezra by uninstalling it from Slack, which revokes its access and shuts down your instance. On exit you get a full export on request, and your data is scheduled for deletion. Start with non-sensitive material until we sign a DPA.

Questions about these terms, an export, or deletion? Contact the person who set up Ezra in your workspace, or reach us through your pilot contact. See also our Privacy page.