← Feztival

Privacy Policy

Effective date: 2026-05-26 Last updated: 2026-11-01 Operator: Feztival LLC (“we”, “us”, “Feztival”)

Matcha is a single-player and multiplayer match-3 puzzle game published by Feztival LLC. This policy describes what data Matcha collects, why it is collected, who has access to it, and how you can exercise your rights over it.

Information we collect

Account information

When you sign in to Matcha we receive the following from your chosen identity provider (Apple, Google, or email/password via Firebase Authentication):

  • A stable account identifier (Firebase UID)
  • Email address
  • Your name, if your provider shares it (Apple and Google sign-in only). We store the name from Apple privately and do not show it to other players. The name from Google stays with Firebase Authentication; we do not copy it to your Matcha account.

We do not receive your Apple ID password, Google password, or any other authentication secret.

When you first sign in, we give your account a randomly generated display name, which you may change in Settings. On an account created with an older version of Matcha, the display name may be the name from your Apple sign-in until you change it.

Gameplay data

When you play Matcha we record:

  • Game session results (final score, match outcome, time spent, mode played, level reached)
  • Currency balances and transaction history (gold, gems, loot box inventory)
  • Progression state (XP, level, achievements, daily challenge progress)
  • Versus match history (for each match: your opponent’s account identifier, or the name of a computer opponent; the outcome; and the rating change it produced). During a match and in their own match history, your opponent sees a label made from the first characters of your account identifier, never your display name or email address.
  • Powerup usage in each game (which powerups appear, which ones you use or leave unused, and the points they score)
  • Tutorial progress (which tutorial lessons you open and the outcome of each move you make in them)

Purchases

When you buy gems through Apple’s In-App Purchase, Apple processes the payment. We never receive your payment card, billing address, or Apple ID password. For each purchase we keep a record linked to your account:

  • The App Store transaction identifiers, the product you bought, and whether it was a live purchase or an Apple test purchase
  • Apple’s signed record of the transaction, as Apple sends it to us. It contains Apple’s transaction identifiers and, when the app provided one, a random token the app generated for your account. It contains no name, email address, or payment details.
  • The number of gems we granted, and, if Apple later refunds the purchase, the refund and the gems it took back
  • The notifications Apple’s servers send us about the purchase, such as a refund

We also record what you spend gems on, and any correction our support staff make to your gems balance.

Feedback

When you send feedback from Settings (Send Feedback), we store the category you choose (bug, suggestion or praise) and the message you write, together with your account identifier. Our own internal test accounts can also attach a screenshot of the app’s screen to a report; other accounts cannot.

Country

  • The home country you choose in Settings or on the Nations screen. It is stored with your account, decides which nation your games count toward in the monthly country competition, and is recorded with each game’s contribution.
  • The country your IP address belongs to. When the app asks our servers which features to turn on, we look up the country from your IP address using a lookup table built into our server software, and use it only to answer that request. We do not store it, and your IP address is not sent to anyone else for this lookup.

The app never uses your device’s GPS or location services.

Device and diagnostics data

When the app runs on your device we collect:

  • Crash reports via Google Firebase Crashlytics, including stack traces, the device model, the operating system version, the app version, and a Crashlytics-assigned installation identifier (a randomly generated value Firebase associates with the installed app; it is not your device serial number, not your Apple ID, and does not persist across app uninstalls). Crash reports are tagged with your account identifier so a crash can be matched to the account it happened on.
  • Basic device metadata supplied by iOS (locale, timezone, screen size), used to render the UI correctly
  • Device context sent with feature requests. When the app asks our servers which features to turn on, it sends your locale, your device platform and operating-system version, the app version, and the identifier iOS gives apps from the same developer on your device (identifierForVendor, which is not your device serial number or your Apple ID). We use them only to answer that request, including to roll a feature out to a share of devices, and do not store them.

We do not collect your device’s contacts, photos, precise location, microphone audio, camera input, or web browsing history. We do not run third-party advertising trackers.

How we use the data

  • To run the game: account information identifies you across sessions; gameplay data persists your progress; versus data powers that mode; purchase records let us deliver the gems you paid for, apply Apple refunds, and stop one purchase from being credited twice; your home country decides which nation your games count toward; the country looked up from your IP address is used to decide which features the app turns on for you.
  • To improve the game: crash reports help us diagnose bugs; usage statistics (how many players are active, how many games are played in each mode, how long games last, which levels players reach, how much gold is earned, spent and held, and which accounts hold the most gold) show us how the game is played; powerup usage records help us balance the powerups; and tutorial progress records show which lessons players get stuck on or leave, so we can improve the tutorial.
  • To enforce fair play: we may review gameplay logs if there is reason to believe a session was tampered with.
  • To respond to feedback and support requests: we read the feedback you send us, and we may inspect your account state, including your purchase records, to answer it or a support ticket you have filed.

