PLAYFRENZY
Google Play Compliant
Privacy Policy
🔒 100% Offline-First Architecture & Zero Cloud Processing
PlayFrenzy is designed and built from the ground up as a 100% offline-first, pass-and-play party
game. The application functions entirely on your local device without requiring an internet
connection or user account. We operate zero servers, store zero audio recordings, capture zero
camera images on the cloud, and never collect, transmit, share, or sell your personal data.
📋 Google Play Data Safety Declaration Summary
This table outlines the exact data
practices for PlayFrenzy as declared in the Google Play Console Data Safety section:
| Data Category |
Collected by App? |
Shared with 3rd Parties? |
Purpose & Handling |
| Audio / Voice Data (Microphone) |
No (Processed live in volatile RAM only) |
No (Never shared or transmitted) |
Live Gameplay Mechanics: Real-time decibel (dB) level computation for sound
challenges. Audio samples are immediately discarded from memory in fractions of a second and
never written to storage or transmitted over network. |
| Photos & Videos (Camera) |
No (Processed live in volatile RAM only) |
No (Never shared or transmitted) |
Live Gameplay Mechanics: Real-time on-device eye blink detection via Google
ML Kit for Blink Showdown. Frames are processed in volatile memory and instantly
discarded. Zero photos or videos are stored or sent anywhere. |
| Device Motion / Gyroscope |
No (Processed live in volatile RAM only) |
No (Never shared or transmitted) |
Live Gameplay Mechanics: Gyroscope and accelerometer tilt and angular rate
metrics for Steady Hand and Tilt Bomb. Handled locally in RAM in real
time. |
| Player Names & Match History |
Stored locally on device |
No (Never shared or transmitted) |
Local Scorekeeping: Nicknames entered for players, round scores, and match
results are stored strictly in private on-device SharedPreferences. Zero cloud syncing. |
| Personal Identifiers & Contacts |
No |
No |
No accounts, phone numbers, email addresses, or contacts are collected, accessed, or
required. |
| Device or Other IDs (Google Advertising ID) |
Yes (via Google AdMob SDK) |
Yes (Google Mobile Ads) |
Advertising, Analytics & Fraud Prevention: Processed securely and encrypted in transit by Google Mobile Ads (AdMob) for ad delivery, analytics, and invalid click prevention. Never linked to gameplay or sensor data. |
| Location (Approximate / Coarse) |
Yes (via Google AdMob SDK) |
Yes (Google Mobile Ads) |
Regional Ad Delivery: Coarse/approximate geographic region derived from IP address by Google AdMob to deliver region-relevant advertisements and satisfy compliance. Zero precise GPS coordinates are accessed or requested. |
| App Info & Performance (Crash Logs & Diagnostics) |
Yes (via Google AdMob SDK) |
No (SDK performance telemetry only) |
Stability & Analytics: AdMob collects crash logs and diagnostic metrics (such as ad load latency and hang rate) to diagnose SDK performance and maintain stability. |
1. Introduction
This Privacy Policy describes how PlayFrenzy ("we", "our", or "the application"), developed
by Crazy Developer, handles device permissions and user privacy when you play our game on
Android devices.
By installing and using PlayFrenzy, you acknowledge and agree to the offline data practices described in this
document. If you have any questions, you can contact the developer directly at ashok.gokulakrishnan@gmail.com.
2. Real-Time Hardware Sensor Processing
PlayFrenzy uses physical smartphone sensors exclusively to provide interactive party challenges. The crucial
distinction between PlayFrenzy and other apps is that sensor signals are analyzed transiently in
volatile RAM and immediately discarded:
A. Microphone (Audio Level Detection)
- Permission:
android.permission.RECORD_AUDIO
- Game Usage: In voice-based modes such as The Whisperer, The Screamer,
and Steady Louder, the app reads 16 kHz PCM audio chunks from the device microphone to compute
real-time Root Mean Square (RMS) amplitudes and decibel (dB) values.
- Privacy Guarantee: Raw audio chunks are processed live in volatile memory to calculate
the decibel meter level and smoothed average, and are overwritten continuously. No audio is ever
recorded to a file, saved to disk, encoded, or transmitted over any network. When your turn
finishes, audio capture stops immediately.
B. Camera (On-Device Eye Tracking)
- Permission:
android.permission.CAMERA
- Game Usage: In Blink Showdown, the front camera streams image frames into
Google's bundled, on-device ML Kit Face Detection library to determine eye-open probabilities for the
staring contest.
- Privacy Guarantee: All image analysis runs 100% offline on your device
processor. Camera frames are never saved to storage, never sent to external servers, and
never converted into persistent video files. When the staring contest ends, the camera is unbound and
completely shut down.
C. Gyroscope & Accelerometer (Motion & Tilt)
- Sensor Type: Rotation Vector, Accelerometer, Gyroscope
- Game Usage: In Steady Hand and Tilt Bomb, the app reads device
orientation to measure balance percentage and sudden hand-off acceleration.
- Privacy Guarantee: Motion sensor readings exist solely within the active game loop in
volatile RAM and are never logged, stored, or profiled.
D. Vibration & Haptics
- Permission:
android.permission.VIBRATE
- Game Usage: Delivers countdown tick feedback, turn start pulses, and penalty alert
vibrations using Android's system
Vibrator. No data is collected through this capability.
E. Multi-Touch Capacitive Sensors (FingerDrop)
- Sensor Type: Capacitive Touchscreen Pointer Events
- Game Usage: In FingerDrop, concurrent fingertip contact positions (2 to 5 participants) are processed in real time to coordinate the 3-second voltage charge and select one random player.
- Privacy Guarantee: Touch contacts exist purely as temporary pointer coordinates in volatile RAM during active touch and are discarded immediately upon round completion. Zero biometric touch patterns or user fingerprints are captured.
3. Local Data Storage & User Privacy
PlayFrenzy is engineered without an external database or cloud infrastructure. All game settings and records
remain under your physical possession on your device:
- Player Roster: The names or nicknames you enter for your game party are stored strictly
in private on-device SharedPreferences.
- Match History & Leaderboards: Historical records of completed party rounds (game
mode, stakes, winner name, penalty player, and score breakdown) are saved locally on your phone so you
can review match history.
- Threshold Preferences: Any custom sensitivity calibrations (such as whisper caps,
scream targets, or gyro hazard limits) are saved in local preferences.
- No Tracking & No Cloud Accounts: You do not need to register an account, sign in,
or provide an email address. We do not maintain any user database or track your gameplay across devices.
Zero Cloud Footprint: Because PlayFrenzy operates with zero backend servers, it is
technically impossible for the developer or any third party to access, inspect, aggregate, or monetize
your gameplay data, voice levels, or camera images.
4. Third-Party Advertising (Google AdMob)
To support ongoing development and keep PlayFrenzy accessible, we display non-intrusive advertisements provided by Google Mobile Ads (AdMob):
- Ad Formats & Placement: Advertisements are strictly confined to non-gameplay screens — sticky bottom banners on the Lobby and game setup screens, an ad inside the match history archive dialog, and native sponsor cards on final round verdict and detonation result screens. No advertisements are ever displayed during active gameplay, live camera staring contests, audio threshold challenges, or motion sensor measurements to preserve the fast-paced, frustration-free party experience.
- Advertising ID (AD_ID Permission): In compliance with Google Play requirements for Android 13+ (API 33+), the app declares
com.google.android.gms.permission.AD_ID to enable the Google Mobile Ads SDK to serve ads, measure ad performance, and detect fraudulent or bot activity.
- Data Handled by Google AdMob: Google AdMob may automatically collect and process:
- Pseudonymous device identifiers (Google Advertising ID / GAID, app set ID).
- Approximate / coarse geographic location (derived from IP address for regional ad delivery).
- SDK diagnostics, crash logs, and load latency metrics to monitor ad reliability.
- Zero Access to Sensitive Sensors or Gameplay Data: Google AdMob and third-party ad networks have zero access to your microphone decibel inputs, camera frames, face mesh tracking, touchscreen contacts, gyroscope/accelerometer readings, player names, or game consequences.
- Opting Out of Personalized Ads: You can manage, reset, or delete your advertising identifier at any time through your Android device settings:
Settings > Google > Ads > Reset Advertising ID / Delete Advertising ID.
- Google Privacy Policy: For more details regarding how Google uses information from sites or apps that use their services, please review How Google uses information from sites or apps that use our services and the Google Privacy Policy.
5. Sharing Match Results (User-Initiated Only)
When a match concludes, PlayFrenzy gives players the option to share their final verdict card with friends:
- Sharing is strictly voluntary and initiated solely by the user by tapping the "Share
Verdict" action button on the Verdict screen.
- When tapped, the app generates a local text summary or rendered score card image saved in the device's
temporary cache directory, and opens Android's native system Share Sheet
(
Intent.ACTION_SEND) through a secure, temporary FileProvider.
- You have full control over whether to share and which external app (e.g., messaging, email, or social
media) receives the shared summary.
6. Data Retention, Backup, and Deletion Policy
In full compliance with Google Play Developer Policies, you have complete control over your data:
- Clearing Match History: You can delete all recorded match history records at any time
by opening the Trophy Match History dialog or Verdict screen and tapping "Clear History".
- App Storage Deletion: You can wipe all preferences, player names, and historical scores
immediately by navigating to Android Settings > Apps > PlayFrenzy > Storage > Clear Data
/ Clear Storage.
- Uninstalling: Uninstalling PlayFrenzy removes all application files and local
preferences from your device completely and irreversibly.
7. Children's Privacy (COPPA Compliance)
PlayFrenzy is a family-friendly party game designed for players of all ages. Because PlayFrenzy does not
collect, transmit, or store any personal information, it complies with the Children's Online Privacy
Protection Act (COPPA) and General Data Protection Regulation (GDPR) standards regarding minor privacy.
8. Security
We prioritize the privacy and security of your party gaming sessions:
- All data is restricted to Android's sandboxed, private internal storage accessible only by the
PlayFrenzy application.
- No data travels over external networks, eliminating vulnerabilities associated with unencrypted
transmissions, data leaks, or server breaches.
- Temporary files generated for the voluntary system share dialog are shared with temporary read-only
permissions via Android's secure
FileProvider.
9. Changes to This Privacy Policy
We may update this Privacy Policy periodically to reflect new features, updated sensor rules, or legal
compliance updates. Any revisions will be reflected with an updated "Effective Date" at the top of this
page.
10. Developer Contact Information