Privacy Policy
Last updated September 23, 2026
This policy explains the information Synchr processes to provide listening, account, subscription, and optional AI voice features.
1. What we collect
If you join our website waitlist, we store your email address, signup time, signup source, and an anonymous browser identifier in Cloudflare D1 to manage the waitlist and contact you about Synchr. A cookie stores the browser identifier. Contact us to have your waitlist entry removed. We use Cloudflare Turnstile to protect the signup form from automated abuse; see the Cloudflare Turnstile Privacy Addendum.
Synchr processes the following information when you use the corresponding feature:
- Your voice — microphone audio captured during the voice interaction.
- Voice conversation content — transcribed speech, conversation history, and generated reply text.
- Episode context — the feed URL, episode identifier, episode transcript and related publisher context, and your current playback position.
- Account and purchase information — Synchr uses Firebase phone authentication to verify your phone number and establish your account. We process your verified phone number, Firebase user identifier, Synchr account and RevenueCat customer identifiers, subscription transactions, credit balances, allowances, and account status.
- Your library and searches — followed feeds, saved episodes, lists, queue and playback progress are stored with your account in Firestore. Search text goes to our search service and its search provider. Synchr does not maintain a server search-results cache or an account search-history feature. Provider processing and infrastructure request logs have separate handling.
- Installation and service information — app-installation identifiers, App Attest verification material, voice usage, and service events needed to secure the service, enforce allowances, and diagnose failures.
- Product analytics — when Product analytics is enabled, Synchr collects an app-installation identifier, event timestamps, feature and screen interactions, search result counts, feed-refresh outcomes, followed and saved status, feed and episode identifiers, playback position and rate, and AI voice-session start method, duration, and end reason. Product analytics does not include search text, feed or episode titles, microphone audio, voice transcripts, conversation content, or generated answers.
2. How it is collected
Live microphone audio and voice conversation data leave your device when you start a voice session — by tapping the microphone button, saying “Hey Pod,” or pressing your AirPods stem — and only after you have granted consent through the in-app permission prompt, which identifies the exact data, recipient, and purpose. Selecting Not Now or dismissing the prompt sends nothing for an AI voice conversation. When the session ends, live microphone transmission stops.
If you turn on Voice commands, Synchr keeps microphone capture active while the app is running so voice mode can start instantly. Nothing from it is recorded or sent while you are not in a session. The audio is checked on your device by a bundled speech model listening for “Hey Pod,” “play” and “pause”; the audio it checks is not stored and does not leave your device. You can turn Voice commands off in Settings; when it is off, microphone capture starts only for a voice session. You can revoke microphone access at any time in iOS Settings.
Product analytics is processed automatically as you use the corresponding app features while the Product analytics setting is enabled. Depending on your region, it is either enabled by default with an opt-out or remains off until you enable it. You can change the setting at any time in Settings → Privacy. Synchr assigns a random identifier to the app installation so related events can be processed together; analytics may also be linked to your Synchr account when you are signed in. Product analytics currently remains on your device. Synchr may send it to its servers when server-side analytics becomes operational.
3. How it is used
Library backup, search, episode preparation, account and subscription requests also communicate with our services outside voice sessions. Required billing, security and server diagnostics continue independently of optional on-device Product analytics and diagnostics settings.
Voice conversation data and episode context are used to transcribe speech, generate answers about the episode you are listening to, and create spoken replies. Account, purchase, installation, and usage information is used to authenticate access, provide subscriptions and allowances, prevent fraud, secure the service, and meet accounting and legal obligations. Synchr does not use this information for advertising or cross-app tracking.
Product analytics is used to understand feature usage, reliability, listening behavior, and AI voice usage; improve Synchr; and measure playback and engagement. Publisher distribution is not currently enabled. Search text and conversation content are not part of optional Product analytics. Separately, retained voice content may be reviewed to evaluate and improve AI voice.
4. Third parties we share data with
- Deepgram receives live microphone audio and necessary request metadata during an AI voice conversation to convert the listener’s speech into text.
- Google Cloud Vertex AI (Gemini) receives conversation text, relevant episode context, the episode transcript or excerpts needed to answer, the listener’s playback position, and necessary request metadata to generate an AI response.
- ElevenLabs receives generated response text and necessary request metadata to create spoken response audio.
- Apple processes Sign in with Apple and App Store subscription information when you use those features.
- Google Firebase and Google Cloud provide authentication, Firestore library storage, our servers, Postgres databases, private recording storage and operational logs. Authentication and service requests also involve technical information such as IP addresses under the providers’ terms. Phone numbers provided for authentication are sent to and stored by Google to improve spam and abuse prevention across Google services, including Firebase. Phone verification sends an SMS to your number; standard SMS rates may apply. Your phone number is not published to other Synchr users.
- RevenueCat processes subscription transactions and an opaque customer identifier associated with your Synchr account to validate purchases, manage entitlements and provide purchase analytics.
- Feed publishers receive ordinary network requests when your device loads their feeds or media. A producer transcript-reading service and publisher analytics distribution are not currently enabled. Before enabling new sharing, we will describe recipients, access, purposes and choices and obtain any required consent. Synchr may internally review conversations to evaluate and improve AI voice.
Synchr requires service providers that receive personal data to protect it to the same or an equivalent standard as this policy and applicable law. We do not permit them to use it for their own advertising.
5. Retention
Synchr stores AI voice microphone audio, generated audio, and conversation content until they become eligible for automatic deletion at 30 days. Scheduled database cleanup and object-storage lifecycle processing then remove them; completion is not guaranteed at the exact 30-day boundary. These records are kept in private storage to operate, diagnose, evaluate, and improve AI voice. Account deletion is a request to remove account information and retained voice content, not a promise that every copy disappears immediately. Transaction, usage and anti-abuse records may remain for security, accounting, dispute resolution or legal obligations; an opaque identifier does not itself make them anonymous. Deletion removes linked sign-in information and requests deletion of the RevenueCat customer record without cancelling an Apple subscription. Completion is shown in the Account view after the service confirms erasure. Financial transaction identifiers may still be linkable through store records and are not described as anonymous. Minimal used-device anti-abuse state is retained without the deleted account link. Cached library bytes may remain on your device, but deleted-account writes are blocked by the server. Backups, operational logs and provider-held copies have separate retention and deletion processes. Deepgram, Google Cloud Vertex AI, and ElevenLabs may temporarily retain request data for safety and abuse prevention under their business-service terms and configured retention controls.
Product-analytics records are retained only for as long as needed for the uses described above. Turning Product analytics off stops new processing and clears analytics waiting on the device. Settings → Privacy → Delete collected data clears analytics on the device and assigns the installation a new identifier. If server-side analytics is operational, you may request deletion of analytics received by Synchr by contacting support@interactivemedia.xyz. Synchr may retain aggregated or de-identified statistics that no longer identify an installation or account.
6. Your choices
You may withdraw AI voice permission at any time in Settings → Privacy → AI Voice Data. Withdrawing permission ends an active AI voice conversation and prevents future sessions from starting; it does not delete data already retained. You can delete your account or contact support to request deletion. You can also revoke microphone access in iOS Settings. You can disable Product analytics or request deletion of collected analytics in Settings → Privacy. Account deletion is available from account settings. For another data request, contact support@interactivemedia.xyz.
7. Children
Synchr is not directed to children under 13.
8. Contact
Questions or removal requests: support@interactivemedia.xyz. Material changes to this policy will be reflected in the “Last updated” date above.