We do not sell your personal data. We do not share it with advertising networks. We do not use it to build behavioral profiles.

Where the data lives

  • Authentication is operated by Google Firebase Authentication.
  • Gameplay and account state, including purchase records, are stored in a Google Cloud Platform (us-west1) Postgres database operated by Feztival LLC.
  • Crash reports are stored in Google Firebase Crashlytics.
  • Feedback screenshots are stored in Google Cloud Storage in the same Google Cloud Platform project.
  • Server logs are stored in Google Cloud Logging in the same Google Cloud Platform project and deleted automatically after 30 days. They include a record of each request to our servers (your IP address, the app’s user agent string and the URL requested), and the powerup usage and tutorial progress records described above.
  • Backup and disaster-recovery copies are encrypted and retained for up to 30 days.

Google’s processing of Firebase data is governed by the Google Cloud Platform Terms of Service and Firebase Data Processing and Security Terms.

Children’s privacy

Matcha is not directed at children under 13. If we learn that we have collected data from a child under 13, we will delete it. Parents or legal guardians who believe their child has registered an account may contact us at the address below and we will remove the account on request.

Your rights

You may at any time:

  • Access the personal data we hold about you by emailing the address below.
  • Correct inaccurate data by editing your profile in the in-app Settings screen or by emailing us.
  • Delete your account from the in-app Settings screen. Deletion is permanent and cannot be undone. It completes while you wait — you do not need to email us or contact support. Matcha deletes your account record and the personal data associated with it: your email address, name, display name and name history, gold and gems balances, match history, inventories, boosters, entitlements, achievements, streaks, settings, stats, saved games, friends connections, pending invitations, guild membership, and any feedback you sent us. Your sign-in credential is deleted too, so the Apple / Google / email login you used will no longer sign in to Matcha. Signing up again later creates a brand-new, empty account — your previous gold, gems, progress and inventories do not come back. Virtual-currency transaction entries and purchase records are retained for accounting and to answer refund disputes; your user ID is stripped from them at deletion, so they no longer name your account. A purchase record keeps Apple’s signed record of the transaction, which holds Apple’s transaction identifiers and, when present, the random token described under Purchases. Copies of your data in server logs, crash reports, feedback screenshots and encrypted backups are not erased at deletion; they expire on the schedules under Data retention. Our staff audit log records support and moderation actions taken on accounts, such as viewing an account, granting it items, or banning or deleting it; those entries keep your account identifier after deletion, and a staff search by your email address keeps that address as it was typed.
  • Export a portable copy of your gameplay data by emailing the address below.
  • Withdraw consent to data processing by deleting your account. Matcha is an online service and an account is required to play; deleting your account ends your use of the Service.

Residents of the European Economic Area, the United Kingdom, and the State of California have additional rights under GDPR, UK GDPR, and the California Consumer Privacy Act respectively. We honor those rights for all users regardless of residence.

Data retention

  • Active account data is retained for as long as you have an active account.
  • On account deletion your account record and associated personal data are deleted immediately and permanently, with two exceptions. Copies in server logs, crash reports, feedback screenshots and encrypted backups are not erased early and are deleted on the schedules below. Staff audit log entries about actions taken on your account keep your account identifier, as described under Your rights. Virtual-currency transaction entries and purchase records are retained for accounting with your user ID stripped, as described under Your rights. Apart from the backups, which can only restore the whole database, nothing is kept that could restore the account.
  • Crashlytics data is retained for 90 days, after which Google purges it automatically.
  • Server logs, including request records, powerup usage records and tutorial progress records, are deleted automatically 30 days after they are written.
  • Feedback screenshots are deleted automatically 90 days after they are uploaded.
  • Backup and disaster-recovery copies of the database are deleted automatically within 30 days of being made.
  • Staff audit log entries have no scheduled deletion; they are kept so that actions taken on accounts stay accountable.

Changes to this policy

We will post a revised version of this policy at this URL if material changes are made. If the change materially affects your rights we will also notify you in the app on next launch.

Contact

Privacy questions, data requests, or complaints: privacy@feztival.io

Feztival LLC
2108 N St Ste N, Sacramento, CA 95816, United States

© Feztival LLC