Privacy Policy for MemoCards

Effective Date: August 23, 2026
Last Updated: August 23, 2026

Thank you for using MemoCards. This Privacy Policy explains what information MemoCards processes, how it is used, when it is sent to service providers, how it is protected, and how you can delete your MemoCards account and associated server-side data.

1. Data Stored Locally on Your Device

1.1 Personal Dictionaries and Learning Data

User-created or user-imported dictionaries, word lists, training state, learning progress, locally cached AI descriptions, app preferences, and similar learning content are primarily stored locally on your device.

MemoCards does not upload your personal dictionaries to our Firebase backend merely to provide cloud synchronization.

MemoCards uses Firebase Storage for application-provided content, such as dictionary/catalog files and tutorial or in-app media. This is different from storing your personal dictionaries in Firebase Storage.

1.2 Android Backup

MemoCards currently permits Android system backup. Depending on your Android version, device manufacturer, account settings, and backup configuration, Android or your device backup provider may back up or transfer some locally stored MemoCards data.

Such system backups are controlled by Android or the applicable backup provider and are separate from the MemoCards Firebase account.

2. Google Sign-In and MemoCards Accounts

Core local MemoCards functionality can be used without creating a MemoCards cloud account. The current MemoCards version does not intentionally create an anonymous Firebase Authentication account merely because the app is used without signing in.

If you choose to sign in with Google, MemoCards uses Google Sign-In and Firebase Authentication. Depending on the information made available through Google Sign-In, MemoCards may process:

This information is used for authentication, account display, purchase/subscription association, account security, and account deletion. MemoCards does not receive your Google password.

3. Purchases and Subscriptions

Purchases and subscriptions are processed through Google Play Billing. MemoCards does not receive your full payment card or bank account information.

To verify purchases and maintain account entitlements, MemoCards and its backend may process information such as:

Purchase verification may use Firebase Cloud Functions and the Google Play Developer API. Google Play maintains its own billing and transaction records under Google's terms and privacy practices.

4. AI Features

When you request an AI-generated word description or another AI operation, MemoCards sends the information necessary to perform that request to a MemoCards Firebase Cloud Function.

This may include the relevant word or phrase, language information, instructions, and other prompt context required to generate the requested content.

In the current privacy-hardened MemoCards release, AI generation is routed through our Firebase backend to Google Gemini.

Older MemoCards versions may have used other configured AI or translation providers, including OpenAI, DeepSeek, Google Gemini, or DeepL. Users are encouraged to keep MemoCards updated to the latest version.

MemoCards does not intentionally include your email address or Google profile information in the text prompt sent to the AI model.

You should not submit sensitive, confidential, or unnecessary personal information through AI input. AI-provider processing and retention are also subject to the provider's applicable terms and privacy policies.

Google Gemini API Terms: Gemini API Additional Terms of Service .

Google Privacy Policy: Google Privacy Policy .

5. Firebase and Technical Service Data

MemoCards uses services provided by Google/Firebase, including Firebase Authentication, Cloud Firestore, Cloud Functions, Remote Config, Firebase Storage, Firebase Cloud Messaging, Firebase Installations, and Firebase App Check.

Depending on the service being used, Google may process technical information needed to provide, configure, protect, or operate those services, including:

5.1 App Check and Play Integrity

MemoCards uses Firebase App Check with Google Play Integrity in production to help protect backend services against unauthorized clients, abuse, and fraud.

Google may process application/device integrity and attestation information for this security purpose.

More information about Firebase privacy practices is available at: Privacy and Security in Firebase .

6. Advertising and Privacy Choices

MemoCards integrates Google AdMob to display advertising.

The app uses Google's User Messaging Platform (UMP) to obtain and manage advertising/privacy choices where required. MemoCards only authorizes ad initialization and loading when UMP reports that ads may be requested.

Depending on your region, consent choices, device settings, and Google's advertising configuration, Google AdMob and advertising partners may process information such as:

MemoCards includes Android's Advertising ID permission because it integrates Google Mobile Ads. Availability and use of the Advertising ID depend on Android settings, Google Play services, applicable law, and your privacy choices.

7. Analytics, Crash Reporting, and Meta SDK

