Effective date: 2 November 2026 · Version 2026-11-02-mockmate-v1
Launch blocker: Draft for review. Insert the actual controller identity, address, contact and retention periods; confirm processor contracts and international transfer arrangements before launch.
The data controller is [INSERT LEGAL BUSINESS NAME], [INSERT POSTAL ADDRESS]. Contact our privacy lead at [INSERT PRIVACY EMAIL]. This policy describes the current service and should be updated if its data practices change.
We use this data to create and fulfil paid orders, verify payment, send and track messages, handle support/refunds, maintain accounting records, prevent abuse, and secure the service. The intended lawful bases are taking steps to perform your contract, complying with legal obligations, and legitimate interests in service security and preventing misuse. The controller must verify that each basis and any balancing assessment is appropriate. Recipient permission is collected from the purchaser as a service safeguard; it is not represented as the recipient's GDPR consent to unrelated marketing.
Data is shared only as needed with Stripe (payment processing), Twilio (message delivery), Google Cloud (voice synthesis), Cloudflare R2 (temporary audio storage), Render or the configured database providers (running and storing the service), and providers used to load site assets. The page currently loads scripts/styles/fonts from Google Fonts, cdnjs, and jsDelivr; those providers may receive browser request data such as IP address and user-agent. Assess whether these external assets are needed and review their terms before launch.
Providers may process data outside the UK. Before launch, identify their processing locations, execute required data-processing terms, and document an appropriate transfer mechanism and safeguards where required. We do not sell personal data.
Order identifiers, payment/refund totals, and delivery statuses are retained in the service database. Stripe and Twilio also keep data under their own retention policies. Voice MP3s and their signed access links are designed to expire after 7 days; an R2 lifecycle rule must be configured to delete the audio objects after 7 days before voice checkout is enabled. [INSERT RETENTION PERIODS FOR ORDER DATA, MESSAGE CONTENT, DELIVERY LOGS, AND HOST LOGS]. The current application does not automatically delete database records, so retention periods and a deletion process for those records must be configured before production. We use access controls and service-provider security features appropriate to the deployment, but no internet transmission or storage method is completely secure.
Depending on applicable law, you may have rights to access, correct, erase, restrict, object to, or port your personal data, and to withdraw consent where processing relies on consent. Contact [INSERT PRIVACY EMAIL]. We may need to verify your identity and may be unable to identify a recipient's record without message details. You can complain to the UK Information Commissioner's Office (ICO) or your local supervisory authority.
Purchasers must be at least 18. A purchaser may submit a minor recipient's details only if they are the recipient's parent or legal guardian, have the appropriate authority, and approve the age-appropriate message. We do not intentionally offer direct purchasing to children. We will post changes here with an updated effective date. For data protection details, see the GDPR Notice.