Privacy Policy
Effective date: July 2026 · Questions? contact@foxbenddigital.com
Foxbend Digital ("Foxbend Digital," "we," "us," or "our") operates Avert (the "App"), a driving-safety app that helps a parent or guardian prevent phone use while a vehicle is being driven. This policy explains what information the App collects, how it's used, and the choices you have. It applies to the Avert Android app only.
If you have questions about this policy, contact us at contact@foxbenddigital.com.
What Avert does
Avert runs on a driver's phone. When the phone connects to a paired vehicle's Bluetooth (or, as a fallback, when GPS shows driving speed while Bluetooth is off), Avert shows a lock screen that blocks most apps until the vehicle stops. A parent or guardian sets this up and controls it with a PIN. If the driver attempts to disable or bypass the lock, Avert notifies a trusted contact the parent has designated.
Information we collect
Avert is designed to keep information on the device wherever possible. Here is exactly what it collects and why:
| Category | What's collected | Why |
|---|---|---|
| Vehicle Bluetooth info | The name and Bluetooth MAC address of any vehicle device you choose to register | To detect when the phone connects to or disconnects from that vehicle, which starts and stops driving lockdown |
| Location | GPS-derived speed | Used only (a) while a registered vehicle is connected, to detect when the car has stopped so the phone can temporarily unlock, and (b) if Bluetooth is turned off while a vehicle is registered, as a fallback check for whether the phone is moving at driving speed. Location is never logged with a history, never used for tracking, and never leaves the device. |
| Trusted contact phone number | The phone number a parent enters | Used to send an SMS alert directly from the driver's phone if tampering is detected (e.g. Bluetooth disabled while driving, the app's Accessibility Service turned off, or the vehicle removed) |
| Driver name | An optional display name a parent enters | Included in SMS alerts so the trusted contact knows which phone triggered the alert |
| Parent PIN | A 6-digit PIN set by the parent | Gates access to settings and to clearing tamper alerts. The PIN itself is never stored — only a salted PBKDF2 hash of it, which is then encrypted using a key held in the device's hardware-backed Android Keystore. Avert cannot recover or display the PIN. |
| Tamper event log | Timestamps and types of tamper events (e.g. "Bluetooth disabled," "vehicle unpaired") | Kept locally so a parent can review what happened and when it was resolved |
| Which app is in the foreground | Read via Android's Accessibility Service | Used solely to decide whether to show or hide the lock screen. Avert's Accessibility Service does not read screen content, does not capture keystrokes, and does not access data inside other apps. |
Avert has no user accounts, no login, and no backend server. There is nowhere for this data to be sent except the actions described above (an SMS sent from the device itself). Nothing is uploaded to Foxbend Digital or stored on our servers, because we don't operate any servers for this app.
How we use information
All of the information above is used exclusively to operate the App's core function: detecting driving, showing/hiding the lock screen, and alerting a trusted contact if the lock is tampered with. We do not use this information for advertising, profiling, or any purpose unrelated to the App's stated function.
Sharing and third parties
We do not sell, rent, or share your information with third parties. The only outside parties involved in the App's operation are:
- Your mobile carrier, which delivers the SMS alert (sent directly from the device using Android's standard SMS capability — not routed through Foxbend Digital).
- Google Play services, which provides on-device location data to the App. Google's handling of this is governed by Google's Privacy Policy. Avert only reads a location fix at the moments described above — it does not use Google's location services for any other purpose.
Android itself may separately collect limited diagnostic data (e.g. crash reports through Google Play) under Google's own privacy policy; that is independent of what Avert collects.
Data storage and security
- All data described above is stored locally on the device, in a local database and local app storage.
- The App disables Android's automatic cloud backup for its data (
allowBackup="false"), so this information is not copied to Google's backup service. - The PIN is never stored in readable form — see the table above for how it's protected.
- Uninstalling the App, or clearing its data in Android's App Settings, permanently deletes all information described in this policy from the device.
Children's privacy
Avert is a parental-control tool: it is installed, configured, and controlled by a parent or guardian, including setting the PIN and trusted contact. It is not directed at children as an audience, and children are not expected to create accounts or provide information to us directly — the App has no account system at all. A parent or guardian should only install Avert on a device they own or have the legal authority to manage.
Your choices
- You can review and change the trusted contact number, driver name, and lockdown settings at any time from within the App (behind the parent PIN).
- You can remove a paired vehicle, which stops Avert from monitoring that connection.
- You can uninstall the App at any time, which removes all locally stored data.
Permissions this App requests
| Permission | Purpose |
|---|---|
| Bluetooth | Detect connection to a registered vehicle |
| Location (including background) | Confirm driving speed as a fallback if Bluetooth is disabled, and detect when a connected vehicle has stopped |
| Accessibility Service | Detect the foreground app to show/hide the lock screen (does not read screen content) |
| Send SMS | Alert the trusted contact if tampering is detected |
| Notifications | Show the persistent "Avert Active" status and alert notifications |
| Run at startup | Resume monitoring after the device restarts |
| Battery optimization exemption | Keep monitoring reliable in the background |
Changes to this policy
We may update this policy as the App changes. We'll update the effective date above when we do. Continued use of the App after a change constitutes acceptance of the updated policy.
Contact us
Foxbend Digital
contact@foxbenddigital.com
https://foxbenddigital.com