LyricHunt

Privacy Policy

Last updated: 2026-10-31

This Privacy Policy explains what data LyricHunt ("we", "us", "the App") collects, why, and how you can control it. LyricHunt is operated by Maksym Romanovych Horak, a registered private entrepreneur (FOP) under Ukrainian law — ФОП Горак Максим Романович, state registration record № 2010350000000578131 — Lviv, Ukraine ("the Operator", "data controller").

Contact for privacy requests: [email protected]

1. Data we collect

Guest play (no account)

If you play as a guest, we store:

We do not collect your IP address in our application database.

If you create an account (Google Sign-In or email)

If you choose to sign in with Google, we additionally store:

If you choose to sign in with email (a one-time code, no password), we store:

Signing in merges any progress you made as a guest into your new account.

Leaderboards (signed-in players only)

If you have an account, you appear on the artist leaderboards inside the App, which rank players by the points they have earned on that artist. What other players can see about you is limited to:

Leaderboards never show your real name, email address, profile picture, Google account, or any account identifier. Guests do not appear on leaderboards. (In a room your Google profile photo is shown to the other players of that room, and to your friends, unless you switch it off — see "Playing with friends" below.)

You can hide yourself from all leaderboards at any time in Settings; you keep your points, and turning it off puts you back. Handles are checked against basic naming rules (for example, no links, contact details or offensive words), and you must not choose a handle that impersonates someone else.

Playing with friends (rooms and friends)

You can play with other people in a room (by sharing a room code or by invitation) and add friends. What other players can see:

What we store about this, and for how long:

Rooms have no chat and no free text between players: the only text another player can put in front of you is a nickname.

Reports and moderation

If another player behaves badly (an offensive nickname, cheating, harassment), you can report them from the room. We store:

Reports are read only by us, to keep rooms safe; they are never shown to the reported player or to anyone in the room. We may use them to restrict a player's access to rooms (a room ban); solo play is not affected. Reports are deleted after 12 months, or earlier if either account is deleted. You can also block a player from a room: they can then no longer join rooms you are in, or send you friend requests, and you cannot join theirs.

Advertising (free tier)

Free-tier players see ads served by Google AdMob. AdMob may use the Android advertising ID and device information to choose and measure ads; ads can be personalised. We do not give AdMob your account data. You can reset or delete your advertising ID, or opt out of ad personalisation, in your phone's Google settings (Settings → Google → Ads). Premium removes ads.

If you are in the European Economic Area, the United Kingdom or Switzerland, the App asks for your consent through Google's consent form before any ad is requested, and no ad is requested until you have answered. You can review or withdraw your choice at any time in Settings → Ad privacy.

If you purchase premium

If you buy a premium subscription or item, we store:

Analytics

We use Google Firebase Analytics to understand how players use the App and to improve it. Firebase Analytics collects:

Firebase Analytics is provided by Google. Google acts as our data processor for this data and may process it in accordance with its own privacy terms — see Google's Privacy Policy and Google Analytics for Firebase's terms. Analytics collection is currently on by default, based on the notice you see and agree to on the App's welcome screen; a more granular in-app consent control is planned for a future update.

Crash reports and diagnostics

We use Google Firebase Crashlytics to find and fix crashes and errors. When the App crashes, or hits an error it could not recover from, it sends a report to Crashlytics. A report contains:

We do not put song lyrics, the words you guessed, your email address, your name, your display name or your public handle into these reports, and we do not attach your account to them.

Crashlytics is provided by Google. Google acts as our data processor for this data; see Google's Privacy Policy and Firebase's privacy and security information. Crash reporting follows the same setting as Analytics: it is on by default, based on the notice you see on the App's welcome screen, and a more granular in-app control is planned for a future update.

Reminders (notifications)

If you turn on reminders (streak, energy restored, daily challenge, and other occasional nudges), they are scheduled on your device from your own game state. We do not send them from our servers, and they need no push-notification token or other additional identifier. Notification permission is requested only when you choose to turn reminders on; you can change how often they arrive, switch individual kinds off, or turn them off entirely in Settings → Notifications, or in your phone's system settings.

Friend requests and invitations (push notifications)

If you have an account and allow notifications, we can tell you when a friend request or a room invitation reaches you while the App is closed. These are the only notifications our servers send. To do this:

You choose: the notification permission is asked only after a friend request or invitation (or from Settings → Notifications), you can switch friend requests and game invitations off separately there, and you can turn notifications off in your phone's system settings at any time. On Android 12 and older, notifications are allowed by default and the App does not ask, so the token is registered when you sign in; the same switches and system setting turn it off. A guest, who has no friends or invitations, never gets a push token.

Your token is removed when you sign out, when Google tells us it is no longer valid (for example you uninstalled the App), and when you delete your account.

2. What we never collect or store client-side

Consistent with the design of the game itself, LyricHunt never sends full, unmasked song lyrics to your device outside of an active, in-progress guessing round, and never logs full lyric text on our servers in a form accessible via the App's API.

3. Why we process this data (legal basis)

4. Third parties we share data with

PurposeThird partyWhat they receive
Sign-in (Google)Google (Google Sign-In)Your Google ID token, used to verify identity
Sign-in (email)Google (Gmail, for outbound delivery)Your email address and one-time sign-in code, to deliver the code to you
PaymentsGoogle Play BillingPurchase/subscription data (handled by Google; we receive only a purchase token)
AnalyticsGoogle (Firebase Analytics)Events and properties listed in §1
Crash reportsGoogle (Firebase Crashlytics)Crash and error reports, device and app information, and a Firebase installation ID, as listed in §1
Push notificationsGoogle (Firebase Cloud Messaging)Your push token, and the text of the notification (the other player's public handle and, for an invitation, the room mode)
Advertising (free tier)Google (AdMob)Ad requests, the advertising ID and device information, as described in §1
Song metadataThird-party music catalog APIsSearch queries (artist/song names) — no personal data
Lyric fragmentsThird-party public lyrics APIsSong title/artist to look up lyric text server-side — no personal data

We do not sell your personal data to anyone.

5. Data retention

6. Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing (for example, under the EU/UK GDPR).

You also have the right to lodge a complaint with your local data protection authority.

7. Children's privacy

LyricHunt is not directed at children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child under 13 has provided us with personal data, contact us at [email protected] and we will delete it.

8. International data transfers

Our service providers (including Google) may process data outside your country of residence, including in the United States. Where required, such transfers rely on the provider's own applicable safeguards (for example, Google's Standard Contractual Clauses for EU data transfers).

9. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above.

10. Contact

Privacy questions or requests: [email protected]