WristBuddy — Privacy Policy
Effective date: Last updated:
Looking for the plain-English overview instead of the formal text? See the Security & privacy page.
WristBuddy is a utility app for iPhone + Apple Watch and for Android phones + Wear OS watches that displays your phone’s status (battery, charging, network, motion, silent / Focus mode, distance, and more) on your watch. This policy explains what data the app handles and why — kept short because the answer is “almost nothing.” It applies equally to the iOS/watchOS and the Android/Wear OS versions of the app.
The developer of WristBuddy is Mario Longhi, an independent developer based in Spain (EU). Throughout this document, “we” refers to the WristBuddy app and its developer.
TL;DR
- WristBuddy collects no personal data — on any platform.
- WristBuddy sends no data to any server, cloud, or third party.
- All data exchanged between your phone and your watch stays on your devices, sent only between the two via Apple’s WatchConnectivity framework (iPhone ↔ Apple Watch) or Google’s Wearable Data Layer API (Android ↔ Wear OS) — over Bluetooth or local Wi-Fi.
- WristBuddy contains no analytics, no advertising, no tracking, and no third-party SDKs.
- Our App Store privacy nutrition label and our Google Play Data safety section both state “Data Not Collected” / “No data shared or collected” — every category unchecked.
Information we do not collect
We want to be specific about what we do not do, because the absence of data collection is the central design choice:
- We do not collect your name, email address, phone number, or any other identifying information.
- We do not require you to create an account or sign in.
- We do not collect device identifiers, advertising identifiers (Apple’s IDFA on iOS, Google’s Advertising ID on Android), or similar.
- We do not track your location.
- We do not track your usage of the app, store crash reports on our servers, or use any analytics service.
- We do not share, sell, or transmit data to any third party — because we do not have any data to share.
- We do not store your data in iCloud, Google Drive, on our servers, or on anyone else’s servers.
How the app works (data flow)
WristBuddy reads certain information from your phone and watch through the operating system’s standard frameworks, and displays it in the app interface. None of this information leaves your devices:
| Information shown | How it’s read | Where it stays |
|---|---|---|
| Phone battery percentage and charging state | iOS / Android battery APIs | On the phone; sent to your paired watch via WatchConnectivity (iOS) or the Wearable Data Layer (Android) |
| Wi-Fi and cellular connectivity status | Apple’s Network framework / Android connectivity APIs | Same as above |
| Whether the phone is moving | Phone motion sensor / accelerometer | Same as above |
| Whether the phone is on silent / in Focus mode (Do Not Disturb) | iOS audio + Focus APIs / Android ringer-mode + Do Not Disturb APIs | Same as above |
| Whether the phone screen is locked | iOS / Android system state | Same as above |
| Air pressure (barometer) and thermal state, where supported | Phone barometer + thermal APIs | Same as above |
| Distance between phone and watch | Apple’s NearbyInteraction (UWB) framework / Android ranging on supported watches (e.g. Pixel Watch 2+) — Pro feature, requires compatible hardware | Computed locally on each device; never transmitted off-device |
| Watch battery percentage and charging state | watchOS / Wear OS battery APIs | On the watch; sent to your phone for the watch status screen (Pro feature) |
WatchConnectivity (Apple) and the Wearable Data Layer API (Google) are the platforms’ built-in frameworks for direct phone↔watch communication. They use Bluetooth or local Wi-Fi between your two paired devices and do not route data through any server.
A randomly generated identifier is created on your device the first time the app launches, stored only in the app’s local on-device storage (iOS UserDefaults / Android SharedPreferences), and used solely to label outgoing “Suggest a feature” feedback emails so we can correlate emails from the same install if you choose to send us follow-up messages. This identifier never leaves your device unless you explicitly tap “Suggest a feature” and send the email yourself.
Permissions WristBuddy may request
Both operating systems require apps to ask for permission before accessing certain capabilities. Every permission below is opt-in and used only for the feature described.
iOS / watchOS
| Permission | Why we ask |
|---|---|
| Motion & Fitness | To detect whether your iPhone is currently moving (accelerometer reading). Used only for the “Motion detection” status row. The accelerometer is sampled on-demand — only briefly when the Watch app is refreshed — never continuously. |
| Focus Status | Optional, only if you enable the Pro “Focus mode” status row. Lets the app know whether iOS Focus mode is active so the corresponding row can show On/Off. The data stays on your devices. |
| Microphone | Optional, only if you enable the Pro “Locator Ring” feature. iOS requires the microphone permission to use the audio category that routes the locator ring sound to the iPhone’s built-in speaker. The microphone is never recorded, listened to, or used for any audio input. Decline it and the ring still works through the default output. |
Android / Wear OS
| Permission | Why we ask |
|---|---|
| Notifications | Optional, only if you enable battery alerts. Lets the app post a local notification when your phone battery crosses a threshold you set. Notifications are generated and shown entirely on-device. |
| Vibration (watch) | Lets the watch buzz when you use the “Buzz watch” / find-my-watch action. |
Motion detection on Android uses the device’s accelerometer through standard sensor APIs, sampled on-demand and not continuously; reading ringer/Do Not Disturb and lock state uses standard Android system APIs. WristBuddy on Android requests no location, contacts, camera, microphone, or phone-identity permissions.
You can revoke any permission at any time in your device settings (iOS: Settings → WristBuddy; Android: Settings → Apps → WristBuddy → Permissions). The corresponding feature will simply stop working; nothing else in the app is affected.
In-App Purchases
WristBuddy offers a one-time Pro unlock through the platform’s standard in-app purchase system — Apple’s StoreKit on iOS and Google Play Billing on Android. When you make a purchase:
- The transaction is handled entirely by Apple or Google. We never see your name, payment information, Apple ID / Google account, or any other personal data associated with the purchase.
- Apple and Google may send us anonymous, aggregated sales reports (e.g., “X copies sold in country Y this month”) through App Store Connect / Google Play Console. These reports do not identify individual customers.
- The Pro unlock is stored locally on your device and verified through the platform’s billing framework. There is no separate account or login.
You can restore your Pro purchase on a new or reset device by tapping Restore Purchases in the app — Apple or Google identifies the entitlement through your store account without us learning your identity.
Children’s privacy
WristBuddy is rated 4+ on the App Store and Everyone / PEGI 3 on Google Play, and is suitable for all ages. The app does not knowingly collect personal information from anyone, including children under 13.
Third-party services
WristBuddy uses no third-party services, SDKs, frameworks, or networks. The app’s runtime dependencies are limited to Apple’s iOS/watchOS and Google’s Android/Wear OS system frameworks (including the platform billing libraries used solely to process the Pro purchase). There are no analytics services, no advertising networks, and no crash-reporting services beyond the operating system’s own (anonymous and controlled at the OS level, not something WristBuddy enables independently).
International data transfers
Because WristBuddy collects and transmits no data, there are no international data transfers to disclose. All app data stays on your personal devices.
Your rights (EU / GDPR)
The app’s design means there is no personal data processing for us to act on. To be explicit:
- Right of access: there is no personal data we hold about you.
- Right to rectification / erasure: there is no data to correct or delete on our end. To remove all app data from your device, simply delete the WristBuddy app — your operating system removes the local app storage along with it.
- Right to data portability: not applicable, as we hold no personal data.
- Right to object / restrict processing: not applicable, as we conduct no processing of personal data.
- Right to lodge a complaint: if you nonetheless believe we have mishandled data, you may contact your national data protection authority. In Spain, that is the Agencia Española de Protección de Datos (https://www.aepd.es).
Changes to this policy
If we ever change how WristBuddy handles data — for instance, if we add a feature that requires a new permission — we will update this policy and the “Last updated” date at the top. Material changes will also be reflected in the App Store privacy nutrition label and the Google Play Data safety section, which Apple and Google display on the app’s listing.
About this website
The website you’re reading this on (wristbuddy.app) uses Cloudflare Web Analytics — a cookieless, no-fingerprinting tool that gives the developer aggregate page-view counts and country-level breakdowns. No cookies are set, no personal data is collected, no cross-site tracking is performed. Visitor IP addresses are processed by Cloudflare only to derive aggregate country statistics and are never stored. The setup is GDPR-compliant by design, which is why there’s no cookie-consent banner.
This section concerns the website only and is independent of the app’s privacy posture: the apps themselves collect, store, and transmit no data, as detailed above. The lightweight site analytics is a marketing-side concern, deliberately scoped not to cross into anything about individual visitors.
Feedback form submissions via the Feedback page are handled by Tally.so, governed by Tally’s own privacy policy. Your email address (if you choose to provide it) is shared only between Tally and Mario Longhi to enable a reply. The launch-notification signup on the homepage uses the same Tally infrastructure and is only loaded when you explicitly open the “Get an email when it ships” disclosure — nothing is sent to Tally until you click.
Web fonts (Bricolage Grotesque and IBM Plex Mono) are self-hosted on wristbuddy.app rather than loaded from Google Fonts, so no request is made to a third party for typography. The third parties that receive any data from a visit to this site are limited to Cloudflare (hosting + analytics, IP processed only for aggregate stats) and Tally (only when you submit feedback or open the launch-notification signup).
Contact
For privacy questions, feedback, or to exercise any of your rights described above, please contact:
Mario Longhi — policy@wristbuddy.app
We aim to respond to privacy inquiries within 14 days.