Privacy Policy
Effective September 4, 2026
This policy describes what ChartBlazer ("we", "us") collects when you use ChartBlazer: Drums, why, and the choices you have. The short version: we collect what the product needs to work, we don't run ad trackers, and we don't sell your data.
1. What we collect
- Account data: your email address, handle, and a securely hashed password (we never store the password itself), plus plan and verification status.
- Your content: the charts, setlists, markup, comments, and settings you create. Private content is visible only to you and the people you explicitly share with.
- AI drafting and conversion inputs: the prompts and song hints you type, any lyric sheet or chart you paste or upload (as text, a PDF, or a photo), and audio you upload for conversion. We never store your recordings. The audio is deleted from our servers as soon as the conversion finishes, and it is handed to the conversion service described below to do the work. A pasted or uploaded sheet goes to the AI model and isn't kept after your draft is made. With a recording, it stays with the conversion job until that job finishes, then is erased. A photo or scan is never written to disk. What we do keep: the uploaded file's name and your song hint, with the conversion job. The first 200 characters of a prompt, and the names of any photos read, with your usage history, so your usage page can show what each request was. In the chart itself: the three cue words per section, the section names and order, an energy level and groove where a playing direction named one, and a description line saying which of those it read.
- Operational data: standard server logs (requests, errors, timestamps) used to keep the Service running and debug problems.
- Public-chart view counts: to count a view once per day without tracking you, we store a one-way hash: your account id, or for signed-out visitors a SHA-256 of IP address + browser user-agent, with the day. The raw IP and user-agent are never stored for this purpose, and the hash can't be reversed into them.
2. Cookies and device storage
We use a session cookie to keep you signed in. That's the only cookie we set. Device preferences (like your chart zoom or column widths) are kept in your browser's local storage and never sent to us. For traffic analytics we use Plausible, a privacy-focused, cookieless tool that counts aggregate page visits without setting cookies, collecting personal data, or tracking you across sites. There's no cookie-consent banner. There are no advertising trackers on the Service.
3. Email
Account email: address verification, password resets, billing and subscription notices, results of work you started (such as a recording you uploaded for conversion), and important account, security or terms changes. This is part of running your account, so we send it for as long as you have one. It can't be turned off.
Product email: occasional news about new features and releases. It goes to account holders by default. Every one of those messages carries an unsubscribe link, and you can switch them off any time on your account page. Turning them off never affects your account email.
We do not send you email on behalf of anyone else, and we never sell, rent or share your address with third-party advertisers. Delivery may be handled by an email service provider processing the message on our behalf.
4. Embedded players
A chart's reference track can embed a YouTube or Spotify player. The embed loads only after you choose to expand it; at that point the provider receives your request (and applies its own privacy policy). Until then, nothing loads from them.
5. Payments
Payments are processed by Stripe. Your card details go to Stripe, not to us. We receive only what's needed to manage your subscription (plan, status, and a customer reference).
6. Service providers we rely on
Running the Service takes a few third parties. Each one processes only what its job needs, acts on our instructions, and is bound to protect it, and we don't sell your data to any of them.
- Render: hosting and the database that stores your account and content. Privacy policy.
- Stripe: subscription payments (see above). Privacy policy.
- Resend: delivers the account and product email described above. Privacy policy.
- Anthropic: the AI model behind chart drafts and section labels. It receives the prompt or song hint you type, any lyric sheet or chart you paste or upload (a photo is sent as an image and a scanned PDF as a document, so they can be read) and, for a conversion, a measured fact sheet describing your recording, never the audio itself. We keep neither the sheet nor the image once the draft is made. Privacy policy.
- Modal: runs the audio conversion. Your upload is handed to its job queue, which holds the audio while the conversion waits its turn and runs, and holds the chart that comes out for up to 7 days so we can collect it. The audio itself is processed in a temporary container, and we never keep a copy of the recording ourselves. Privacy policy.
- Cloudflare Turnstile: checks that sign-ups come from a person, not a bot. It sees your IP address and basic browser signals on the signup page. Privacy policy.
- Sentry: receives an error report when something breaks, which can include the page you were on, your browser, and your account id, so we can fix it. Privacy policy.
- Plausible: cookieless, aggregate traffic counts with no personal data (see §2). Privacy policy.
7. Who can see your content
- Private charts: you, plus anyone you share them with by handle/email.
- Public charts: anyone, including signed-out visitors, can view, play, print, and clone them (see the Terms for the community license). Your handle appears as the author credit.
- Comments: visible to anyone who can see the chart they're on.
8. How long we keep things
Your content stays until you delete it. Deleting a chart removes it from the Service (clones others made from a public chart are their content and remain). To delete your account and its data, contact us at the address below; we'll complete verified requests within 30 days, except records we must keep for legal or security reasons.
9. Security
Passwords are hashed with a modern algorithm, transport is encrypted (HTTPS), and access to production data is restricted. No system is perfectly secure. If we learn of a breach affecting your data, we'll notify you as the law requires.
10. Children
The Service isn't directed at children under 13, and we don't knowingly collect their data. If you believe a child has an account, contact us and we'll remove it.
11. Changes and contact
If this policy changes materially we'll give notice before the change takes effect. The effective date above reflects the current version. Questions or requests: support@infoblazer.com.
Also see our Terms of Service.