Privacy Policy

Camera, movement, and videos

BuzzUps uses your front camera to detect eye and head movement and control the game. The app processes camera frames, video, and movement on your iPhone. We do not send camera frames, face data, or movement recordings to our server, RevenueCat, DataFast, or TikTok's App Events SDK.

Videos stay on your iPhone unless you choose to share them using the iOS share sheet. You choose the destination, such as TikTok, Instagram, or another app. You can also choose to save a video to Photos. Your Photos and backup settings may also copy saved videos to your own cloud storage. BuzzUps does not request microphone access.

Data stored on your iPhone

The app stores settings, free-run allowance, best scores, completed pushup totals, recent run results, and saved videos on your device. It uses this data to run the game, show your progress, and keep your choices. It also saves your preset leaderboard name, bee, and pending score submissions locally. Your random leaderboard sign-in key is stored in Keychain.

Keychain also stores your free-run allowance and notification record. These records can remain after you delete and reinstall the app on the same iPhone. When available, BuzzUps reuses them to keep your remaining free runs and notification choices, and to update the existing notification registration. The free-run allowance and notification Keychain records do not sync through iCloud Keychain. Reinstalling the app does not guarantee that these records will be cleared or recovered.

Subscriptions and RevenueCat

Apple processes App Store payments. We use RevenueCat to check purchases, restore access, and manage BuzzUps Plus. RevenueCat processes an anonymous app user ID, purchase and receipt information, subscription status, and technical information such as app version, device type, and operating system. We do not send it your leaderboard nickname, camera footage, or movement data.

We also use RevenueCat's subscription analytics to understand paywall impressions, purchases, renewals, cancellations, and subscription performance. This helps us operate and improve BuzzUps. Apple handles your payment details; BuzzUps does not receive your payment card number.

Learn more in RevenueCat's privacy policy and Apple's privacy policy.

Optional notifications

BuzzUps asks for notification permission after your first Try again tap. If you choose Allow after reading the explanation, you agree to receive new content and feature updates, leaderboard updates, and bonus runs, special offers, and play reminders. You can turn each type off under More options → Notifications. You can keep playing if you refuse.

We use a random notification recipient ID, an authentication credential, your Apple push token, notification choices and consent date, time zone, and the time your app last updates its notification registration. The recipient ID, credential, and notification choices stay in your iPhone Keychain. The server stores the recipient ID, a hash of the credential, and the registration data described above. The recipient ID is randomly generated by BuzzUps, not derived from your face or device characteristics. We use it to manage your notification choices, update changing push tokens, and limit repeated messages. Apple Push Notification service delivers notifications, and Cloudflare hosts the registration and delivery service. We do not send your camera images or videos with notification data.

The current notification registration does not include your RevenueCat app user ID or leaderboard player ID. Keeping a Keychain record does not override your iPhone notification permission or your in-app notification choices. Turning notifications off stops delivery once the change reaches our service; it does not itself delete the registration or earlier delivery records.

We retain delivery records for up to 90 days and remove notification registrations after 180 days without a registration update. To request removal of your push token, choices, and delivery history, contact support@buzzups.app with the Notification support ID from More options → Notifications. We keep a minimal credential hash and recipient ID for up to 180 days to prevent old requests from restoring deleted data. Deleting this record does not reset free runs or cancel Plus. Offline changes take effect on the server after your iPhone reconnects.

App and website analytics

App analytics

When configured for the app build, DataFast records screen, dialog, and game-state views, feature actions, paywall openings, selected plans, and purchase or restore outcomes. This helps us understand which parts of the app people use and where they leave the purchase flow. Events also include camera and notification permission answers, notification openings, and sharing outcomes, without shared video contents.

The app creates a random installation ID and session ID. It stores these IDs on your iPhone, without browser cookies or Apple's advertising identifier. We send the DataFast installation ID to RevenueCat to connect app events with subscription events. This ID is separate from your leaderboard profile and does not include your nickname or email.

Events include app version, operating system, screen size, language, timezone, and whether the build uses the test environment. DataFast receives your IP address when the app sends an event. We do not send scores, pushup totals, camera images, face coordinates, video files, captions, or leaderboard sign-in keys to DataFast.

The app keeps up to 500 unsent events locally for up to seven days and retries failed requests. Test builds use a separate DataFast website ID. Collection stays off when that build has no website ID.

TikTok advertising measurement

With your permission through Apple's tracking prompt, BuzzUps uses TikTok's App Events SDK to measure and improve our ads. It sends app install, launch, return-use, and purchase events, advertising and device identifiers, app and device details, and SDK diagnostics to TikTok. TikTok also receives your IP address, language, region and time zone. This can indicate approximate location; BuzzUps does not request GPS access. Purchase events can include product, price, currency, transaction identifiers, and StoreKit transaction details. TikTok can match event data with its users, measure and personalize ads, build advertising audiences, and personalize other content under its Business Products (Data) Terms. SDK diagnostics include timing measurements, error information, and technical device information. TikTok diagnostics do not include automatic crash reports.

