Privacy & files.

What we use and why

The studio uses your name, email, recording choices, selected professional and service, sound/selector names, instructions, shoutouts, pronunciation guidance, messages and reference files to handle your enquiry and prepare any booking you later agree. Account credentials and session records provide secure access. Abuse-prevention counters and limited activity records help protect the service. Payment-card details are not collected or stored by this website.

Drafts that survive a reload

On the recording request form, your brief and contact fields are saved on the server, rather than in unprotected browser storage. Guest drafts expire 24 hours after the last edit. Signed-in drafts expire 30 days after the last edit. Expired draft records and their private files are removed by the maintenance worker. If the service is offline or saving fails, the page reports unsaved changes; avoid closing it until saving succeeds.

Submitted enquiries and recordings

Submitted requests are held while the studio handles them. Closed or declined enquiries, their messages, related queued emails and reference files are removed after 90 days. That period remains subject to owner approval before public launch. Any future paid recording order needs an approved retention policy that also addresses accounting obligations; existing paid-order records are not automatically removed by the enquiry cleanup.

Essential cookies and access

Essential HttpOnly cookies identify your login session, private draft and recent request. Login sessions normally last 24 hours. Recent guest confirmations remain accessible on that browser for 24 hours. Draft cookies follow the guest/member draft periods above. Signing out clears the browser's private access cookies. No advertising or analytics trackers are included.

Files and published samples

Reference files and delivery recordings use a private object store. Access checks run on the server. A recent guest request uses a time-limited private cookie; account requests require ownership or administrator access. Only audio explicitly published by an administrator as a catalogue sample can be played publicly. Do not upload personal information that the studio does not need.

Providers and payments

The application is hosted on a Hetzner server with its own database and object storage. When transactional email is configured, the approved email provider will process delivery information. Online payments are disabled. A future payment integration and its privacy details must be verified and approved before activation.

Your requests and choices

Contact the studio to request access, correction, deletion or withdrawal of an enquiry, or to raise a privacy concern. Use your reference to help locate the request. Account holders can change their password from account security. You may also contact the Information Commissioner's Office about data-protection concerns.

Owner review before public launch: full controller/service postal address, lawful bases, final retention periods, email-provider details and any international data transfers. These must be confirmed, not invented.