Static site
Website pages
The public website is built as static Astro output and served from cPanel. It does not run the app backend, license backend, or render service.
Data handling
What stays local and what goes through the access path.
ReelCool Studio is designed around a local-first creative workflow. This page summarizes the website, access-request, and local-project boundaries in plain language.
Hosted form
Access requests
Access requests are submitted through Tally and used to review fit, project readiness, and follow-up contact.
User machine
Local projects
Song files, lyrics, generated media, render attempts, project files, and editor exports are expected to remain local unless the user intentionally moves or uploads them elsewhere.
Separate path
Purchase services
Checkout, license activation, production downloads, analytics, and support services are documented separately when those paths open.
What access requests are for
Access requests are for identifying creators, musicians, editors, producers, AI visual creators, and technical users who may be a fit for ReelCool Studio.
The form may ask about role, operating system, local workflow, current tools, song/project readiness, and product interest.
Open Access FormWhat not to submit
- Payment-card data or billing credentials through the access request form.
- Passwords, API keys, private service tokens, or hosting credentials.
- Confidential client files, unreleased stems, or private music assets unless directly requested under a separate process.
- Questions that require legal rights-clearance advice through the access request form.
- Third-party software files or licensed media packages.
Plain boundary
The website does not need your creative files.
ReelCool Studio projects are local-first. Do not send songs, stems, project files, credentials, or private client material through the public website unless a separate approved process asks for it.