Privacy notice
Stories are personal. Their handling should be clear.
This pre-launch notice describes the intended data flows. Retention periods, subprocessors and the accountable legal entity must be verified against the live system before launch.
1. Information the service may handle
Account and contact details; the conversation you have with Annie; transcripts and story notes; names, relationships, dates and pronunciation guidance; package and order records; uploaded or generated project files; support messages; and limited technical or security data.
Do not include information that is not needed to create or support the song. Your story may mention other people, so consider their privacy as well as your own.
2. Why it is used
Information may be used to create and manage your personalised song, operate Mission Control, process an order through connected providers, provide support, prevent abuse, maintain security and meet legal obligations.
The service should not present a private story, transcript, song or reaction publicly as customer content without an appropriate permission and documented purpose.
3. Microphone and conversation
Your browser asks for microphone permission before Annie can listen. The live implementation must confirm whether raw audio is retained, which provider processes it and for how long. The final notice must match that verified behaviour exactly.
Opening page help requests a pause in the Annie interface. Closing help does not automatically resume the microphone.
4. Sharing and service providers
Necessary information may be processed by contracted hosting, AI, payment, email, analytics or support providers. The final notice must identify categories accurately and explain any relevant overseas processing or transfer safeguards.
An unlisted gift-reveal link is not the same as a password-protected page. Anyone who receives the link may be able to open it, so share it deliberately.
5. Access, correction and deletion
You may ask about access, correction or deletion by contacting privacy@yourgiftisasong.com. Some information may need to be retained for an active order, dispute, security record or legal obligation.
The final notice must include the accountable entity, postal contact, complaint process and effective date.
6. Security and retention
Reasonable technical and organisational safeguards should protect project information, but no internet system can promise absolute security. Report suspected account misuse promptly.
Retention must be limited to a documented operational or legal purpose. Exact periods should be published only after they are confirmed in the production system and contracts.