Gridhush

Gridhush privacy policy

Version 1.0, in effect from 15 October 2026. Earlier versions are kept on the history page.

Gridhush and your privacy, on one page

Gridhush is a calm block puzzle for the web and Android, made by TwoBrosDev. This page is the short version. The full policy below has the details, and if anything here is unclear, the full policy is what counts.

Your game stays on your device. Your scores, Daily results, streak and settings are saved on your phone or in your browser. They never come to us, and we can't see them. Deleting the app, or clearing this site's data in your browser, deletes them from your device. If your phone backs up apps to your Google account, a copy may stay in that backup (section 3).

No accounts. Gridhush has no sign-up and asks for no name, email or password.

What leaves your device, and when. Gridhush is being released in stages. This policy says what happens now and what comes with each update:

Not for children. Gridhush is for teens and adults, 13 and over. It is not made for children under 13.

We never sell your data for money. Some US state laws count Google's personalised ads as "selling" or "sharing" data. Section 17 explains how to opt out.

Your choices:

Contact: [email protected]

At a glance

What Where it goes From
Progress and settings Nowhere: your device Now
A result you share The app you pick First Android test
An email you send us Us Now
Gameplay analytics PostHog, EU Web launch
Ad data Google Ads update
Payment Google Play or Stripe Unlock update

1. Who we are

Gridhush is made by Mark Bischetsrieder, trading as TwoBrosDev, in the United States. In this policy, "we" and "us" mean TwoBrosDev. Under EU and UK law we are the "controller" of the information described here: we decide how it is used.

2. What this policy covers

It does not cover itch.io, CrazyGames, Google Play or the apps you share results to. Each of those has its own privacy policy.

3. What the game keeps on your device

Status: in every version of the game.

Gridhush saves these on your device so the game works:

Where it lives. In the app, it's in the app's own storage on your phone. On the web, it's in your browser's storage for that site. The gridhush.com, itch.io and CrazyGames versions each keep separate records, and so does the app.

Who can see it. Only you, and anyone who uses your device. None of it is sent to us.

How to delete it. Uninstall the app, or open your phone's Settings, then Apps, Gridhush, Storage, and clear storage. In a browser, clear the site's data. We hold no copy, so we can't bring back a deleted streak.

Phone backups. If your Android phone backs up apps to your Google account, Android may include Gridhush's saved data in that backup, and may put it back if you install Gridhush again. Google holds that backup for you, and we can't see it.

Permissions. Gridhush doesn't ask for your contacts, photos, files, location, camera or microphone.

Cookies. The game sets no cookies. The tester site uses one sign-in cookie (Part 2).

4. Sharing your result

Status: in the Android app from its first test version on Google Play, and on the web from the web launch.

After a Daily you can share a short text card. On a phone it opens your phone's share menu. Otherwise the game copies the card for you to paste.

The card shows the puzzle number, your score, a small grid of symbols showing which moves cleared lines, a one-line summary and a link such as https://gridhush.com/d/42. The link names the puzzle number only. It carries nothing that identifies you.

You choose whether to share, what app to share to and who sees it. We don't learn whether you shared, where, or with whom. Once analytics is live, it can record that the share button was tapped and whether sharing finished (section 5). The app you share to handles the card under its own privacy policy.

5. Gameplay analytics

Status: not in Gridhush yet. It is planned to start with the web launch. In the Android app it starts with a later update, which this policy will name before that update ships. Until then, nothing in this section happens.

This section sets out what is already decided. The rest, listed at the end of this section, will be set out here before analytics starts.

Why. We use analytics to learn whether players come back, finish the Daily and share it, and where the game frustrates them, so we know what to fix. We look at totals, not at individual players.

What is sent. It is sent only while analytics is on:

What is never collected: your name, email or advertising ID; your contacts, or anything about other apps on your phone; your precise location, city or region; recordings of your screen or session; anything you type. Like any internet connection, sending an event shows your IP address to the analytics service, but your IP address is never stored.

