Last updated: August 2026
Subprocessors
This page describes current practice in plain language. It is a statement of how Ezra operates, not legal advice to you. Where a signed agreement exists between Ezra and an agency, that agreement controls.
How this list works
Ezra uses a small number of service providers to run the website, the Slack application, and the pilot infrastructure. Pilot agencies are notified before a new provider is added and may object on reasonable data protection grounds.
Every provider below is engaged under written terms that limit its use of the data to serving Ezra.
Current providers
Application hosting and content delivery for the public website. Purpose: serving pages and static assets. Data: request logs. Location: United States.
Managed database, authentication, and application infrastructure. Purpose: storing access requests and pilot workspace records. Data: contact details, agency profile, pilot records. Location: United States.
Slack. Purpose: the workspace where Ezra is installed and where agency conversations take place. Data: channel messages directed at Ezra and workspace identity. Location: United States.
Large language model providers. Purpose: producing reviews, investigations, and drafts. Data: the prompt content needed for the requested task, under zero retention or no training terms. Location: United States.
Advertising platform interfaces authorised by each agency. Purpose: read access to the performance data the agency approves. Data: campaign and performance metrics. Location: United States.
Requesting details
Pilot agencies can request the current provider list with legal entity names, processing locations, and the safeguards in place, along with notice of planned changes. Write to the address below.
Contact
Ezra is operated from the State of Michigan, United States. Postal address available on request. Written notices reach us at the address below and are answered in writing.
support@ezra.work