Scripts and synthesis
Text submitted for synthesis is sent to Microsoft’s online speech service to generate audio. The server queue stores the submitted script while a job waits or runs. Its application payload is cleared on completion, failure or cancellation. Application logs do not intentionally record scripts. Database journals or operator backups may retain older data; application deletion is not a guarantee of physical erasure.
Audio and local storage
The server caches generated audio for the configured retention period, normally 48 hours. Cleanup runs every five minutes. The current browser stores completed takes, their scripts and settings in IndexedDB; preferences, drafts, session tokens and consent choices use local storage. Browser storage is not an account or a cross-device backup.
Member accounts and saved work
Creating an account stores your email address, display name, salted password hash and email-verification status. Sign-in uses an essential session cookie. Projects, up to 20 previous project versions, voice presets and recordings you choose to save to cloud are stored privately on this installation until you delete them or your account. Cloud audio is separate from the temporary synthesis cache. Limits are 100 projects, 100 presets and 200 cloud recordings totaling up to 1 GB. Registration requires email verification. Verification and password-reset links are sent through the operator’s configured email provider; the application stores hashes of these short-lived, single-use tokens. Verification links expire in 24 hours and password-reset links in 30 minutes. The email provider processes the recipient address and message content to deliver these account emails.
Administrator access
Other members cannot access your account workspace. Authorized site administrators can review your account profile, saved projects and their versions, voice presets and cloud recordings, and can download these saved files, suspend accounts or revoke sessions. Administrator review and account actions are recorded in an access log. Passwords are stored as hashes and are never displayed. Files saved only in your browser are not available in the administrator workspace.
Operational information
A short-lived hash based on the connecting IP and a rate-limit window is used to count requests. An anonymous browser token controls access to job results. The infrastructure running the website may maintain its own operational logs according to the operator’s configuration.
Contact messages and optional embeds
Messages submitted through Contact are stored in the administrator inbox on this installation. They are not automatically sent by email. Advertising code is optional and does not load until advertising consent is granted. A configured independent CMP may load to present consent controls. Interface fonts and illustrative portrait images are served from this installation.
Your controls
Delete individual takes or clear local history in Your takes. Use Cookie settings to change optional advertising consent. Use Contact to request review or deletion of an inbox message and include its reference. Do not send passwords or confidential scripts. This policy describes the application behavior; the site operator must keep deployment-specific details current.