Android messaging SDKs
The Android app includes Firebase Cloud Messaging and Firebase Installations. These SDKs can initialize before you enable notifications and send an installation identifier, app version and configuration, and SDK, operating-system, and device information to Google to operate and maintain messaging. This processing is separate from permission to display notifications and from linking a push token to your LynxTTS account. Turning notifications off or deleting your LynxTTS account does not by itself delete the Firebase installation identifier held by Google.
About LynxTTS
LynxTTS is operated by Zhihao Wu. This privacy policy applies to the LynxTTS website, mobile apps, and API. For privacy or account questions, contact support@lynxtts.com.
Google Play purchases
For purchases made through Google Play, Google handles payment credentials. LynxTTS links a purchase to your account using an opaque account reference and stores its product, package, purchase-status and credit records, timestamps, an encrypted purchase token, and a receipt reference. We use these records to verify and deliver credits, handle refunds, prevent duplicate claims, and reconcile purchases. Payment and credit records may remain after account deletion when needed for reconciliation, fraud prevention, disputes, or legal obligations.
Reports about generated content
Where the app offers Report content, submitting a report sends your account identifier, the generated output identifier, selected reason, and any details you choose to provide to LynxTTS. We retain the report and its review status and timestamps to investigate safety or rights concerns. Authorized LynxTTS administrators may review the report and the existing text and audio it refers to; submitting a report does not create another copy of the recording or send it to a third-party reporting service. Reports and their details are removed when the associated output or account is deleted.
Delete your account and data
You can request account deletion in the mobile app under Account → Delete account, or use lynxtts.com/delete-account even after uninstalling the app. Website users can use Settings → Data & Privacy. You can also email support@lynxtts.com from your account address; we may verify ownership. Deletion removes or anonymizes personal account details and removes projects, scripts, generated files, preferences, sessions, push-notification records, and content reports from the active service. File removal and provider cleanup are retried if temporarily unavailable. Payment, credit-ledger, security, and audit records may be retained for the purposes explained above. A pending purchase or active generation may need to be resolved first; contact support if you cannot complete deletion.
GitHub sign-in
GitHub provides an account identifier, verified primary email address, and display name or username. We use these to create or link your LynxTTS account. We request profile and email access, not repository access, and do not receive your GitHub password.
Newsletter and mobile updates
Signing up is optional. We record your email address, signup time, and the kind of updates you chose. Resend manages mailing lists, delivery, unsubscribes, and suppression of bounced or reported addresses. Mobile-only consent is not used for general product campaigns. Every newsletter includes an unsubscribe link that works without signing in. Unsubscribing does not stop essential sign-in or payment emails. Account deletion removes linked signup records and queues removal from the mailing provider; failures are retried. Contact support if you need help changing your preference.
Information we collect
We handle your verified sign-in identity. Google may provide your name, verified email address, and profile picture. Apple provides a verified identity and may provide your name and email address, including a private relay address if you choose Hide My Email. Email sign-in provides the verified address. For email-and-password accounts, we store a salted password hash, never the plaintext password. We also handle projects, submitted text, generation settings, output files and metadata, saved voice preferences, account activity, credit-ledger entries, payment references, API credential metadata, and security or request records. Newsletter subscriptions include your email address and consent to LynxTTS product updates. Mobile-waitlist submissions also include your platform preference. We do not receive your Google or Apple password or store raw card details, security codes, or bank passwords.
Speech and project processing
Text submitted for synthesis passes through LynxTTS infrastructure to an authorized outbound inference worker so it can generate speech. Generated audio is returned to private owner-scoped storage. Customer text, credentials, and generated audio are not placed in public logs, and files are not public sharing links by default.
Payment processing
Dodo Payments handles payment credentials for website purchases. Apple handles payment credentials for purchases made through Apple's in-app purchase system. LynxTTS receives customer, subscription, payment-status, reference, amount, and currency information needed to verify a purchase, grant the correct credits, reconcile billing, prevent fraud, and provide support. For Apple purchases, we store verified transaction, product, and subscription references and status linked to your LynxTTS account. A checkout redirect or purchase-screen message alone does not prove payment.
Cookies and device storage
The website uses essential cookies to establish and protect signed-in sessions. Local or session storage keeps interface language, draft recovery, recent or favourite voices, sidebar state, checkout recovery, and similar product preferences. The mobile app uses operating-system secure storage for sign-in credentials, ordinary app storage for drafts and preferences, and on-device files for cached or downloaded audio. Blocking or clearing storage may sign you out, remove unsaved local state, or interrupt recovery; it does not delete records held in your LynxTTS account.
Audio-ready notifications
If you enable notifications, LynxTTS links a device installation identifier, push token, notification permission, app language, and delivery records to your account. We use Expo and the operating system notification service (Apple Push Notification service on iOS and Firebase Cloud Messaging on Android, where notifications are available) to deliver a generic audio-ready message and an output identifier that opens your recording in History. Notification payloads do not include your script or audio file. You can turn notifications off in Account or device settings. Signing out disconnects this installation from your account; deleting your account removes its stored push tokens and notification delivery records.
Google sign-in in the iOS app
The iOS app includes Google's sign-in SDK. Its privacy declaration lists data linked to the user: name, email address, phone number, and approximate location for app functionality; user identifiers and other data types for app functionality and analytics; and device identifiers and other usage data for analytics. The SDK declares that these data are not used for tracking. These are Google's SDK practices; LynxTTS does not ask for your phone number during sign-in.
How we use information
We use information to authenticate accounts, save and deliver projects, generate and download speech, calculate and reconcile credits, operate API credentials, secure the service, prevent abuse and fraud, provide requested newsletter or waitlist updates, troubleshoot failures, and meet legal obligations.
Providers and disclosure
We disclose only what is reasonably needed to providers that support authentication, email delivery, infrastructure, storage, inference, security, or payment processing. We do not sell personal information. We may disclose or preserve information when legally required, to protect users or the service, investigate suspected fraud or abuse, or establish and defend legal claims.
Retention and deletion
Project records remain until you delete the project or account, subject to backup, security, and legal requirements. Completed private outputs are available for 90 days. At expiry, LynxTTS marks the output unavailable, scrubs stored request and audio material, and queues deletion of the private audio file. A temporary storage error may delay physical file removal while deletion remains queued for retry. Security, credit, payment, and audit records may be retained longer for reconciliation, fraud prevention, disputes, enforcement, or legal obligations.
Security
LynxTTS uses encrypted transport, server-side sessions, access controls, owner checks, private output storage, and other technical and organizational safeguards. No online system is completely secure, so you should protect your sign-in methods and API credentials and report suspected account misuse through the available support channel.
Your choices and rights
You can review and manage projects and credentials through the product. Where applicable, you may request access, correction, deletion, portability, restriction, objection, withdrawal of consent, or other available privacy rights through support@lynxtts.com. We may need to verify identity and may retain information where an exception or legal obligation applies.
Your submissions and lawful consent
Do not submit another person's personal information, private communications, or identity for speech generation unless you have a lawful basis and any consent required for that use. You remain responsible for notices, permissions, and disclosure obligations connected to the material you submit and the audio you publish.