Privacy Policy

1. Scope and who is responsible

This Privacy Policy applies to Ruscha Gaps (Android package app.qomus.compose) and related language-learning editions published by Muhammadyusuf Abdullayev that link to this page (together, the “App”). Muhammadyusuf Abdullayev is responsible for the App's privacy practices and is referred to as “we,” “us,” or “our.”

NoEasy.work hosts this page for us. The Ruscha Gaps App is separate from the NoEasy product available at the root of this domain.

2. Information the App processes

Accounts and sign-in

The App creates an anonymous Firebase Authentication account on first use so app services can identify the installation without requiring you to enter personal details. If you choose Google or Apple sign-in, Firebase and the chosen provider process your sign-in credentials and may provide us with a user ID, email address, display name, or profile image. Firebase Authentication also processes technical information such as IP address and user-agent data to secure sign-in and prevent abuse. We do not receive your Google or Apple password.

App configuration, analytics, notifications, and diagnostics

Firebase services may process Firebase installation identifiers, push-notification tokens, app/package/version information, device model, operating system, language, time zone, country or approximate location derived from IP address, app opens, sessions, and feature interactions. On Android, those interactions include onboarding progress; practice mode selection; microphone-permission outcomes; practice session starts, completions, and exits; session-level question totals, scores, percentages, and result bands; and paywall, offer, purchase, restore, and support-button outcomes. We do not send phrase or answer text, speech audio or transcripts, search queries, receipt or order identifiers, or raw error messages to Firebase Analytics. Android advertising ID collection and ad-personalization signals are disabled, although Firebase installation and app-instance identifiers and other technical data may still be processed. We use Remote Config to deliver settings and links, Cloud Messaging for transactional notifications, and Crashlytics for crash reports, stack traces, relevant app state, and device diagnostics.

When available, a notification token is associated with your Firebase user ID and sent to our backend so we can deliver messages such as payment confirmations. Notification display permission is controlled through your device settings.

Purchases and premium access

Purchases are processed by Google Play or Apple's App Store and managed for us by RevenueCat. These services may process a purchase token or receipt, transaction and purchase history, product, price, currency, store account context, premium entitlement, locale, and technical device information. We use your Firebase user ID as a RevenueCat App User ID so premium access can be restored to your account. We do not receive or store your full payment-card or bank-account details.

Microphone and speech recognition

Pronunciation practice requests microphone permission only when you select a mode that needs it. Your device's speech-recognition service may send captured audio to Google, Apple, or another recognition provider to produce a transcript. The App evaluates the recognized text for pronunciation feedback. We do not intentionally upload audio to our own servers, and we do not save recordings or transcripts in our database. The provider's handling depends on your device, operating system, language, and settings.

Information stored locally

Downloaded lesson content, favorite phrases, search history, study progress, onboarding status, practice limits, and preferences are stored locally on your device. They are not synced to your Ruscha Gaps account. Normal network request information, such as IP address and user agent, may be processed by Firebase when lesson content is downloaded.

Support and external services

If you contact us by email or choose the in-app Telegram link, we and the selected service receive the information you decide to send, such as your contact details, message, attachments, or transaction evidence. Telegram is a separate service governed by its own terms and privacy notice. Visiting these legal pages also causes Firebase Hosting to process standard web request information, including IP address, browser details, requested URL, and request time, for delivery, security, and abuse prevention.

3. How we use information

We process the information described above to:

• provide accounts, lessons, pronunciation feedback, preferences, and other App features;
• verify purchases, unlock premium access, and restore entitlements;
• deliver configuration, updates, and transactional notifications;
• understand feature use and improve reliability and performance;
• diagnose crashes, prevent fraud or abuse, and protect users and our services;
• answer support requests and comply with legal, accounting, or store obligations.

Where applicable law requires a legal basis, we rely on performance of our agreement with you, our legitimate interests in operating and securing the App, your consent for optional permissions or sign-in choices, and compliance with legal obligations.

4. Service providers and disclosures

We disclose information only as needed to operate the App, follow your instructions, protect rights and safety, or comply with law. Our principal providers are:

• Google and Firebase — authentication, hosting and content delivery, Remote Config, installations, analytics on Android, Cloud Messaging, and Crashlytics. See Firebase privacy and security and the Google Privacy Policy.
• Google Play and Apple — app distribution, payments, optional sign-in, and platform speech-recognition services. Their policies apply to their processing.
• RevenueCat — purchase validation, purchase history, and premium entitlement management. See the RevenueCat Privacy Policy.
• Telegram or your email provider — only when you choose to contact us through those external services.

These companies may use subprocessors and process information in countries other than your own. We do not sell personal information or display third-party ads, and we have not added an advertising SDK. In the Android App, Firebase Analytics advertising ID collection and ad-personalization signals are disabled. Firebase and the platform may still process app-instance, installation, and technical identifiers as described above.

5. Retention

Local learning data remains on your device until you delete it, clear App storage, or uninstall the App. Account and service data is kept only as long as reasonably necessary to provide the App, maintain security, resolve support requests, and meet legal, tax, accounting, fraud-prevention, and app-store requirements. Retention periods can vary by service and data type.

Developer-controlled notification tokens and account or support records may remain until we can identify and complete a deletion request; the current in-app deletion control does not remove them automatically. Crash, analytics, installation, and hosting records follow the retention and deletion controls of Firebase and Google. Store and purchase processors may retain transaction records when required by law or to prevent fraud, even after an account is deleted. After a verified request, we delete or de-identify the developer-controlled information we can identify unless it must be retained for the reasons above.

6. Account deletion and your choices

• Delete your authentication identity: open Profile in the App and choose Delete Account. The current control deletes only the Firebase Authentication identity; it does not automatically delete linked backend, purchase-profile, analytics, diagnostic, installation, or local learning data. A Google or Apple account may need to authenticate again. Continued or later use of the App may create a new anonymous identity.
• Delete local learning data: clear the App's storage or uninstall it. Local favorites, search history, progress, and preferences are not restored from your account.
• Delete other linked cloud data: send the request above so we can address developer-controlled notification, support, and purchase-profile records that are not removed solely by deleting Firebase Authentication.
• Control permissions: use device settings to revoke microphone or notification permission. Pronunciation or notification features may then stop working.

Some records may be retained where necessary for legal compliance, accounting, security, fraud prevention, dispute resolution, or proof of a purchase. Deletion of a Ruscha Gaps account does not delete your separate Google, Apple, Google Play, App Store, or Telegram account. Depending on where you live, you may also have rights to access, correct, object to, restrict, or receive a copy of personal information; contact us to exercise them.

7. Security and international processing

We use HTTPS and the security controls offered by our platform providers to protect data in transit and restrict service access. No system is perfectly secure, so we cannot guarantee absolute security. Google, Apple, RevenueCat, and their subprocessors operate globally, which means information may be processed outside your country under their contractual and legal safeguards.

8. Children's privacy

The App is a general-audience language-learning service and does not knowingly ask a child to submit personal information beyond what is needed to provide the features described in this policy. If you are a parent or guardian and believe a child provided personal information without appropriate permission, contact us so we can review and delete it. Parents and guardians should supervise children's use of optional sign-in, purchases, microphone features, and external support links.

9. Changes to this policy

We may update this policy when the App, our providers, or legal requirements change. We will post the revised version at this URL and change the effective date. If a change materially affects how we use personal information, we will provide additional notice where required.

10. Contact