BeepBit Privacy Policy
BeepBit (formerly BeepBoopBing) is an Android app by SimpleeLabs that pairs phones so each one can make the other ring. This policy explains what the app stores, why, who can see it and how to delete it. Questions: simpleedev@gmail.com.
In short
- There's no account. The app never asks for your name, email or phone number.
- We store only what's needed to pair phones, deliver Beeps and provide Pro.
- No ads, no analytics, no tracking, and we never sell your data.
- Ring by Text reads message notifications on your phone only. Your messages never leave it.
- Settings → Delete My Data deletes this phone's data, anytime.
- Settings → Send Error Report emails us only if you send it, from your own email app, after you've seen what's in it.
What we store on our servers
When you open BeepBit, it signs in anonymously and gets a random install ID. The records below are tied to that ID. Pro purchases also have a Google Play purchase identifier so they can be verified and restored.
- Your phone's model name (for example "Pixel 7 Pro") and that it runs Android. Phones you pair with see the model name. Nicknames you give other phones stay on your phone.
- A push token from Firebase Cloud Messaging, so Beeps can reach your phone. Google's push service also reports to us each push it accepts for your phone (such as a Beep, a Beep's stop or the daily check) and, from version 1.0.6, whether it reached BeepBit on your phone, with the ID the push service uses for this install of BeepBit. We use these reports only to find out why a Beep didn't arrive, and they're deleted after 30 days (Delete My Data doesn't remove them sooner).
- Your pairing and group: which phones are paired or grouped with yours and which phone owns the group. A pairing code is 6 characters and expires after 10 minutes.
- Beeps: which phone Beeped which, when, and how it ended (rang, found, stopped or missed), plus how long it rang. Also any optional Pro message you send (up to 160 characters). From version 1.0.6, if a Beep reached your phone but didn't ring, your phone later reports when it arrived and why it didn't ring (for example, it arrived too late).
- "Ready to be found" status: whether the settings that keep your phone reachable are on, and whether it answered the app's daily check. Your group sees it as a dot on its Home screen and, with which settings are off, in Settings → Paired Phones.
- Force-stops: from version 1.0.6, if Android tells BeepBit it was force-stopped, when it last ran before that and when it was opened again (the last five), so a missed Beep can be explained. Android 11 to 14 can't always tell a force-stop from a swipe out of recent apps, so those are marked as uncertain.
- Battery when Beeped: when Share Battery Level (Share Battery When Beeped before version 0.4.7) is on, a Pro phone reports its battery percentage and whether it is charging with its Beep delivery report. This setting defaults off and can be turned on or off independently of location sharing in Settings. No periodic battery monitoring.
- Location when Beeped: only if you enable Share Location (Share Location When Beeped before version 0.4.7), a fresh approximate or precise location, its estimated accuracy and fix time. It tries for 10-metre accuracy within 45 seconds of delivery while the app is on screen, then shares the best fresh fix available; this accuracy is not guaranteed. We never request a stored last-known location or continuously track your phone.
- Pro status, and during the beta, a record that the install took part.
- Purchase history: if you buy or restore Pro, the product, subscription plan, purchase status, renewal setting and expiry date. Your phone sends the Google Play purchase token to our backend for verification with Google; we store its SHA-256 fingerprint, not the raw token. The purchase record lists the install IDs of the phones that have verified it, and a hashed install ID sent to Google Play when you buy lets our backend finish a purchase if the app closes during it. When the app checks purchases with our backend, it also sends the fingerprints of the purchases Google Play lists on the phone, so one that's no longer there stops giving it Pro. We do not receive your card details or Google account email.
- Counters for abuse limits, such as how many pairing codes were tried or Beeps were sent today.
- Server logs: our backend's request logs, including the connecting IP address, install and group IDs, and any errors. Google Cloud keeps them for 30 days.
What stays on your phone
These are never sent to us:
- Nicknames for other phones, your settings, and your choice of built-in ring sound, vibration and camera flash.
- Everything about Ring by Text (below).
Messages you choose to send are stored and delivered through Firebase, as described above. In version 0.3.7 and later, a message is sent only when you choose Send. Older versions may automatically send a configured thank-you message if you enabled Auto-Thanks.
BeepBit's data is not included in Android backups or transfers to a new phone.
Google Play purchases and Restore
Google Play processes Pro payments and sends our backend notifications about purchases and subscription changes. We verify them with Google to provide Pro and handle renewals, plan changes and refunds. The phones in your group can read your Pro status, where it comes from (subscription, lifetime purchase or beta), the plan, its expiry and whether it is set to renew, so they can share your Pro until it ends. Purchase fingerprints and billing account mappings are private to our backend.
Pro you buy works on every phone signed in to the Google account that bought it: each phone gets Pro when the app checks Google Play, and shares it with its group. Restore purchases asks Google Play again. An eligible beta lifetime purchase redeemed through Google Play works the same way.
Ring by Text and Notification access
Ring by Text is an optional Pro feature. In version 0.3.7 and later, it rings your phone when the entire message is your full secret code, ignoring capitalization and surrounding whitespace; older versions check whether a message contains your configured code word. Codes start with bb- (bbb- before version 0.4.4; the older form still works during the beta). To spot it, the app needs Android's Notification access, which lets it read notifications on your phone. The app asks before opening that setting.
- The check happens entirely on your phone. Nothing from your notifications is ever sent anywhere, including to us, and message text is never stored or logged.
- Android shows the app every new notification. It ignores everything except message notifications, and checks those only for your code word.
- When a message rings your phone, the app keeps the messaging app's name, the message time and a short fingerprint (not the text) for one day, so the same message doesn't ring twice. It also briefly keeps the sender's name to show on the ringing screen.
- Your code word and the people you choose stay on your phone. You choose people with Android's contact picker, so the app sees only the contacts you pick (name, number and Android's contact key), never your address book. You can also type a number.
- To stop, turn Ring by Text off. You can also remove BeepBit under Android Settings → Notification access.
Error reports
If you tap Send Error Report in Settings, the app opens your email app with a message to simpleedev@gmail.com. Nothing is sent until you send it from your email app, and you can read or change all of it first. It contains what you write, plus:
- the app's version, and your phone's model and Android version;
- your phone's install ID and its group's ID, so we can find the matching server logs (above), which we may read to find the problem;
- which Phone Setup items are done, whether you have Pro and where it comes from, and whether Ring by Text, Share Battery Level and Share Location are on;
- how far your phone's clock is from our server's, and when you wrote the report.
It never includes your code word, the people you chose for Ring by Text, your location or your messages. Your email address comes with the email, as with any email, and we use it only to reply. We use reports only to find and fix problems.
Permissions the app uses
- Notifications: to show Beeps, messages and setup reminders.
- Display over other apps: to bring up the ringing screen when a Beep arrives.
- Do Not Disturb access (asked for on Android 14 and older): so a Beep can ring through Do Not Disturb. On Android 15 and later it isn't asked for: a Beep rings through Do Not Disturb when it lets alarms through, so the checklist reads whether it does (no permission is needed for that) and counts it with the "Ready to be found" status.
- Notification access (only if you turn on Ring by Text): described above.
- Location while using the app (only if you enable Share Location): the app explains who sees the report before asking. You can grant approximate or precise location, turn sharing off in Settings, or revoke permission in Android. The screen can stay on for up to 45 seconds for a fresh fix; finding the phone stops acquisition. No background-location access is requested.
- Battery set to "Unrestricted" and "Pause app activity if unused" turned off: settings, not data access. They keep Android from stopping the app so it can still be Beeped.
The app uses the camera flash as a ring signal without taking pictures. It doesn't access photos, the microphone, SMS or the call log. Location is used only with the optional setting above; Ring by Text does not collect location.
How we use it
We use this data only to run the app: to pair phones, deliver Beeps and messages, show their status, remind you when a setting is off, provide Pro, prevent abuse and look into error reports you send. We don't use it for advertising or profiling, and we don't sell it.
Who can see it
- Phones in your group: your phone's model name, its "Ready to be found" status, the Beeps between you and the messages you send. Whether a phone has Pro is also visible to its group, with where it comes from, its plan, its expiry and whether it is set to renew. The phone that Beeped yours sees its battery report and, if you opted in, its location report. Other group members cannot read that Beep report.
- Google, which runs the services the app is built on: Firebase Authentication (the anonymous sign-in), Cloud Firestore (storage), Cloud Functions (our backend), Firebase Cloud Messaging (delivery), Firebase App Check with Google Play Integrity, and Google Play Billing with the Google Play Developer API (Pro purchases). App Check confirms requests come from the real app on a genuine device. Google processes this data, including your IP address when the app connects, to provide these services. See Firebase's privacy information and Google's Privacy Policy.
- The law: if we're legally required to disclose data, we will. Given how little we hold, it would be limited to the above.
Our database and backend run on Google Cloud in the United States.
How long we keep it
- Beeps and messages: deleted automatically 30 days after the Beep.
- Location reports: disappear from the app after 24 hours. Server copies are deleted by the first daily cleanup after they are 24 hours old, normally within 48 hours, or sooner by Delete My Data. Battery reports remain with the Beep event for its 30-day lifetime; the displayed report expires after 24 hours.
- Pairing codes: deleted when used or cancelled, otherwise automatically within about a day of expiring.
- Groups: removed when fewer than two phones remain.
- Your phone's record, its status and Pro record: kept while you use the app. They're deleted when you use Delete My Data, or automatically once the app hasn't been used on that phone for 90 days, unless it's paired with another phone or was given Pro directly by SimpleeLabs. A purchase doesn't keep it: if you use the app on that phone again, it gets Pro back from Google Play.
- Purchase verification records: kept while any phone that has the purchase is still kept. Delete My Data or the 90-day cleanup removes that phone from them, and a record is deleted once no phone has it. A phone that checks Google Play later verifies the purchase again and recreates the records it needs.
- Billing account mappings: deleted with the phone's record.
- Server logs: 30 days.
- Error reports (emails you send): until the problem they report is solved, or sooner if you ask.
- On your phone: until you use Delete My Data, clear the app's storage or uninstall it.
Uninstalling doesn't delete what's on our servers right away; that happens after 90 days, as above. To delete it sooner, use Delete My Data before uninstalling, or email us.
Deleting your data
In the app, go to Settings and tap Delete My Data at the bottom. After you confirm, it:
- removes your phone from its group;
- deletes its record, status, Pro record, billing account mapping and pairing code;
- removes it from purchase verification records, deleting each record no other phone has (other phones on the same Google account keep their Pro);
- deletes every Beep it sent or received, with their messages;
- deletes its anonymous sign-in;
- erases the app's data on your phone and closes the app.
Server logs expire on their own within 30 days.
Deleting your data or uninstalling does not cancel a Google Play subscription. Cancel it in Google Play → Payments & subscriptions → Subscriptions to stop future payments. Google retains its own payment records under its policies; Delete My Data deletes ours for this phone.
If you've already uninstalled, email simpleedev@gmail.com with your phone's model, the names of the phones you were paired with and roughly when you last used the app. We'll delete your data within 30 days.
You can also unpair or leave a group at any time in Settings → Paired Phones.
Security
All traffic between the app and our servers is encrypted (HTTPS), and Google encrypts stored data. Access rules let each phone read only its own record and its group's data. Only our backend can change pairings, groups and Beeps, and it accepts requests only from the genuine app.
Children
BeepBit isn't directed at children under 13, and we don't knowingly collect personal information from them. If you think a child under 13 has used the app, email us and we'll delete the data.
Changes to this policy
If this policy changes, we'll update it here with a new effective date. If a change affects how your data is used, we'll also say so in the app or its store listing.
Contact
SimpleeLabs · simpleedev@gmail.com