Who handles it. PostHog stores the data for us on its EU servers in Frankfurt, Germany. PostHog handles it only on our instructions, under a data processing agreement. We never combine it with ad data.

Your switch. Settings will have an analytics switch. While it is off, the game sends no analytics. In the EU, the UK and Switzerland, nothing is sent until you agree.

How long. Events are deleted automatically 12 months after they're recorded.

Still to be set out here before analytics starts:

6. Ads (Android)

Status: not in Gridhush yet. It is planned for the ads update. Until then, the app shows no ads and contains no ad code.

This section sets out what is already decided. The rest, listed at the end of this section, will be set out here before ads start.

Which ads.

Who shows them. Ads come from Google AdMob, through Google's Mobile Ads code in the app. Consent is handled by Google's consent tool, the User Messaging Platform.

What Google collects. Google's own disclosure for its Mobile Ads code lists:

Google says this is collected for advertising, analytics and fraud prevention, and that it is encrypted in transit. Google's code also asks Android for permission to use Android's own ad features: the advertising ID, ad topics and ad measurement. Before ads start, we will check this list against the version of Google's code the game ships with.

Google uses this data under Google's Privacy Policy. Google explains how it uses information from apps that show its ads at policies.google.com/technologies/partner-sites.

Your consent in the EU, UK and Switzerland. Before any ad is requested, Google's message asks whether Google and its ad partners may store and read information on your phone and personalise ads. The message lists the companies involved. If you say no, Google may still show non-personalised or limited ads. You can change your answer at any time: in Settings, tap Privacy options.

In US states with privacy laws. Google's message for those states lets you opt out of the "sale" or "sharing" of your information for ads, through the same Privacy options row.

Ad content. We ask Google to limit the ads the game shows by content rating. Gridhush isn't made for children, so we don't ask Google to treat it as a children's app (section 16).

Your advertising ID. In your phone's settings you can reset or delete your advertising ID, which stops ads being tied to the old one. Where the setting sits differs from phone to phone; searching your phone's Settings for "ads" usually finds it.

A settings file for ad timing. From the ads update, the app also downloads a small, signed file that sets how often the full-screen ad may appear. If the file can't be reached, the game uses limits built into it. Like any download, fetching the file shows your IP address to whoever hosts it.

After you buy the unlock, no ad plays again.

On the web. The gridhush.com and itch.io versions show no ads. CrazyGames may show its own ads in and around its version, under CrazyGames' privacy policy (section 8).

Still to be set out here before ads start:

7. Purchases

Status: not in Gridhush yet. It is planned for the unlock update.

This section sets out what is already decided. The rest will be set out here before the unlock starts.

There is one purchase: a one-time unlock that removes ads.

On Android: Google Play. Google Play takes the payment, under Google's terms and privacy policy. The game never sees your card or payment details. Google gives us a record of each order, without your card details; what that record holds will be listed here before the unlock starts. The game checks with Google Play when it opens to confirm you own the unlock. The Restore purchases button in Settings asks Google Play again, for example after you reinstall. Purchases are tied to your Google account, not to us.

On the web: Stripe. Stripe takes the payment, under Stripe's privacy policy. We never see your full card number. What Stripe passes on to us, and how your browser remembers the unlock, will be set out here before the web unlock starts.

No account links them. A purchase on the web can't unlock the Android app, and a purchase on Android can't unlock the web version, because Gridhush has no accounts to connect them.

8. Websites, hosting and the game sites

Status: gridhush.com is live now. The itch.io and CrazyGames versions come with the web launch.

9. Totals we see from the services we use

Google Play, Google AdMob (from the ads update) and Cloudflare show us totals, such as installs, visits or ad views by country and phone model. Google Play also gives us crash and freeze reports from phones whose owners let Google collect diagnostics. We use these to fix problems and to judge how the game is doing. They don't tell us who you are.

10. When you contact us

