Privacy Policy

Privacy Policy

This Privacy Policy explains how Saavo handles information when you use our website, account, checkout, support tools, OAuth authorization, Saavo CLI integrations, newsletter, and template delivery services.

Last Updated: August 11, 2026

How We Handle Information

The information involved depends on which Saavo features you use.

1Information We Collect

  • account details such as name, email address, profile data, roles, and security settings;
  • authentication records, session metadata, verification events, recovery actions, and abuse-prevention signals;
  • OAuth request, client, consent, token, and revocation metadata needed to authorize Saavo CLI or another approved client;
  • purchase, payment, receipt, entitlement, and provider reference data, but not full payment-card details;
  • template release, authorization, download, checksum, and initialization diagnostics;
  • support tickets, messages, attachments, and related correspondence;
  • newsletter subscription details such as email address, page language, and subscription time;
  • website usage, page, session, event, device, referrer, and performance data collected by Saavo Analytics according to your cookie choices.

2How We Use Information

We use information to:

  • create, secure, and manage accounts and sessions;
  • process OAuth authorization and validate CLI access;
  • confirm purchases and determine access to Saavo Starter releases;
  • deliver downloads, verify integrity, and diagnose failed initialization flows;
  • provide support and communicate about account or service changes;
  • send product and architecture updates requested through the newsletter page;
  • prevent fraud, abuse, unauthorized access, and security incidents;
  • understand website usage and improve reliability and product experience.

3OAuth and Saavo CLI

When Saavo CLI opens an authorization request, the website shows the requesting client and requested permissions. If you approve, the authorization service issues credentials scoped to that client. We store the records needed to validate, audit, expire, and revoke that access.

Do not paste access tokens, authorization codes, recovery codes, or template download URLs into support tickets or public messages.

4Payments and Service Providers

Payment providers process checkout and payment credentials under their own privacy policies. We receive the transaction and billing metadata needed to identify a purchase and grant product access.

We may use infrastructure, storage, email, authentication, analytics, payment, and support providers to operate the Services. They receive only the information needed to perform their role.

5Retention

We retain information only for as long as needed to provide the Services, secure accounts, maintain purchase and license records, resolve disputes, meet legal obligations, and enforce agreements. Different records have different retention periods based on their purpose and configured lifecycle.

6Security

We use measures such as access controls, signed sessions, encryption for sensitive values, rate limits, audit records, and least-privilege authorization. No system can guarantee absolute security, so you should also protect your account, devices, and credentials.

7Your Choices

You can review account information, manage authentication settings, revoke supported sessions or OAuth grants, update cookie preferences, and request account deletion through available account features. You may also contact support to remove a newsletter subscription or for other privacy requests.

Some transaction, security, and license records may need to be retained after account deletion where required for legal, accounting, fraud-prevention, or dispute-resolution purposes.

8Changes and Contact

We may update this Policy when our products, providers, or legal obligations change. The updated date above identifies the current version.

Review our Cookie Policy and Terms of Service. For questions or requests, use support or email support@saavo.dev.