Loading Zenith
Skip to privacy policy

Your information, in view

Privacy policy.

What Zenith handles, why it is needed, and the choices you have.

Last updated

This policy covers the Zenith website and deployment workspace at tryzenith.cloud. Zenith lets you describe infrastructure, review changes and collaborate with your team. Applications you build or operate with Zenith may have their own privacy notices and data practices.

01 Information we handle

  • Account information. Your email address, account identifier, display name, profile image when supplied by a sign-in provider, linked sign-in methods and authentication records. Supabase handles sign-in credentials and sessions.
  • Workspace content. Workspace names, memberships, invitations and roles; project definitions, source you submit, infrastructure settings, revisions, deployment records, logs, activity history and configured secrets.
  • Requests and integrations. Instructions you give Navigator or a connected agent, and the connection details and permissions you provide for integrations.
  • Waitlist information. If waitlist registration is available and you join, we store your email, occupation, primary use case, submission time and admission status.
  • Technical information. Requests to the service generate operational and security logs, which can include IP addresses, browser information, request times and errors. Where enabled, waitlist abuse protection uses a keyed hash of your IP address for rate limiting.

02 Google sign-in

When Google sign-in is available and you choose it, Google shares basic identity information with Zenith through Supabase: your Google account identifier, email address and verification status, and profile information such as your name and picture. We use this information to create or authenticate your Zenith account, display your profile and link your sign-in methods.

Zenith does not receive your Google password. This sign-in flow does not request access to Gmail messages, Google Drive files, contacts or calendars. Google identity information is handled as account information; signing in does not itself send it to an AI provider.

You can review or revoke Zenith’s connection in your Google Account connections. Revoking that connection does not delete information already stored in Zenith.

03 How information is used

We use this information to authenticate users, enforce access permissions, maintain workspaces, prepare and carry out supported operations you request, show change history, diagnose failures and protect the service against abuse. Waitlist information supports reviewing registrations and granting access.

If Navigator’s AI translation is enabled, your instruction and relevant context—service and resource names and types, and environment names and classes—are sent to Anthropic to interpret your request. Anything you include in that instruction is part of the submission. Avoid putting passwords or unrelated personal information in prompts.

04 Who can access it

Your collaborators. Workspace members can access content according to their roles. Sharing a workspace gives others access to its information; administrators and owners can manage membership and permissions.

Service providers. Zenith uses Vercel to host the website and application, and Supabase for authentication and database storage. These providers process information needed to deliver their services. Anthropic receives the prompt and context described above when that optional feature is enabled.

Connections you choose. Connected agents can receive information within the permissions you grant. Configured notification channels and other integrations receive information needed for the action you request, such as an alert or an export. Their operators have their own privacy practices.

Zenith operators. Privileged operators can access stored account and workspace information to operate and troubleshoot the service. Access controls and encryption do not make your workspace content unreadable to the service operator.

Provider processing can occur in locations outside your country. This policy does not promise that all information remains in one country or region.

05 Cookies and browser storage

Zenith uses cookies for authentication and sign-in security. Local and session storage remember preferences and working state, such as your theme, selected environment, onboarding progress and dismissed guidance. Blocking these features can prevent sign-in or cause preferences to be forgotten.

You can clear this information through your browser settings. Clearing browser storage does not delete account or workspace information stored on the server.

06 Retention and deletion

Account, workspace and waitlist records are stored to support the service and its history. Zenith does not currently apply a single automatic deletion period to all records. Removing an account or leaving a workspace does not automatically erase shared project content, revision authorship or audit history.

Self-service account deletion is not currently available for the production database. Contact the operator to request access, correction or deletion of your information. Requests require verification of your identity and may need coordination with workspace owners. Backup and operational records may remain after a change to active data; immediate erasure from every copy is not guaranteed.

07 Your choices

You can manage available account settings, sign out, choose which workspaces to join and revoke connected agent access. Workspace owners and administrators can manage collaborators using Share. Owners must transfer ownership before leaving a workspace.

You can choose whether to use optional Google sign-in, AI features and integrations. Review the permissions and information involved before connecting a service or sharing a workspace.

08 Questions and updates

For privacy questions or requests, contact the Zenith operator at support@tryzenith.cloud. Do not post passwords, secrets or private workspace content in public issues.

This page will be updated as Zenith’s features and data practices change. The date above identifies the latest revision.