If you decline tracking permission, BuzzUps does not start this SDK. You can change permission in iPhone Settings under Privacy & Security, then Tracking. When BuzzUps detects withdrawn permission, it stops TikTok requests, cancels pending requests, clears saved device identifiers from the SDK, and deletes queued SDK events. If you later allow tracking again, restart BuzzUps before the SDK can resume. This does not remove data TikTok already received. We do not send camera images, face coordinates, videos, scores, pushup totals, contact details, or leaderboard profiles to TikTok's App Events SDK. Video sharing remains a separate action that you control.

TikTok's Business Products (Data) Terms set a maximum retention period of 18 months for Event Data, subject to applicable terms and law. Audience data can remain until deleted or until 12 months after its last use or change. Changing tracking permission does not delete data already received. Contact support@buzzups.app for privacy requests. See TikTok's Business Products (Data) Terms and TikTok's privacy policy for its data uses and privacy controls.

Website analytics

We use the Whop Pixel on this website to measure page views and connect visits with our advertising. Whop receives page and browser information and uses browser storage and identifiers to recognize visits. See Whop's privacy policy for information about its data handling.

We use DataFast on buzzups.app, including our support and privacy pages, to understand visits, traffic sources, and use of the website. It records page addresses, referring pages, campaign parameters, and selected clicks, such as video controls and support links. It also receives technical information such as browser, device, screen size, language, timezone, and IP address.

We use DataFast's cookieless website tracker. It does not use cookies to identify visitors. It may use browser storage for the current tab session. DataFast creates a temporary visitor identifier from signals such as IP address, browser information, and our domain. This identifier changes daily, so it does not create a lasting visitor profile across days.

Website visits and app events appear in the same analytics project. We do not automatically link a website visitor to a leaderboard profile or an app installation. Website click events do not include the contents of support emails, camera images, or payment details.

See DataFast's privacy policy.

DataDad analytics and uptime

We use DataDad on the BuzzUps website to understand page visits and App Store link clicks. The website tracker does not receive camera frames, workout recordings, or leaderboard sign-in keys. An App Store click does not confirm an installation or subscription.

DataDad receives page paths, referring pages, campaign information, and selected click names. It uses request IP addresses and browser information to derive approximate location, device categories, and a daily visitor identifier scoped to this website.

DataDad runs in cookieless mode. Its temporary tab identifier stays in page memory, and we do not enable its persistent identity cookies. DataDad also checks website availability and response time from its servers. Those uptime checks are separate from visitor tracking.

How DataDad handles analytics.

Leaderboard

Your game score is sent to the leaderboard automatically after each completed game. Your preset nickname, avatar, best scores, and rank are public. A Plus label shows when you had Plus access when a score was saved for submission. Scores from games played offline stay on your iPhone until the app can send them.

Camera and video processing happen on your iPhone. Videos stay on your iPhone unless you choose to share them using the iOS share sheet. Automatic score submissions never include video.

We store a random player ID, a protected hash of your sign-in key, preset profile choices, run IDs, scores, dates, and removal records. We use this data to display the leaderboard and accept your results. Earlier app versions may also have stored private player-block records. Guest profiles do not require an email address or social login.

Use “Delete leaderboard” in Profile to delete your leaderboard data, scores, and associated personal records. After your next completed game, the app automatically sends your score to a new leaderboard record. This does not upload video. Deleting leaderboard data does not cancel your Apple subscription or automatically erase subscription records held by Apple or RevenueCat. Losing your device sign-in key can prevent access to your guest profile.

Hosting, security, and service providers

Cloudflare hosts our online services and leaderboard database. Requests pass through its network, which processes technical request data, including IP addresses, to deliver and protect the service. Our server uses short-lived hashed request identifiers to limit service abuse. Operational logs help us find service errors. We do not intentionally log sign-in keys or request bodies.

We share data with providers as needed to operate these features, process purchases, provide analytics, and protect the service. Providers may process data outside your country. Their applicable privacy policies and data-processing terms explain their handling of that data. We may also disclose data when required by law or to protect users and the service. With tracking permission, we share the advertising data described above with TikTok. Privacy laws can classify advertising data sharing as a sale or sharing of personal data, even without a monetary payment.

Read Cloudflare's privacy policy. When you open external links or share videos, the destination's privacy policy applies.

How long data stays

Local game data stays on your device until you remove it or the app clears it. Keychain items and copies saved to Photos can remain separately from the app. Leaderboard records normally remain while your profile exists.

Our server clears expired rate-limit records after seven days, during daily maintenance. Deleted database records may remain in recovery copies for up to 30 days. We do not reopen deleted profiles to public access after a restore. Subscription records may remain longer where needed to manage purchases, resolve disputes, or meet legal obligations. Provider retention terms also apply to data they hold.

Your choices and privacy requests

If you contact support, we receive your email address and the message and attachments you choose to send. A message may include a Notification support ID, device model, app version, or other details needed to answer your request. We use this information to provide support and handle privacy requests.

You can control camera and Photos permissions in iPhone Settings. Use “Delete leaderboard” in Profile to delete your guest account and scores. Manage or cancel an Apple subscription in Apple's subscription settings.

Depending on the law that applies to you, you may request access, correction, deletion, or a copy of your personal data. You may also have rights to object to or restrict processing, withdraw consent, and complain to a data-protection authority. We may need information to confirm that a request concerns your data. Use BuzzUps support for privacy requests.

Changes to this policy

We will update this page when our data practices change. The date above identifies the current version. We will provide additional notice or request consent when required.