Zodeen / Security

Security

How Zodeen keeps your workspace private, backed up and running.

Sign-in and access

You sign in with an emailed link or with Google; Zodeen keeps no passwords.

Each workspace opens only for its members, matched by verified email. Roles (owner, lead, member, viewer) are enforced by the database’s own rules, not only by the screens, so a viewer cannot change a plan even by calling the database directly.

Everyone acts as themselves: the person shown on an update is the person signed in.

Your data

Stored in Google Cloud (Firestore) in the United States, encrypted at rest and in transit (HTTPS only).

Connector keys (GitHub, Jira, Linear, Slack, email) are kept in Google Secret Manager on the server, never in the database or the browser.

Every change to a plan and to a workspace’s people is recorded in an audit log: who, what and when.

Backups

Every workspace is backed up each night to Google Cloud Storage and kept for 35 days. Owners can also download a full backup any time and restore from one, as copies or over the current version.

AI that cannot change your numbers

Isabella’s numbers come from Zodeen’s own engine. Claude writes only the prose, and every number in it is checked against the plan before it is shown. Changes she proposes wait for a person’s approval unless your settings allow that kind.

Claude receives the facts of the plan it writes about. Under Anthropic’s commercial terms, that data is not used to train its models.

Monitoring

zodeen.com is checked every five minutes from several regions. Errors in the app and on Isabella’s server are collected and alert us, so we usually know about a problem before you do.

Report a problem

If you find a security issue, write to privacy@zodeen.com. We reply within two working days and will not take action against good-faith research. Last updated 29 October 2026.

Get started · Why it matters · Features · Charts · Why Zodeen · FAQ