VOKPIT: Privacy Policy

Last updated: October 2026 · VOKPIT app for Android and iPhone (com.vokpit.app)

1. Who is responsible for your data

VOKPIT is published by a private individual based in France, the data controller under the General Data Protection Regulation (GDPR), who remains anonymous on this site for now (legal notice). For any question or request about your data: [contact address to come].

Two Android versions. VOKPIT is distributed through Google Play and, for beta testers only, outside Google Play, directly by its publisher. This policy covers both; when a feature exists in only one of them, it says so.

2. What stays on your phone

To work, VOKPIT reads or produces the following data. It stays on the device and is sent neither to the publisher nor to any third party, except as stated in each item and in the cases of §5.

• Voice and microphone. The microphone opens during a voice command, during an SOS alert countdown (to hear "cancel") and, if you turn on the wake word (off by default), continuously on your headset microphone while the app is on screen, never in the background. Understanding commands (rules and on-device AI) always happens on the phone, and the app keeps no recording. If you teach VOKPIT your wake word, it keeps a sequence of symbols derived from your pronunciation, never the sound. Transcription depends on the screen: on the Music screen, an embedded model does it offline; for the headset assistant, dictating a destination or a text and cancelling an SOS by voice, VOKPIT uses your phone's speech recognition service (usually Google's), see §5.
• Contacts. To call or text someone by name, and to choose your emergency contacts and tracking recipients. Only the name and number of the people you choose are kept by the app.
• Texts and notifications. With notification access, VOKPIT reads incoming texts aloud and announces calls. If you turn on the automatic reply (version outside Google Play), it reads the sender's number of an incoming text to reply to it. Message content is not kept and does not leave the phone.
• Calls. To announce the caller in your helmet and place a call by voice.
• Music. Tracks being played and commands sent to your music apps. Learned Spotify tracks: with notification access, VOKPIT remembers the title, artist and Spotify identifier of the songs Spotify plays on the phone and of its queue (2,000 at most), with how many times each one started playing, with no date or listening time, so it can start them again by voice and, between two tracks with the same name, prefer the one you play most. If you import the data file Spotify sends you on request, it is read on the phone (liked songs, playlists, listening history) and only those same tracks are kept from it, with their play counts; the dates of the history only serve to prefer recently played tracks and are not kept. In the settings (Music and voice), a switch stops the learning and a button erases everything. These tracks go neither to our servers, nor into sync, nor into Android backup; only the word list described in §5 reuses part of them.
• Sensors. Accelerometer, gyroscope and the phone's orientation (which may rely on the compass), for lean angle, G-force, crash detection and automatic ride detection. When crash detection opens an alert, the app keeps the 30 seconds of sensor readings around it (acceleration, rotation, tilt and speed, no position), marked "crash" or "false alarm" depending on whether you let it go or cancelled it, to fit detection to the way you ride: 50 alerts at most, on the phone, included in the Android backup. Proximity sensor, to turn the screen off when the phone is covered (pocket, tank bag) on the ride screen and the map, and during guidance.
• Bluetooth. To recognise your intercom, start ride mode when it connects, and tell a motorcycle ride from a car ride (type of connected device).
• Your data in the app. Ride log (rides and GPS tracks), reported hazards (gravel, slippery roads, animals, objects and accidents also go to other riders while their sharing stays on, §5), garage and maintenance log (plate and mileage included), favourites, tours, shortcuts, dictation corrections, settings.

Android backup. Depending on your Android settings, the system may back up part of the app's data to your Google account (device backup). Location histories, other people's data (emergency contacts, tracking recipients) and learned music (learned Spotify tracks) are excluded.

3. Your location, including in the background

VOKPIT uses the phone's precise location (GPS) for speed, lean angle, the map, guidance, the ride log, hazard alerts and the SOS alert. It is also used when the app is closed or the screen is off, in five cases, each shown by a permanent notification that lets you stop it:

