Privacy Policy

Information processed

• Account and sign-in information:identifiers and sign-in information handled through WorkOS so ListenFlow can authenticate your account.
• Material you submit:text, article and RSS URLs, audio imports, titles, rewriting instructions, and the settings used to create an episode.
• Library and playback information:item status, listening and feed-inclusion choices, generated audio, transcripts, and usage totals.
• Provider and storage settings:provider, model, and voice selections; encrypted provider credentials; private feed information; and connections you choose to make to external storage.
• Support correspondence:the email address and information you include when contacting support.

How information is used

• To authenticate your account and operate your library, private podcast feed, and playback.
• To extract or prepare material you ask ListenFlow to turn into an episode, and to generate audio or transcripts.
• To apply usage limits, protect the service, troubleshoot failures, and respond to support requests.
• To store or archive content in a destination you explicitly connect.

When information is shared

• Infrastructure:ListenFlow runs on Cloudflare Workers and uses Cloudflare D1, R2, queues, and related services to operate the application and store service data.
• Authentication:WorkOS processes sign-in and account authentication.
• Generation providers:When you request generation, the relevant source material is sent to the language and/or speech provider selected for that work. Provider privacy terms and retention rules also apply. If you provide your own API key, the provider may associate usage with your provider account.
• Connected storage:If you connect Google Drive or an S3-compatible destination, the artifacts you choose to archive are copied there under that provider account.
• Podcast apps:If you add your private feed URL to Apple Podcasts or another player, that app fetches the feed and audio. Anyone with the private feed URL may be able to access its episodes.
• Information may also be disclosed when required by law or to protect the service and its users.

ListenFlow does not need your full chat history. It processes the material and settings explicitly submitted for a task.

Storage and retention

• Library items and their source material remain in your ListenFlow library until you delete them. Deleting an item removes its database record and ListenFlow-managed R2 objects. Copies you archived to your own Drive or S3 account remain under that provider until you remove them there.
• Provider credentials are encrypted at rest and retained until you delete them. ListenFlow API-key tokens are shown once; the service stores a hash rather than the recoverable token.
• When an artifact has another verified storage copy, an expired Cloudflare R2 hot copy may be removed under the storage-retention process. The service avoids evicting the only verified copy.
• Operational records needed for security and service reliability, support emails, and records held by infrastructure or generation providers may be retained under the relevant service configuration and provider policies. ListenFlow does not currently publish one fixed expiry period covering every such record.

Your controls

• Delete individual episodes or listened episodes from your library.
• Delete saved provider credentials, revoke ListenFlow API keys, and disconnect storage providers in the app.
• Ask the developer to help with account-level access or deletion requests. ListenFlow does not currently provide a self-service account-deletion control.

For privacy or data requests, emailsupport@kunkun.sh.Please do not send passwords, API keys, or private feed URLs.

Cookies and contact

The website uses an essential sign-in session cookie. The cookie is configured for up to 400 days; actual session validity may also depend on WorkOS session rules. The service does not use this cookie to advertise to you.

Questions about this policy? Contactsupport@kunkun.sh.