stio

Last updated: October 3, 2026

Privacy Policy

Stio processes account, session, upload, generation, playback, analytics, feedback, report, advertising-consent, and purchase-related information to provide its creative and audio products.

Information Collected

Product workspaces may collect session identifiers, uploaded media, generation parameters, output assets, credit activity, playback events, feedback messages, operator reports, support context, and technical request metadata. Signed-in accounts and billing flows may also collect email, provider identifiers, plan names, transaction metadata, and purchase or entitlement status records. Stio Listen stores playback preferences and free-quota state locally as described in its product privacy policy.

Use Of Information

Information is used to operate generation jobs, protect private assets, maintain credits, provide support, investigate reports, restore purchases when enabled, improve product quality, and keep services reliable.

Authentication And Payments

Google provides Web authentication; supported native clients also use Apple or Huawei. Web, Photo and Music use a shared Creator identity for the same verified sign-in provider and subject. Listen remains independent. Accounts from different providers are not automatically merged by email. Stio receives the verified account identifier, email, profile name, and basic profile metadata authorized by the user for that product. Stripe processes web payments and may provide customer, checkout, subscription, invoice, payment status, and refund identifiers. Stio does not receive or store full payment-card details. Resend may process the verified email address when Stio sends an account deletion confirmation code.

Media Privacy

Uploaded and generated assets are private by default and require the owning account context for access. Web, Photo and Music share the Creator private library. Web, Photo App and Music App have separate purchase wallets. Listen has its own account and content.

Analytics And Tracking

Stio may collect product interaction events such as app launch, catalog view, upload, generation, result export, feedback, and report actions to operate and improve the service. Stio does not use this data for cross-app or cross-site advertising tracking.

Retention And Deletion

Uploaded media, generated assets, session records, feedback, reports, and related product records are retained while needed to provide the service, maintain abuse controls, support users, and satisfy operational or legal requirements. Signed-in users can request an export or start deletion of the shared Photo, Video, Music and MV studio from its account page, or for a Listen account from the app's account settings. Deleting a Creator account removes access across Web, Photo App and Music App, but does not delete a Listen account. Active studio creations must be resolved first. Deleted media is queued for physical object removal, the deleted account's active sessions are revoked, and its direct identity fields are removed. Deleting an account does not by itself cancel an Apple App Store or Google Play subscription; the user must manage that subscription with the store. Billing and audit records may be retained where required for fraud prevention, accounting, dispute handling, or law.

Service Providers

Stio may use infrastructure, storage, analytics, payment, authentication, email delivery, and AI processing providers to deliver the service. OmnAPI processes photo and music generation through Vidu and Suno; the configured video service processes MV generation. Uploaded references may be shared with those services using temporary private links. Providers receive only the data needed for their role and are subject to their own privacy terms.

Contact

Privacy questions and assisted requests can be directed to privacy@stio.ai. General support is available at support@stio.ai.

Technical diagnostics

Release builds send technical error reports to Stio to help diagnose failures. Reports contain a reference, app and platform, release and native build, error category, and compiled JavaScript locations or native binary identifiers and offsets. Operating-system reports may arrive after a restart or update. Reports exclude error messages, full stacks, URLs, device and account identifiers, prompts, and media. Up to 20 JavaScript reports may wait on the device for 24 hours, and up to 20 native reports for seven days. Server records become eligible for scheduled deletion after 30 days. This reliability reporting is separate from optional product analytics.

The website also samples loading, interaction and layout stability on 10% of page loads. Reports contain a random metric reference, a fixed page category, build version, viewport size group, navigation type and numeric measurement. They exclude full URLs, account or persistent visitor identifiers, page content and browser performance entries. Reports wait only in page memory for up to five minutes; server records become eligible for scheduled deletion after 30 days. Collection is disabled when the browser sends Do Not Track or Global Privacy Control. Network requests still expose an IP address for delivery and abuse limits. This website measurement is separate from the Listen app’s optional product analytics.

Release apps also sample the elapsed time from native initialization to the first root screen layout and foreground memory use. The default sampling rate is 10% of app runs and may vary by release. Reports contain a random measurement reference, app, platform, release and numeric value, without account or persistent device identifiers, content or boot timestamps. Each sampled process takes at most ten memory measurements, at least one minute apart. Reports wait only in memory for up to five minutes; server records become eligible for scheduled deletion after 30 days. Network requests expose an IP address for delivery and abuse limits. This reliability measurement is separate from optional product analytics.