Privacy Policy
This draft covers the current Satsun Voice Studio and developer API beta. It describes the data flows implemented for this product, including invite-only access, speech generation, projects, credits and API keys.
Sign-in and beta access
Satsun Voice uses Firebase Authentication, including configured Google Sign-In and email sign-in. Identity information includes your email address, Firebase user identifier, verification status and available profile information. The beta checks an approved invitation and links your user identifier to your own account and credit allowance.
The browser uses Firebase session storage to maintain sign-in. A pending narration script may be stored in the browser tab's session storage until completion or sign-out. These functions support sign-in and recovery of an in-progress request.
Text, generated audio and projects
Text you submit is processed to generate speech and is stored with its generation record. Records include the selected public voice, language, generation status and timing, character count and audio reference. Stored text supports features such as regeneration. Generated audio is stored for retrieval through your account. Projects store names, optional descriptions and references to generations rather than separate copies of the audio.
Credits, usage and API keys
Usage records connect generation activity to your account. The credit ledger records allowance grants, reservations, settlements and releases. Studio and developer API usage share the account's configured allowance.
A new API key is displayed once. The backend stores its hash and management information such as name, prefix, environment, creation and last-use dates, and revocation status. The key list does not redisplay the full key.
Service providers, logs and support
Managed identity and cloud services support authentication, application operation and storage. Firebase Authentication and Google Sign-In process identity information as part of sign-in. The current speech-generation path uses Satsun's self-hosted engine.
Routine product logs are configured to record operational events, identifiers, status codes, timing and character counts without full narration text, API keys, authentication tokens or temporary audio links. No additional third-party product analytics has been enabled for this beta.
If you email support, Satsun receives the contact information and content you choose to send. Include only what is needed to explain the issue, such as a generation ID. Do not include credentials or temporary audio links.
Access, retention and account deletion
Account authorization restricts access to your projects, generations, usage and API keys. Authorized service operations process this information to run the product and handle support or security issues. This describes the implemented controls and is not a guarantee against every security incident.
Audio access follows the plan's retention period. Expiry of audio access does not itself promise immediate physical deletion. Deleting a project removes its references; it does not delete the underlying generation or audio.
An account-deletion request immediately suspends beta access. After in-flight work finishes, an authorized operator removes that beta account's stored narration text, audio and projects and revokes its API keys. Usage, reservations, immutable ledger records and minimal identity/security records are retained separately. These include records used to prevent repeated beta-credit grants. Final retention periods and handling require legal review.
Deletion of the Firebase identity is handled separately because the identity may also be used by another application. See account deletion information for the current workflow.
Questions and requests
You can revoke keys, delete projects, sign out or request account deletion from Studio. For help with access or data questions, use Satsun Voice support or email support@satsuntech.com.
Legal review must finalize applicable notices, retention periods and procedures for privacy requests before external public beta. This draft does not specify unapproved legal guarantees or response deadlines.