Privacy policy
Privacy policy
Last updated 2026-07-14
Blockmatic is operated by TLM Software Design, Inc., a Michigan corporation with offices at 27280 Haggerty Road, Ste C-6, Farmington Hills, MI 48331, USA ("we", "us", "our"). This policy describes what the app collects, why, where it goes, and the choices you have.
Summary
- The game itself is fully offline. We don't run a server that your gameplay touches.
- Your best score, selected difficulty, and audio toggle live only on your device and are lost on uninstall.
- No account, no sign-in, no profile lookup. We never see your name or your score.
- The only network traffic the app generates is to Google AdMob (ads), RevenueCat (purchase verification for the one-time Remove Ads unlock), and Google Firebase (crash reports and basic install/lifecycle analytics).
- On iOS the app does not request App Tracking Transparency and does not read the IDFA. Ad personalization is otherwise governed by Google AdMob, applicable regional consent (GDPR / CCPA), and your device-level ad settings.
What the app stores on your device
The following values are written to platform key-value storage
(SharedPreferences on Android,
NSUserDefaults on iOS). None of it
is transmitted to our servers, the ad network, or any third party.
- Best score — your highest score across all sessions. Not tied to any difficulty; a single running best.
- Selected difficulty — Easy, Normal, or Hard. Chosen from the New Game dialog and remembered for next time.
- Audio toggle — whether music and sound effects are on or off.
- Remove Ads entitlement flag — a cached boolean (set by RevenueCat on successful purchase/restore) so the app can skip ad requests without a network round-trip on every launch. RevenueCat is the authoritative source; this cache is advisory only.
There is no account, no cloud sync, no backup target. Wiping the data is one app-uninstall away.
Network behavior
Gameplay is fully offline. Piece dealing, drag-to-place, line-clear detection, scoring, and game-over all run locally. Only three external services receive traffic:
- Google AdMob — when the app needs to fetch an ad creative (a banner, and an interstitial shown periodically on the free tier).
- RevenueCat — when you initiate or restore the Remove Ads purchase.
- Google Firebase — Crashlytics uploads on crash, Analytics on app-launch and lifecycle events.
If the device is offline, the game runs normally. The banner slot remains reserved but blank, interstitials and the purchase flow retry once connectivity returns, and crash reports queue locally and upload on the next connectivity window.
Android permissions
The app itself requests only network-access permissions, both required for the ad network:
android.permission.INTERNETandroid.permission.ACCESS_NETWORK_STATE-
com.google.android.gms.permission.AD_ID— declared by the bundled Google Mobile Ads SDK (not by the app's own manifest); it lets the ad network use the resettable advertising ID for ad delivery and fraud prevention.
No camera, microphone, location, contacts, storage, calendar, or biometric permissions are requested.
Ad network — Google AdMob
The free tier of Blockmatic is ad-supported. Google AdMob serves a banner ad and an interstitial ad shown periodically between games, deliberately paced to stay non-intrusive rather than maximize ad density.
On iOS the app does not request App Tracking Transparency and does not read the IDFA, so iOS ads are served without that identifier. The app does not set ad-personalization flags itself — whether ads are personalized is governed by your Google AdMob settings, applicable regional consent (GDPR / CCPA), and your device-level ad preferences. AdMob's data practices are governed by Google's privacy policy at policies.google.com/privacy and the AdMob & AdSense privacy and terms page at policies.google.com/technologies/partner-sites.
Purchasing the one-time Remove Ads unlock permanently removes both the banner and interstitial.
In-app purchase — RevenueCat
The Remove Ads non-consumable purchase is managed by RevenueCat. When you initiate or restore a purchase, RevenueCat receives an anonymous, app-generated user ID and the store receipt to verify the entitlement. Payment itself is handled entirely by Apple App Store or Google Play — we and RevenueCat never see your payment method or financial details.
Crash reporting and analytics — Google Firebase
Firebase Crashlytics captures stack traces, device model, OS version, app version, and a Firebase installation ID when the app crashes. Firebase Analytics records a small set of install and lifecycle events, on both iOS and Android. Neither service receives gameplay data, board state, your score, or your saved settings.
Firebase data is governed by Google's privacy policy. Default retention is up to 14 months for Analytics; Crashlytics reports can be purged on demand from the Firebase console.
Children
Blockmatic is intended for a general audience aged 13 and up (16 in the EU/UK). It is not listed as a children's app and is not directed at children, and we do not knowingly collect personal data from children. If you believe a child has interacted with the app and we have collected anything we shouldn't have, contact privacy@swtlm.com and we will delete it.
Your rights and choices
Because we hold no account data or personally identifiable information on our servers, most data-subject rights — access, portability, deletion — are satisfied by uninstalling the app, which removes all on-device storage. Ad-personalization preferences can be managed through your device's settings (Settings › Privacy › Ads on Android; iOS Tracking is never requested). For AdMob or Firebase data held by Google, see Google's privacy controls.
To exercise any rights or raise a privacy concern, email privacy@swtlm.com and we will respond within 30 days.
This website
These pages (apps.swtlm.com/blockmatic) are
static and hosted on AWS S3 + CloudFront. As of
this writing, no Google Analytics (or any other) tag is wired into this site — it loads no
third-party scripts and sets no cookies at all. If
GA4 is added in a future update, it will only load after you explicitly accept via a cookie
banner, and this section will be updated to describe the consent-gated analytics cookies
(_ga, _ga_*)
and how to withdraw consent. The only data that flows today is standard CDN access logs
(IP address, timestamp, requested URL) retained by AWS per their default logging policy —
not joined to any in-app identifier.
Service providers
- Google AdMob — in-app advertising (banner + interstitial).
- RevenueCat — Remove Ads in-app purchase management and entitlement verification.
- Google Firebase — Crashlytics + Analytics.
- Amazon Web Services (S3 + CloudFront) — hosts this marketing page; receives standard CDN access logs that are not joined to any in-app identifier.
Changes to this policy
We will post material changes here and update the "Last updated" date above.
Contact
Privacy questions: privacy@swtlm.com. General support: info@swtlm.com.
TLM Software Design, Inc.27280 Haggerty Road, Ste C-6
Farmington Hills, MI 48331
USA