Your listening life belongs to you.

Information in SoundAnew

What the product can store.

• Account informationEmail address, authentication records and the display name you choose.
• Listening preferencesDefault intention, preferred format, duration and optional digest preference.
• Your LibraryFavorites, playlists, listening progress, recent sessions and completion state.
• Personalized briefsThe intention, voice, atmosphere, duration, session name and private notes you save.

When the secure account connection is not configured, the published preview uses representative data and does not persist edits made through those controls.

How information is used

Only to provide the listening experience.

Account data is used to authenticate you, restore your Library, resume audio, display listening insights and manage personalized briefs. SoundAnew does not run advertising trackers or sell personal information. When paid Plus access is activated, SoundAnew stores payment status and access dates but does not receive or store full card details.

Infrastructure

Service providers process limited data for us.

Supabase provides authentication and private structured records, while Cloudflare-backed Sites and object storage deliver the application and audio. The prepared Plus checkout uses PayTR’s hosted payment screen; PayTR receives the billing and card information needed to process, secure and report a transaction. These providers may process technical request information needed to operate and secure their services.

Your choices

Control stays close to the data.

You can remove favorites, playlist items, playlists and personalized briefs from the relevant product screens. You can change profile and listening defaults in Account, where you can also download a readable copy of your account, Library, listening, reflection and membership records. A verified account-deletion workflow will be added before public account activation.

Retention and security

Keep only what the product needs.

When cloud sync is activated, user-owned records are retained while the related account exists or until the listener deletes them. Database ownership rules restrict private records to their authenticated owner. No privileged service key is exposed to the browser.