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 explore the beginning of Glimzy without an account. 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 link. 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, native language, coarse English level, primary learning goal, English use context, topic interests, followed shows, favorites, episode progress, Vocabulary entries, and durable daily learning aggregates. The account record is associated with the verified account identity rather than a device-local identifier.
3. Data kept on your device
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, pronunciation data, 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.
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. Pronunciation requests may send the requested word. Preparing an episode may process its audio through transcription and private hosting/storage infrastructure. Glimzy may use Cloud Run, Supabase, and configured transcription, translation, pronunciation, and hosting providers to provide these features.
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, interests, coarse English level, learning goal, English use context, onboarding state, sync outcome, and coarse feature status. Onboarding does not ask for exact age or date of birth, and Glimzy does not record those fields for this profile. It is not used for advertising or cross-context behavioral advertising. These learning-profile categories are not shared with ad networks or used to build cross-context behavioral advertising audiences.
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.
Glimzy uses Mixpanel as its product-analytics provider. Before sign-in, an enabled device may have an anonymous install identity; after sign-in, product events may be associated with the verified Supabase account UUID. 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, raw feedback text, 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 legal site does not load Glimzy analytics, advertising tags, marketing cookies, or a data-collection form.
6. Shared transcripts, retention, and providers
Account data, access records, analytics, translation, pronunciation, and transcript-processing records are kept only as needed for the relevant feature, security, troubleshooting, accounting, or legal obligations. Transcripts and dynamic audio prepared through Glimzy may be stored as private shared technical assets so they can be reused by authorized learners; they are not owned by the first account that requests them. 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.
Providers may include the app store, RevenueCat, Podcast Index, configured translation and pronunciation services, transcription infrastructure, Supabase, Cloud Run, hosting/storage providers, 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. It does not delete shared transcript or audio assets that are not personal to that account, and 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, correction, restriction, deletion, 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.