VoidscapeNo Voidscape tracking.
The static project site sets no Voidscape cookies, creates no account, runs no analytics, and accepts no media upload.
Privacy, in plain sight.
Voidscape has no hosted media service, account database, or telemetry pipeline. The important boundary is which command you choose: local processing, a public source request, a model download, or an explicitly approved cloud transcription.
DRAFT — not reviewed by counsel. This page accurately describes the current open-source prototype, but it is not legal advice or a substitute for a professionally reviewed privacy policy before a hosted or commercial launch.
Local by default.
Frames, transcripts, manifests, configuration, and local media stay on the machine unless you choose a networked operation.
Approval before transfer.
Cloud audio and first-time model downloads have separate approval gates. An environment key is never treated as consent.
What the website collects
The Voidscape website is a static site served through Vercel. Voidscape does not add forms, authentication, advertising, analytics, cookies, pixels, or browser storage. Vercel and the network providers between you and the site may receive ordinary request data such as IP address, user agent, requested URL, and timestamps under their own policies.
Following a link to GitHub, a media platform, or a separately hosted feedback form moves you to that provider. Review the provider's notice before submitting information.
Field-level disclosure
This is the practical data map for the current CLI and skill bundle.
Local mediaRead from the path you provide to inspect, preview, or process. Voidscape has no server that receives it.Local by default
Frames and transcriptsWritten to the local work directory you choose, together with the manifest and run metadata.Local files
Public media URLsThe source host receives a request when `yt-dlp` or related tooling inspects or downloads the URL.Source request
API keysRead only from environment variables when you select a compatible cloud backend. Voidscape does not write them to outputs or load `.env` files.Environment only
Cloud transcription audioSent to the provider you explicitly select only after `--allow-cloud`. The chosen provider's retention and training terms apply.Approval required
Local model filesDownloaded from the model host only when a required model is missing and `--allow-model-download` approval is given.Approval required
Cookie exportAn optional, user-created Netscape cookie file can be passed to `yt-dlp`. Voidscape never discovers browser credentials and does not copy the file into the repository.User controlled
Community feedbackIf you choose to use a separately linked third-party form, that provider processes the response. Never submit secrets, cookies, private media, or confidential URLs.Optional
What still requires trust
- The operating system and installed tools such as Python, ffmpeg, yt-dlp, and a selected local transcription backend.
- The source platform when you inspect or download a URL, including its access logs and account rules.
- The selected cloud transcription provider when you approve an upload.
- The model host when you approve a first-time model download.
- GitHub when you visit the site, repository, issue tracker, Security page, or License page.
Retention, deletion, and control
Voidscape has no project-operated database and therefore no central account or media record to delete. You control the local inputs, output directories, workspace configuration, environment variables, model cache, and optional cookie file. Delete those items using your operating system when you no longer need them.
For data sent to a source host, cloud transcription provider, model host, GitHub, or feedback-form provider, use that provider's controls and retention policy.
Security and questions
Read the project's Security documentation. Report public problems through GitHub Issues. For sensitive reports, use the contact address on the maintainer's GitHub profile rather than posting details publicly.
This notice will be updated if Voidscape adds accounts, hosted storage, analytics, a first-party feedback form, or other project-operated data collection.