Privacy Policy
Effective October 1, 2026. Contact: hello@tapston.com.
1. Scope, controller, and contact
This Privacy Policy explains how information is processed when you use Flashcards and its related services. The controller is the provider of Flashcards identified on the app-store listing. In this Policy, "we," "us," and "our" refer to that provider. For privacy questions, complaints, or rights requests, email hello@tapston.com.
2. Categories and sources of information
We receive information directly from you when you register, edit your profile, create cards, submit feedback, request an AI memory aid, or contact us, automatically from the app, device, Firebase and Meta SDKs, and hosting infrastructure, and from Apple or a sign-in provider when you authenticate or make a purchase. Categories include contact information, identifiers, user content, preferences, study activity, purchase and entitlement information, approximate location, usage information, diagnostics, security and attestation data, and support communications. Free-form fields can contain information you choose to enter. Do not include sensitive, confidential, regulated, or third-party personal information unless necessary and lawful.
3. Account and profile information
Firebase Authentication processes your email address, authentication-provider information, account identifier, verification status, and, when provided, your display name. Google Sign-In or Sign in with Apple also processes information that provider returns under the permissions you approve. We use this information to create and secure your account, sign you in, link sign-in methods, synchronize your data, and support account recovery and deletion.
4. Cards, settings, progress, and feedback
Your words, translations, set names, selected languages, profile name, goals, reminder settings, study progress, and synchronization metadata are stored locally for the signed-in account and synchronized with Cloud Firestore. Unsynchronized changes may remain only on the device and can be lost if the app or its storage is removed. If you tap Send in the feedback form, the message, category, request identifier, and account identifier are sent through Firebase and made available to the Flashcards team. A feedback draft otherwise remains in the open form until you close or send it. In mobile versions that include device-state reporting, the app also saves a private latest-known device snapshot under your account for service diagnostics when Firebase analytics is enabled. This includes a random device identifier, reminder and Random Words settings, system notification-permission status, local word count, library synchronization-pending status, and revision and update metadata. It does not include card content or notification schedules. Turning off Firebase analytics replaces prior snapshot metrics with the collection choice and synchronization metadata once the request succeeds. This device snapshot is not sent to Meta.
5. Purchases
Apple processes payments and may act as an independent controller under its own terms. Flashcards receives and stores the subscription product, entitlement status, expiration information, an app-specific account token, and transaction or notification identifiers needed to verify, restore, and protect purchases. We do not receive your full payment-card details.
6. Analytics and crash diagnostics
Google Analytics for Firebase is enabled by default in regular app builds. It collects app lifecycle and usage information such as first launches, app opens, sessions, screen views, app updates, and in-app purchase events, together with app-instance identifiers, app version, operating system, device model, language, and approximate location derived from a masked IP address. We also send product events about creating and editing cards, using sets, study and review sessions, card outcomes, goals, reminders, and notification opens. These events contain random card and session identifiers, device-salted set identifiers, fixed action labels, and numeric counts or durations. We set the internal Firebase Auth account UID as the Analytics user ID to measure usage across sessions and devices. We do not send card text, translations, set names, mnemonic content, recognized text, audio, feedback, email addresses, passwords, or payment details to Analytics. You can turn off Firebase Analytics in the app settings. When off, we disable Analytics collection and stop sending product events. Firebase Crashlytics separately collects crash stack traces, exception information, relevant application state, timestamps, app and OS versions, device model and technical state, Crashlytics and Firebase installation identifiers, session information, and available Analytics breadcrumbs immediately before a crash. We use it to diagnose crashes and improve reliability. We do not set a Crashlytics user ID or add custom Crashlytics keys or logs. Analytics and Crashlytics collection are disabled in demo builds. Crashlytics collection is disabled in debug builds. Firebase advertising storage and advertising-personalization signals are disabled. We do not link Firebase Analytics data to advertising destinations or use it for cross-app advertising profiles. Meta app measurement is a separate data flow described in section 7.
7. Meta app measurement
Mobile versions of Flashcards that include the Meta (Facebook) SDK send app events to Meta to measure the performance of Flashcards advertising. This measures promotion of Flashcards and does not display third-party advertisements inside the app. Automatic event collection is enabled by default after the app reads the saved device preference. Events can include installation activity, app launches, and eligible purchase or subscription activity. The SDK may also report trial activity if an applicable store offer is available. This does not create a trial or change the purchase terms shown by the store. Custom events record completed registration, card creation, completed learning sessions, and completed daily goals without additional event parameters. The SDK also processes its installation identifiers, app and operating-system versions, device information, event timestamps, and technical network information such as the IP address used to connect to Meta. We do not pass card text, translations, set names, mnemonic content, audio, feedback, email addresses, Firebase account identifiers, or other account details to Meta. IDFA and Android advertising ID collection are disabled. We do not request App Tracking Transparency permission, set a Meta user ID, or enable advanced matching. We configure the SDK to limit event-data use to analytics and conversion measurement. These settings do not make SDK data anonymous or mean that no identifiers are collected. On supported iOS versions, the SDK can use Apple's SKAdNetwork for installation and conversion attribution. Meta measurement is controlled separately from Firebase analytics. You can disable future automatic and custom Meta event collection in Settings → Privacy and Data → Meta advertising. The choice is saved on the device and does not affect study features or your subscription. Disabling collection does not recall events already sent or a request already in flight, and does not automatically erase information Meta already holds. Meta processes received information under the applicable Meta Business Tools Terms and its Privacy Policy: Meta Privacy Policy.
8. Security and service metadata
Firebase App Check processes device or app-attestation assertions and related tokens to verify genuine requests and reduce abuse. Firebase and Cloud Functions process technical request metadata such as the called function, IP address, app and SDK versions, device platform, and user-agent information to provide, secure, troubleshoot, and maintain the service. Firebase Hosting processes request IP addresses and technical logs for delivery, abuse detection, and operational analysis. Google states that Hosting retains IP data for a few months. These systems may generate rate-limit, authentication, fraud-prevention, and audit records.
9. AI memory aids
When you explicitly request an AI memory aid, the selected word or phrase, its translation, and selected languages are sent through a Cloud Function to OpenAI. Your email address and the rest of your library are not included. OpenAI responses are requested with response storage disabled. OpenAI states that API data is not used to train its models unless the customer opts in, but its default abuse-monitoring logs may contain prompts and responses and may be retained for up to 30 days, or longer when legally required. The completed aid may be saved on your device and in a shared server cache so an identical normalized language pair can reuse it. The cache is not publicly readable and is not keyed to your account. Do not include personal, confidential, regulated, or proprietary information in an AI request.
10. Device permissions and on-device processing
Microphone, speech-recognition, and notification access is requested only when you use the related feature. Audio used for speech recognition is processed on the device and is not uploaded by Flashcards to Firebase or OpenAI. You can review recognized text before saving it. Study reminders are scheduled locally and cancelled on sign-out. You can change permissions in system settings, and refusing a permission does not prevent typing cards manually or studying. We do not collect precise location, contacts, health or fitness data, payment-card details, browsing history, or advertising data through these features.
11. Purposes and legal bases
We process information to provide accounts, synchronization, study features, support, purchases, and requested AI memory aids, authenticate users and prevent abuse, maintain security and reliability, diagnose crashes, understand product use, measure the performance of Flashcards advertising, enforce terms, protect legal rights, and comply with law. Where a legal basis is required, account, content, purchase, and requested-feature processing is necessary to perform our contract with you. Security, fraud prevention, support, service improvement, and analytics rely on our legitimate interests where those interests are not overridden by your rights. Legal records are processed to comply with law and establish or defend claims. We rely on consent where required by applicable law, including for advertising measurement or access to device information where applicable. A default setting or acceptance of the Terms of Use does not replace consent when the law requires it. We do not use solely automated decision-making that produces legal or similarly significant effects.
12. Service providers, disclosures, and transfers
We use Google Firebase for authentication, App Check, database synchronization, server functions, analytics, crash reporting, and hosting, Apple for subscriptions and Sign in with Apple, Google for Google Sign-In, OpenAI for requested AI memory aids, and Meta for app advertising measurement as described in section 7. Providers may act as processors or independent controllers depending on the service and applicable terms. We may also disclose information to professional advisers, authorities, or transaction counterparties when reasonably necessary for legal compliance, safety, enforcement, or a legitimate corporate transaction, subject to appropriate safeguards. Cloud Firestore and Cloud Functions are configured in europe-west1, but providers, including Meta, may process information in other countries using their applicable transfer safeguards. We do not sell your cards or account information or provide them to advertisers or data brokers. We do disclose SDK events and technical identifiers to Meta for advertising measurement. Some privacy laws may classify certain advertising-related disclosures as sharing even when no money changes hands. The available choices and rights are described in sections 7 and 14.
13. Retention and deletion
Account information, synchronized cards, settings, progress, and entitlement records are kept while your account is active and then deleted through the in-app deletion flow, unless longer retention is reasonably necessary for security, fraud prevention, disputes, or law. Submitted feedback is queued for automatic deletion after 90 days. AI memory-aid cache records are queued for automatic deletion after 180 days and, because they are not keyed to your account, are not deleted with the account. Apple server-notification deduplication records are queued for deletion after 30 days, and a completed account-deletion marker after 7 days. Automatic deletion may occur after the stated period rather than at its exact end. Google states that Crashlytics keeps crash traces and associated installation identifiers for 90 days before beginning removal from live and backup systems. Google Analytics retains user-level and event-level data according to the Analytics property setting. Aggregate reports may remain longer. Provider security logs, fraud-prevention records, and backups follow provider schedules and may persist for a limited period after deletion. Account deletion removes local account data only from the device used to request deletion and does not cancel an Apple subscription. Meta retains information it receives according to its applicable policies, processing purposes, and legal obligations. We do not set a fixed retention period for Meta-held data. Deleting your Flashcards account does not automatically recall events already sent to Meta. You can disable future Meta collection through the separate advertising switch and contact us about access or deletion requests.
14. Your privacy rights
Depending on where you live, you may have rights to know or access information and processing details, correct, delete, restrict, or object to processing, receive a portable copy, withdraw consent, opt out of sale, sharing, targeted advertising, or certain profiling, appeal a denied request, and complain to a regulator. You can disable future Meta app measurement through the separate advertising switch in section 7. For any additional applicable objection, consent-withdrawal, sale or sharing opt-out, or deletion request, contact us using the address below. Turning off Firebase Analytics alone does not turn off Meta measurement. We will not unlawfully discriminate against you for exercising a right. Email hello@tapston.com to submit a request or appeal. We may verify your identity, account, or authorized agent, respond within the period required by law, and retain limited records of the request where permitted. Withdrawing consent does not affect earlier lawful processing.
15. Children
Flashcards is a general-audience service and is not directed to children under 13. We do not knowingly collect personal information from a child under 13 without legally sufficient parental authorization. If local law sets a higher age for independent consent, a parent or legal guardian must provide any required authorization and supervise use. If you believe a child has provided personal information contrary to this section, email hello@tapston.com. After appropriate verification, we will take reasonable steps to delete it. Do not use Flashcards in a manner inconsistent with the age rating or children's-privacy settings shown in the applicable store.
16. Security and changes
We use access controls, encrypted transport, App Check, least-privilege rules, rate limits, and data-minimization measures designed to protect information. No transmission, storage, or security system is completely secure, so we cannot guarantee absolute security. You are responsible for protecting your credentials and device. We may update this Policy when practices, providers, features, or legal obligations change. We will update the effective date and provide additional notice or obtain consent when required for a material change. Earlier versions may be retained for compliance records.