ZETT.

Privacy Policy

Last updated: 4 September 2026

This is a launch-ready template for ZETT soft launch. It is not formal legal advice. Have counsel review before large-scale or paid marketing launch.

Who we are

ZETT is a SaaS product ("we", "us"). Contact: support@tryzett.com.

Data we process

  • Account data: email, name, authentication session.
  • Workspace data: studio profile, members, clients, projects, leads, quotes, invoices.
  • Uploaded files and video deliverables (including review comments and timestamps).
  • Client portal activity tied to invite tokens you issue.
  • Payment / billing metadata when you share payment links or accounting integrations.
  • Operational data from infrastructure providers (hosting, auth, storage, email, video streaming), plus optional analytics/error monitoring if configured.

Why we process it

To provide the product (workspaces, collaboration, client review, invoicing), secure accounts, prevent abuse, improve reliability, and respond to support requests.

Processors / infrastructure

Depending on configuration, processing may involve:

  • Supabase (auth, database, storage)
  • Cloudflare (Workers hosting, Stream video)
  • Resend (transactional email)
  • Optional analytics and error monitoring vendors when enabled by environment config
  • Optional invoicing integrations you connect (e.g. Oblio)

Retention and deletion

We retain workspace data while your account is active. You can request account deletion from Settings → Danger zone (or by emailing support). Backups and logs may persist for a limited operational period after deletion.

Your rights (GDPR)

If you are in the EEA/UK, you may have rights to access, rectify, erase, restrict, or port personal data, and to object to certain processing. Contact support@tryzett.com. You may also lodge a complaint with your local supervisory authority.

Cookies and analytics

Essential cookies/local storage are used for authentication and preferences. Product analytics, if enabled, are configured to avoid capturing video contents, comments, tokens, or other confidential client text. Non-essential tracking is only enabled when configured for the deployment.

Security

We use access controls, encrypted transport (HTTPS), and server-side secrets for sensitive integrations. No method of transmission or storage is 100% secure.

Changes

We may update this policy. Material changes for existing users will be reflected by the "Last updated" date on this page.

Back to home · Support