Legal information

Privacy policy

How VocAll uses the information required to operate the Android app, public ride directory and website.

1. Data controller and general principles

VocAll is a motorcycle intercom app published by Benoit Botella under the name Tatsunao. Contact: tatsunao@hotmail.fr.

VocAll does not require an account, does not use data for advertising and does not record or store the content of audio conversations.

2. Microphone, WebRTC and TURN relay

Android microphone access is used to transmit your voice while your microphone is enabled in a ride. VocAll uses WebRTC. Where network conditions permit, WebRTC favours a direct connection. If a direct connection cannot be established, WebRTC traffic may temporarily pass through VocAll’s private TURN relay.

WebRTC audio content remains encrypted between participants. The relay forwards encrypted packets in real time and does not record audio. VocAll does not record or store conversation content.

3. Bluetooth

On relevant Android versions, Bluetooth permission can be used to identify and route audio through a connected headset or motorcycle intercom. VocAll does not build a database of your Bluetooth devices.

4. Background operation and notifications

During a ride, VocAll can use an Android foreground service so communication can continue while the app is in the background or the screen is off. Android may show a persistent notification for this service.

5. Optional group location

GPS sharing is optional. When enabled, the current useful position can be exchanged inside the room for group map features. VocAll does not build a detailed route history.

6. Public rides

When a host publishes a ride, the public ride service receives the information needed for the listing: technical room code, ride title, host/rider name, optional description and ride type, capacity, current participant count and a rounded position used for nearby search. Listings expire quickly when the active host stops maintaining them.

For a join request, the requester’s optional message and rider profile can be associated temporarily with that request so current room members can review them before voting. VocAll does not use this mechanism to build a permanent public profile directory.

The public map preview does not expose the exact GPS point. It returns a further-coarsened centre and an approximate area of about 2.5 km radius. The precise meeting point, individual rider positions and private room map markers are not published in the nearby directory.

7. Meeting point

A precise meeting point can be set by the current host inside the room. It is exchanged with admitted participants and is not sent as a public directory field.

8. Local preferences and rider profile

VocAll can store local preferences such as rider name, avatar, theme, GPS preference, explicitly saved ride codes and optional rider-profile fields (age, gender, motorcycle, experience, riding style and short bio). While a public join request is pending, its technical request identifier can also be kept locally so the app can continue tracking the response outside the nearby-rides screen.

9. Technical room data, rider profiles and chat

Session identifiers, peer identifiers, connection states, network-quality information, alerts and other room messages are exchanged as required for the live session.

Rider profiles are exchanged with current room members so they can be viewed in the participant list. Room chat exchanges the text messages and images required for the live session. Received images are session-oriented content and are not presented as a permanent VocAll-hosted gallery.

10. Host removal

If the host removes a rider, the rider is disconnected. The app clears that room code from the removed rider’s recent-room recovery data and from saved rides on that device.

11. Mapping providers

Map display uses third-party mapping services including OpenFreeMap, OpenMapTiles and OpenStreetMap data. Loading a map therefore contacts the services required for map tiles and styles.

12. Technical infrastructure and providers

Signalling and public ride services use Netlify infrastructure. VocAll’s TURN relay is hosted on Oracle Cloud Infrastructure in the France Central (Paris) region.

When a device contacts the TURN service or its access service, the infrastructure processes the technical data required for connectivity and security: public IP address, network ports, date and time, temporary technical identifier, session duration and traffic volume. TURN credentials are generated on demand, do not create an account and expire after twelve hours.

TURN technical logs and associated access logs are retained for no more than seven days and are then deleted automatically, except where temporarily required for a security incident or legal obligation. Oracle and Netlify may process operational data as technical service providers under their data-protection terms and safeguards, including applicable mechanisms for international transfers.

13. Website and hosting

The website is hosted by Netlify. Hosting infrastructure may process technical request data such as IP address and request metadata needed to deliver and protect the site. Public ride API requests are also hosted through Netlify.

14. Google Play

Installation and updates are distributed through Google Play, which processes its own account, device, download and security data under Google’s policies.

15. Purposes, legal bases and retention

Technical processing is used to provide the app features requested by the user, establish and secure communications, maintain live rooms and prevent abuse. Depending on the relevant operation, processing is based on providing the service requested by the user and on VocAll’s legitimate interest in maintaining secure and reliable infrastructure.

Session and ride data is retained only for as long as required for the operation described in this policy. Local preferences remain on the phone until the user deletes them. TURN log retention is described in section 12.

16. Your choices and rights

You can remove Microphone, Bluetooth, Notification or Location permissions in Android settings. Local VocAll preferences can be deleted by clearing the app’s data or uninstalling it.

You may request access, rectification, deletion or restriction, or object to processing where these rights apply. Because VocAll does not create accounts, technical information and an approximate connection period may be required to locate relevant data. You may also lodge a complaint with the French data-protection authority, the CNIL.

17. Contact

To exercise your rights or ask a question about VocAll and this policy: tatsunao@hotmail.fr.