Privacy draft

Privacy posture for the current tester-intake stage.

ReelCool Studio is currently operating a static staging website and controlled tester-intake flow. This draft explains the current data posture before public checkout, customer accounts, license activation, production downloads, or production analytics are connected.

Plain-language status

This is a pre-launch privacy draft, not final legal policy.

The current website collects tester-request information through Tally and serves static website pages from cPanel hosting. Before paid launch, this page must be reviewed and updated to match the actual checkout, account, licensing, download, support, analytics, and error-reporting services used in production.

What may be collected now

Tester-intake information submitted through the linked Tally form.
Basic email communication if a tester is selected or asks a follow-up question.
Standard web-server access logs generated by the cPanel hosting environment.
No production checkout, account, license activation, or customer-download data is collected by this static site.

What this site does not collect now

Payment card details or billing credentials.
Customer-account passwords or login credentials.
License activation secrets, device fingerprints, or entitlement records.
Song files, stems, lyrics, generated media, render outputs, or project manifests through this website.
API keys, ComfyUI credentials, model files, or private helper-tool configuration.

Tester-intake form

The tester-intake form is hosted by Tally. Information submitted there is used to review whether a person is a useful fit for controlled pre-release testing and to contact selected testers by email.

Tester intake is not a purchase, download, customer-account, license-activation, or support-ticket system. Applicants should not submit payment information, credentials, confidential client files, unreleased stems, or private keys through the form.

Local project posture

ReelCool Studio is planned as a local-first creative workflow. Song files, lyric sheets, generated media, project manifests, render attempts, and editor exports are expected to remain on the user machine unless the user intentionally moves or uploads them elsewhere.

The staging website does not upload or inspect local creative projects.

Third-party services

The current staging path uses cPanel hosting for the static website and Tally for tester intake. Future production releases may add third-party services for checkout, accounts, downloads, licensing, support, analytics, and error reporting.

Any production services must be named and reflected here before public sales or production downloads go live.

Future production policy requirements

Final checkout provider and purchase-record handling.
Final account/download provider and password-reset process, if accounts are used.
Final license-entitlement and activation-data handling, if activation is implemented.
Final support-ticket, diagnostics, crash-reporting, or analytics behavior, if implemented.
Data-retention and deletion request process for production customers.

Launch requirement

Replace or review before accepting payments.

This page is suitable as a conservative staging draft for tester intake, but it is not final legal language. It must be reviewed and updated before public checkout, customer accounts, paid downloads, license activation, production analytics, production support, or formal customer data-retention workflows go live.

Read the data-handling summary