Privacy Policy

Last updated: 2026-10-11. Clipra is provided by Noyan Çepikkurt. For privacy requests, you can reach cepikkurtnoyan@icloud.com.

Information processed

When you create an account, we process your email address, account id, the username you choose, and your display name. You can sign in with email and password, Sign in with Apple, or Sign in with Google. With Apple, we receive the name and email Apple shares (or Apple's relay address if you choose to hide your email); with Google, we receive the name, email address, and account id from your Google account. This information is only used to create your account and recognize you. Your guesses, scores, XP, badges, viewing history, likes, and duel records are stored to provide the game's features. For email/password sign-in, Firebase Authentication handles password verification.

Guest viewing history and preferences are kept on your device. If you sign in, your likes and the videos whose results you've already seen can be carried over to your account. The share button opens the system share sheet; you send to whatever destination you pick.

When you report a user or a video, the reason you chose, any note you write, and the username at the time of the report are kept for review. The list of accounts you've blocked is tied to your account and is only visible to you.

Visibility

Your username, display name, and weekly score may appear on the leaderboard; your duel details may appear to your opponent. Opting in to daily-opponent matching is optional. Your email is never shown to other players.

Service providers

We use Firebase Authentication for sign-in and account management (plus Sign in with Apple and Sign in with Google if you choose them), Cloud Firestore and Cloud Functions for game records, Firebase App Check and Apple App Attest for request security, Firebase Crashlytics for crash diagnostics, the Meta Platforms (Facebook) SDK for ad measurement, Firebase Analytics (Google Analytics for Firebase) for usage measurement, and Cloudflare R2 to serve video. These services may process your IP address, request timing, and technical security information. App Check processes information that verifies app and device integrity. Service data may be processed outside your country depending on each provider's processing locations. Details: Firebase privacy information, Apple Privacy Policy, Google Privacy Policy, Meta Privacy Policy, and Cloudflare Privacy Policy.

To verify purchases and subscription status we use RevenueCat; it processes Apple's transaction identifier and your access status, and does not process an advertising identifier. Details: RevenueCat Privacy Policy.

This version shows no in-app advertising, and does not use location, contacts, microphone, or camera access. To measure whether ads promoting the app are working, we use Meta Platforms' measurement SDK; its scope is described in "Ad measurement" below. Your advertising identifier (IDFA) is never read, and there is no cross-device tracking. Beyond that, we do not share personal data for advertising or sale purposes, and we do not sell your data. Notifications are optional, on-device reminders. Usage measurement does not read the advertising identifier (IDFA), and ad-related signals start turned off in the app.

Purchases

If you buy a Clipra Plus subscription or lifetime access, payment is taken by Apple; we only store, linked to your account, whether your access is active, its type, and (if any) its end date. We never see your card or payment details. Your purchase record at RevenueCat is associated with your Clipra account id.

Usage measurement

To improve the app, we measure which screens are shown and which buttons are tapped. This measurement sends only two kinds of events: a screen or component being shown, and a component being tapped. Each event carries only four short technical tags: a screen id (e.g. feed), a component id (e.g. choice), a content category if any (e.g. football), and a status tag if any (e.g. duel). These tags are fixed, English, human-readable abbreviations; they are not derived from the text shown on screen.

Your account id, username, display name, or email address are never attached to these events; this measurement is not linked to your account. Question text, choice text, the note you write in a report, your invite code, the id of the video you watched, and your score/XP values are never written into this measurement. The advertising identifier (IDFA) is not read, ad personalization and ad-related data-sharing signals start turned off, and the app does not request App Tracking Transparency permission. This measurement is only used to understand and improve app usage; it is never used for advertising or sale.

Measurement uses a random identifier specific to this app install (an app instance id) and device-level identifiers; this id becomes invalid once you uninstall the app. Firebase Analytics derives an approximate, city-level location estimate from your IP address; your device's location services are not used, and the app does not request location permission. Collection only happens in store-distributed release builds; it is off in development builds. Details: Firebase privacy information.

Crash and diagnostic records

If the app closes unexpectedly, a crash report is sent to Firebase Crashlytics so the issue can be found and fixed. This report includes the call stack at the moment of the crash, the app version, device model, OS version, language and region setting, available memory/storage, and a random identifier specific to this app install. Text you've written, your username, your email address, the id of the video you watched, and the content of your guesses are never written into a crash report. Because Analytics is enabled, the crash report includes a trail of your last steps before the crash (which screen you saw, which component you tapped, and the short technical tags described in "Usage measurement" above); that trail is also not linked to your account. Records are only used to improve app stability; they are not used for advertising, profiling, or tracking, and are not shared with anyone for those purposes. Collection only happens in store-distributed release builds; it is off in development builds. Details: Firebase privacy information.

Ad measurement

To promote Clipra, we may run app-promotion ads on Meta (Facebook and Instagram). To measure whether those ads are working, the app includes Meta Platforms' measurement SDK. What's sent to Meta: that you installed and opened the app, that you completed the walkthrough (the how-to-play steps), that you completed account registration, in-app purchase events (logged automatically by the Meta SDK), the app version, device model, OS version, language and region setting, IP address, Apple's vendor identifier scoped to this app only (IDFV), and an anonymous identifier specific to this install.

The advertising identifier (IDFA) is not collected. The app does not show iOS's tracking permission prompt and never accesses the advertising identifier, so no identifier that tracks you across other companies' apps and sites is created. Install attribution is done primarily through Apple's SKAdNetwork, where Apple itself produces the report and delivers aggregated counts that can't be tied to your device or identity to the ad platform. On Meta's side, only Aggregated Event Measurement is used.

What is never sent: your account id, username, display name, email address, guesses, scores, XP, badges, videos you've watched, likes, duel records, report/block information, the names of screens you navigate within the app, and your in-app interaction details are never sent to Meta. Sending a user identifier and advanced matching are both turned off.

Collection only happens in store-distributed release builds; it is off in development builds. To opt fully out of measurement, you can remove the app from your device or write to cepikkurtnoyan@icloud.com. How Meta processes this data: Meta Privacy Policy.

Retention and deletion

Account data is kept for as long as your account is open, to provide game features. From Settings → Delete Account, you can delete your account along with the associated profile, likes, personal guesses, leaderboard and duel records, your block list, and report records about you. Re-authentication is required for security. If you signed in with Apple, deletion also revokes the app's authorization on your Apple account. Your duel opponents' own scores, and aggregated answer counts not linked to a person, may remain.

Deleting your account does not cancel a Clipra Plus subscription; you cancel it in your Apple account (Settings > Apple Account > Subscriptions). Purchase records may continue to be kept by Apple and RevenueCat, separately from your account, where legal and financial record-keeping obligations require it.

Deleting your account is different from uninstalling the app: uninstalling does not delete your server-side account. A security record that prevents an old session from recreating your account, and that contains no raw account id, is marked for automatic deletion after 24 hours; infrastructure cleanup may complete afterward. Rate-limit records are kept briefly. Firebase states that removing deleted authentication data from live and backup systems can take up to 180 days. Infrastructure logs and backups are subject to each provider's own retention processes. Because crash records are never linked to your account, deleting your account does not make you identifiable through those records; they are deleted at the end of Firebase's own retention period for Crashlytics and are not kept permanently. Ad-measurement records are not linked to your account and contain no advertising identifier, so deleting your account does not make you identifiable through those records either; their retention and deletion follow Meta's own processes. Usage-measurement records are likewise not linked to your account, so deleting your account does not make you identifiable through those records; they are deleted at the end of Firebase Analytics' applicable retention period. Once you remove the app from your device, the app instance id becomes invalid, and a new install gets a new id.

Your choices and requests

You can change your profile and matching preference in the app, and turn off notification permission from device settings. For access, correction, deletion, and other privacy requests, you can write to cepikkurtnoyan@icloud.com. If you have a request regarding a child's data, you can reach the same address.

This website and support correspondence

These pages are hosted on GitHub Pages. GitHub may process connection information to serve the pages and keep them secure; the GitHub General Privacy Statement applies. No analytics or advertising script is added to these pages (see "Usage measurement" above for in-app measurement). When you email support, your address, message, and any attachments are processed to answer your request; never send a password or sign-in code.

Changes

If our data practices change, this text will be updated. Significant changes will be communicated appropriately.