MotMatch Privacy Policy
Effective date: (UTC)
Using an earlier MotMatch version? Read the previous public notice.
Who is responsible
MotMatch is operated by Na Fang, based in Vancouver, British Columbia, Canada. In this policy, “we” means Na Fang operating MotMatch. For privacy questions or requests, contact support.easystart@gmail.com. Our website is motmatch.easystart.app.
This policy covers MotMatch V2 for Android and iOS, its account and game services, and support communications. Cloudflare handles delivery and protection of our website and can process request information such as IP addresses. This policy does not describe a previous version's data practices. MotMatch is a language-learning game and is not specifically directed to children. Formal accounts require confirmation that you are at least 16. Without that confirmation, only accountless local Practice is available.
Information and purposes
| Information | Why we process it |
|---|---|
| Verified email, sign-in-provider account information, authentication-provider identifiers, account/player identifiers, and session/security information | Create and secure your account, sign you in, link eligible login methods, and send account verification, welcome or password-change messages. Email passwords are handled by the authentication service; never send them to support. |
| Language choices, settings, chapter progress, cards, Book access, Coffee, in-game Cookie balances and owned digital entitlements | Provide the game, save account progress, and synchronize the same MotMatch App account between Android and iOS. “Cookie” is also the name of our in-game currency; it does not mean a browser tracking cookie. |
| Minimal formal-run records | Maintain and improve account gameplay: run/chapter identifiers, platform/build, duration, result/reason, unlock source, reward placement/result, fallback use and optional tool-use counts. Formal runs also include the difficulty actually used (opening types, held-back groups, reveal pacing, copies and vocabulary size, configured time and easing), final completion ratio and remaining time, recovery-use and revealed-item counts, the two app language codes used for that run and its content manifest version. We use these run attributes for analytics and product improvement. These records are account-linked, not anonymous analytics. |
| Product and store transaction identifiers, purchase verification material, purchase status, grants and reversals | Validate purchases, restore eligible entitlements, prevent duplicate grants and handle revocations. Your store processes payment details; MotMatch does not ask you to enter card details into the game. |
| Reward tickets, operation identifiers, ad-unit and ad-transaction identifiers, verification times and claim results | Associate an earned reward with the correct account and verify it without granting it twice. |
| Network request information and operational diagnostics processed by our service providers | Deliver requests, protect the service and investigate faults. This can include IP addresses and technical logs. |
| Failed purchase/restore diagnostic time, platform, catalogue product, stage/reason, Apple environment, current player link and hashed transaction reference (server); bounded local queue counts and owner-match booleans (client) | Investigate purchase faults and provide customer support. These diagnostics contain no receipts, tokens, payment details, store-account identifiers or free-text store errors. Local entries are only sent if you send the prepared feedback email. |
| Emails and attachments you choose to send us | Respond to support and privacy requests and verify ownership when needed. |
Google sign-in can also supply a name and profile-image reference, which our authentication service stores with the sign-in identity. These are not a public MotMatch profile or access to your device photo library.
Practice does not create a formal account or upload formal-run records. The formal-run record does not contain the full board, every tap or movement, sharing recipients, specific ad contents or text you enter. This limitation describes our run-history feature, not the separate data processed by an advertising SDK.
Advertising and privacy choices
Android and iOS can offer optional rewarded ads for Coffee, tools (Undo/Shuffle/Vacuum), Revive and Extra Time. Google AdMob and its advertising services may process IP-derived approximate location, device or advertising identifiers, ad views/interactions and diagnostic/performance information for ad delivery, measurement, fraud prevention and, where allowed, personalization.
On iOS, tracking for advertising requires your permission through Apple’s App Tracking Transparency prompt. If you allow it, Google AdMob and its advertising partners may use your device’s advertising identifier to link information from MotMatch with information from other companies’ apps and websites to personalize ads and measure advertising. If you do not allow tracking, you can still use MotMatch, and we may request ads without that tracking; ad availability can vary. You can change this permission in your device’s Settings under Privacy & Security → Tracking. This Apple permission is separate from the advertising privacy choices described below, which also continue to apply.
MotMatch supplies a reward ticket reference and operation identifier to Google for reward verification. Our backend associates that ticket with your account. The custom verification data does not include your email, password or full MotMatch player identifier. These references are not anonymous to our backend.
Advertising choices are separate from the information needed to run an account. Where applicable, Google's User Messaging Platform presents privacy choices. When the privacy-options entry is available, open Profile → Privacy & help → Ad privacy options to review them. Device settings also provide advertising/tracking controls. Refusing personalization may still permit non-personalized or limited ads; ad availability is not guaranteed.
Learn about Google's use of data from partner apps and Google's privacy policy. Ad partners may process information under their own policies and the choices shown to you.
Who receives information
Supabase provides account authentication, databases and server functions. Apple and Google provide their respective sign-in and store services; Google provides AdMob/UMP and reward verification. Resend delivers welcome messages; Google Gmail handles messages sent to our support address. The authentication service and its configured mail-delivery provider handle verification and password-related messages. We disclose information needed to operate those services. Providers may also have independent purposes described in their notices. We may disclose information when required by law or necessary to address fraud and protect rights.
Provider references: Supabase, Apple, Google, Resend, and Cloudflare.
The advertising choices shown to you identify applicable advertising partners. Advertising disclosures can fall within regional definitions of selling or sharing personal information even when money is not exchanged for the data. Where an applicable privacy message offers an opt-out, use it to change those choices. You may also contact us about rights available where you live.
Storage, retention and security
Account and saved-game data is kept while needed to provide your account. Raw account-linked formal-run records are kept for up to 90 days; after that, any retained run-history aggregates must not contain player identifiers. Reward verification records and purchase records support account reconciliation, restoration and prevention of duplicate grants. A reward ticket's short validity period is not a deletion schedule for those records.
Language-pack ownership can move after an explicit Buy or Restore. Each move records its time, pack, store environment, hashed transaction reference and new player link. An internal reference to a live previous player supports revocation and audit; it is erased if that previous account is deleted. The transfer record is removed when the receiving account is deleted. These records contain no payment details, email, store-account identifier or retained deleted-player ID. Private language-loss notices remain until presentation is acknowledged or the player account is deleted. The device keeps only per-player shown notice IDs to avoid repeating a line after restart, and removes them on account deletion.
Failed purchase/restore server diagnostics are deleted once older than 90 days by our existing periodic housekeeping, or when the current player account is deleted. The game keeps at most ten local failure entries per installation, clears them on sign-out or account deletion, and never syncs them. Feedback emails you choose to send use the support-correspondence retention criteria below.
Retention depends on the kind of information and its purpose. For support correspondence and operational records, the criteria include resolving the request or incident, protecting accounts and meeting applicable legal obligations. Our service providers also maintain logs or backup copies under their applicable retention processes. Account deletion and any limits on deletion are explained in Account deletion. We do not promise that deleting an account instantly erases every provider log or backup.
We use access controls and protected network connections to reduce unauthorized access. No system provides an absolute guarantee of security. We operate in Canada; our Supabase project is hosted in the United States (US West). We also use international email, website and advertising services. Information may be processed outside your country, where laws and government-access rules may differ. Contact us for information about relevant processing locations and safeguards; a provider's privacy notice does not replace your rights against MotMatch.
Your choices and rights
Contact support.easystart@gmail.com to request access, correction or deletion, ask about our practices, or raise a privacy complaint. We may request limited information to verify ownership; we will not ask for a password or login code. Depending on applicable law, you may also have rights to obtain a portable copy, restrict processing, object to certain uses and withdraw optional consent. Withdrawal does not change processing already lawfully carried out. You may complain to the privacy regulator where you live; in British Columbia this is the Office of the Information and Privacy Commissioner.
Removing the app alone does not delete your cloud account. See our account deletion page for the request process and deletion consequences. Deleting an account does not erase records that Apple, Google or another provider maintains independently.
Where the EEA or UK data-protection rules apply, we process information necessary to deliver the account and game service you request on the basis of that service relationship; optional advertising consent is handled separately. Security and fault investigation serve our interest in protecting a reliable service, subject to applicable safeguards and your rights. Processing required by law relies on the relevant legal obligation. Contact us to exercise your rights or ask which basis applies to a particular use.
If you believe someone under 16 has created a formal account, contact us so we can investigate. Do not send unnecessary identity documents or sensitive information.
Changes
We will date updated notices and explain material changes through appropriate in-app or website communication. Where a new use requires consent, publishing an updated notice alone does not replace that consent.