Effective 27 October 2026
Nimo is a puzzle game for everyone, including children. This policy explains what information Nimo uses, why it uses that information, who can receive it, and what you can choose. It applies wherever Nimo is offered. Some features depend on your country and phone. Your rights under local law still apply.
These are the main points:
- You can play puzzles without an account. Your guest progress stays on your phone.
- The usual minimum age for an account is 13. Some countries have a higher age or limits on connected features.
- Existing and new eligible active accounts appear on public rankings by default. You can confirm that you want to hide in Settings. Manual visibility changes must be at least 30 days apart. Turning rankings off does not hide your profile from people who reach it through a friend code or friendship.
- App health reports are for eligible players 13 and older. On is the starting preference before a reporting choice is made. Existing reporting choices, including Off, are kept. Nothing is captured until you choose Send reports. You can keep them off. Reports stay separate from accounts.
- Ads, purchases, sign-in and phone notifications use the services explained below. Their information is separate from Nimo's app health reports.
- Deleting an account starts a 30-day waiting period. Delivered gifts, some security records and backup copies have separate rules.
How to read this policy
Start with the sections that match how you play. Age and country rules explains which features you can use. The guest and account sections explain what we receive in each case. What other players can see explains the difference between a profile and a place on the rankings. How long we keep it and Deleting your account explain what happens to information later.
You do not have to turn on every feature to play. For example, you can keep app health reports off, hide your account from rankings under the rules below, or decline phone notifications. Each choice controls the feature described here. It does not automatically change your other choices.
We use these words:
- Account: your Nimo sign-in and the game information kept with it. You use an email code or Google sign-in to open it.
- Guest: someone playing without signing in. Guest progress is kept on that phone rather than in an account's cloud save.
- Cloud save: a copy of your game progress on our servers. It lets a signed-in player who meets the account rules bring progress back on another phone.
- Profile: the card other players can open. It shows your game name, Nimo's look and some game statistics. It is different from your private sign-in details and your full save.
- Service provider: another company or service that helps deliver a feature. Examples are an email delivery provider, Google for ads and Android payments, Apple for App Store payments where enabled, and a provider that stores encrypted backups. The sections below explain what each receives.
- ID or code: a number or group of letters and numbers used to recognise something, such as an account, phone, purchase or report. An ID can connect information even when it does not contain a real name.
- Game statistics: numbers about your play, such as solved stages, scores or time spent playing. The profile section explains which of these other players can see.
- IP address: the internet address seen when your phone connects to a server. It can give an estimate of your country. It does not tell us your exact GPS location.
- Consent: a choice to allow a particular use of information where that use relies on your permission. Deliberately signing in to use an account, your ad choices and your app health choice serve different purposes.
Who we are
John Philip Sabinet operates Nimo, an independent game. In this policy, “we”, “us” and “our” refer to Nimo's operator. For anything about your privacy, email support@sabinex.app.
Age and country rules
When you first open Nimo, it asks for your birth month and year. That answer stays on your phone. It is not sent to Nimo. The app uses it to decide which features you can use. This is your own answer, not a check of your identity.
The account age is the minimum age for an account where Nimo supports connected features. Nimo's default minimum is 13. A higher age or a limit on connected features can apply under our reviewed local rules. Our server tells the app which country rule to use. The app does not send your birth month, birth year or exact age to the server.
The purchase age is the minimum age for buying something with real money, such as coins or Infinity. The default is 13. A country may require a higher age. You also need an account to buy. If the account age is higher than the purchase age, you must meet that higher age too.
We review country rules and update the rules supplied to the app. Where the support needed for connected features is not available, those features stay unavailable. This includes accounts, purchases, ads and technical reports. You can still play local puzzles.
To choose a country rule, our server uses your connection's IP address and DB-IP's IP-to-country data. Credit: db-ip.com, licensed under CC BY 4.0. The country lookup does not add your IP address or country to your account. Ordinary connection logs can still contain the IP address, as explained under Technical connection information.
The country is only an estimate. Travel or a VPN can change it. It does not prove where you live or how old you are. For example, a VPN may make your connection appear to come from another country.
The app regularly asks for a fresh country rule. If it has no fresh answer, it uses the default age of 13 for accounts and purchases. A country we cannot identify does not automatically block every account feature. The server also applies country restrictions when it can identify the country. If the app already knows that connected features are restricted, it keeps that restriction until the server confirms a change.
App health reporting uses its own 13+ minimum and fresh country permission. Some countries need a higher reporting age or remain unavailable while their requirements are assessed. An unknown country or expired permission does not enable reports. Account and purchase ages do not grant reporting permission.
Guests below the account age or with an unknown age
If you are below the account age, or have not answered the age question, you play as a guest. Nimo sends us no account, sign-in session or device ID for this guest play.
- Your progress, coins, items and settings stay on your phone.
- Nimo downloads public game content. This includes new puzzles, game settings and news.
- You can browse public rankings and see other players' displayed names. You are not listed yourself.
- You cannot sign in, make purchases, use friends, send likes or gifts, send player or problem reports, or choose a custom name. Real-money prices are not shown.
- App health reports are unavailable when your age is unknown or below the reporting minimum. An eligible guest can choose reports without an account.
Our servers still see an IP address when the app downloads public content or rankings. They use it to handle the request, apply country rules and protect the service. Ordinary connection logs keep it until newer records replace it. App health requests have different protections and are left out of those connection logs.
Playing without an account does not mean there are no internet connections. It means that your guest progress is not saved in a Nimo account and these requests do not send an account or sign-in session.
Players from the account age to 17
Before you sign in, Nimo explains that signing in starts account use and automatic cloud saving. If you meet the age and country rules, you can sign in directly; there is no second Save progress or account/data choice to make. You can still choose to remain a guest.
If you sign in and use an account:
- The phone sends us an account-use acknowledgement after a successful sign-in you start. It includes the version of the sign-in disclosure and when it was acknowledged. Loading or refreshing an existing session does not create a new acknowledgement.
- We keep that record with your account and rankings setting. The same acknowledgement is used for eligible adults and teens, so it does not identify you as a minor. It does not include your birth month/year, birthday or exact age. Older account-choice records may show that an account previously used the teen flow.
- We keep the sign-in details, save and profile described under If you sign in. We also keep the device code described in the next section.
- You can keep the name Nimo drew for you, such as ink·1234, or choose a nickname. Our server checks nicknames for inappropriate words before accepting a change. Please do not put your real name, contact details or other private information in a nickname.
- Existing and new eligible active accounts are shown on public rankings by default. You can hide in Settings › Privacy & safety › On the rankings after confirming. A successful manual change starts a 30-day wait before you can change visibility again, including turning rankings back on. A later sign-in keeps a confirmed manual visibility setting.
- If you meet the account rules, you can add friends by code, send and receive friend requests, and block or report another player. Other players can open your profile through a friend code or friendship. They can see your accepted nickname or drawn name and the game statistics shown there. Using friends does not turn rankings on.
- You can send and receive likes, use supporters and view popularity statistics. Paid gifts and boosts follow the account and purchase rules. You can turn gifts off.
- You can buy items allowed by these rules through Google Play once you meet the purchase age and account age. A parent can turn on purchase approvals for a child's Google account through Google Play.
Gift access and phone gift alerts have different age rules. A teen who meets the account rules can use gifts when the account and purchase rules allow it. The remote gift alerts sent to a phone are adult-only. Receiving a gift in Nimo does not by itself allow a teen to receive those phone alerts.
Use Settings › Account & cloud › Delete account if you want to stop account use and request deletion. The separate account-choice/take-back control from older app versions is no longer offered. A withdrawal already recorded by an older version is still respected: account use stays restricted and its 30-day deletion request remains protected until you deliberately sign in to recover before the waiting period ends. Loading or refreshing an existing session does not undo it. A ranking list another phone has already loaded may still show an old entry until it refreshes, usually within a few minutes.
Your ad treatment does not depend on signing in. It follows the separate rules under Ads. The age and country rules still apply when someone else uses the phone or its age answer changes. Signing in is not a parental identity check.
Guests who meet the account age
If you are at or above the account age but do not sign in, your progress, coins, items and settings stay on your phone.
For this guest play at or above the account age, we receive a device code. On Android, it is a scrambled version of the Android ID, made using a process called hashing. The original Android ID is not sent. On other supported platforms, it is a random code kept on the device.
We use the device code to deliver news and maintenance notices and to enforce device restrictions. Our account service keeps the code's platform and app version. It also records when the code was first and last seen. This code is not part of app health reports.
A device code can recognise the same phone across requests. It is different from the fresh random code used for an individual app health report. For guests at or above the account age, this device code can stay the same even without a signed-in account.
If you sign in
You must be at or above the account age and allowed to use online features. Deliberately signing in starts account use and automatic cloud saving for eligible adults and teens. There is no additional account/data choice. A connection problem can delay a save; the app distinguishes a confirmed save from saving, offline or an account that needs attention. When you sign in, we keep the following information:
- Sign-in details: your email address if you use email codes, or your Google account ID and email address if you use Google sign-in. Nimo has no passwords.
- Your save: solved stages, stars and times, coins, hints, items you own, rewards you have claimed, streaks, play time, stamps, level and Notebook entries you have found.
- Your appearance and choices: your appearance, theme and profile choices, plus up to five saved wardrobe presets. We keep the edit records needed to sync them between devices. Saved presets are private. Other players see the appearance you wear on your profile.
- Account-use acknowledgement: the version and time of the sign-in disclosure acknowledged through a successful sign-in you start. It is linked to your account, not your birthday or exact age, and is not a minor-only record. Older agreement and withdrawal records remain protected as described above.
- Your rankings setting: whether you are shown on public rankings and when visibility changed. Existing and new eligible active accounts are shown by default. Hiding requires confirmation in Settings › Privacy & safety › On the rankings. Manual visibility changes must be at least 30 days apart; signing in again does not reset a confirmed manual choice or that wait.
- Your public profile: your accepted nickname or Nimo's drawn name, Nimo's look, your level, some puzzle statistics, popularity and gift totals. The visibility rules are explained below.
- Sign-in sessions: the devices signed in to the account, with their platform and app version.
- Friends: the players in your Nimo friends list and the friend requests you send or receive. This is a friends list inside Nimo. It is not your phone's contacts.
- Likes, gifts and boosts: the records explained in the next section.
- Blocks and player reports: the players you block and reports you make about another player. You select a reason, such as cheating, name or other. There is no free-text field for these player reports. We keep moderation notes and name history to handle reports and enforce name rules.
- Problem reports: reports you choose to send about a problem in the game. These are linked to your player account, as explained under Reports about a problem.
Play Games on Android
Where Play Games is available, you can connect your Play Games profile in Account settings. Nimo checks the profile with Google and keeps its player ID, the linked Nimo account and connection history. The first connection is your choice. A known, active connection can help restore the same Nimo account later. Google and email sign-in remain available, and your Nimo save and purchases stay with your Nimo account.
After connection, Nimo sends Google the achievements you have earned, including earlier ones. This does not award Nimo coins or items again. Our server keeps confirmation records so another phone does not create a separate copy of each record. We do not send your full cloud save, purchase receipts or Nimo friends list through this feature.
Google's Play Games service handles its gamer identity, achievement history, and service analytics and diagnostics. Your Google profile settings control who can see your Play Games activity. Nimo uses an authorization code briefly to verify a connection; it does not keep a Google refresh token for this feature. See Google's privacy policy.
Disconnecting in Nimo stops future achievement sync and automatic restoration through that link. Signing out also stops automatic restoration on that phone until you deliberately connect again. Neither action deletes achievements already held by Google. You can manage or delete those through your Play Games profile or Google Account. Final Nimo account deletion removes our game-side sync records; limited revoked-link records can remain to prevent an old connection from restoring a deleted or disconnected account.
Likes, gifts and boosts
The Google Play payment descriptions in this section apply to Android. App Store purchases, where enabled, follow the separate Apple purchase section below and the same Nimo account, purchase and gift rules.
Signed-in players who meet the account rules can like another player's profile. They can also buy a coin pack, Infinity card or popularity boost for another player through Google Play. The default account and purchase ages are 13. Higher country rules and restrictions on connected features still apply. A recipient can turn gifts off. Blocks, account restrictions, deletion holds and previously recorded account-choice withdrawals also prevent these interactions.
For likes, we keep who liked whom for today and yesterday. You can like each profile once a day. After that short history ends, we keep only totals. These include likes received and the number you have given for stamps.
For each gift or boost, we keep who gave it and who received it. We also keep the product, gift points, popularity boost, the month it counted in, when it was granted and whether it was refunded. A gift's purchase record keeps who received it too. The gift record does not include amounts of money. Google Play handles the payment. Separate purchase receipt records are explained below.
Popularity records include lifetime totals for likes and boosts received. They also include gifter points based on each gift's tier, who has boosted you and by how much, and whether you accept gifts. We keep monthly records for accounting. The Popular and Gifters boards do not reset each month. You can turn gifts off in Settings.
What other players can see
Your rankings choice controls public ranking participation. It does not make your whole profile private.
A player can open your profile through a friend code or friendship even when rankings are off. The profile can show your accepted nickname or drawn name, Nimo's look, level, some puzzle statistics, lifetime popularity, gifter points and received-gift totals. It also shows whether you accept gifts. It does not show your sign-in email or your private saved wardrobe presets.
For example, confirming that you want rankings off keeps you out of the public ranking lists. If you give another player your friend code, that player can still use it to reach your profile. Choose a nickname you are comfortable showing to other players.
The all-time Popular and Gifters boards show the names, Nimo looks and points of eligible accounts whose rankings setting is on. This is the default for existing and new eligible active accounts, subject to the manual visibility setting described above. Your profile can also show your place on either board when you are in its top 3.
Your supporters list can show up to 50 players who boosted you, with their boost points, if those players are shown on rankings. If you boost someone while you are shown on rankings, your name and boost points can appear on that person's supporters list.
When you receive a gift, your Inbox shows who sent it and what it was. This is another way your game name can be shared. Turning off ranking participation does not erase a gift message already delivered to someone. The storage and deletion rules for those messages appear under How long we keep it.
These are game names and game statistics, but they can still identify you if you choose a recognisable name or share your friend code. Do not use a nickname to publish private information about yourself or another person.
Reports about a problem
When you choose Report a problem, we keep the topic you select: puzzle, progress, purchase, display or other. You may add a note of up to 500 characters. Before you send it, What's sent shows the technical details that will be included.
Those details include the app version and build, system and screen size, text size, language, game and stage, and sync status. The app does not attach a screenshot or email address. Because you send the report while signed in, it is stored with your player account. Please leave personal details out of the optional note.
A manual problem report is different from an automatic app health report. Turning off App health reports does not delete a problem report you already chose to send. It also does not prevent you from choosing to send another problem report if you meet the account rules. Its own storage period is 90 days, or until account deletion if that is sooner.
Technical connection information
Ordinary server requests create connection logs. These can contain the IP address, request time and address requested. We use them to protect the service and keep it reliable.
The logs have size limits. Newer records replace older records once a log reaches its limit. How long an entry stays depends on how busy that service is. There is no fixed number of days for these ordinary logs.
Downloading public content, using account features and receiving a reward confirmation can create ordinary connection records. App health requests have the separate rules below. Clearing local progress does not remove existing server connection records.
Optional app health reports
App health reports are optional and available from 13 where supported. A country may require a higher reporting age. Your age answer stays on this phone; we do not receive your birthday or exact age. On is the initial preference for new and existing installations without a current reporting choice, but it is not permission to collect. Nimo starts collecting only after an eligible player chooses Send reports. An existing reporting choice, including Off, stays in force. You do not need an account.
The server supplies the reporting rule for a known supported country, with a 13+ baseline and stricter regional safeguards where needed. This is separate from account and purchase rules. Unknown age, age below the reporting rule, an unknown or held country, expired permission or an unsupported app version does not enable collection. Nimo needs fresh permission each run. Losing eligibility or a reporting shutdown stops collection and removes waiting reports. These product safeguards are not a certification of every law worldwide.
Before reporting begins, Nimo shows a short explanation with Send reports, an Off option and a link to this policy. Dismissing that explanation records Off. A player without a current reporting choice sees the notice when they first become eligible. Lowering the reporting minimum does not reset an existing choice. After the choice, Off stays Off across restart and sign-in. You can keep playing puzzles and change the choice in Settings › Privacy & safety › App health reports without signing in.
Turning it off stops new collection and uploads. It also clears reports still waiting on that phone. The setting stays on the phone and is not part of your cloud save. Turning it off does not remove totals the server has already received. Those totals follow the storage periods below.
The reports contain only approved technical fields:
- Crash or error summaries: an error type and fault code from fixed lists, the affected part of Nimo, approved locations in Nimo's code or known software it uses, the Nimo screen, app version, system such as Android or iOS, and phone memory size in broad steps. The phone leaves out the error's own message and other text. The server checks the allowed fields again. Matching faults are grouped together. We keep their count and the times they were first and last seen.
- Daily totals: app opens and returns, unexpected endings, broad ranges for start-up time and screen smoothness. They are grouped by app version, system and phone memory size in broad steps (2, 3, 4, 5, 6, 7, 8, 12, or 16 GB and up), never the exact amount of memory.
- A fresh random report code: this helps recognise retries and reduce duplicate counting. It is not an account, device or installation ID. Each upload also confirms that the compatible app checked eligibility and the reporting choice against the current policy. These constant confirmations do not contain an age or identity and are not stored with technical totals.
Stored reports have no field for an account, player, name, contact details, age, device ID, installation ID or advertising ID. We do not connect them to an account. We do not use them to build a history of an individual player. A technical summary can still describe a particular fault or occurrence, so it follows this policy's protections and storage limits.
As with any internet request, the connection temporarily exposes an IP address. For app health requests, we use it only to handle the connection, check country availability and limit abuse. We do not save it with health reports or in logs of health-report connections. Address-based abuse checks use temporary information in server memory. That information is not saved with health reports or linked to the stored health statistics.
App health requests leave out account sign-in details. They also leave out cookies, which are small records used by websites, and information about the web page you came from. We do not redirect these requests to other services. The logs for health reporting leave out the connection details, information added to the request address, and the full error-report contents. These protections apply to Nimo's app health reporting. Other requests the app makes have their own rules.
We use app health reports to keep Nimo reliable and fix faults, and, with the onboarding step totals described below, to improve new players' first days. We do not use them for ads, player profiling or account decisions. The updated optional reporting flow relies on your informed reporting choice where consent is required. You can withdraw that choice by turning reports off, without losing game features. Temporary connection, country and abuse checks have the separate service/security purposes described above. You can contact support@sabinex.app about these uses.
We may use these reports to send Nimo's operators limited reliability summaries through our existing mail and alert systems, so they can prioritise faults and record whether a fix has been reviewed. A module-fault summary contains only the affected part of Nimo, a fixed fault code, app build and platform, plus counts, timing and review status calculated on the server. These summaries exclude account, player and device identifiers, saves, request bodies and raw error text. They follow the same reporting choice and eligibility rules above.
Onboarding step totals
App health reports from new players also count three steps: that a new player chose Send reports, that they finished First steps, and that they came back on another day. Each phone counts each step once. Nimo starts counting only after you choose Send reports on the notice that names these counts, so nothing from before that choice is included. We use these totals to improve Nimo's first days for new players.
The server groups these counts by UTC day, step, app version and system. They contain no account, player or device ID, and they follow the same eligibility, choice, IP address and storage rules as other app health reports: daily totals are removed after 90 days. Turning app health reports off stops these counts too. The phone keeps a small note of which steps it has already counted, so none is counted twice; that note is never sent.
Optional Training learning counts
If this separate option becomes available, Nimo will ask before collecting Training learning counts. It starts off and is independent of your app health choice. With your permission, Nimo can send totals for how often each Training trick is started, finished or uses Show me. We use these counts to understand and improve lessons. The initial intended availability is players aged 13 or older in the Philippines, subject to the separate country rule and the app health eligibility rules above. App health reporting must also be on; allowing one option does not turn on the other. You can use Training without sending counts.
The server groups these counts by UTC day, trick, app version and system. They contain no account, player or device ID. A fresh random report code helps avoid counting retries twice. As with app health reports, your IP address is used temporarily for the connection, country checks and security; it is not stored with these totals or in app health connection logs. Daily totals are removed after 90 days; backups follow their own retention schedule.
If available, you can turn Training learning counts off in Settings › Privacy & safety. This stops new collection and removes waiting Training counts from that phone while leaving other permitted app health reports intact. A request already sent cannot be recalled. Totals already received cannot be identified as yours and removed individually. Turning off app health also stops these counts. You can continue playing without either option.
We may use these reports to send Nimo's operators limited reliability summaries through our existing mail and alert systems, so they can prioritise faults and record whether a fix has been reviewed. A module-fault summary contains only the affected part of Nimo, a fixed fault code, app build and platform, plus counts, timing and review status calculated on the server. These summaries exclude account, player and device identifiers, saves, request bodies and raw error text. They follow the same reporting choice and eligibility rules above.
The health switch controls Nimo's app health reports only. It does not turn off technical information about Google's ad software, purchase checks, ordinary connection logs or reports you choose to send to support. Those have separate purposes and rules in this policy. Reading the health notice is not parental verification and is not the account and data agreement.
Information we do not collect and purchase information
Nimo does not use a separate analytics service from another company. Google AdMob handles ads and has its own information practices, including technical information about crashes and performance. The optional adult-only PubMatic experiment is explained under Ads.
Your birth month and year stay on your phone. We do not receive them or a full birth date. We do not access your phone's address book, photos, microphone or camera. Nimo does not ask for permission to read your device's location. We do not collect precise GPS location. Google's ad software can estimate an approximate location from an IP address.
Google Play purchases on Android
Purchases use Google Play. You must meet the purchase age and account rules described above. Google handles payment. Nimo does not receive your card or bank details. We receive purchase confirmations and keep the records needed to deliver items, handle renewals and handle refunds.
When purchase receipt delivery is available, we email the receipt to an address that belonged to your account when you bought and still belongs to it. We use your email-code sign-in address, or otherwise the address from Google. If that address changes or is removed, we do not send the receipt to a replacement address.
Receipt records include Google's order number, the product and items granted, purchase time, language and delivery status. Our account service also records which sign-in address the receipt was for and when that address was used. Nimo's receipt records do not contain the payment price, tax or billing address. Google Play supplies its own payment receipt.
For example, changing the account email does not cause an old Nimo receipt to be sent to the new address. The section on how long we keep information explains how we keep a receipt that can no longer be sent.
On Android, the app may request a Play Integrity token from Google during a purchase. When Play Integrity verification is enabled, we receive Google's verdicts about the app and phone. We use them only to help prevent fraud. They are not part of optional app health reports.
App Store purchases on iPhone and iPad
App Store purchasing is currently off. The following describes the purchase information used where that service is enabled; it does not mean purchases or production verification have been activated.
Apple handles payment. Nimo does not receive your payment card, bank details or Apple Account password. Nimo sends Apple a random purchase code called an app account token. Nimo can connect that code to the account and player that started the purchase, the selected product and any intended gift recipient. The code is not your sign-in email or Apple Account ID. It is separate from an advertising ID, Nimo's device code and an app health report code.
The app sends Nimo Apple's transaction number and signed transaction confirmation. When configured, our verification service checks Apple's signed purchase facts and obtains transaction, subscription and refund updates from Apple. The information includes product and transaction identifiers, the original transaction linking a purchase or subscription's history, the app account token where present, purchase and expiry times, and renewal, ownership, refund or revocation status. It distinguishes test transactions from production transactions. We keep verified facts, verification hashes and delivery records with the account and player references needed to deliver the right benefits and prevent repeated claims. A gift can also leave a recipient reference under the gift rules above.
Apple confirms the store purchase; Nimo decides which Nimo account can receive its game benefits using the recorded ownership and verified transaction. Restoring a purchase checks that ownership and its current entitlement. It does not transfer purchases to another Nimo account, restore an erased cloud save or grant the same spent coins again. The app also keeps a local pending-purchase record so it can retry delivery after interruption.
Apple supplies its own payment receipt. The Google Play receipt-email process and address rules above describe Nimo's Android receipt service; we do not promise that service for Apple purchases. Manage an App Store subscription through Apple's subscription controls and request an App Store refund through Apple. These purchase checks are separate from optional app health reports.
Previous closed-test sign-ups
Public sign-ups for Nimo's closed test have ended. Before the public release, the form on sabinex.app asked for your email address and confirmation that you were 13 or older. It sent an email link to confirm the sign-up.
The sign-up record contained the address, the email's language, and when you signed up and confirmed. The confirmation link was stored in a scrambled form. We used the address only to add you to the tester list in Google Play Console and to email the invitation. Google handled participation in the test under its own terms.
These records were separate from game accounts and did not put email addresses on public rankings. The storage rules for unconfirmed and confirmed sign-ups are listed below.
Guide counts and reactions on the website
The guides on nimo.sabinex.app can show how many times each guide was read and how readers reacted to it. When this is turned on, your browser tells us once a day that you read a guide, after the page has been open for about 10 seconds. You can also pick one reaction (Helpful, Love it, Confusing or Something's wrong) and preset reasons for what was unclear. There is no box to type in.
We keep only a total for each guide, day and kind of count. We do not use cookies, accounts, device IDs or fingerprints for this, and we do not store your IP address or browser details with these counts. Our server uses part of your IP address for a short time, in memory only, to limit how often counts can be sent. These requests are not written to our connection logs. Your browser keeps a small note of what it already sent, so that a read is counted once a day and you keep one reaction per guide. You can clear it by clearing this site's data in your browser.
How we use information
We use the information described in this policy for these purposes:
- To choose the account age for the country your connection appears to come from.
- To save account progress and bring it back on another phone.
- To run rankings, including Popular and Gifters, as well as friends, likes, gifts, the Daily set and events.
- To keep the game fair and secure and help stop cheating.
- To send sign-in codes, purchase receipts and important account emails.
- To deliver the notifications you allow.
- To fix bugs and slow screens, handle the problems you report and keep the servers working.
We do not use your account details or saved puzzle progress to personalise ads. Advertising information is handled separately. Providers' own disclosures may describe uses that count as a “sale” or “sharing” under some privacy laws. See Ads for those providers and choices.
Ads
Nimo shows ads from Google AdMob. These include a small banner and, from age 13 and the applicable account age, videos you choose to watch for a reward. There are no pop-up ads between levels. Only family-friendly, G-rated ads are allowed. No ads forever and Infinity remove banners.
To show and count ads and stop ad fraud, Google's ad software in Nimo collects and sends information to Google for players of every age. It includes:
- An IP address. Google uses it to estimate an approximate location, such as country or city.
- On Android, the phone's app set ID and information about the phone and Nimo. Examples include phone model, Android version, language and app version. On iPhone and iPad, device and app information can include phone or tablet model, iOS version, language and app version; identifiers depend on the platform, SDK configuration and permissions.
- Ad interactions, such as views, taps and completed videos.
- Crash and performance information about the ad software.
An app set ID is a code used by Google's software. It is different from Nimo's account ID and the random code used for an app health report. This ad information is collected through the ad software. Turning off Nimo's app health reports does not turn off the ad software's technical reports.
On Android, from age 13 and the applicable account age, Google's ad software may also send the phone's advertising ID. Adults' ads may be personalised unless they turn that off. Personalised ads use information to help choose ads for that person. We tell Google's ad software to use non-personalised ads for teens who meet the ad rules.
On iPhone and iPad, Nimo does not ask for tracking permission or use Apple's advertising identifier. Nimo tells AdMob to use non-personalised ads and disables AdMob's publisher first-party identifier. Google may still process app- or device-scoped identifiers and the information described above to deliver and measure ads and help prevent fraud.
For anyone under 13, under the applicable account age, or whose age Nimo does not know, we tell Google's ad software to treat the player as a child. Children and teens explains what this means under Google's rules. Account permission and ad treatment are separate. A lower country account age never makes ads less restricted for an under-13 player. Signing in, or an account-choice withdrawal recorded by an older app version, does not change these age rules for ads.
This list follows Google's own description of what its ad software collects. Google updates its description from time to time.
Where Google's consent tool requires it, Nimo asks players who meet the ad rules and are at or above age 13 and the account age for consent before requesting any ad. Settings › Ad privacy options appears wherever that consent tool needs it. You can use it to change your choice.
Players under 13, under the account age or with an unknown age are not asked for advertising consent. Nimo tells the consent tool that they are under the age of consent. We tell Google's ad software to use the restricted child treatment described below.
You can also reset the advertising ID or turn off personalised ads in your phone's settings. Depending on your phone, look under Settings › Google › Ads or Settings › Privacy › Ads. This is separate from the app health switch and the public rankings choice.
Those Google and advertising-ID setting paths describe Android controls. On iPhone and iPad, use Apple's privacy and tracking controls where available; their effect depends on the iOS version, permissions and ad service. Refusing tracking authorisation does not turn off all ad connections or the SDK's separate technical reports.
Optional adult-only PubMatic experiment
We are preparing an optional advertising experiment using PubMatic through Google AdMob. It is currently off. No Nimo ad requests go to PubMatic through this experiment.
If enabled, it will apply only to players whose age answer makes them 18 or older. It also requires a current check that the feature is allowed in your country and follows the existing advertising consent choices. Anyone under 18, or with an unknown age, is excluded from this added bidder. Teens who meet the ad rules keep their existing Google AdMob non-personalised ads. G-rated ads and the existing placements and rewards still apply.
A bidder is an advertising company that may take part in choosing an ad. If this experiment is enabled, PubMatic may process information about ad requests and interactions. This can include approximate location estimated from an IP address, permitted advertising or other device identifiers, and information about the device and app.
PubMatic may use that information for bidding, delivering and measuring ads, personalisation where permitted, and fraud prevention. It may share it with advertising buyers, measurement partners and service providers. Its Platform Privacy Policy explains its uses, storage periods and privacy choices. It also explains uses that may count as a sale or sharing under some US state laws.
The experiment does not upload Nimo account records, cloud saves or Nimo app health reports to PubMatic. Google and Nimo's server continue to verify rewards as explained next. This section describes the experiment's privacy effects if it is enabled; it does not change its current off state.
Videos for a reward
When you choose a rewarded video, Nimo gives Google's ad software a one-time code for that video. If you are signed in and this phone's progress belongs to your account, it also gives a scrambled code that our server can connect to your account. That code changes for every video. Google does not receive your player ID itself through this reward code.
After the video, Google sends the codes back to our server with a signed reward confirmation. The confirmation contains Google's transaction number, the ad, the reward and the time. We use it to check that the reward was earned and, for a signed-in player, which account should receive it.
The changing code does not make the reward unrelated to your account. Our server can connect the confirmation to the right account so it can deliver the reward and prevent repeated claims. A signed-in reward also leaves a record in that account's coin history.
We keep Google's confirmation for 30 days. The video code in your coin history stays until account deletion. Account records also keep information about when this method for checking a reward first applied to the account. That record stays until account deletion too. Like other ordinary requests, Google's confirmation also appears in server connection logs. Those logs have the storage periods based on log size explained above.
Google uses information under its own policy: https://policies.google.com/technologies/partner-sites
Optional notifications
Notifications are a choice on each phone. After answering the age question, you can enable local Daily reminders, Daily puzzles and known event alerts without an account. These local choices do not enable account alerts or register a remote delivery address. Public Inbox messages remain available inside Nimo.
Signed-in players who meet the account rules can separately allow account alerts. Android uses Google's Firebase Cloud Messaging (FCM). iPhone uses Apple's Push Notification service (APNs) when configured.
The selected provider receives the delivery address for your phone and the limited alert content needed to deliver the alert. The delivery address is a notification token, not your home address. Content can include the category, title, body, a public display name for a friendship alert, and a destination code used to open the right place in Nimo. These notifications are not end-to-end encrypted. The delivery provider can process the content needed for delivery.
Nimo keeps the verified connection between the installation and account. It also keeps delivery state to respect your choices and avoid duplicate alerts. Friend alerts follow account and friendship age, country and access rules. Remote gift alerts are for adults only. Access to gifts inside the game for teens who meet the rules follows the separate rules already explained.
You can turn notifications or individual categories off in Settings. You can also change permission in your phone's settings. Signing out or changing accounts stops the former account's alerts on that installation. An alert already passed to the phone's operating system may still arrive; cancellation is best effort at that stage.
Delivery depends on permission, internet access, device settings and provider availability. Turning on a local reminder does not automatically turn on remote account alerts. Turning off phone alerts does not delete an Inbox message already present in the game.
Contacting support
If you email support@sabinex.app, we receive your address and whatever information you include. We use it to answer your request. Send only what is needed to explain the problem. For account requests, we may ask you to confirm that the account is yours so we do not disclose or remove someone else's data.
Support email is separate from automatic app health reports and from Report a problem inside the app. An email can contain identifying information you choose to include. Please do not send passwords, payment card details or other unnecessary private information.
Where information is kept and who receives it
Our servers are in the European Union. Encrypted backup copies are also kept by a backup storage provider in the European Union. The copies are encrypted before they leave our servers. The provider stores those encrypted copies rather than an ordinary readable copy of your save. We control access to the readable backup data.
Sign-in codes are protected while stored and expire after 10 minutes. That short expiry concerns the sign-in code. It does not mean your account or sign-in email is deleted after 10 minutes.
Other services receive information for the features they provide. The earlier sections describe Google sign-in, Google Play purchases, App Store purchases where enabled, Google AdMob ads, the currently off PubMatic experiment, and FCM or APNs notification delivery. Apple and the configured purchase-verification service receive the purchase information needed for those App Store checks. Other players receive the profile, ranking, supporters and gift information explained under What other players can see.
Emails we send: sign-in codes, purchase receipts and important account notices are sent through email delivery providers or our own server. The provider sending an email receives your address and that email's contents. It receives them to deliver the email under its data processing terms.
- A provider may keep the email and sending logs for up to about a month. It may also count opens and clicks in aggregate, meaning combined totals.
- One of these providers processes emails mainly in the United States. Your address and the email can therefore be processed there.
- Invitations to the previous closed test were sent from our own server.
For example, an email delivery provider needs the sign-in email's address and contents to send your code. It does not receive your full cloud save through that email delivery. Server storage in the European Union does not mean every service described here processes information only there.
Messages to Nimo's operators: the mail or alert provider delivering a reliability summary receives the limited contents described under Optional app health reports. These diagnostic messages are separate from operational account, security or moderation messages, which may include the information needed to handle that particular matter.
Operator reliability records and delivered mail or alert copies follow the operator's and delivery providers' retention settings. The app health rules of 30 days after a fault group's last sighting and 90 days for daily totals do not automatically delete operator records or copies already delivered.
How long we keep it
Different records have different lifetimes. The periods below concern the records described. Removal is carried out through scheduled processing rather than necessarily at the exact moment a period ends. Backup copies follow their own schedules. The exceptions below explain records that can remain after account deletion.
- Account and save: kept until your account is deleted, including deletion after a long period of no use where applicable. See Deleting your account and Accounts nobody uses.
- Account-use acknowledgements, older account choices and rankings settings: kept with the account until deletion. This includes the disclosure version, when it was acknowledged, ranking visibility and manual-change times, and any withdrawal recorded by an older app version. Those older withdrawals retain their 30-day account deletion waiting period and recovery protection.
- Launch-reset and important account-notice records: kept with the account until deletion, including when it has no current game save. They record eligibility, one-time rewards and notice status so the same bundle or message is not issued again. Emails already delivered to your mailbox follow your email provider's rules.
- Individual ranking results: kept for 30 days. After that, only the best result per stage stays as part of your save.
- Problem reports: kept for 90 days, or until account deletion if that is sooner.
- App health fault groups: removed once 30 days have passed since the fault was last seen. A fault that keeps recurring can stay longer because its last-seen time changes.
- App health daily totals: kept for 90 days. These totals are kept apart from accounts. Deleting an account does not let us identify or delete that account's contribution to them. Backup copies follow the backup schedules below.
- Google's rewarded-video confirmations: kept for 30 days. Video codes in the account's coin history and the account's history of reward checks stay until account deletion.
- Likes: the record of who liked whom is kept for today and yesterday only. The totals stay with the account.
- Gifts and boosts: records stay with the account. An unpaid gift you started is removed after 30 days.
- Purchase receipt records: normally removed 90 days after the receipt is finished and both our game server and account service have recorded that finish. Finished means it was sent or the purchase was refunded. The confirmation between services normally happens within minutes. If receipt emails are switched off or that confirmation fails, the 90 days start when the confirmation is made.
- Receipts not yet sent: kept until sent, refunded or account deletion. A receipt that cannot be sent at all, for example because your address changed, stays without an address until account deletion. This prevents it from later going to a different address.
- App Store purchase and ownership records, where enabled: transaction and original-transaction numbers, purchase codes, account/player reference codes, verified purchase and delivery facts, and refund or reconciliation records are kept separately from Google Play receipt emails. These records can remain after account deletion to reconcile the purchase and stop a transaction being claimed again or by another account. They cannot restore the erased account or its cloud save. The Google Play receipt-email 90-day period does not apply to these records; no fixed automatic expiry for these Apple ownership records is currently implemented.
- An email address no longer used for sign-in: kept for 90 days. This can happen, for example, after your Google account's email address changes.
- Unconfirmed closed-test sign-ups: removed 7 days after our last email.
- Confirmed closed-test sign-ups: kept until the closed test ends or you ask us to remove you.
- Ordinary server logs: kept until newer records replace them. Each log has a data-size limit rather than a fixed time limit. Retention depends on traffic for that service.
- Backups on our own servers: replaced within a few days.
- Encrypted copies at the backup storage provider: daily copies are normally deleted 2 to 3 weeks after they are made. Weekly copies are normally deleted after about 2 months. Deletion can take a little longer on the provider's side.
- Backups needed to investigate a fault or security problem: the copies involved may be kept until the investigation is resolved.
- Limited deletion and security records: account or player reference codes, dates, actions and deletion audit totals can remain. They help confirm deletion, coordinate removal between services, and protect the service and backups. They cannot restore a deleted account or cloud save. Device restriction records are separate from app health reports.
- Support correspondence: kept as needed to handle your request and applicable obligations.
Gifts when the sender deletes their account: the sender's records of gifts and boosts given, popularity and gifter points, supporters list and place on others' supporters lists are erased with the account. Items already delivered to recipients remain theirs. Some delivered copies still name the sender.
Each recipient's gift or boost Inbox note keeps the sender's game name as it was then, player ID and what was given. Notes expire 20 days after they are sent. Regular clean-up normally removes them about a day later, or sooner if the recipient deletes their account. An Infinity card that was given keeps the sender's player ID. After the sender's account is deleted, that ID no longer opens an account.
Gifts when the recipient deletes their account: the gift no longer names the recipient. The sender's purchase record can still keep a reference code for that recipient, but it no longer opens an account.
For example, deleting your account does not take back coins already delivered to another player. It also does not immediately remove the gift note from that player's Inbox. The note follows its own short lifetime described above.
Deleting your account
Open Settings › Account & cloud › Delete account in Nimo. When the app confirms that the request was accepted, this phone's game progress is cleared and sign-in sessions on all devices are ended. We start removing your profile from public rankings. The services involved may need a short time to process that change. A list another player already opened may show your old entry until it refreshes.
There is a 30-day waiting period. After that period, scheduled processing deletes the sign-in methods and cloud game data. This includes your save, wallet, items and ranking records. Removal need not happen at the exact second the waiting period ends.
If you meet the account rules and deliberately sign in again before the wait ends, you can keep the account and restore its cloud save. There is no second teen account-choice step. Once the account and cloud data have been deleted, the waiting-period recovery described here is no longer available.
Gifts already delivered to another player, limited deletion and security records, and separate technical totals follow the storage rules above. Backup copies expire on their own schedules. Asking for deletion does not cause every copy or separate record to disappear immediately.
You can also email support@sabinex.app from your sign-in address to request deletion. We may need to confirm account ownership. Guests can clear local game progress in Settings or remove the app's local data. Clearing local data does not remove separate server connection records or technical totals.
Deleting a Nimo account does not cancel an Infinity subscription. Cancel the subscription in Google Play. Removing the app or its local data also does not cancel the subscription. Account deletion, clearing a phone's progress and cancelling a store subscription are separate actions.
For an Infinity subscription purchased through the App Store where enabled, cancel through Apple's subscription controls instead. The same separation from Nimo account deletion and local-data removal applies. Apple purchase and ownership records follow their separate retention rules above.
Accounts nobody uses
If an account has not been used for 365 days or more, we may delete its sign-in methods and cloud game data under the same rules. This is not a fixed deletion date. An unused account may remain longer. We do not delete an account for inactivity while it has an active subscription.
The separate storage rules for delivered gifts, limited security records, technical totals and backups still apply when an unused account is deleted.
Children and teens
Nimo is made for everyone, including children. Account access depends on the age answer on the phone and the account age for the estimated country. The default account age is 13. Some countries have a higher age or connected-feature restrictions. When the app has no fresh country answer, the default is 13, while a known connected-feature restriction stays in place as explained above.
The age answer and estimated country do not verify who you are. Nimo does not offer a parental-verification route to an account below the applicable account age. A parent approving a store purchase does not change Nimo's account age.
Below the account age, or age unknown: you play as a guest. There is no account, sign-in or purchase, and real-money prices are hidden. You can browse public rankings, but are not listed. You cannot use friends, likes, gifts, player or problem reports, or custom names. Nimo downloads public content and rankings without an account, online session or device ID. Ordinary connection information and optional health reports follow the separate rules above.
From the account age to 17: if you meet the country rules, deliberately signing in starts account use and automatic cloud saving without a second account/data choice. You can choose an accepted nickname, use friends, blocks and player reports, and use likes, supporters and popularity statistics. Existing and new eligible active accounts appear on public rankings by default; hiding requires confirmation and manual visibility changes must be at least 30 days apart. Other players can still reach your profile through a friend code or friendship when rankings are off.
Purchases, paid gifts and boosts also require meeting the purchase rules and any Google Play approvals. Gift access can be available to teens who meet the account and purchase rules, while remote phone gift alerts remain adult-only. From age 13 and the account age, you may choose rewarded videos with the appropriate ad treatment whether or not you have an account. Country restrictions still apply.
Adults: adults who meet the rules can use the account and purchase features described here, with the same rankings default and manual visibility controls. Adult ad personalisation and consent follow the ad rules above. Adult status does not automatically enable health reports or phone notifications.
App health reports from 13: these are separate from account permission and advertising. A higher country rule may apply. On is the initial preference before a reporting choice is made, and an existing choice is kept. Capture waits for an eligible player to choose Send reports. Younger and unknown-age players do not report. Dismissal and Off keep collection off. Guests can use Settings › Privacy & safety › App health reports without an account or loss of puzzle play.
All ads are family-friendly and G-rated. For anyone under 13, under the account age or whose age Nimo does not know, Google's ad software is told to treat the player as a child. Under Google's rules, this means:
- No advertising ID.
- No personalised ads.
- No remarketing, which means using previous activity to show ads again to that person.
- No requests to third-party ad vendors, such as outside ad servers or ad-measurement trackers.
Google still receives the other information listed under Ads, such as an IP address and ad-view information, to show and count ads and stop fraud. These players see small banners only, never video ads. Ads are unavailable where Nimo holds connected features. Restricted child ad treatment does not mean Google receives no information at all.
If you believe a child has sent information that should not have been collected, email support@sabinex.app. We can review it and arrange removal where required.
Your rights and choices
You can ask us to show, correct, export or delete your data, or object to its use. Email support@sabinex.app. We may need to confirm that the account is yours to protect your information.
Your rights depend on the law that applies where you live. They may include asking us to limit processing, withdrawing consent where processing relies on it, and complaining to your local data protection authority. This policy does not limit those rights. Withdrawing a choice concerns the use covered by that choice; separate records may follow the storage rules above.
You can use these controls directly:
- App health reports: use Settings › Privacy & safety › App health reports to stop future reporting on that phone. No account or email request is needed. This does not turn off technical reports from other service providers or delete technical totals already received.
- Rankings: use Settings › Privacy & safety › On the rankings. Hiding requires confirmation, and manual visibility changes must be at least 30 days apart. This controls ranking participation, while profile access through friend codes or friendship follows the profile rules above.
- Gifts: turn gifts off in Settings if you do not want to accept them.
- Ads: use Settings › Ad privacy options where Google's consent tool provides it, and the separate ad controls on your phone.
- Notifications: turn them or individual categories off in Settings, or change phone permission.
- Account: use Settings › Account & cloud › Delete account. Follow the separate deletion and recovery rules above. Previously recorded withdrawals from older app versions remain protected; there is no separate take-back control in the current app.
Changes
If we change this policy, we will update the date at the top. We will tell you in the game about important changes.