Short answer: not who you are. There are no accounts and your progress never leaves your phone. What does leave it goes to three services: Google AdMob, for the ads that pay for the game; Google Analytics for Firebase, to see how the game is played; and Tenjin, to learn which ads bring players in. The long answer is below, in plain language.
At a glance
This is the complete list. Each item is collected by third-party software inside the app (Google’s for ads and analytics, Tenjin’s for ad measurement). None of it reaches a Lab-47 server, because there isn’t one.
Blockwave stores your progress so that it is there when you return. It is held in the app’s private storage on your device and is never sent to us.
None of this identifies you, and uninstalling the app removes all of it.
Blockwave is free and funded by advertising supplied by Google AdMob: a banner while you play, a full-screen ad between games, and an optional video you may watch in exchange for a second chance or an extra undo. You are never required to watch an ad to continue playing.
To select and measure those ads, Google’s software inside the app collects:
This data is collected by Google and its advertising partners and handled under Google’s privacy policy; the partners are listed on Google’s ad technology providers page. We receive only aggregated reports: how many ads were shown and what they earned.
From version 1.4.0, Blockwave includes Google Analytics for Firebase, an analytics service operated by Google. It shows us how the game is played, for example where players stop and whether a change made the game better or worse, and it tells Google Ads and AdMob which installs and play came from our own ad campaigns.
Through its software inside the app, Firebase collects:
It does not collect your name, email address, contacts, files, precise location or anything you type, and the game has no crash reporting.
Google processes this data for Lab-47, and we see it as reports in the Firebase console. Because the Firebase project is linked to Google Ads and AdMob, Google uses it to measure which ads led to installs and play. Google’s description of how Firebase handles data is at firebase.google.com/support/privacy.
Nothing is sent to Firebase until the consent screen in section 5 has been answered, where that screen is shown.
Blockwave also includes Tenjin, a mobile measurement service operated by Tenjin, Inc. It tells us which ad, on which network, brought a player to the game, and whether the players who arrived that way keep playing. Lab-47 needs that to spend on advertising sensibly, and uses it for nothing else.
Through its software inside the app, Tenjin collects:
Tenjin passes attribution results to the ad networks Lab-47 buys ads from, such as Google Ads, Meta, TikTok, AppLovin and Unity Ads: each network learns only whether an install came from one of its own ads. Tenjin’s policy is at tenjin.com/privacy.
If you are in the European Economic Area, the UK or Switzerland, the game asks for your consent using Google’s consent screen before it requests personalised ads. You can accept or decline. Declining does not limit the game; you will simply see ads that are not personalised.
Your answer covers analytics and measurement too. Nothing is sent to Firebase or Tenjin until you have answered. Firebase receives your choice through Google’s consent mode: if you decline, it does not use your advertising ID or keep an identifier for your installation, and sends only limited signals that carry no identifier. Tenjin runs in its opted-out mode, which records the install without the advertising ID.
You can change your answer at any time in the game under Options > Privacy.
Blockwave is not directed at children under 13, and we do not knowingly collect data from them. The game has no accounts and no messaging, so there is no way to send us personal information through it. If you believe a child’s data has been collected, please contact us.
Where the EU or UK GDPR applies, we rely on:
You can ask to see, correct, delete or export personal data about you, object to how it is processed, or complain to your data protection authority. Write to us for anything in sections 3 and 4, and we will take it up with Google and Tenjin. The ad data in section 2 is held by Google itself, so requests about it are best sent to Google. We will assist where we can.
Depending on your state, you may have the right to know what personal information is collected, ask for it to be deleted, and opt out of it being sold or shared for targeted advertising. We do not sell personal information. The advertising in section 2, and the attribution results Tenjin passes to ad networks in section 4, may still count as sharing for targeted advertising under some state laws. The Android settings in section 6 let you opt out of both.
Lab-47 is based in Melbourne, Australia. The law that applies here is the Privacy Act 1988 (Cth) and the Australian Privacy Principles made under it. Whether or not that Act applies to Lab-47 as a small business, we handle personal information in line with the Australian Privacy Principles, and this section sets out what that means for you.
What we hold. Nothing on our own systems. Your progress stays on your device (section 1), and the advertising data in section 2 is collected and held by Google. The analytics and measurement data in sections 3 and 4 is held by Google and Tenjin for Lab-47, and we see it as reports in their dashboards, keyed to install and advertising IDs rather than to names. We do not sell personal information, and we do not disclose it to anyone in exchange for a benefit.
Overseas disclosure. Google and Tenjin, Inc. process data on servers outside Australia, including in the United States. Advertising data is handled under Google’s own privacy policy; analytics and measurement data is handled for Lab-47 under Google’s and Tenjin’s data protection terms.
Access and correction. You can ask us what personal information we hold about you and ask for it to be corrected. Because analytics data is keyed to install and advertising IDs rather than names, we usually cannot connect it to you without more detail from you. For the advertising data, the controls in section 6 are the direct route, and we will help you use them.
Complaints. If you think we have mishandled your personal information, email contact@lab-47.com with “Privacy” in the subject line. We aim to respond within 30 days. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner.
Children. Section 7 applies in Australia as it does everywhere else. When the Children’s Online Privacy Code takes effect, we will meet it to the extent it applies to Blockwave.
Data breaches. The Notifiable Data Breaches scheme requires organisations to tell affected people and the Commissioner about breaches likely to cause serious harm. We hold no personal information on our own systems. If Google or Tenjin reports a breach affecting Blockwave players, we will notify you as the scheme requires.
We keep no personal data on our own systems. Google keeps Firebase event data for the retention period set on Blockwave’s Analytics property, at most 14 months, after which only aggregated reports remain. Google keeps advertising data, and Tenjin keeps measurement data, under their own policies. Your progress stays on your device until you delete the app.
Ads, analytics and measurement all use encrypted (HTTPS) connections. The game makes no other network connections.
Most of these are required by the ads, analytics and measurement software rather than by the game itself:
| Permission | Why it is there |
|---|---|
INTERNET, ACCESS_NETWORK_STATE | Request ads, send analytics and measurement, and check whether you are online. |
AD_ID, ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS | The advertising ID and Android’s Privacy Sandbox ad features, used by AdMob, Firebase and Tenjin. |
BIND_GET_INSTALL_REFERRER_SERVICE | Read the install referrer from Google Play, used by Firebase and Tenjin (sections 3 and 4). |
VIBRATE | Haptic feedback when pieces land and merge. This can be turned off in the game’s options. |
WAKE_LOCK, FOREGROUND_SERVICE, READ_BASIC_PHONE_STATE | Required by Google’s ads and analytics software to load ads and send data reliably. |
DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION | An internal permission Android libraries add so that only Blockwave itself can send messages to its own components. No other app can hold it. |
The game asks for no access to your camera, microphone, contacts, files, precise location or messages.
The analytics and measurement in sections 3 and 4 are active. Two further capabilities are planned. Neither is active as of the effective date shown above.
Remote configuration would let us adjust settings such as difficulty or how often ads appear without releasing a new version of the game. The app would fetch a configuration file, which reveals your IP address to whoever hosts it, as any web request does.
A/B testing would assign installations to variants of a change and compare how they play. It would add one item to the data in section 3: which variant your installation was shown.
Before either is enabled we will update this page and its effective date, update the Data Safety section of the Google Play listing, and request consent where it is required.
For any question about this policy or about data in Blockwave, write to contact@lab-47.com.
If the game changes in a way that affects this policy, we will update this page and the effective date shown above, and note material changes in the app’s store listing. This policy applies to the Blockwave app only, and not to any site or service it links to.
Changes in v1.2 (1 October 2026): added Google Analytics for Firebase (section 3), which ships in version 1.4.0, and a description of Tenjin ad measurement (section 4); updated the consent, choices, legal bases, retention and permissions sections to match.