MemoCards contains integrations with Firebase Analytics, Firebase Crashlytics, and Meta/Facebook App Events.

In the current privacy-hardened release, optional Firebase Analytics collection, Firebase Crashlytics collection, Meta automatic initialization, Meta automatic app-event logging, and Meta advertiser-ID collection are disabled by default.

The current release does not provide an independent analytics opt-in that enables these optional telemetry systems. Advertising consent through UMP is not treated as consent to analytics.

Older MemoCards versions may have used analytics or diagnostic collection under their then-current configuration. Information previously transmitted to a service provider may remain subject to that provider's retention and deletion practices.

If MemoCards enables optional analytics or diagnostic collection in a future release, this Privacy Policy and any required in-app disclosures will be updated accordingly.

8. Notifications

MemoCards can provide local reminders and can use Firebase Cloud Messaging for remote notifications.

Firebase Cloud Messaging may process an app-instance or registration token and technical application/device information required to route notifications. Android may also request permission before MemoCards can display notifications.

You can manage notification permission through Android settings and available MemoCards notification settings.

9. Sensitive Device Permissions

The current MemoCards release does not request access to your precise location, contacts, microphone, camera, SMS messages, call logs, or broad all-files storage for its normal functionality.

10. How We Use Information

Information described in this Privacy Policy may be used to:

11. Service Providers and Disclosure

We do not sell your personal information.

We use third-party service providers where necessary to provide MemoCards features. Depending on the feature and app version, these can include:

We may also disclose information when required by applicable law, valid legal process, or when reasonably necessary to protect MemoCards, its users, or others against fraud, abuse, security threats, or unlawful activity.

12. Data Security

MemoCards uses reasonable technical and organizational measures designed to protect information handled by the service.

Current protections include HTTPS/TLS connections, Firebase access controls, authenticated backend operations where applicable, server-side purchase verification, and Firebase App Check / Google Play Integrity protection for supported backend functions.

No method of electronic transmission or storage can guarantee absolute security.

13. Data Retention

MemoCards server-side account records are retained while they are required to provide account, entitlement, purchase, or subscription functionality. They are deleted as described in the Account Deletion section unless retention is necessary for a legitimate legal, security, fraud-prevention, billing, or regulatory reason.

Local content remains on your device until you delete it, clear MemoCards application storage, uninstall the application, or it is removed through Android/device backup management.

Copies contained in Android or other device backups are controlled by the applicable operating-system or backup provider and its retention rules.

Google Play transaction history and service-provider security, operational, billing, and backup records are controlled by the applicable provider and may be retained according to that provider's legal and operational requirements.

14. MemoCards Account Deletion

If you created a MemoCards account using Google Sign-In, you can initiate account deletion inside the app:

MemoCards → Account Settings → Delete account

You can also request account deletion without having MemoCards installed by using our public Account Deletion page: Delete Your MemoCards Account.

A successful MemoCards account deletion removes:

If Google Play reports that a subscription is still set to auto-renew, MemoCards requires you to manage or cancel that subscription in Google Play before MemoCards account deletion can be completed.

Deleting a MemoCards account does not itself cancel a Google Play subscription.

When account deletion is completed inside the app, MemoCards also clears local account-linked subscription, entitlement, purchase-cache, and AI-description/regeneration state.

Personal dictionaries that exist only locally on your device are intentionally preserved because they are not MemoCards cloud-account data. You can delete those dictionaries inside the app, clear MemoCards application storage, or remove them through the applicable Android storage/backup controls.

15. Your Choices and Rights

Depending on your location, applicable privacy law may provide rights such as access, correction, deletion, restriction, objection, portability, or withdrawal of consent.

You can contact us using the email address below. We may request reasonable verification where necessary to prevent unauthorized access to or deletion of another person's account.

Advertising/privacy options made available through Google UMP can be revisited through MemoCards where required. Android also provides device-level controls for notification permissions, advertising identifiers, application storage, and device backups.

16. Changes to This Privacy Policy

We may update this Privacy Policy when MemoCards features, service providers, or legal requirements change. The latest version will be published on this page with an updated effective or last-updated date.

17. Contact

For privacy questions, data requests, or account-deletion assistance:

Email: Tolkien2007@yandex.ru

MemoCards