Privacy Policy

Last updated:

This policy explains what StageVoice (“we”) collects, why, and what happens to it. We built the Service to need as little personal data as possible: there are no audience accounts, no tracking pixels, and we never see your audience's payment details.

1. Data we process

• Customers (artists, venues). E-mail address and name from checkout, your plan and payment status (from Creem, our merchant of record), event settings (event name, goal, tip link, voices, branding), and the messages shown during your events (history). We do not receive or store card numbers.
• Audience members. The message text, the optional name they type, the optional tip amount they select, and a short-lived technical identifier used to rate-limit submissions. We do not ask for e-mail, phone or account. Tips are paid on the customer's own payment page; we are not involved in that transaction and do not receive its data unless the customer enables a verified-payment integration, in which case we receive the transaction ID, amount and message only.
• Technical logs. Standard server logs (IP address, user agent, timestamps, requested URL) kept by our hosting provider (Cloudflare) for security and debugging, retained for a limited period.
• Demo on our website. The live demo runs entirely in your browser. Messages you type into the demo are not sent to our servers, except the text sent to the voice engine to generate audio (see section 3).

2. Why we process it

To run your events (show messages on your screen, voice them, keep history), to provide customer support and billing, to prevent abuse (rate limiting, banned-words filtering, blocking of abusive submissions), and to comply with legal obligations. The legal basis is performance of a contract with customers, and our legitimate interest in running a safe service for audience data.

3. Third parties

• Creem — payment processing, invoices, subscription management (merchant of record).
• Cloudflare — hosting, networking, storage of event state and history.
• Speech engines — the text of approved messages is sent to a text-to-speech provider (currently Microsoft neural voices) to generate audio. Only the message text, the chosen voice and speed are sent; no names or identifiers.
• E-mail delivery — transactional e-mails (access links, receipts) are sent through an e-mail provider.

We do not sell personal data and do not use advertising trackers.

4. Retention

Audience messages and event history are kept for 90 days after the event ends, then deleted, unless the customer exports or deletes them earlier from the remote. Customer account and billing records are kept for as long as the account exists and as required by tax law afterwards. Server logs are retained for up to 30 days.

5. Your rights

Depending on where you live (including under the GDPR and UK GDPR), you may have the right to access, correct, delete or export your personal data, to object to or restrict processing, and to complain to a supervisory authority. Audience members who want a message removed can ask the event organiser or write to us; customers can delete event data from the remote at any time. Contact: .

6. Security

Data is transmitted over HTTPS. Remote links contain private keys; treat them like passwords. We apply rate limits and content filters to reduce abuse. No system is perfectly secure; if you believe a key has leaked, contact us and we will rotate it.

7. Children

The Service is intended for adults organising events. We do not knowingly collect data from children under 16; audience messages are not linked to identities.

8. Changes and contact

We will post changes to this policy here and, for material changes, notify customers by e-mail. Operator: , . Contact: .