1. Who we are
Glimzy is developed by Volodymyr Kobyletsky. For privacy questions or requests, contact volo@glimzy.app.
2. Accounts and sign-in
You can view the public Glimzy website and begin onboarding without an account. An authenticated account with a completed profile is required to use the app's product routes. To sync your learning data and subscription access across devices, you can create or access an account with Sign in with Apple, Google, or an email sign-in code. Glimzy uses Supabase Auth to maintain the sign-in session. Depending on the method you choose, the identity provider may provide a name, email address, or a private relay email address. Glimzy does not ask you to create a separate password for the current passwordless-email flow.
Account-backed data may include your profile and onboarding status, language preferences, followed shows, favorites, episode progress, Vocabulary entries, and durable daily learning aggregates. During setup, Glimzy asks for your translation language, your main goal with English, what you need English for, how much you currently understand, and optional show selections. The three questions use fixed answer choices, rather than free-form demographic information. These answers help order show suggestions; they do not restrict the full catalog or your access to features. Glimzy does not ask for or store a name of its own: the app shows the name supplied by Apple or Google when one is available, and otherwise shows "You". Language and question answers are stored with account preferences; selected shows are saved as followed shows. Signing in to an existing completed account restores that account's information instead of replacing it with an unfinished anonymous setup. The account record is associated with the verified account identity rather than a device-local identifier.
3. Data kept on your device
Before sign-in, Glimzy keeps your unfinished setup on your device, including your language, three answers, show selections, current step and notification-choice handoff. This lets you go back, cancel sign-in or reopen the app without losing your setup. Before verified sign-in, this unfinished setup stays local to your device, apart from eligible bounded analytics described below. After verified sign-in, existing language and followed-show synchronization may save those choices while setup finishes. The three question answers are committed by successful account completion; saved partial choices do not mark setup as complete. The setup draft is removed when account completion is confirmed or when existing account restoration discards the draft. Account sign-out, deletion and account-switch cleanup keep account data separate. A draft that has not been completed can remain on the device until it is cleared or the app's data is removed; Glimzy does not promise automatic deletion after a fixed number of days.
Glimzy keeps a local-first copy of supported account data so the app can remain useful during temporary connectivity problems. It may also keep disposable technical caches such as podcast feeds, prepared transcript and audio data, translations, and playback metadata. These caches are not a replacement for the account record and may be removed when you sign out, change accounts, reinstall the app, or when the app needs to recover storage.
To decide which episodes your account can open, Glimzy keeps on your device the last access state it verified with the server for your account: your plan, your preview episode, when your free week ends if your account has one, and the list of your free episodes. It does not keep a queue of listening intervals or other playback records for access. This cached state is cleared when you sign out, change accounts or delete your account.
You can remove device-only data by uninstalling Glimzy or clearing its app data, subject to platform backups and settings. Removing the app does not by itself delete account data; use the in-app Delete account control for that.
4. Data sent to services
To provide the app, Glimzy may send podcast search and feed requests to catalog providers such as Podcast Index. When you use translation, the selected word or phrase and necessary surrounding context may be sent to a configured processing provider. Preparing an episode may process its audio through transcription and private account-owned hosting/storage infrastructure. Glimzy may use Cloud Run, Supabase, and configured transcription, translation, and hosting providers to provide these features.
When you open Contact us, your conversation is handled by our support-chat provider, Crisp. Crisp receives the messages you write, your Glimzy account identifier, and bounded support context: support entry point, plan, app version, platform, app environment, coarse preparation and access state, and a random preparation reference that helps us find a technical problem. Glimzy does not attach transcript text, selected words or phrases, translations, audio, episode titles or source URLs to the conversation. Anything you choose to type yourself is received as written.
If you allow notifications, Glimzy registers your device's push token and platform with your account so it can tell you about new episodes with a reminder. Your account keeps the reminder setting (on or off), the reminder time Glimzy set when you finished setting up and the time zone your device reports, so that Glimzy can send at most one reminder a day at that time, and only when a show you follow has published a new episode that you have not started. The reminder names that show and episode, and your listening that day does not affect it. To find new episodes, Glimzy looks up recent episodes of the shows you follow with Podcast Index at the time the reminder is prepared. Reminders are delivered through Expo's push service and Apple Push Notification service. Reminders pause by themselves if you stop opening Glimzy. You can turn the New episodes reminder off at any time in Settings, or turn notifications off for Glimzy in your device settings. When you start a free trial of the subscription and notifications are allowed, Glimzy also schedules one reminder on your device for two days before the trial ends, with the trial end date and renewal price from the app store. This reminder is scheduled and shown by your device; no account, notification or analytics data is sent to Glimzy for it, and it is cancelled when Glimzy sees that the trial will not renew or when you sign out. The reminder setting, time and time zone are included in the supported export of your account data and are removed when you delete your account.
Earlier versions of Glimzy showed a listening streak, and Glimzy's account service still keeps the streak dates and streak-protection state that those versions derived from confirmed listening on your device. The current app no longer shows or updates them, and they stay with your account until you delete it. To rank shows and episodes in Discover, the service records at most one private popularity contribution for your account and an episode in each ranking period, after verified playback. Other learners see only aggregate rankings, never who listened. Streak records and Discover contributions, like your push-device registration, are included in supported account export and removed when you delete your account.
A new account gets a free preview: the first episode you open plays with its transcript and tap-translate for the first 5 minutes, and that episode keeps the same preview when you open it again. Other episodes play as audio only, and their transcript and tap-translate need a Glimzy subscription. When you open your first episode, Glimzy's account service records it as your preview episode: it stores a reference to the episode (the show and episode identifiers used to prepare it) and when it was recorded, together with your verified plan. Accounts that already had a free week before the preview was introduced keep it until it ends: for them, each episode opened during the week is recorded in the same way as one of your free episodes, and those episodes stay available after the week. The preview and the free week do not restart when you reinstall the app or sign in on another device. These records are necessary to provide the preview, the free week and your free episodes and are kept with your account. They are separate from product analytics: declining or objecting to product analytics does not remove your preview, your free week, your free episodes or subscription access. If product analytics is permitted, Glimzy may record that the preview started, that its audio reached 5 minutes, that an episode opened as audio only, or that a new episode could not be opened offline, as bounded categories. These events contain no episode identity or reference, media positions, transcript content, signed media URLs or provider details.
When you listen to an episode as audio only, the audio streams directly from the podcast's own host to your device, as in any podcast app. The host, and any advertising or measurement services it uses, can see your device's network address and app information. Glimzy's servers do not fetch or store that audio. Glimzy does not control how a podcast host handles this information, which is governed by the host's own policies. Glimzy does not send the episode, its audio address or its title to product analytics for audio-only listening; it records only that an episode opened as audio only.
Purchases and subscription status are handled through the applicable app store and RevenueCat. Product analytics is enabled by default in jurisdictions where Glimzy has documented a lawful basis for that processing and applicable law permits it. It may receive bounded events and technical or product dimensions such as app version, platform, language, plan, onboarding state, sync outcome, and coarse feature status. Eligible onboarding events may also include which setup step was viewed, the confirmed fixed-choice goal, need and comprehension answers, selected-show count, and up to 15 deduplicated catalog category identifiers. These bounded signals help us understand setup and show preferences. They do not include show names, show identifiers, descriptions or URLs. Glimzy does not collect a separate topic-interest questionnaire or free-form demographics in setup. Onboarding does not ask for exact age or date of birth, or for gender, and Glimzy does not record those fields for this profile. It is not used for advertising or cross-context behavioral advertising, and it is not shared with ad networks.
For product learning measurement, Mixpanel may receive coalesced confirmed podcast listening seconds, successful visible translation outcomes, bounded Vocabulary save/remove outcomes, and a once-per-device-local-day meaningful learning milestone. These records contain only bounded numbers, event kinds, surfaces, access plan, and outcome categories; they do not contain transcript text, selected words or phrases, translation results, episode identifiers, or source URLs.
After your first minute of listening, Glimzy may ask how your session was in a short in-app feedback sheet. If product analytics is permitted, Mixpanel receives whether you sent or closed the sheet, your 1–5 score, the reasons you tick, a listening-time bucket, and your access plan. The sheet also has an optional comment field. If you choose to write a comment and send it, that comment (up to 250 characters) is sent to Mixpanel exactly as you wrote it, so we can read it and improve Glimzy. It is the only text you type that Glimzy sends to product analytics. Please do not include personal information in it. Closing the sheet without sending never sends a comment.
Glimzy uses Mixpanel as its product-analytics provider. Before sign-in, an enabled device may have an anonymous install identity; after verified sign-in, product events from that journey may be associated with the verified Supabase account UUID. Mixpanel may also receive the name supplied by the verified identity provider and normalized email in its restricted user profile so the owner can recognize the account. If no provider-supplied name is available, the email may be used as the profile's human-readable label. These profile fields remain excluded from ordinary product event properties and event-wide properties. Glimzy does not ask you to type a name, so no name entered in Glimzy is sent to Mixpanel. An anonymous user remains unnamed until authentication is verified. The product analytics processing is separate from accepting the Terms of Use and acknowledging the Privacy Policy. Where Glimzy relies on legitimate interests, a person may object to product analytics and ask us to stop future account-linked events by using Contact us in Settings or emailing volo@glimzy.app. We will verify and process the request under applicable law, including stopping future account-linked product analytics where required. This request does not affect sign-in, synchronization, playback, translation, purchases, or account deletion. If a jurisdiction requires consent for a particular analytics operation, that operation will not be treated as covered by the Terms/Privacy acknowledgement.
If product analytics is permitted for the active release and a separate, dated environment approval exists, Mixpanel may derive coarse country, region, and approximate city from the event transport IP. This is provider-side IP enrichment: Glimzy does not request location permission, use GPS or an application location API, attach latitude/longitude or other coordinates, or persist or send the IP address. Approximate city is not precise location. The GeoIP switch is separate from listening-event dispatch and is disabled when the privacy state or approval is missing.
Glimzy does not use Session Replay and does not record or upload session-replay content.
EAS Observe may collect anonymous per-install startup, update, and performance metrics plus a small allowlist of operational milestones. Sentry may receive sanitized JavaScript/native crash diagnostics with release metadata. These operational diagnostics do not receive the account UUID, transcript or translation content, credentials, request bodies, or raw feedback. They are separate from product analytics and may remain enabled for service reliability where the disclosed build configuration and applicable law allow them.
5. What analytics and support do not receive
Glimzy's product analytics boundary excludes transcript text, selected words or phrases, translation results, audio content, source URLs, Vocabulary entries, receipts, credentials, free-text feedback (other than the optional comment described in section 4), GPS coordinates, precise location, and IP addresses. Support diagnostics use only bounded account and technical context when available; they do not include transcript text, selected words, translations, audio, source URLs, provider responses, credentials, or raw feedback text. This website does not load client-side Glimzy product analytics, advertising tags, marketing cookies, or a data-collection form. Hosting infrastructure may process standard request and security logs needed to deliver and protect the site.
6. Private transcripts, retention, and providers
Your fixed-choice setup answers are retained with your account while needed for the disclosed account and personalization features. Supported account export includes your question answers, and account deletion removes their owning profile and preference records, subject to applicable legal obligations. Account data, access records, analytics, translation, and transcript-processing records are kept only as needed for the relevant feature, security, troubleshooting, accounting, or legal obligations. Transcripts and audio snapshots prepared through Glimzy are private, account-owned learning assets and are not exposed to or reused by another learner. Access to private media uses short-lived authorization. Exact retention periods, locations, and international transfers depend on the active configuration and the policies of the service providers involved; we do not promise zero retention or a fixed global storage location.
Your preview, free-week and free-episode records are kept with your account until you delete it. Records from earlier versions of Glimzy's listening access (weekly, daily or bonus minute summaries, first-listening time and coalesced heard-audio ranges) are no longer used for access and are kept only as history with your account until you delete it; any remaining report acknowledgement metadata is removed by routine cleanup within 30 days. Supported account export includes your preview episode and your free episodes, with their episode references and when each was recorded, and any of these historical records. Account deletion removes them, subject to applicable legal obligations described in this policy.
Providers may include the app store, RevenueCat, Podcast Index, the podcast hosts that stream audio-only episodes, configured translation services, transcription infrastructure, Supabase, Cloud Run, hosting/storage providers, Crisp for support chat, Expo and Apple for push notifications, and analytics providers such as Mixpanel. Their current privacy policies and terms may also apply to the processing they perform.
7. Your choices and requests
Settings provides controls to open Account and Subscription, sync now, export your supported personal data, sign out, and delete your account. Account deletion removes the account profile, supported personal learning records, and sign-in identity, subject to records that must be retained for security, accounting, or legal obligations. It does not cancel an App Store subscription. You may contact us through the in-app Contact us path or email volo@glimzy.app to request access, request deletion of your account, access, correction, restriction, or an objection to future product analytics where applicable law provides those rights. We may need to verify the request and will respond within the deadline required by applicable law. Some requests may be limited by law, provider controls, or the fact that certain data exists only on your device.
8. Children and updates
Glimzy is not directed to children who are not permitted to use the app under applicable law. We may update this policy when the product or its data practices change. The latest version and date are always published here.
Contact: volo@glimzy.app. See also the Terms of Use.