• Automatic ride detection ("Detect my motorcycle rides by itself" setting, on by default in the version outside Google Play and off by default in the Google Play version, which you can turn off with one tap): the app watches the phone's movement and, when a trip starts, reads the GPS to record the ride in your log and advance your motorcycle's maintenance counter. It requires the "Allow all the time" permission; without it, it stays on standby. A trip recognised as a car trip is deleted, track included.
• Guidance you started, so the voice keeps going with the screen off.
• Recording a ride you started.
• Live tracking, if you opened it (§5).
• Crash detection (off by default): the last known position is used to estimate speed and to put your position in the SOS alert.

If you refuse notifications to VOKPIT, Android hides these permanent notifications: guidance, recording, live tracking and crash detection carry on, and show and stop in the app (and, since Android 13, in the active apps list of quick settings); automatic ride detection, on the other hand, stays on standby while its notification cannot be shown.

These positions stay on the phone. They only leave it for the uses of §5: rerouting during guidance, live tracking, SOS alert, hazards shared between riders (the area you are in during guidance, the position of a hazard you report), syncing the ride log if you tick it.

4. Your account

The app requires an account from first launch. It syncs your settings if you turn syncing on (§5), shares the hazards you report with other riders (§5) and, on Android, activates a code offered to beta testers. A subscription bought in Google Play or in the App Store is not linked to it: it stays tied to your Google Play or Apple account (§5). Two ways to sign in on Android; the iPhone adds Sign in with Apple (§13):

• With Google. Google gives us your Google account identifier (the same for every service you sign in to with Google) and your email address (kept only if Google has verified it). The sign-in token also carries your name and the address of your profile photo: our server does not keep them. Google knows that you sign in to VOKPIT, under its own privacy policy.
• With an email address and a password. We keep your email address and a hash of the password (salted PBKDF2-SHA256): the password itself is never kept. At sign-up and on a password change, the server checks that the password does not appear in a known breach by sending to the Have I Been Pwned service the first 5 characters of a SHA-1 hash of the password, never the password or your address. Verification and reset emails are sent by our email provider.

As soon as you sign in, your account is created on our server, which keeps a session for each signed-in phone: the device's pseudonymous identifier (§6) and the dates it was opened and last used. Signing in sends none of the app's data: syncing stays off until you turn it on. Hazards you report, however, go to other riders while their sharing stays on (§5). An inactive session expires after 180 days. An account that holds no activation code and that no phone has used for two years (no sign-in, no sync) is deleted: an email warns you 30 days before, with a link to keep it, and signing in to the app is enough too. An email account never opened in the app is deleted two years after its last sign-in, without a warning email, since we hold no plain address to write to.

5. What goes over the network

VOKPIT is not a fully offline app. Here is the complete list of its network exchanges. Connections are encrypted (HTTPS), except the audio stream of some web radios, which carries no data about you. Every connection also carries the phone's IP address and standard technical information (depending on the case, app version, phone model and Android version).

With our servers

