Privacy Policy

Who we are

Ezra is operated by Mellies Inc., a Delaware corporation. For anything in this policy, write to hello@tryezra.ai.

What we collect

• Workspace and account data. When an admin installs Ezra, Slack gives us your workspace ID and name, and the user ID, display name and email of people who interact with Ezra.
• Content you point Ezra at. Messages in channels Ezra has been invited to, and documents and records in the systems your workspace connects (such as document storage, email, calendars and customer records). Ezra reads a channel only after someone adds him to it, and reads a connected system only through a company connection or the asking person’s own connection.
• Usage records. What Ezra read, when, and for whom; which model ran; how much work it consumed. This is what the audit log and the usage meter are built from.

Company and personal connections. Company tools can be used by anyone in the workspace through Ezra, so connect only what your team should share. Personal connections are used only for the person who connected them. Connect your own Gmail or calendar and Ezra can draft your replies or prep your next meeting when you ask. If a colleague asks Ezra to read your email, in a shared channel or a direct message, the request is refused. When you ask in a shared channel, the answer is posted there for everyone in it, so ask in a direct message for anything private.

What we do not collect

• Passwords. Every connection is OAuth. We never see or store a credential for a connected system.
• Anything outside the sources your workspace connects.
• Channels Ezra has not been invited to.

How we use it

To answer questions, do the work asked of Ezra in your workspace, keep the audit log, meter usage for billing, diagnose faults, help when you ask for support, keep Ezra secure, and meet legal obligations. That is the complete list. We do not sell data, we do not share it for advertising, and we do not build profiles from it.

Training

Your workspace’s content is not used to train or fine-tune any model, ours or a provider’s. Model providers are engaged under terms that exclude API content from training.

Who we share it with

We use service providers for the following functions:

• Workspace communications and connected applications: the channels Ezra works in and the systems your workspace chooses to connect.
• Authorisation and integrations: connecting to those systems and reading the information needed for your requests.
• Model inference: processing requests and generating responses.
• Public web search: finding public sources when a question requires them.
• Workflow scheduling: running recurring standing orders.
• Payments and usage metering: processing payments and recording billable usage.
• Hosting, compute and data storage: operating Ezra and storing workspace records in managed databases.

Content sent to an inference provider serves that one request. It is not retained for training, by us or by them. For the current list of providers and their roles, write to hello@tryezra.ai.

Where it lives and how long

Data is encrypted in transit and at rest. Disconnecting a source immediately revokes Ezra’s access to it. Content the workspace produced stays until offboarding. When a workspace uninstalls Ezra, workspace content is scheduled for deletion within 7 days; billing records are kept as long as the law requires.

Cookies and this website

tryezra.ai sets no cookies and runs no advertising pixels or cross-site trackers. Its fonts, images and scripts are served from tryezra.ai itself, so loading a page sends nothing to third parties beyond our hosting provider.

We count visits with Vercel Web Analytics, which does not use cookies. It recognises a visit by a hash of the request that is discarded after 24 hours, and records the page, the referring site, approximate location, and browser and device type. It does not tie a visit to your IP address or follow you to other sites.

Booking a call opens Calendly, which has its own cookie policy. If we ever add advertising or tracking that needs your consent, we will ask for it on this site before anything loads, and update this section first.

Your rights

If you are in the UK, EU or another region with equivalent law, you can ask us to access, correct, export or delete your personal data, and object to or restrict processing. Workspace admins can request the audit log at any time. The memory Ezra builds is yours: export it anytime. Write to hello@tryezra.ai and we will respond within 30 days.

Security

OAuth only, no stored passwords. Encryption in transit and at rest. An audit log of what Ezra read, when, and for whom. Access to workspace content is limited to the people who need it, and only to support you, fix problems, keep Ezra secure, or meet legal obligations. SOC 2 Type II is in progress and not yet complete.

Children

Ezra is a workplace product and is not directed at anyone under 16.

Changes

If this policy changes materially, workspace admins get notice in Slack before the change takes effect.