Privacy
Privacy
What this website and CueTwin’s bug reporter collect, and where it goes.
Last updated: 14 November 2026
This website
The CueTwin website is a static site. It has no accounts, sets no cookies, and runs no analytics, advertising or tracking scripts. It doesn’t load fonts, images or scripts from other sites.
The site is hosted by Netlify. Like any web host, Netlify processes standard request data (such as your IP address and browser details) to deliver pages. Downloads and bug reports link to GitHub, which has its own privacy practices once you’re there.
The app and its installer
CueTwin works on your PC. Your projects, recordings, cloned voices, settings and API keys stay there; keys are encrypted with Windows secure storage. CueTwin has no accounts and sends no analytics.
The installer and every update contain only the application. They include none of the developer’s voices, recordings, projects, API keys, logins or AI connections. Each user connects their own.
CueTwin itself contacts the internet only to download its AI and speech models, to check GitHub Releases for updates, when you send a bug report, and when you choose a cloud AI or voice service (which then receives the prompts or text you send it).
Bug reports are public
Bug reports sent from the CueTwin app, or opened directly on GitHub, becomepublic GitHub issues in thear3emis/cuetwinrepository. Anyone can read them.
A report sent from the app contains:
- The title, description, steps to reproduce and expected result you write
- App version and release channel
- Operating system, CPU, GPU and amount of RAM
- A shortened install ID (the first 8 characters of a random ID created by the app)
- Optionally, the last part of the app’s logs
- Optionally, a screenshot
Before a report is published, it’s automatically checked, and anything that looks like a secret (API keys, access tokens, licence keys), an email address, or a Windows username in a file path is replaced with [redacted]. This is automatic and can miss things, so please don’t include personal or confidential information, licence keys, or private footage in a report.
Screenshots
If you attach a screenshot, it’s stored on Netlify (Netlify Blobs) and shown in the public issue through a link on this website. Anyone with the issue can see it.
Contact email (optional)
If you add a contact email to a report, it’s stored privately on Netlify together with the report number and your install ID. It’s never published in the issue, and it’s used only to follow up with you about that report.
Abuse protection
To limit spam, the bug-report service allows a few reports per hour from each install and from each network address. To do that it briefly keeps your install ID and a salted hash of your IP address (not the address itself). These records are counted over a rolling one-hour window and deleted automatically, usually within two hours.
How long things are kept
Public issues, screenshots and contact emails are kept until they’re deleted. You can ask for your report, screenshot or contact email to be removed at any time (see below).
Services we use
- Hosting and storage: Netlify (Netlify privacy policy)
- Issues and downloads: GitHub (GitHub General Privacy Statement)
Removal requests and contact
To have a report (or its screenshot or contact email) removed, open an issue onGitHub asking for removal and mention the report number, or contact Athian Games throughathiangames.com/contact.