If you email us, we receive your email address and whatever you write. We use them to answer you and to improve Gridhush. We keep them for 2 years after the last message between us, then delete them.

11. Why we use data (for people in the EU, UK and Switzerland)

These are the legal reasons we rely on under the GDPR, the UK GDPR and Swiss law:

We make no automated decisions about you that have legal or similar effects. If you allow personalised ads, Google uses profiling to choose them.

12. Who receives data

Code from other companies in the game. Gridhush is built with these pieces of other companies' code:

13. Where data goes (international transfers)

We're based in the United States. Information that reaches us, such as your emails, purchase records and the analytics we look at, is handled in the US.

14. How long we keep data

15. How we protect data

16. Children

17. Your choices and rights

17.1 For everyone, wherever you live

17.2 In the EU, UK and Switzerland

You have the right to:

You can also complain to your data protection authority. In the UK that's the Information Commissioner's Office (ico.org.uk). We answer within one month.

17.3 In California and other US states with privacy laws

You have the right to:

We don't collect sensitive personal information. To opt out of sale or sharing in the app, use Privacy options in Settings (from the ads update). Someone you authorise can ask for you. We answer within 45 days.

17.4 Do Not Track and Global Privacy Control

Gridhush itself doesn't track you across other websites or apps; ads in the Android app are covered in section 6. Nothing on gridhush.com tracks you today, so these signals have nothing to switch off. How the web version will treat them once analytics starts will be set out in section 5 before then.

17.5 How we find your data

Gridhush has no accounts, so the only data we can link to you is:

We may ask for one of these to make sure we're dealing with the right person. Data on your device and data Google holds for ads are outside our reach, so use the controls above for those.

18. Changes to this policy

When we change this policy, we update the version and the date at the top and add a line to "What changed and when" below. If a change is significant, for example it adds a new kind of data or a new company, we'll also show a one-line note in the game the next time you open it. Where the law needs your consent first, we'll ask for it before the change applies to you. Earlier versions are kept on the history page.

19. Contact

Part 2: the tester site (test.gridhush.com)

Status: live now, for friends we invite. Its data is deleted when testing ends. It is not part of the public game.

The tester site lets invited friends play test versions of Gridhush in a browser with a personal code. No email or sign-up is involved. When you sign in, the site tells you what it keeps. In full:

On your phone: one sign-in cookie, which keeps you signed in for 90 days. Game reports, answers, messages and error notes wait in your browser's storage until they're sent.

IP addresses are never stored. To slow down anyone guessing codes, the site counts sign-in attempts per network under a scrambled key. Those counts are deleted after an hour.

Who handles it: Cloudflare hosts the site and its small database for us.

How long: everything is deleted when testing ends. Cloudflare's database restore feature can bring it back for up to 30 days after that, and then it is gone. To stop sooner, ask us: we'll switch off your code and delete your records.

Testing on Android through Google Play. If you join the Android test, we add the email address of your Google account to the test's list in Google Play, so that you can join through the link we send you. Google runs the test under its own terms. What you tell us by message may go into our test notes under your tester number, never your name.

What changed and when

Versions so far

Version In effect from What changed
1.0 15 October 2026 The first version, for gridhush.com and the first Android test on Google Play. Sections 5 to 7 are published as "not yet".

Planned updates

Release dates are plans and may move. Each update brings a new version of this policy, published before the update reaches you.

Update When (planned) What changes here
Web launch Early November 2026 Section 5 starts on the web; sections 3, 8, 12, 13 and 14 updated
Analytics in the Android app A later Android update, named here first Section 5 applies in the app
Ads update (Android) Mid November 2026 Section 6 starts; sections 8, 9, 11, 12, 16 and 17.3 updated
Unlock update Late November 2026 Section 7 starts; sections 3, 12 and 14 updated
If TwoBrosDev becomes a company Not dated Sections 1 and 19 name the company
End of testing Not dated Part 2 removed; tester data deleted