Legal
Privacy Policy
Last updated · November 21, 2026
1. This website
This marketing website is a static page. It sets no cookies, runs no analytics, and uses no tracking or advertising scripts. It does not collect personal information.
2. What the Ezza software stores
When you use an Ezza instance, the software keeps per-user state in file-backed JSON on your own server (under its data directory) — there is no database. Depending on which features you use, this can include:
- Chat sessions and history, including messages, tool results, and attachments you add.
- Settings — providers and models, voice settings, agents, tools, and preferences.
- Memories the assistant creates, updates, or removes (you can review and edit these).
- Kanban boards, workflows and execution history, notes, and to-dos.
- Your profile picture and display name, if you set them.
- Integration grants (for example, a Google Calendar access token) when you link an integration.
Data is isolated per user. Configuration that an administrator manages centrally (such as providers and voice settings) is shared read-only with members of that instance.
3. Sign-in and accounts
Ezza uses Google sign-in. When you sign in, the server receives your Google account's email address, name, and profile picture to create or identify your account, and issues a session cookie (ezza_session) to keep you signed in. Access is invite-only, with admin and member roles and one-time invite links. Ezza does not receive or store your Google password.
4. Optional integrations and where data goes
These features are off until you configure them. When enabled, data flows only to the services you choose:
- Google Calendar & Tasks — read-only access (
calendar.readonly,tasks.readonly). The access token is stored in your integrations record on your server; tokens are short-lived and re-linked when they expire. - Web search & crawl (Brave, Firecrawl) — use your own API keys; your search queries are sent to those providers.
- Weather (Open-Meteo) — fetched through your server using a configured city or your device's coarse location. No API key is required.
- Language and voice models — your prompts and audio are sent to the OpenAI-compatible and audio.cpp-compatible endpoints you configure.
5. Diagnostics
The optional four-phase voice calibration measures audio characteristics (energy, noise floor, and echo correlation) to tune voice detection for your device. These measurements are logged and flushed to your server to inform settings — they stay on your hardware.
6. What Ezza does not do
The software contains no analytics, no billing, no advertising, and no third-party tracking. It does not sell or share your data. Backups are plain, portable exports of your own server state that you can import elsewhere or delete.
7. Your choices
Within Ezza you can edit or delete chats, memories, boards, workflows, and notes; unlink integrations; remove your profile picture; and export or wipe your data. Because the data lives on your server, you (or your instance administrator) can also remove it directly at the storage layer.
8. Security
Access is gated by sign-in and an optional origin allow-list; production web access is served over HTTPS (for example, via Cloudflare Zero Trust). Per-user data routes verify that the requested user matches the authenticated session.
9. Children
Ezza is not directed at children, and the software does not knowingly collect information from children.
10. Changes and contact
This policy describes the software's behavior and may be updated as the software evolves. Each self-hosted operator is the data controller for their own deployment. For questions about a specific Ezza instance or your data on it, contact that instance's administrator. For questions about this website or the Ezza project, contact the project maintainer.