Privacy Policy

Controller and contact

Vamit, Belgium. Privacy and deletion questions can be sent to support@vamit.net. Company identifiers: VAT BE1039001840 and D-U-N-S 374183137.

Privacy summary

• No advertising SDK.
• No Vamit analytics or behaviour tracking SDK.
• No route history is uploaded.
• No camera image is uploaded or permanently stored by default.
• No access to SMS or chat message content.
• No automatic messages are sent.
• Regular consumer journeys do not require a Vamit account.

Location, speed and movement

Safe Ride uses Android location services to calculate current speed and GPS accuracy. Activity Recognition may report categories such as in vehicle, on bicycle, still, walking or running with a confidence value. These signals are used by the on-device safety state machine. The app does not create or upload a route history.

When automatic dusk mode is enabled, one coarsely rounded last valid position may be stored locally and overwritten. It is used only to calculate local dawn and dusk times.

Bluetooth and vehicle profiles

With permission, Safe Ride can read supported Bluetooth headset or hands-free connection status. When you register a vehicle, the device name, Bluetooth address, vehicle type and steering-side preference may be stored locally. Bluetooth behaviour can differ by manufacturer.

Optional camera processing

Camera use is optional and requires explicit permission, visible use, calibration and a fixed mount. CameraX frames are analysed on the device with ML Kit face detection. Frames are held briefly in memory and closed after analysis. Images are not uploaded or saved by default. Numerical confidence values and decisions may be used during the active session or included in an optional local trip summary.

Camera-based driver or passenger detection is experimental and is never treated as infallible.

Notifications, calls and messages

If you grant Android Notification Policy Access, Safe Ride can request a Do Not Disturb policy that silences ordinary call, SMS and chat alerts during protection while keeping alarms audible. Safe Ride does not read message content, stop network delivery, terminate calls or universally block the system phone and messaging apps.

Local storage

The app may store language and appearance choices, safety thresholds, profile type, permissions state, camera opt-in and calibration, passenger cooldown, optional trip-log setting, known vehicle profiles, a safe non-camera runtime snapshot, subscription entitlement indicators and local administrative configuration.

Optional local trip summaries contain limited derived information such as start/end time, travel mode, peak speed and an optional average confidence. They do not contain GPS coordinates or route points.

Administrator PIN and device security

A Fleet or Family administrator PIN is not stored in plain text. Safe Ride stores a cryptographic verifier and uses non-exportable Android Keystore material. Failed attempts may trigger a local delay. The encrypted business synchronisation queue and cache use Android Keystore-backed AES-GCM encryption.

Google Play Billing and reviews

Google Play handles purchases, payment details, subscription administration, updates and the official review flow. Safe Ride receives product details, purchase state and technical purchase tokens needed to grant or verify access. Business purchases require server-side verification before rights are activated. Google's processing is governed by the Google Privacy Policy and Google Play terms.

Firebase for Family, Fleet and Enterprise

Ordinary Free and Premium journeys do not require Safe Ride cloud processing. Optional Family, Fleet and Enterprise functions can use Firebase Authentication, Cloud Firestore, Cloud Functions and App Check to process the minimum account, organisation, licence, role, member, device, enrolment and safety-policy information needed to coordinate multiple devices.

Fleet synchronisation does not include route history, camera images, message content or permanent location points. App Check and Play Integrity may process app/device attestation signals to help protect the service from abuse.

On-device language models

For some selected interface languages, Android may download a free ML Kit language model over Wi-Fi. Translation then runs on the device. Safe Ride settings, business data and user content are not sent to an online translation service.

Permissions

Depending on device version and enabled features, Safe Ride may request fine location, Activity Recognition, nearby-device/Bluetooth access, notifications, foreground service/location, optional camera access and optional Notification Policy Access. The app does not request background location in the current MVP. Android permissions can be withdrawn in system settings.

Retention and deletion

Local information remains until you delete it in Safe Ride, clear Android app storage or uninstall the app. The in-app delete function removes local settings, calibration, vehicle profiles, trip summaries, administrative verifier, synchronisation queue/cache and related Keystore material.

Organisation administrators may need to retain limited business records for account security, subscription administration and legal obligations. You can request access, correction or deletion at support@vamit.net. Google Play purchase records must be managed through Google.

Security, transfers and processors

Safe Ride uses Android platform security, encrypted transport and access controls. Firebase and Google Play services may process limited service data in regions operated by Google under their applicable terms and transfer safeguards. No system can guarantee absolute security.

Children and family use

Safe Ride is a road-safety utility and is not designed as a social service for children. Family features should be configured by an adult account holder. Local Family policy on an ordinary phone is not unbreakable parental control; stronger enforcement requires an appropriately managed Android device.

Changes

This policy may change when features, Android requirements, subscriptions or connected services change. The effective date at the top identifies the current version.