MazeMe Privacy Policy

Last updated: 14 November 2026 · Applies to the MazeMe mobile app on Google Play and the App Store, and to its web pages.

MazeMe is a puzzle game published by Golden Diary App Private Limited, a company based in Hyderabad, Telangana, India, and developed by Vikranth Sai and Akshay ("we", "us"). Golden Diary App Private Limited is the data controller (under India's DPDP Act, the "data fiduciary") for the data described below. Contact, and the person who answers questions about your data: Vikranth Sai, mazemearrow@gmail.com, or Settings → Contact in the app. We have not appointed a Data Protection Officer, because the law does not require one for MazeMe.

The short version: You can play MazeMe without signing in. When the app first connects it creates a random, anonymous player ID, and your progress is saved against that ID. You can choose to sign in with Google, or with Apple on iPhone, so your progress and friends follow you to another phone. The friends list and making a photo maze need signing in; playing, including a photo maze a friend sends you, does not. If you sign in with Google, MazeMe receives your email address and Google name (and the address of your Google profile picture, which it does not show or use); if you sign in with Apple, it receives only your email address, which can be a private relay address if you use Apple's Hide My Email. If you email us, we receive your email address and your message. MazeMe never asks for a phone number or a password. If you choose a display name, other players can see it in live rooms, on challenges you send and in friends lists. If you allow notifications, the app stores a device token so a friend's race invite, or news that a friend accepted your request or passed your level, can reach your phone, with your phone's time-zone offset so that friend news never arrives at night. If you turn on reminders, they are planned on your phone, at most one a day. The app collects gameplay analytics and crash reports, checks that it is the genuine app, and shows ads through Google AdMob, which can fill an ad from Google or from AppLovin, Mintegral, Unity Ads or Meta Audience Network, personalized only where the law and your choices allow it. Photos you turn into mazes never leave your phone; when you send a photo maze as a challenge, you can choose to send its small pixel-art picture with it (it starts on Maze only), through the app you share with, or its clear picture, which we store locked with a key only the link carries, so we cannot see it, and delete after 90 days. To keep that link short, the app stores the challenge on our servers locked with a key that only the link itself carries, so we cannot see the maze or the picture; the locked copy is deleted after 90 days. We keep a record that your account shared it, with a fingerprint of the picture (never the picture), and a friend's game shows the picture only after checking that record exists, so a picture shown in MazeMe can be traced to the signed-in account whose app shared it (not to anyone who forwarded the link). We do not sell your data for money. You can delete your data from inside the app, or by email (see Deleting your data).

In version 1.0, race invites, friend notifications and notes sent to your phone are available on Android only, and challenge links open straight in the game on Android only. Reminders, sign-in and the friends list are available on both Android and iPhone. The parts of this policy about race invites, friend notifications, notes and the notification token do not apply to the iPhone version until they arrive there.

1. Data we collect

DataWhat it containsWhy
Player ID (account)A random ID created automatically by Firebase Authentication (anonymous sign-in). You do not have to do anything to get one. You do not need to look it up: an email you write from the app (Settings → Contact) carries it, so we can find your data when you contact us.Keeping your cloud save, your friends and your place in live rooms; matching support and deletion requests to you
Sign-in with Google or Apple (optional)Only if you tap Sign in with Google (Android and iPhone): your email address, your Google account name, Google's identifier for your account and the web address of your Google profile picture (MazeMe does not show or use it). Only if you tap Sign in with Apple (iPhone only): your email address, which may be a private relay address if you use Apple's Hide My Email, and Apple's identifier for your account; MazeMe does not ask Apple for your name. Either way, they are stored by Firebase Authentication and linked to your player ID. MazeMe never sees your Google or Apple password.Letting you get the same progress and friends back on another phone or after a reinstall; letting you make photo mazes, which are kept to signed-in players so that action we take against misuse of pictures stays with your Google account or Apple ID; confirming it is you when you delete your account or ask for support
Cloud saveLevels played, stars, best moves and best time per level, highest level reached, daily-maze results and streaks, Sparks balance (the in-game currency, which has no cash value), hints and undos held, play streaks, badges, skins you own and the one you use, challenge wins, losses and streak, your display name if you set one, how many ads of each kind you have seen and when you last saw one, which item grants from us have been applied, the app version, build and platform (Android or iOS) that last saved, and dates (created, last seen, last updated). From the level where the game first offers reminders, also a short reminder record: which of two test groups you are in (in one, the game does not offer reminders, so we can compare), your answer on the reminder card, whether your phone last allowed MazeMe's notifications, and the day the group was pickedRestoring your progress; balancing the game; support; finding out whether reminders help players
Display name (optional)A name you type, up to 32 characters in your save and up to 16 characters in a live room. It is optional everywhere, including races, and can be any nickname: it does not need to be your real name. In a live room, a blank name shows as "Player". Names are checked on entry and checked again before they are shown to anyone.Showing who is who in live rooms, on challenges and in friends lists
Profile card (sign-in needed)Only once you have signed in: a small card kept under your player ID with your display name, the level you have reached and when the app last synced ("last seen"). It is updated each time your progress syncs. Earlier versions of the app also published a card for players who had not signed in; this version removes it the next time it syncs, and we are removing the rest from our servers.Showing friends, and people you send a friend request or race invite to, who you are. It is published for every signed-in player, including one who signed in only to make photo mazes.
Friends (sign-in needed)Your friends list (each friend's player ID, the name shown for them, the date you became friends, a win, loss and draw record and when you last played each other), friend requests waiting for an answer (the sender's player ID, name, level and the time), race invites (the sender's player ID and name, the room code and the time; an invite is valid for 15 minutes), and your friend code (a 10-character code that works for 24 hours). If you decline a friend request, the sender's player ID and the time are noted in your account so the same player cannot keep asking (see §7). Small counters record how often you use these actions.Running the friends list, friend requests and race invites; stopping spam and abuse
Notification token (optional)Only if you allow notifications, and while Race invite notifications, Reminders or Friends is switched on: a Firebase Cloud Messaging device token, the platform of your phone (Android or iOS), when it was registered, whether race invites and friend notifications are switched on for it, and your phone's time-zone offset from UTC (for example +5:30, updated when it changes, such as after travel or a clock change), kept under your player IDSending a race invite from a friend, news from your friends, or an occasional note about the game or your account, to your phone; keeping friend notifications out of 9:30 pm to 9:30 am on your phone's clock (see §6)
Daily play statsOne record per day you play: levels cleared, sessions, play time, Sparks earned and spent, and ads shown and completedUnderstanding how the game is played and balancing it
Live-room dataFor each room you open or join: your player ID, display name, the time you joined, your request to join, and your race progress (percent cleared, hearts left, finish time, whether you are online). The host's room record also holds the host's player ID, the level, a random seed and timestamps.Running the race
Race summariesFor each finished race: level, difficulty, number of players and finishers, and duration. No names and no player IDs.Counting races
Player reportsIf you report a player: your player ID, their player ID, the name shown for them, the room code, the reason you picked, and the time. If you report a picture that came with a challenge: your player ID, the picture's fingerprint (below), the name on the challenge, the reason you picked, the time, and the picture's pixel-art data from the link you received, so that a person can see what was reported; if a clear picture came with the challenge, also the key that opens it and its fingerprint, so that a person can open and check the clear picture too.Moderation and keeping players safe
Rules agreementWhen you tap I agree on the Play nice rules (before your name is first shown to other players, every 90 days after that, and when the rules change): your player ID, which version of the rules you agreed to, when our server received it, the time on your phone when you tapped, the platform (Android or iOS) and the app build. Each new agreement replaces the last one. If you agreed while offline, it is sent the next time you use a room or a challenge with a connection.A record that you agreed to the rules, for moderation, complaints and app-store reviews
Picture-share recordsWhen you tap Share or Copy link with Pixel picture or Clear picture chosen (even if you then cancel the share or never paste the link): your player ID and the Google or Apple account identifier you are signed in with, a fingerprint of the picture (with Clear picture, a fingerprint of the clear picture too, kept the same way), the name that went with the challenge, and when you first and last shared it; sharing the same picture again updates the name and the last time. A fingerprint is a one-way code worked out from the picture's squares; the picture cannot be rebuilt from it. Alongside, we keep the fingerprint on its own, with the time and no player ID, so that a friend's game can check a picture was recorded before showing it. Your photo is never sent to us, and the picture never in a form we can see (see Short challenge links and Clear pictures).Finding the account that shared a picture reported to us, and acting on it under the rules (§2, Terms §6, §7, §12); showing only pictures that can be traced
Short challenge linksWhen you share a photo maze, the app makes its link short by storing the challenge (the maze, your challenge name and score, and the picture if you chose to send it) on our servers, locked on your phone with a key that only the link carries. The key is in the part of the link after the #, which is never sent to our servers, so neither we nor our service providers can open what is stored. It holds no player ID or other detail of who made it. If the copy cannot be stored, the app sends the long link instead, which carries everything itself.Keeping challenge links short enough to send and scan; deleted 90 days after the link is made
Clear pictures (optional)Only if you choose Clear picture when you send a photo maze: a clear picture of the square you framed (a JPEG of at most 560×560 pixels, usually 40 to 90 KB), stored on our servers locked on your phone with a key that only the challenge link carries, in the part of the link after the #, which is never sent to our servers. Neither we nor our service providers can open it unless someone reports it with the key (see Player reports). It holds no player ID or other detail of who made it; the picture-share record above is what names the account that sent it. Anyone who has the link can open it, including people your friend forwards the link to, until it is deleted.Letting your friend's game end on the clear picture, as yours does; deleted 90 days after you send it
Deleted accounts that shared picturesIf an account that shared pictures is deleted: the email address it signed in with and its Google or Apple account identifier, and when it was deletedTracing a reported picture after its sender deleted their account, and recognising them if they come back
Messages you send us (optional)If you email us, including from Settings → Contact (which adds your player ID), we receive your email address, any name on it and what you writeAnswering you; handling reports, complaints, privacy and deletion requests
Items and changes we makeIf we grant you in-game items (such as Sparks, levels or skins) or change your account: a record of what was changed and when, under your player ID, and a line in our staff log (see §2)Support; a record of changes made to the game and to accounts
Error reportsWhen the app hits an error: a short error message (at most 300 characters, which can include technical details such as an internal ID or file name), where in the code it happened, whether the app crashed, the platform, the app version and build, your player ID, and the timeFinding and fixing bugs
Crash reportsStack traces and the device's state at the time of a crash: device model, OS version, app version, free memory and similar, with a Crashlytics installation ID (Firebase Crashlytics). They are not linked to your player ID, name or email.Fixing crashes
Gameplay analyticsEvents such as level started, completed, failed or quit (campaign and daily maze), with how long it took, hearts left and continues used; finishing the tutorial; hints used; ads shown, completed, abandoned or skipped; Sparks earned and spent; skins bought with Sparks or unlocked; rooms created, requests to join and races finished; friend codes scanned, friends added and how many friends you invited to a race (never who); item grants applied (the kind only); your consent choice and, on iPhone, your tracking choice; and events the Analytics software records by itself, such as first open, sessions, app updates and ad impressions. Also a broad region tier worked out from your phone's region setting, the analytics app-instance ID, a Firebase installation ID, how the app was installed (the Play Store install referrer, on Android), and standard device and app information (Google Analytics for Firebase). No names, email addresses, contacts, photos or precise location, and not your player ID.Understanding difficulty and improving the game
App integrity checksEach time the app talks to our servers it attaches a token showing the request comes from the genuine MazeMe app on a real device. To get it, the app asks Google Play Integrity (Android) or Apple App Attest or DeviceCheck (iPhone), which check your device and the app (Firebase App Check). We receive only a pass or fail token.Security; stopping fake apps, cheating and abuse
Advertising dataYour device's advertising ID (on iOS only if you allow tracking in Apple's prompt), on iOS an app-specific identifier for vendor, your IP address, from which Google estimates an approximate location, device information, your interactions with ads and, on Android, interest topics and ad-attribution signals from Android's Privacy Sandbox where your phone provides them (Google AdMob, and the ad networks that bid for an ad through it: AppLovin, Mintegral, Unity Ads and Meta Audience Network, see §3). Ads may start loading in the background from your first session, so they are ready later, even though none is shown until you have cleared the first five levels.Showing ads, which pay for the game; measuring and limiting ads; preventing ad fraud
App configurationWhen the app fetches its settings (Firebase Remote Config), Google receives the request along with basic device and app information such as country and language, and the Firebase installation IDTuning the game and switching features on or off without an update
Web visitsIf you open a challenge link in a browser or read these pages on the web, or the app fetches the latest copy of these pages to show you (when you open one, and at most twice a day at launch), our host (Vercel) receives the request: your IP address, browser type, the page address without the part after the #, and the time. The pages set no cookies and use no analytics, advertising or third-party scripts.Delivering the page; security

MazeMe does not collect your phone number, postal address, contacts, messages, precise location, photos, biometric data or payment information. The only picture that ever reaches us in a form we can see is the pixel-art picture a player attaches to a report about it (above); a short challenge link stores one locked with a key we never receive (above). It collects your email address only if you choose to sign in with Google or Apple, or if you email us, and your Google name only if you sign in with Google. There are no in-app purchases: Sparks are earned by playing or by watching optional ads. No law requires you to give us any data. A player ID is needed for the online features, because the game cannot save your progress online or put you in a room without one. Signing in with Google or Apple is needed only for the friends list and for making a photo maze; without it, everything else works the same. Everything else is optional, and if you refuse ad or analytics consent the game works the same.

Stored only on your phone

A copy of your progress, levels you are part-way through, your settings (sound, haptics, theme), the players you have blocked (their player IDs and the names shown when you blocked them), the codes of rooms you have opened or joined in the last 30 days, whether and when you agreed to the rules, your last consent answer, whether Reminders is switched on and where you are with the reminder card, the times you opened the game in the last two weeks (used only to plan reminders around when you usually play) and the reminders booked. They stay on your phone, are not included in Android backups, and are removed when you uninstall the app.

Signing in with Google or Apple (optional for playing)

Signing in is never required to play. The campaign, the daily maze, challenges (including a photo maze a friend sends you) and live rooms all work on the anonymous player ID. Two features need signing in (with Google, or with Apple or Google on iPhone): the friends list, because a friends list tied to an anonymous ID would be lost when the app is reinstalled; and making a photo maze, because a photo maze can hold a picture of a person. Signing in to make a photo maze adds no data to the maze, and the photo still never leaves your phone; only if you send its picture with a challenge do we keep a picture-share record (§1), and, if you choose Clear picture, a locked copy of the clear picture for 90 days. Signing in does mean we hold your sign-in email address (and, with Google, your name), and that your profile card is published, as described in §1.

Friends

You add a friend by showing them your friend code (or its QR code), or by scanning or entering theirs. Scanning or entering a code sends a request; you become friends only when the other player accepts. Either of you can remove the other at any time, which removes the link on both sides. The friends list, requests and invites are written by server code (Firebase Cloud Functions), not by other players' phones.

Photos and the camera

MazeMe never collects your photos. We store a picture made from one only if you choose Clear picture when you send a challenge, and then only locked so that we cannot open it (below). (If someone you send a photo maze's picture to reports it, the picture reaches us with the report, §1.) Making a photo maze needs signing in (see Signing in with Google or Apple), but the photo-maze feature turns a picture into a puzzle on your phone. The image is read into memory and turned into two things: a colour portrait of the square you framed and a maze. The portrait is hidden under the maze, and each part of it is uncovered as you clear the arrows above it. It starts as pixel art (84×84 squares) and gets sharper as you play; when the maze is cleared it ends as a clear picture of the framed square (at most 560×560 pixels). MazeMe does not detect, recognise or analyse faces, and does not create face geometry or any other biometric identifier from your photos.

Challenges

When you challenge a friend, the app makes a code (text and a QR code) that carries the level or maze and your result (stars and time) if you have one. For a photo maze, the code, and so the QR code, also carries your display name if you add one; a name you add to a level challenge goes in the message instead. You send it yourself, through your phone's share sheet or by showing the QR code. The share message and the QR code carry it as a link (https://mazeme-game.vercel.app/c# followed by the code). The code sits after the #, a part of a web address that browsers do not send to the website: the page reads it on your friend's phone to offer the game, and on Android, with MazeMe installed, the link opens straight in the game. We do not receive or store challenge codes. A photo-maze code never carries the photo or its picture unless you choose Pixel picture or Clear picture. Then the link also carries the maze's pixel-art portrait, after the code and still after the #, and your message comes with a picture of the maze over it (see Photos); with Clear picture, it also carries the key to the locked clear picture. The QR code never carries the picture. The photo itself is never part of a code or a link. A picture that arrives with a challenge you open is kept in memory only while that challenge is open, and the app never sends it on, except to us inside a report you choose to make (§1).

2. Who can see your data

3. Services we use

Each provider receives only the data it needs to provide its service to us, and we use only providers that commit to protecting it at least as well as this policy describes. Google processes Firebase data for us, as our processor. For personalized ads and ad measurement, Google acts as an independent controller under the Google Privacy Policy.

Where data is stored. Cloud saves, stats, friends data, profile cards, notification tokens, reports, error reports, race summaries, picture-share records, the picture fingerprints a game checks, and notes on deleted accounts that shared pictures are stored in Cloud Firestore in Mumbai, India. Live rooms are stored in the Firebase Realtime Database in Singapore. Our server code (friends, invites, account deletion and the daily clean-up) runs in Mumbai, India, and the staff tool's server runs on Vercel in the United States. Account data held by Firebase Authentication (including an email address if you signed in, and a name if you signed in with Google), and analytics, crash, integrity-check, messaging, email and advertising data, are processed by Google in the United States and wherever else Google operates, advertising data for an ad another network answers also by that network wherever it operates (§3), and web requests by Vercel in the United States and wherever else Vercel operates.

Transfers. We are based in India, so if you live elsewhere your data is collected by a company outside your country. India does not have an adequacy decision from the EU or the UK. Google takes part in the EU-US Data Privacy Framework and its UK and Swiss extensions, and its data processing terms with us include the European Commission's Standard Contractual Clauses and their UK and Swiss equivalents. Vercel, which hosts our web pages and staff tool, is certified under the Data Privacy Framework. We store data outside India only where the Indian government has not restricted it, and follow any conditions it sets. You can ask us for a copy of these safeguards.

We do not sell your personal information for money. When personalized ads are shown, Google, and the ad network that answers the ad request (§3), receive your advertising ID, IP address, device information and ad interactions to choose and measure ads. Under California law this may be "sharing" for cross-context behavioral advertising, and under other US state laws it may be "targeted advertising" or, under some definitions, a "sale"; you can opt out (§4 and §9). Apart from this, we disclose personal information only to our service providers above, which process it for us, and to authorities when the law requires it. We do not disclose personal information to anyone for their own direct marketing.

4. Ads and your choices

5. Legal bases

EEA, UK and Switzerland

Your right to object

Where we rely on legitimate interests, you can object at any time, for reasons relating to your situation, by writing to us (Settings → Contact, or mazemearrow@gmail.com). We then stop, unless we have compelling legitimate grounds or need the data for legal claims. MazeMe sends no marketing; if it ever did, you could object to it at any time without giving a reason.

India

For players in India, we process personal data to provide the game you chose to use, for the uses the DPDP Act allows, such as data you give us yourself for a purpose (an email, a report), and where the law requires it. You can stop all processing at any time by deleting your data (Settings → Delete my data). Until the main parts of the Digital Personal Data Protection Act, 2023 and its Rules apply (13 May 2027), we follow the Information Technology Act, 2000 and its rules on reasonable security practices; before that date, the app will ask for your consent where the DPDP Act requires it, purpose by purpose, and let you withdraw it in Settings as easily as you gave it. After you withdraw, we and our service providers stop within a reasonable time, unless the law requires us to keep the data. MazeMe does not collect passwords, financial information, health, biometric or other sensitive personal data.

Automated decisions

We do not make decisions about you based only on automated processing that have legal or similarly significant effects. An automatic filter checks display names: it can stop a name being used, but it never suspends an account, and you can choose another name or ask us to review it. If you consent to personalized ads, Google uses automated profiling to choose them, as described in Google's policy.

6. Notifications

MazeMe sends notifications only if you allow them, and never asks at first launch. They have three switches, under Settings → Notifications: Reminders, Friends (shown once you have signed in) and Race invite notifications. The app asks for your phone's permission only when you tap Turn on reminders on the reminder card (shown after you clear level 5, or level 6 on iPhone), tap Turn on race invites on the Friends screen, or switch one of them on in Settings. Not now on the card does not ask, and the card comes back at most once. While any switch is on and your phone allows it, the app keeps a device token for your phone under your player ID (§1).

7. How long data is kept

DataKept
Account (player ID and, if you signed in, your email address, plus your name if you signed in with Google), cloud save, daily stats, profile card, friends list and notification tokenUntil you delete them. There is currently no automatic deletion of inactive accounts. A notification token is also removed when a message we send to it bounces.
Friend requests, race invites and friend codesA request stays until it is answered, and is deleted after 90 days if it never is. A race invite is valid for 15 minutes and a friend code for 24 hours; expired ones are deleted within a day.
The note of a declined friend request (the sender's player ID and the time)It stops having any effect after 30 days. It is cleared the next time the player who declined declines someone else, and otherwise stays stored, in their account, until they delete their data.
Counters that limit how often friend actions, race invites, reports, shared pictures and links, and deletion requests can be usedThey cover a window of an hour or a day and hold only a player ID (or, for race invites, the two players' IDs), the action and a count. They are deleted automatically within a few days after the window ends. Two records about friend news are kept longer: when friend news last reached you (a week), and the highest level a "friend passed you" notice was counted from (a year from your last new level). Both are deleted with your data.
Live roomsLeaving a room in the app removes you from its player list and removes your race progress; if the app closes or loses its connection instead, your entry stays. A room can be taken over and overwritten once it has been idle for 6 hours. There is no scheduled clean-up yet, so an abandoned room, with the names and player IDs still in it, can stay stored until its code is reused. Deleting your data removes you from the rooms your phone remembers (see §8).
The record that you agreed to the rulesUntil you delete your data; replaced each time you agree again
Error reports90 days, then deleted automatically
Player reportsKept for moderation and to keep other players safe, for up to 12 months after the report is made, then deleted automatically
Picture-share records, and the fingerprints a game checks12 months after the last time the picture was shared, then deleted automatically. They are kept for that time even if you delete your data, so that deleting an account cannot hide the misuse of someone's picture.
Short challenge links (locked copies)90 days after the link is made, then deleted automatically, and the link stops opening
Clear pictures you send (locked copies)90 days after you send them, then deleted automatically; earlier if we take a reported picture down. Because a locked copy holds nothing that links it to your account, deleting your data cannot find it; to have one deleted sooner, email us the challenge link (§8).
Deleted accounts that shared pictures (email address and Google or Apple identifier)12 months after the account is deleted, then deleted automatically
Emails you send usUp to 24 months after the conversation ends, unless we need them longer to show how we handled a legal request or complaint
Records of items we granted, and our staff logKept as a record of what was changed in the game and on accounts, for as long as MazeMe is offered. They hold player IDs and the staff member's account, and no contact details of players. If you delete your data in the app, the grant records stay; if we delete an account for you, they are deleted with it. The staff log is kept.
Race summariesKept (they contain no personal data)
Analytics eventsThe Google Analytics retention setting, currently 2 months, after which only aggregated reports remain
Crash reportsAbout 90 days (Firebase Crashlytics)
Web request logsA short period under Vercel's own log retention
Advertising dataHeld by Google under its own retention policies (see the Google retention policy), and by the ad network that answered an ad request under its own policy (§3)

Records the law makes us keep. Where a law or a lawful order requires it, we keep the limited records it covers for the period it sets, use them for nothing else, and then delete them.

8. Deleting your data

In the app: Settings → Delete my data. This deletes your cloud save, your daily stats, your notification tokens, your profile card, the record that you agreed to the rules, your friends list, friend requests, race invites and friend code (including your entry in each friend's list, and requests or invites you sent to players who are not yet your friends), and your account. It removes you from the live rooms your phone remembers (the last 50 rooms from the past 30 days), resets your analytics app-instance ID, and resets your progress, levels in progress, block list, remembered rooms and rules agreement on the phone. It needs an internet connection. If you are offline, nothing is deleted and the app tells you so; if the connection drops part-way, some data may already be gone, so run Delete my data again to finish. It also switches race invite notifications and reminders off on this phone, puts the Friends switch back to how it starts, cancels any reminder already booked and deletes the phone's notification token, so the new anonymous player your phone becomes is not sent any. Signing out also switches race invite notifications off and deletes the token.

If you signed in with Google: deleting the account also deletes the email address and name held for it, except that if you shared a picture with a challenge we keep the email address and Google account identifier for 12 months (§7). Google may ask you to sign in again first, to confirm it is you. If you cancel that step, your game data is still deleted but the sign-in record (email address and name) is not: the app tells you so and keeps you signed in. Run Delete my data again and confirm with Google to remove it, or email us and we will remove it.

If you signed in with Apple: Apple asks you to confirm once more; the app then revokes the sign-in tokens Apple issued to MazeMe and deletes the account and the email address held for it, except that if you shared a picture with a challenge we keep the email address and Apple account identifier for 12 months (§7). If you cancel, your game data is still deleted but the sign-in record is not; run Delete my data again.

Without the app (for example, if you uninstalled it): email mazemearrow@gmail.com with the subject "MazeMe data deletion" and your Player ID, or the Google or Apple email address you signed in with (if you used Apple's Hide My Email, the relay address shown in the app's Settings). Full steps are on the data deletion page. To protect your account, we may ask you to confirm the request first, for example by writing from the app (Settings → Contact) or from the email address you signed in with; a player ID on its own is not secret, so we will not act on a request we cannot reasonably verify, and we will tell you why. We reply within 30 days.

What remains after deletion: clear pictures you sent with challenges, until each is deleted 90 days after you sent it (§7; email us the link to have one deleted sooner); records of items we granted to you (after an in-app deletion), and entries about your account in our staff log; error reports that carry your player ID, until they expire (§7); reports filed by you or about you, which are kept for a limited period for safety and abuse prevention (§7); picture-share records of pictures you shared, for 12 months after you last shared each one, and, if you shared any, the email address and Google or Apple identifier you signed in with, for 12 months after the deletion (§7); a note in another player's account that they declined a friend request from you (§7); the short-lived counters in §7; race summaries, which contain no personal data; records the law makes us keep (§7); and your entries in rooms that your phone did not remember. We can remove those room entries if you ask by email. In rare cases the app cannot remove an anonymous player ID itself; it then signs you out and leaves an empty ID with no data in it, which we remove if you email us. Data that Google holds for analytics and ads follows Google's retention (§7).

9. Your rights

You can use the in-app tools, or write to us (Settings → Contact, or mazemearrow@gmail.com), to use any of these rights. We will need your Player ID, or the Google or Apple email address you signed in with, to find your data, and we may ask you to confirm the request is yours (§8). If you never signed in, the Player ID is the only thing we hold that identifies you. Someone you authorise, such as a parent or an agent with your signed permission, can ask for you; we may ask you to confirm it directly. We will not treat you differently for using your rights.

Other countries: wherever you live, you can ask us for access to, correction of or deletion of your data in the same way, and we will answer.

10. Children and teenagers

MazeMe is a general-audience game for players aged 13 and over. It is not directed at children under 13, we do not market it to them, and its store listings target players aged 13 and over. The app does not ask your age. We do not knowingly collect personal data from children under 13. If we learn that a player is under 13, for example from a parent, a report, a support message or an age range provided by Apple, Google or the phone, we stop collecting their data except what we need to act, and delete their account and data within 30 days. Parents: email us with the subject "Child account" and the Player ID (any email written from the app's Settings → Contact carries it) or the sign-in email address, and we will confirm the deletion. We never ask a child for more than we need to delete their data.

Players aged 13 to 17 should use MazeMe with a parent or guardian's agreement, and where local law sets a higher age for consent (for example, 18 in India), a parent or guardian must agree before a younger person uses MazeMe. Display names cannot be searched, profile cards cannot be listed, and sending a picture with a challenge starts switched off. If we receive an age range for a player from their app store, their phone or the player, we use it only to give an age-appropriate experience and follow the law, such as turning off personalized ads, and never for advertising or analytics. If you are under 18 and live in California, you can remove your display name by deleting your data (Settings → Delete my data), or ask us by email and we will replace it with a neutral name; this cannot remove copies other people made, such as a challenge you already sent.

11. Security

All traffic between the app and Google's servers is encrypted in transit (TLS). Security rules on the server limit each player's save, stats, friends list, notification tokens and account to that player; a friends list can only be changed by the server code, never by another player's phone; a room's settings and player list can only be read by someone who is signed in and has the room's code, join requests only by the host and the person asking, and race progress only by the players in the room; requests to our servers carry an app integrity check; and only authorised staff can read reports, error reports and the staff tool's data. No system is perfectly secure. MazeMe holds no passwords and no payment data. If you signed in, the contact details it holds for you are your email address and, if you signed in with Google, your name.

If something goes wrong. If a personal data breach affects you, we will tell you without undue delay: signed-in players by email, and other players in the app, through an app update or a notice, where we can. We will say what happened and when, the likely effect on you, what we are doing about it, what you can do to protect yourself, and who to contact. We also report breaches to the authorities where the law requires, such as the Data Protection Board of India, CERT-In and data protection authorities in the EEA and UK.

12. Changes to this policy

If this policy changes materially, we will update the date above, note the change below, and tell you in the app (with an app update or a notice) before it takes effect; where the law requires, we will ask for your consent again. We review this policy at least once a year. The version on our website, mazeme-game.vercel.app/legal/privacy.html, is the current one; earlier versions are available on request.

14 November 2026: from the next app version, an ad can come from AppLovin, Mintegral, Unity Ads or Meta Audience Network as well as Google. These networks bid for an ad through Google AdMob, receive the advertising data for the ad requests they answer, and follow your choices in Google's consent and US-states messages; we tell AppLovin and Unity Ads not to sell or share the data of players in US states with privacy laws (§3).

1 November 2026: when you send a photo maze you now choose Maze only, Pixel picture or Clear picture. With Clear picture, a clear picture of the square you framed (at most 560×560 pixels) is stored on our servers locked with a key that only the challenge link carries, so we cannot open it unless someone reports it; it is deleted after 90 days, and we keep a picture-share record for it as for the pixel picture. Before, only the pixel picture could go with a challenge, and the clear picture never left your phone.

25 October 2026: photo-maze challenge links are now short. The app stores the challenge on our servers locked with a key that only the link carries, so we cannot see the maze or the picture, and deletes the locked copy after 90 days; it holds nothing about who made it. On iPhone, challenge links now open in the game. Challenge links and these pages moved to mazeme-game.vercel.app; the old addresses forward there.

21 October 2026: added reminders, off until you turn them on: planned on your phone, at most one a day, never between 9:30 pm and 9:30 am, and at most four if you stop playing. Your cloud save now keeps a short reminder record (your test group, your answer on the reminder card, what your phone last said about notifications, and the day), so we can tell whether reminders help; the times you open the game stay on your phone. Notifications now have their own section in Settings. Switching off Race invite notifications now stops race invites only; important notes about the game or your account still arrive while Reminders, Friends or Race invite notifications is on, and on Android under their own category. Added friend notifications, with their own Friends switch: when a friend accepts your request or passes your level, never between 9:30 pm and 9:30 am on your phone's clock; for this the notification token now also records whether they are on and your phone's time-zone offset.

20 October 2026: when you tap I agree on the Play nice rules, we now keep a record of it (your player ID, the version of the rules, when, and the platform and app build), replaced each time you agree again and deleted with your data. An agreement made in an earlier version of the app is recorded the next time you use a room or a challenge.

19 October 2026 (picture records): when you tap Share or Copy link with a picture switched on, we now keep a picture-share record (your player ID, a fingerprint of the picture, the name on the challenge and the time) for 12 months after you last share it, also after you delete your data, and a friend's game shows a picture only after checking it was recorded. If an account that shared pictures is deleted, we keep its sign-in email address and Google or Apple identifier for 12 months. You can report a picture from the challenge it came with; the report carries the picture's pixel-art data so a person can check it. The picture is still never sent to us when you share it.

19 October 2026 (later the same day): making a photo maze now needs signing in with Google, or Apple or Google on iPhone; signing in adds nothing to the maze and the photo still never leaves your phone. Playing a photo maze a friend sends you needs no sign-in. Signing out drops the picture of a photo maze you made from the phone's memory.

19 October 2026: Firestore data is stored in Mumbai, India (an earlier version said the United States). In the EEA, UK and Switzerland, Google Analytics and analytics and ad storage are now on only if you agree to device storage and accept Google in Google's consent form, and go off again if you withdraw. Deleting your data or signing out now also switches race invite notifications off on the phone. Profile cards are published only for players who have signed in. Leaving a room now also removes your race progress. When you send a photo maze as a challenge, you can choose to send its pixel-art portrait with it: inside the link, after the # that browsers do not send to our site, and as a picture attached to your message. It starts switched off, travels only through the app you share with, never through our servers, and the photo and its sharper pictures stay on your phone. Added: the app integrity checks; emails you send us; what is stored only on your phone; web visits to our pages; fuller lists of saved, analytics and advertising data; how staff access works; authorities; transfers; legitimate interests and your right to object; India's legal bases and rights in full; US state rights and appeals; automated decisions; children and teenagers; breach notices; that notifications can carry a note about your account; and that we may ask you to confirm an emailed request.

18 October 2026: challenges are shared as links that open in the game; the code stays in the part of the link that is not sent to our site. Photo mazes now hide a colour portrait of your photo under the maze, uncovered as you clear it, which sharpens from pixel art to a clear picture of the framed square. Explained the colour portrait, which stays in memory on your phone only while you make and play that maze; that the photo is shown back only while you frame it; and that challenge codes still carry the maze only, never the photo or its colours. Friend requests now expire after 90 days and expired codes and invites are deleted daily; a declined request is remembered for 30 days; deleting an account also removes requests and invites you sent to people who are not yet your friends. Copies of a photo the phone's picker leaves behind are deleted, including any left from an earlier session.

16 October 2026: added Sign in with Apple on iPhone; sign-in and the friends list are now on iPhone too; named the publisher, Golden Diary App Private Limited, and its developers; set retention periods.

11 October 2026: added optional Google sign-in (email address and name), the friends list and profile card, opt-in notifications, and the banner on the level screen; updated the list of services, staff access, retention and deletion.

MazeMe · Golden Diary App Private Limited · mazemearrow@gmail.com · Terms of Service · Delete your data