Blocker · Pie Labs
Privacy policy
This policy explains how Blocker handles information when you use the game, its online services, and this website. It also explains the controls available to you.
1. Who and what this policy covers
Blocker is a multiplayer game published under the Blocker and Pie Labs brands. In this policy, “Blocker,” “Pie Labs,” “we,” and “us” refer to the developer responsible for Blocker. This policy covers the Blocker Android application, game and social services, and public pages hosted at blocker.pielabs.dev.
This public website does not run first-party advertising or analytics code. Its home page loads an autoplaying, muted YouTube gameplay video in privacy-enhanced mode and shares the player data described below. The policy and account-resource pages do not load that player. Gameplay remains available only in the Android app.
2. Information we collect
Account and profile information
Blocker creates an installation guest credential and player ID so that your profile can be restored. We store the profile details you choose, such as username, biography, equipped character and paddle artwork, country or region, equipped items, and premium status.
Google Play Games connection
If you choose to connect Google Play Games, Blocker receives a Google player identifier and may receive the email address and authorization scopes returned by Google. Any server refresh token retained for the connection is encrypted. You can disconnect this link from the app; disconnecting does not automatically erase the underlying Blocker profile.
Gameplay, social, and economy activity
We process matchmaking and match activity, scores, results, statistics, campaign and league progress, virtual balances, inventory, rewards, and transaction or claim receipts. Social features store friendships, blocks, direct messages, challenges, conversation-read state, and related moderation or delivery data.
Character portraits
Character portraits are packaged with the app and rendered locally; displaying them does not request an image from an external avatar provider. We store the character you have equipped and the characters you have unlocked so the collection, public identity, and reward systems work across devices.
Website gameplay video
The home page uses YouTube API Services to load and start a muted gameplay video in privacy-enhanced mode after at least half of its player is visible. When the player loads, Google/YouTube receives ordinary connection, browser or device, and playback information; autoplay means playback information begins to be shared without a separate play-button action. YouTube API Services may access or store cookies or similar browser/device technologies for playback, security, measurement, and any non-personalized ads YouTube serves under its own practices. The policy and account-resource pages do not load this player.
Network, location, and service records
Our servers receive connection information such as IP address, request time, route, response status, app version, and network or security events. If your profile has no country selected, the server may send a validated public IP address to country.is to obtain only a two-letter country code. Private or local-network addresses are skipped, and a country you select is not overwritten by this lookup.
Optional gameplay diagnostics
Gameplay diagnostics are enabled by default after the saved device setting loads and can be switched off in Blocker Settings. During a mounted player or spectator session, these records may include match and role references, app and protocol versions, frame and network timing, transport quality, state-synchronization events, and bounded error details. On Android they may also include Blocker's own WebView console output, lifecycle and crash events, process or memory state, and coarse active-network state. They do not provide privileged device-wide system logs. Turning diagnostics off stops collection and removes unsent local diagnostic evidence.
Advertising and consent data
Non-premium mobile players may be offered Google Mobile Ads, including interstitial and voluntary rewarded ads. Google and its advertising partners may process IP address, device or account identifiers, approximate location inferred from IP, app and ad interactions, and diagnostic information for ad delivery, measurement, fraud prevention, and—where permitted—personalized advertising. Google's User Messaging Platform (UMP) obtains and stores applicable privacy choices. A completed rewarded ad also creates a reward session with a limited verification window and signed verification data, such as ad-unit, reward, timestamp, and transaction information, so the server can safely grant one in-game reward. Verified transaction and grant records are retained for anti-duplication, accounting, security, and dispute handling.
For more about Google's practices, read the explanation of how Google uses information from sites or apps that use its services, Google Privacy Policy and Google advertising technologies policy.
Device storage
Blocker uses Capacitor Preferences on supported mobile devices and app-local WebView storage as a fallback. Essential local entries can include your guest credential, preferences, diagnostic choice and queued evidence, ad cadence or reward-verification state, and other data needed to resume the game. These technologies are not used by the policy pages for behavioral advertising. Depending on your operating-system and backup settings, app data may also be included in a device or cloud backup and restored later.
3. Why we use information
- Provide the game: authenticate an installation, operate matches and social features, save progress, deliver entitlements and rewards, and restore linked profiles.
- Operate safely: prevent abuse, cheating, fraudulent reward claims, security incidents, duplicate transactions, and service disruption.
- Improve reliability: investigate crashes, latency, synchronization, rendering, ad-loading, and infrastructure problems using bounded operational evidence and gameplay diagnostics controlled by the device setting.
- Fund the service: request and measure ads for eligible non-premium players, subject to applicable consent and privacy choices.
- Comply and communicate: respond to requests, enforce terms, maintain required records, and comply with law.
Where a legal basis is required, processing may be necessary to perform the service you request, based on your consent, based on our legitimate interests in security and reliable operation, or needed to meet a legal obligation. You may withdraw consent for future processing where consent is the basis; earlier lawful processing is not undone.
5. Retention and deletion
We retain account, profile, social, progression, inventory, and match records while needed to operate and preserve the integrity of your Blocker profile. Transaction, reward, security, and anti-abuse records may be kept longer when needed to prevent duplication, resolve disputes, enforce rules, or comply with law. Server access records and diagnostics are currently configured for a 14-day rotating operational-log period, unless a shorter period applies or particular evidence must be preserved for security, a dispute, or law. Local unsent gameplay diagnostics are deleted when you opt out.
Retention may also continue in backups for a limited replacement cycle. Google and other independent providers apply their own retention practices. To request deletion of server-held Blocker information, use the public account-deletion request. Public submissions are unverified and manually reviewed; the authenticated deletion action in Blocker Settings is the verified path. Uninstalling normally clears the app's active local data through the operating system, but backup copies may remain or be restored under device and cloud-backup settings. Uninstalling does not by itself submit a server deletion request.
6. Your choices and controls
- Open Blocker Settings to disable gameplay diagnostics. Unsent diagnostic evidence is then removed.
- Use the in-app privacy entry when UMP reports that privacy options are available to review or change Google advertising choices.
- Decline a voluntary rewarded ad; no reward is granted unless Google's completion signal is verified.
- Use the YouTube player controls on the home page to pause the gameplay video or manage its sound.
- Edit profile information, manage friendships and blocks, and disconnect Google Play Games through available app controls.
- Use Android settings to clear local Blocker app storage. Doing so may prevent restoration of an unlinked guest profile.
- Use the account-deletion page to request deletion outside the app. Do not send passwords, guest credentials, authorization codes, or tokens.
- Contact the developer to ask for access, correction, restriction, objection, or portability where applicable.
7. International processing
Blocker's current primary server is hosted in Frankfurt, Germany. Providers such as Google may process information in other countries where they or their subprocessors operate. Those locations may have different privacy laws. Where required, we and our providers rely on recognized transfer mechanisms and safeguards.
8. Security
We use measures designed to protect Blocker information, including encrypted transport on public services, server-side hashing of guest credentials, encryption for retained Google refresh tokens, bounded and redacted diagnostics, signed rewarded-ad verification, and access-controlled infrastructure. A guest credential remains on the device so the profile can be restored and is protected by the device's storage and backup controls. No system can guarantee absolute security, so protect access to your device and linked accounts.
9. Children's privacy
Age and consent requirements vary by country. Blocker's store target audience, advertising treatment, and UMP under-age setting must match the audience configuration of each distributed release. We do not knowingly process a child's information in violation of applicable requirements. If you believe a child provided information without required parent or guardian authorization, use the developer contact below so the situation can be reviewed and appropriate action taken.
10. Contact and policy changes
For a privacy question or rights request, use the current developer contact published on Blocker's Google Play listing. Include enough information to identify the relevant Blocker profile and the request, but do not send passwords, guest credentials, OAuth codes, or other secrets.
To delete a Blocker account and its associated data, use the public account-deletion request or the authenticated deletion action in Blocker Settings.
We may update this policy as Blocker or applicable requirements change. The effective and updated dates above identify the version in force. Material changes will be communicated through an appropriate in-app or service notice when required.