Privacy policy

What is available today

RezSat Tools is currently an informational website with optional account registration and sign-in. It has no payment processing, released file-upload tools, contact form, embedded advertising, or configured analytics tracker.

Information processed when you visit

The hosting provider may process technical request information, such as IP address, user agent, requested URL, timestamps, and security or network logs, to serve and protect the website. We have not independently verified or specified the provider’s log-retention period. We store account records and sessions in Cloudflare D1 when visitors choose to sign in.

Accounts and authentication

Account sign-in is provided by Auth0, with Google available as an identity provider. When you sign in, Auth0 handles authentication and provides an account identifier, email address, and email-verification status to RezSat Tools. We store these fields and account creation and update timestamps in Cloudflare D1. We also store a cryptographic hash of a randomly generated session token and its creation and expiry times; the session token itself is kept in a secure, HTTP-only browser cookie. We do not store your Google password or Auth0 login credentials. Usage metering and subscriptions are not active.

Processing files and text — future tools

Future tools may process files or text locally in your browser or via a server, depending on the implementation. Individual tool pages and an updated policy will explain the method, retention, and deletion behavior before such tools launch. Do not assume on-device processing for a tool unless its own documentation confirms it.

Payments and subscriptions

We are integrating Lemon Squeezy for future recurring subscriptions. At present, the checkout is not enabled for public purchases. When it is activated, Lemon Squeezy will handle payment information and billing transactions on its own hosted checkout, while we will store linked subscription identifiers, status, plan variant, renewal and cancellation dates, and billing webhook event fingerprints in Cloudflare D1. We do not store card numbers. Subscription prices and terms must be published before real payments are enabled.

Cookies and similar technologies

Signing in uses strictly necessary first-party authentication cookies. We do not currently set first-party analytics or advertising cookies through application code. Hosting infrastructure and identity providers may also use technical or security cookies. See our cookie policy for details.

Analytics and advertising

We have not configured analytics scripts, advertising tags, or personalized advertising. If any are introduced, we will update this policy and explain the relevant controls and technologies before activation.

Third-party services

The website is hosted on Cloudflare Pages, and Cloudflare D1 stores account and session records. Auth0 provides authentication and Google may process identity information when you choose Google sign-in. The site’s source code is maintained on GitHub. The Lemon Squeezy billing integration is being prepared and is not yet accepting real payments. Service providers and practices will be reviewed as features are added.

Retention, access and deletion

Application login sessions expire seven days after creation, although expired records may remain in the database until cleaned up. Account records remain stored unless deleted through an authorized process; an automated self-service deletion workflow is not yet available. Hosting and identity-provider logs may follow their respective retention practices. Retention and deletion procedures must be finalized before a broader public launch.

Your choices and requests

You can browse the public website without registering and sign out at any time. A verified contact address for access, correction, deletion, or other privacy requests is pending publication on the contact page; this is an outstanding requirement before broader launch. You may also use browser settings to control optional cookies.

Changes

We will update this policy when functionality changes and revise the effective date. Operator legal identity and jurisdiction-specific details remain to be confirmed and must be completed where legally required before operating data-collecting services.