BufferBeat Privacy Policy

Effective: February 12, 2026 · Last Updated: February 12, 2026

1. Introduction

BufferBeat ("the App") is a video quality monitoring application. This Privacy Policy explains how we collect, use, store, and protect information when you use our Android application and associated web heatmap portal.

We are committed to protecting your privacy. BufferBeat is designed to measure video streaming quality — not to record, store, or transmit any video content. We collect only the minimum data necessary to detect buffering events and map video quality by location and carrier.

By installing and using BufferBeat, you agree to the data practices described in this Privacy Policy.

2. Information We Collect

2.1 Screen Analysis Data

BufferBeat uses Android's MediaProjection API to analyze screen frames in real time. This is used exclusively to detect video buffering events (frozen frames).

✓ What we DO: Analyze pixel hash values and variance between consecutive frames to detect when video playback freezes.

✗ What we DO NOT do: Record, capture, save, screenshot, or transmit any video content, images, or visual data from your screen. No frames are stored. No video is recorded. Frame data is processed in memory and immediately discarded.

Screen analysis runs only during active monitoring sessions that you initiate and control. It does not run in the background without your knowledge.

2.2 Buffer Event Data

When a buffering event is detected, we collect the following data points:

Event details: Duration of the buffer (in milliseconds), number of frozen frames detected, detection confidence score (0–100), timestamp, and the platform being monitored (YouTube or TikTok).

Network data: Cellular signal strength (RSRP in dBm), signal quality (RSRQ in dB), network type (4G, 5G, WiFi), and wireless carrier name.

Location data: GPS coordinates (latitude and longitude) at the time of the buffering event. This is used to plot buffer events on the public heatmap. Location is collected only during active monitoring sessions.

2.3 Anonymous Network Identifiers (Non-Persistent)

Monthly Salted Hashing: Unlike traditional apps, BufferBeat does not store or transmit your persistent hardware ID. Instead, your device generates a unique identifier using a SHA-256 cryptographic hash combined with a monthly rotating "salt."

✓ Privacy Benefit: This allows us to verify data density (ensuring map accuracy) without ever knowing who you are. Because the "salt" changes every month, it is mathematically impossible to link your February activity to your March activity.

We do not collect your IMEI, phone number, Google account email, or hardware serial numbers.

2.4 Information We Do NOT Collect

Your name or email address

Google account or login credentials

Video titles, URLs, or search history

Data from other apps

Text messages or phone calls

Contacts, photos, or files

Browsing history or passwords

Financial information

3. How We Use Your Data

3.1 In-App Results

Buffer event data is displayed to you in the app's results screen after each monitoring session, showing where and when buffering occurred, signal conditions at the time, and overall video quality score for the session.

3.2 Public Heatmap & K-Anonymity

Anonymized buffer event data is aggregated into a public heatmap. To protect individual privacy, we enforce a K-Anonymity threshold:

✓ The 5-User Rule: A specific geographic tile will only appear on the public map once at least five unique, anonymous users have contributed data to that area. This ensures that no single user’s home or workplace can be identified through the map.

3.3 Data Aggregation

We aggregate buffer event data across all users to identify patterns in video streaming quality by geographic area, carrier, network type, and time of day. This aggregated data may be used for research, analysis, and to improve the BufferBeat service.

4. Data Storage and Retention

30-Day Raw Purge: We maintain a strict data minimization policy. Raw session bundles (the detailed technical logs of a streaming session) are stored in a private, encrypted database for a maximum of 30 days. After 30 days, these raw logs are permanently deleted.

Permanent Intelligence: Only aggregated, non-identifiable "Tile Intelligence" (e.g., "Verizon avg. quality in Aurora") is retained long-term. This data contains no device hashes or individual timestamps.

5. Android Permissions Explained

MediaProjection

Required to analyze screen frames for buffering detection. Android displays a system consent dialog each time monitoring starts. BufferBeat does not record or store any screen content. You can revoke this at any time by stopping the monitoring session.

ACCESS_FINE_LOCATION

Required to tag buffer events with GPS coordinates for the heatmap. Location is collected only during active monitoring sessions. You can deny this permission — the app will still work, events just won't appear on the heatmap.

READ_PHONE_STATE

Used to read carrier name and network type (4G/5G). This permission does not access your phone number, call history, or any personal telecommunications data.

FOREGROUND_SERVICE

Required by Android to maintain the screen analysis service while you watch video in another app. A persistent notification is displayed whenever monitoring is active.

INTERNET

Required to upload anonymous buffer event data to the Firebase cloud database.

6. Third-Party Services

6.1 Google Firebase

We use Google Firebase for anonymous authentication, cloud data storage (Firestore), and web hosting. Firebase is operated by Google LLC. Google's privacy policy applies to data processed by Firebase services. For more information, visit: firebase.google.com/support/privacy

6.2 Google AdMob

BufferBeat displays advertisements through Google AdMob. AdMob may collect device advertising identifiers and usage data to serve personalized or non-personalized ads. You can opt out of personalized advertising through your Android device settings under Google → Ads → Opt out of Ads Personalization.

Advertisements are never displayed during active monitoring sessions — only on the dashboard and results screens.

6.3 Leaflet / OpenStreetMap / CARTO

The public heatmap uses Leaflet (an open-source mapping library), OpenStreetMap map data, and CARTO map tiles. These services may log standard web server access data (IP address, browser type) when you view the heatmap.

7. Data Sharing & Monetization

BufferBeat may share or sell Anonymized Network Intelligence with wireless carriers, infrastructure researchers, or city planners. This data consists exclusively of aggregated network performance metrics (RSRP, RSRQ, and Stall Rates) within geographic tiles.

✗ We Never Share: Raw GPS breadcrumbs, device hashes, or individual user session logs with any third party. Our partners only receive the "Big Picture" of network health.

8. Children's Privacy

BufferBeat is not directed at children under the age of 13. We do not knowingly collect any personal information from children. Since BufferBeat uses anonymous authentication and collects no personal information, no age verification is required.

9. Your Choices and Rights

Start and stop monitoring: You have full control over when BufferBeat monitors your screen. Monitoring only occurs during sessions you explicitly start.

Location permission: You can deny or revoke location permission at any time through Android Settings. The app will function without it.

Ad personalization: You can opt out of personalized ads through Android Settings → Google → Ads.

Uninstall: Uninstalling BufferBeat removes the app and its local data from your device. Previously uploaded anonymous buffer events will remain in the aggregated heatmap database, but cannot be linked to you or your device.

Data deletion request: Since all data is anonymous and not linked to personal identifiers, we cannot identify or delete data belonging to a specific user. If you have concerns, please contact us.

10. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify users through an in-app notice or by updating the "Last Updated" date at the top of this policy. Your continued use of BufferBeat after changes are posted constitutes your acceptance of the revised policy.

11. Contact Us

If you have questions or concerns about this Privacy Policy or BufferBeat's data practices:

privacy@bufferbeat.com

bufferbeat.com