• Routes (nav.vokpit.com). Computing a route sends your starting point (your position), stops and destination, with your route preferences (tolls, ferries, unpaved roads, bends). This applies to a "take me to…", a scenic tour, a roadbook, an imported GPX track, a point tapped on the map or a fuel station. Rerouting after leaving the route sends your position and direction of travel, including while riding. The server also returns the route's speed limits. Guidance itself is then computed on the phone. Routes are not kept.
• Maps (nav.vokpit.com). Until an offline map is installed, the base map is read online for the area on screen. The Maps screen reads the catalogue of available maps. An offline map cut on demand sends the area to cover: a disc centred on your position, or the bounds of a route.
• Vigilance zones (nav.vokpit.com, on by default): download of two public zone files, France and the other countries where the law allows it, at most once a month each. The same file for everyone: nothing says where you ride, nothing leaves your phone.
• Sights to see (nav.vokpit.com): download of a public file of places to visit (castles, passes, abbeys, from Wikidata), at most once a month, for the map and rides. Nothing leaves your phone.
• Updates (nav.vokpit.com), version outside Google Play only: at each launch, the app reads a public file giving the latest version. Nothing leaves your phone. The app never installs itself: an update downloads in your browser.
• Live tracking (nav.vokpit.com, off by default). During a share you opened, the phone sends your position, speed, altitude, position accuracy, heading, battery level and the positions travelled since the previous send; if guidance is running, the destination you asked for, the estimated arrival time and the remaining distance. About every twenty seconds while moving, less often when stopped. This data is tied to a random token, never to your identity or your device. Anyone holding the link can see it; the link only allows viewing. It stops working two hours after the last point (or as soon as you stop sharing) and the data is deleted within 24 hours.
• Account and activation codes (activation service hosted by Cloudflare). Sign-in, account creation, email verification and password reset; activating a code offered to beta testers (the code, the app version, the device's pseudonymous identifier; if the code requires an account and this phone is not yet registered to it, the app opens Google sign-in, even if you signed up with an email address, and sends the token of that sign-in: the code is then linked to that Google account); account deletion. A subscription bought in Google Play never goes through this service.
• Settings sync (same service, off by default, impossible without an account). If you turn it on, your settings and app data are copied to the server so you find them on another phone: home and work addresses, favourites, music shortcuts, garage and maintenance log, radio stations, tours, SOS settings except a personal emergency number, automatic text reply, the first name shown in the tracking text, intercom settings, language, dictation corrections. Your ride log and reported hazards contain positions: they are only copied if the matching box stays ticked. Other people's data (emergency contacts, tracking recipients, call tiles) only leaves with separate, explicit consent. Sync happens at launch, after a change, when you leave the app or on request, and never while riding. Your phone remains the reference: a failed sync never takes anything away.
• Hazards shared between riders (same service, on by default, impossible without an account, and nothing is sent or received before you accept, while stopped, the rules of article 18 of the terms; turned off on that notice or on the Road hazards screen). When you report gravel, a slippery road, an animal, an object on the road or an accident, the phone sends its type, its position (your position when you report it), your direction of travel and the time. Without network, sending is retried at the next read of nearby hazards, for an hour at most and while the app is running, then dropped. While the ride screen is shown or a route is open, guidance with the screen off included, the phone asks for nearby hazards by sending the area of about twenty kilometres you are in (a 0.2-degree cell), never your position: on entering a new area, and otherwise every ten minutes at most (two minutes after a failed exchange). When the app has just announced a hazard, your "still there" or "gone" is sent too. From the Road hazards screen, you can report another rider's hazard announced in the last 24 hours, and choose to stop seeing that rider's hazards: the hazard's identifier and that choice are then sent. Each exchange carries your account session and the device's pseudonymous identifier (§6), used to refuse anonymous sends and to limit abuse. The hazard is kept without your name, your email address or your account identifier, under a pseudonym specific to that hazard and an author fingerprint, the same for all your hazards, used so that a rider can stop seeing yours and to suspend an author reported by five different riders (90 days without sharing, automatically, with nobody reading the reports); other riders only see its type, position, direction and time, never the fingerprint nor who reported it. To answer a court order, the server also keeps for ONE YEAR, for each hazard you publish, your account reference, the hazard's identifier and type and the time, never your IP address, even after the account is deleted (§9, §12). The server also keeps, for your account, the list of your 200 latest reports, used only to erase them if you delete the account. Potholes and hazards without a type never leave, and the app reports no police checks. Received hazards stay in memory and are never written to the phone. Turning sharing off stops sending and receiving at once, but does not withdraw what you already shared: it expires (§9), or other riders remove it. These shared copies are separate from your synced reported hazards above: deleting a hazard from your list, with sharing on and a network, also withdraws its shared copy; otherwise it expires on its own.
• Listen together (same service, only on your action). To play the same web radio on the phones of a group riding together. The phone that opens the session sends the station it plays (its name and stream address) and whether it is playing, then the same at each change and, without a change, once every ten minutes. The service returns a random six-character code, which you give to the group, and a key that only this phone knows, to change or end the session. A phone that joins with this code asks about every thirty seconds which station is playing, then opens that station's stream itself (see "Web radio" below). Nothing else leaves: no position, no name, no account, no device identifier, and the service knows neither who listens nor how many. The audio never goes through our servers. Anyone holding the code can see the station and the playback state while the session lasts; the phone that opened it does not see who joined. A permanent notification shows it while it lasts, with a button to leave. The session becomes unreadable 45 minutes after the last send from the phone that opened it, 15 minutes after that phone ends it, and in any case 12 hours at most after it was opened.

With third-party services, directly from your phone

• Phone speech recognition: the speech recognition service chosen in Android (usually Google). It transcribes your voice for the headset assistant (the command said after the wake word, which is itself recognised on the phone), dictating a destination or a text, cancelling an SOS by voice, and the Music screen until the embedded model is installed. Depending on the phone, transcription happens on the device or on that service's servers; when the internet connection is missing or not verified, VOKPIT first asks it to transcribe on the device. To help it recognise proper names, VOKPIT passes it a word list: learned Spotify tracks with their artists, names and addresses of your favourites, hazard words. This processing is governed by the service provider's privacy policy.
• Address and fuel-station search: Photon (komoot GmbH, Germany, OpenStreetMap data). The text you type or dictate as an address or destination, with your last known position to rank results; the coordinates of a point you tap on the map; your position for the nearest fuel station, including when you ask for it by voice while riding.
• Phone geocoder: Android's address service (usually Google) first receives the coordinates of a point tapped on the map, and an address when Photon finds nothing.
• Weather: MET Norway (api.met.no, Norway). A position rounded to about 11 m when the ride screen or guidance opens (at most once every ten minutes), and one point about every 20 km along a route, a reroute or each loop proposed for a tour, to forecast rain, wind and fog. Never fetched on a timer.
• Spotify: VOKPIT exchanges nothing with Spotify and writes to no third-party account. "Play X on Spotify" hands the track to the Spotify app on the phone (see below), and "I like this song" asks it to like the current track through the command the app itself shows in Android's media panel. Connecting a Spotify account no longer exists since 7 October 2026: the sign-in tokens and the copy of the library it kept on the phone are erased at the first launch of this version.
• Tracks never played and artists: MusicBrainz and ListenBrainz (MetaBrainz Foundation, a non-profit, servers in Germany). When you ask by voice for a track this phone has never seen play in Spotify, or that it cannot recognise with certainty among those it knows, the text of the request (four wordings at most) goes to MetaBrainz to find the track and its Spotify identifier, riding included, followed by the MusicBrainz identifiers of the tracks found, to learn their Spotify identifier and play count. When you ask for an artist without a title ("play some Linkin Park"), the name as you said it goes to MusicBrainz to find the artist; if nothing is found, a second search adds at most three names of well-known artists that sound like it (taken from a public list built into the app, never from what you listen to); then come the MusicBrainz identifiers of the artists found, to learn their play count and the Spotify link of the one to be played. The same happens when a title said alone is also an artist's name ("play Nirvana"), to know which of the two to play. Nothing else: neither your identity, nor your position, nor what you listen to. MetaBrainz keeps the IP address and the request in its logs, under its own privacy policy. Setting "Look up tracks never played" in Music settings, on by default.
• Web radio: the server of the station you listen to, while it plays; the broadcaster's service for the current title (e.g. Radio France); when the Radio page opens, an availability check of each station in your list (at most once every ten minutes). Only the connection itself is visible to these servers. When you join a listen-together session, your phone opens the stream of the station chosen by the phone that opened it: a station from the list supplied with the app plays at the address your app knows; any other station, at the address the other phone sent (https only), without being added to your list.
• Hugging Face: download and update of the public speech-recognition model used by the Music screen, on Wi-Fi by default.
• Google Play, delivery of the speech model (Google Play version): the AI model that helps understand voice commands is not in the installed app; Google Play downloads it right after, like the rest of the app, under its own privacy policy. VOKPIT passes it nothing about you for this download.
• Google: the "Sign in with Google" window, if you use it.
• Google Play, for a subscription bought in the Google Play version. The Google Play purchase sheet takes the payment, and Google handles renewal, cancellation and refunds under its own privacy policy. Each time you return to the app, VOKPIT asks the phone's Play Store app which subscriptions are active, and acknowledges each paid purchase, as Google requires. The phone keeps the list of active modes and the date of the last answer, so that paid modes keep working for up to 30 days if Google Play does not answer. No purchase data is sent to our servers: the subscription stays tied to your Google Play account, never to your VOKPIT account. Google makes the app's orders available to the publisher in its developer console (including order number, subscription, price, date and country of purchase). We never receive your card details.

None of these requests send your address book, the content of your texts or an advertising identifier.

To other apps, on your request

Some commands hand over to another app on the phone, which then receives what you asked for: a general question to the phone's assistant or a Google search, a destination to Google Maps or Waze when VOKPIT's guidance is not available, a track or a search to the Spotify app (for a search, the words you dictated), a "like" to the music app that is playing, the Google Play subscriptions page (Google Play version), the code and link of a listen-together session to the app you choose to share them with, the page where Spotify sends you your data to your browser, and, through "Report a bug", an e-mail to the publisher prefilled with the phone model and the Android and VOKPIT versions to your e-mail app, which only leaves if you send it.

By text message, from your phone

Some messages leave from your phone, through your carrier, like any text: none of our servers sees them, and your contacts' numbers go to nobody but the carrier.

• SOS alert: when you trigger it, or when a crash is detected and you do not cancel within two minutes, a text with your position and a map link goes to the emergency contacts you chose. A text refused for lack of network is resent on its own as soon as the network returns, for at most one hour after the alert and while the app is running, marked "sent late" with the time of the alert; for an alert opened on screen (SOS button or detected crash), the alert screen lets you stop these resends, which an alert triggered by voice does not offer. If you set it up, the app calls the designated contact and opens the dialer on the emergency number: you place that call yourself, VOKPIT never dials an emergency number on your behalf.
• Live tracking link, sent to the recipients you chose.
• Arrival message (off by default): no coordinates and no link. When guidance reaches its destination, the message names it as displayed: what you typed or dictated, the address found for a point tapped on the map, the chosen fuel station (brand, street, town), the end point of a tour, or the name of a roadbook or imported GPX file. With no named destination (a loop, or the end of a ride detected by the sensors), if you stop near a pinned place (home, work, favourite), it gives that place's saved address; otherwise it only says you finished your ride.
• Dictated text, after read-back and confirmation, and automatic reply to incoming texts, if you turn it on (version outside Google Play).

6. Device identifier

To tie a licence to a phone and limit a code to three devices, VOKPIT computes a pseudonymous identifier: an irreversible hash, specific to VOKPIT, of the device's Android identifier. It is sent when activating a code, when opening an account session, on each sync and with each exchange of hazards shared between riders (§5). It cannot track you across other apps. VOKPIT does not use the advertising identifier.

7. Who your data is entrusted to

The third-party services of §5 (phone speech recognition and geocoder, komoot, MET Norway, MetaBrainz, web radios, Hugging Face, Google) receive directly from your phone what is described for each, under their own responsibility. Hazards you share are shown to other VOKPIT users passing nearby, with nothing that identifies you (§5). We neither sell nor rent any data. When data is processed outside the European Union, it is under the safeguards provided by the GDPR (European Commission standard contractual clauses or adequacy decision) that these providers include in their terms.

The providers that process your data on our behalf (Cloudflare, Clouvider, Resend) do so on our instructions and give it protection at least equal to the protection this policy describes. Google and Apple also act on their own behalf, under their own privacy policies.

8. Why, and on what basis

9. How long

10. Security

Exchanges with our servers are encrypted (HTTPS). Passwords are only kept as a salted hash. Session tokens are only kept server-side as a hash. The backup copy kept at Clouvider is encrypted before it leaves Cloudflare, and the key that opens it is on no server. The licence is verified on the phone by cryptographic signature, without a connection. Tracking links rely on random 128-bit tokens, separate from the secret that allows publishing. Likewise, the code of a listen-together session only lets you follow it: changing or ending it takes a random 128-bit key that only the phone that opened it holds, and that our server keeps only as a hash.

11. Your rights

You have the right to access, rectify, erase, restrict, object to and port your data, and to withdraw your consent at any time. Part of this is done directly in the app: turning a feature off, erasing your synced data, exporting a ride or a maintenance log, deleting your account. For the rest, write to [contact address to come]: we answer within one month. You may also lodge a complaint with the French data protection authority, the CNIL (www.cnil.fr), or the authority of your country.

12. Deleting your account

In the app, for any account: Settings › Store and license › Account › Delete my account on Android, Settings › Store and account › Account › Delete my account on iPhone; an email account confirms by typing its password again, and on iPhone an Apple or Google account confirms by signing in again with the same account. Without the app: follow www.vokpit.com/delete-account. Deletion erases your account, your email address, your sign-in identities, your password hash, your sessions, the synced copy of your settings and the hazards you shared with other riders (the 200 most recent; older ones expire on their own, §9). Your "still there" and "gone" on other riders' hazards stay until those hazards expire, under a pseudonym, without your account or address; only the account reference kept in the log of operations could still link them to it. The one-year line of each hazard you published also stays until its term (§9). What remains, for 3 years, is one line in the log of operations (§9): the date, the account reference, its activation codes and the sign-in type (Google, Apple, email), with no address and no Google or Apple identifier, so the deletion can be proven. A verification or reset link already sent erases itself within 24 hours. Backup copies keep them for 30 more days at most while copies run (§9), and are only used to rebuild the service after a failure. The activation codes described in §9 are kept for the stated period, because they keep the licence already activated on your phones working. Deleting the account stops no subscription. Cancel a Google Play subscription in Google Play (Payments & subscriptions › Subscriptions), or with the "Cancel or manage my subscription" button in the Store; cancel an App Store subscription in your Apple Account settings (Settings › [your name] › Subscriptions) or with the "Cancel or manage my subscription" button in the iPhone Store. For an account created with Sign in with Apple, deletion also asks Apple to revoke the authorization given to VOKPIT (§13).

13. On iPhone

The iPhone version of VOKPIT follows this policy, with the following differences.

• Sign in with Apple. Apple sends us an account identifier specific to VOKPIT and an email address, which may be an Apple relay address if you choose to hide yours. We do not ask for your name. When you delete your account, our server asks Apple to revoke the authorization given to VOKPIT, using the code that Apple's sheet hands to the app for this deletion. If the revocation fails, the app explains how to turn it off yourself in the iPhone settings.
• Sign in with Google. A Google window opens inside the app, with no Google library embedded. Google sends us your Google account identifier and your email address, as on Android (§4), but neither your name nor your photo: the app does not ask for them.
• Purchases. The subscription is bought in the App Store. Apple collects the payment and handles renewal, cancellation and refunds, under its own terms and privacy policy. The app asks Apple's purchase service, on the iPhone, which subscriptions of your Apple Account are active. No purchase data is sent to our servers, and your VOKPIT account holds no purchase. The iPhone keeps the list of active modes and the date of the last answer, so that paid modes keep working for up to 30 days if the App Store does not answer. Apple gives the publisher sales reports in App Store Connect. On iPhone there is no VOKPIT activation code and no licence: an offer code, if you are given one, is redeemed in the App Store.
• Sync. It works as on Android (§5), with the same families and the same separate consent for other people's data, off by default. Before sending, the iPhone reads its speed so that nothing is sent while riding: that reading stays on the iPhone.
• Hazards shared between riders. They work as on Android (§5): same account, same article 18 rules to accept while stopped before any exchange, same data sent, same "Report" and same choice to stop seeing a rider's hazards, on the Road hazards screen. One difference: the iPhone asks for nearby hazards (the area of about twenty kilometres, never your position) whenever it reads your location for VOKPIT, that is while the ride screen or the SOS screen is shown, or during a guidance, a ride recording or a live share, at most every ten minutes in the same area, and only if your subscription includes riding or guidance. Without them, your reports are sent, but the iPhone receives no hazards from other riders. Demo mode sends and receives nothing.
• Your voice does not leave the iPhone. Voice commands are recognized on the iPhone: by the recognition model the app downloads from Hugging Face (the same as on Android) or, until it is downloaded, by Apple's speech recognition in on-device mode. No sound and no word list is sent to a recognition service. Siri shortcuts go through Siri, under Apple's policy. The wake word only listens while the app is on screen.
• On-device artificial intelligence. As on Android, an on-device model helps understand a command the rules did not understand, on the iPhone, once you have accepted the terms of use, and never on the Music screen. It is not in the installed app: the App Store downloads it right after, like the rest of the app, under Apple's privacy policy, and again over Wi-Fi if the iPhone removed it to free up space. VOKPIT sends nothing about you for this download.
• Location. VOKPIT only asks for "While Using the App". Location goes on with the screen off only during a guidance, a ride recording or a live share you started, and iOS shows it in the status bar. Automatic ride detection does not exist on iPhone. Crash detection only works while VOKPIT is on screen or one of these activities is running.
• Addresses. There is no phone geocoder: a point tapped on the map is sent to Photon (komoot) only.
• Apple Maps. Without the mode that unlocks guidance, a destination (address, home, work, tapped point) opens in Apple Maps, and a fuel-station search opens there around your last position: Apple receives them, under its own privacy policy.
• Weather. Only along a route or a scenic tour, not when the ride screen opens.
• Messages and calls. The app sends no text message itself. For the SOS alert and the live tracking link, it opens the Messages app with the message ready, and you send it. A dictated text opens in Messages the same way, read back and ready: you send it. The call to your designated contact, after an SOS alert or a crash, opens in the Phone app, which asks you to confirm. The arrival message, reading incoming texts and the automatic reply do not exist on iPhone.
• Contacts. To choose a contact or a recipient, the iOS contact picker only hands VOKPIT the contact and number you pick. For dictated texts only, VOKPIT asks for access to your contacts the first time you dictate a name: names and numbers are used to recognise that name on the iPhone, and are neither stored nor sent. Without this access, everything else works.
• Device identifier. On iPhone, the pseudonymous identifier of §6 is an irreversible hash of the iOS vendor identifier (specific to the publisher's apps on that iPhone), never of the advertising identifier. It is sent when an account session opens and at each sync.
• iCloud backup. VOKPIT data follows the iPhone's iCloud backup, except data that holds a location history or other people's data, which is excluded: ride log, reported hazards, recent places and the coordinates of pinned places, emergency contacts, live tracking, call tiles, as well as the account, sync, purchases and Spotify data.
• Apple Music. You choose the music source in Settings, Music: Spotify by default, or Apple Music. Only if you choose Apple Music and allow it, VOKPIT reads on the iPhone, through Apple's MusicKit, the songs of your Apple Music library with their artists, play counts, last-played and added dates and ISRC code, to find the one you ask for by voice. This list stays in memory on the iPhone: it is neither written to storage nor sent to the publisher, and it is cleared when you change source. A voice correction of an Apple Music song (the phrase said and the song chosen) stays on the iPhone and is not synced. The music is played by Apple, inside VOKPIT, under Apple's terms and privacy policy; the Apple Music subscription is managed with Apple. VOKPIT does not search the Apple Music catalog.
• Spotify. The track index is only filled on iPhone from the Spotify data export you import, and it stays on the iPhone. "Play X" opens the track in the Spotify app; VOKPIT does not control Spotify and exchanges nothing with it. A track or an artist missing from that export is looked up at MusicBrainz and ListenBrainz as on Android (§5, "Tracks never played and artists"): only the text of the request is sent, never the export or what you listen to, and the list of well-known artists ships inside the app. Setting "Look up tracks never played" in the Music settings, on by default. When Apple Music is the chosen source, nothing goes to MetaBrainz unless you ask for a track "on Spotify".
• Listen together. The same transmissions as on Android (§5), on your action. No notification on iPhone: you leave it from its screen, and it carries on with the screen off only while the radio plays.
• Notifications. Local only (crash alert while the app is in the background); guidance shows on the Lock Screen and in the Dynamic Island. No remote notification.
• Updates. Through the App Store. The app does not check for updates itself.

14. Children

VOKPIT is meant for riders of motorised two-wheelers. It is not intended for children and knowingly collects no data about them.

15. Changes

This policy changes along with the app. Any significant change is published here with a new update date.

16. Contact

The publisher of VOKPIT: [contact address to come]