Last updated September 27, 2026
PEV Ride Computer is provided by Neuralis, LLC. This policy explains the Android app's data practices and the public PEV website. Questions and privacy requests can be sent to support@neuralisai.com.
The app is currently in testing. The group features described below are optional. Public website contributor accounts and uploads are not available yet; this policy does not describe a live community account service.
Personal recording and local information
Your personal ride library, vehicle configurations and settings are stored on your device. Solo recording does not require an account. The app has no Neuralis ride cloud, advertising or embedded analytics service. Neuralis does not automatically receive your ride history.
Location and available phone sensors support the live map, personal recording, ride statistics, local analysis and optional safety functions. A recorded ride can include precise coordinates, timestamps, speed, distance, elevation and related observations. The app also stores names and notes you enter, vehicle specifications, battery entries, trip counters, saved setups, analysis choices and display settings.
Recording can continue with the screen locked or another app visible. A recording notification identifies the running service. Pause does not stop all location acquisition. Group participation can use and share location independently of personal recording. The finish sheet lets you choose saving your recording, leaving the group, or both. Saving alone leaves group sharing active; leaving alone leaves a personal recording running. Hosts must explicitly choose to end the group for everyone. Review the result if either operation needs attention.
Information leaves the device through the optional functions and choices explained below.
Optional group rides and Tailscale
Group setup uses your own Tailscale account through an external browser sign-in. Tailscale provides connection coordination and may relay encrypted peer traffic. The app does not introduce a Neuralis-operated group server. Tailscale handles its account and network service under its own privacy policy.
After admission to a group, participants receive current rider names and markers, positions with accuracy and freshness information, speed, phone battery and participation status. They also receive the group's planned route, rally points and notes, named responses and attendance, SOS/all-clear information, optional SOS messages you choose to send or edit, and any shared Spotify Jam invitation. SOS messages can appear in group alerts and notifications. Pending join requests do not receive or contribute rider locations before host admission.
For supported rally attendance, the host evaluates locations already shared with the group to estimate arrival and departure. Riders can also confirm or undo their own arrival. The group receives these named attendance states, and the host can receive arrival notifications. This does not add a location permission, external geofence service or third-party place lookup. Attendance belongs to the current rally and group; a new or moved rally resets it, and leaving or removal clears that rider's attendance.
Group members receive a current roster and the latest shared state. This version does not save other members' ride tracks, a group ride recording or a multi-rider replay. Your own safety history can retain the linkage and outcome of a group alert.
Incoming group alerts can repeat until acknowledged. Silencing or dismissing an alert stores a limited private acknowledgement on your phone; it does not send a response to the group. That acknowledgement record contains event identifiers and state, not message text, locations or rider names. Choosing I'm coming or On my way also submits a shared response. An edited SOS message can alert someone who only silenced or dismissed its previous version again. Editing the message updates the same group incident and does not send emergency-contact SMS.
Leaving stops your phone's group sharing. If the connection is unavailable, other members may continue to see your last known state until their session updates or ends. They may also retain screenshots or other copies they make. Leaving does not send an all-clear or recall information already shared.
When a host publishes a previous personal ride as a planned route, the group receives a separate copy of its route geometry and name. That copy excludes the original ride's samples with timestamps, battery estimates and event history. Route geometry still reveals where the route goes, including its endpoints. Deleting the source ride does not retract the published copy.
Group identity, keys and invitation information are kept in app-private storage and excluded from portable app backups. Removing a saved friend in PEV Ride Computer is not the same as revoking access through Tailscale. Manage provider account and network permissions with Tailscale.
Optional Ride safety and SMS
If you configure Ride safety, the app stores the rider name, contact names and phone numbers you enter, your confirmation that contacts agreed to receive messages, and local incident and message history. It does not request your address book, read your SMS inbox or read replies.
Recent detection checks keep limited local explanations and numeric evidence, such as phone placement, impact strength and duration, rotation and prior speed. These check records do not contain raw sensor streams, coordinates or contact details and are not automatically sent to Neuralis.
With your setup choices and SMS permission, your phone sends messages through your mobile carrier to selected contacts. Adding a contact sends an introduction. A manual emergency-contact alert or enabled possible-incident countdown can request a help message. You can also choose an all-clear update.
Texts may include your rider and vehicle names, alert time, last known coordinates and their age or accuracy, a Google Maps link and phone battery level. An all-clear refers to the earlier alert location. Message content and available send or delivery results are retained locally.
SMS and group alerts have separate recipients and results. A manual Group SOS goes to the admitted group, without sending emergency-contact SMS. A manual emergency-contact alert uses SMS. An automatic possible-incident alert can use both channels when its requirements are met. Emergency-contact names and phone numbers are not sent to group peers.
SMS is not end-to-end encrypted. Carriers and recipients handle messages under their own practices. Opening a map link connects the recipient to Google. Removing a contact or deleting app data cannot recall a message already sent.
Map downloads
When you check or download an offline region, the app connects over HTTPS to Geofabrik at download.geofabrik.de
. Geofabrik receives your IP address, the requested region file and ordinary request information, including an app identifier. The app does not attach your recorded routes, live coordinates, contacts or ride notes to these requests. Searching the region list happens locally.
Downloaded maps are stored on your device for map display and replay rendering. Map data comes from OpenStreetMap contributors. See Geofabrik's privacy statement and OpenStreetMap attribution and licensing.
Replay photos and story edits
You can give a replay its own title, review or add stops, name them, choose events, attach up to 12 photos with captions and route positions, select a replay range and choose Smooth Stops pacing. These edits are stored privately on your phone for future exports. Suggested stops are derived from your recording; optional nearby place names are read from installed offline map packs without an online place-name request.
Selecting a shorter replay range changes the video's route and section statistics. It does not delete or trim the original recording, remove attached photos or erase approved events outside the range. Smooth Stops changes replay pacing, not the underlying ride. A full backup retains the original ride and attached photos even when the current replay omits them.
You select photos through Android's photo picker. The app reads a selected photo's available capture time and time-zone offset to suggest placement, then saves an optimized private JPEG copy without the original image metadata. You can correct its position manually. Your original photo is not changed. The app does not request broad photo-library access for this feature or automatically upload selected photos to Neuralis.
Excluding a photo from a replay keeps its private copy and edits for later use. Removing it deletes that app copy. Titles, captions, chosen locations and the visible contents of photos can still identify people or places even when original image metadata has been removed.
Music and Spotify
You choose local music and import files through Android's file picker. Replay music is processed on your phone.
Spotify Jam is a separate external-link handoff. A shared Jam invitation is visible to the group; opening it takes you to Spotify. PEV Ride Computer does not stream, synchronize or record Spotify audio, and Spotify audio is not included in exported ride videos. Spotify handles its service under its own privacy policy.
Exports, sharing and backups
You choose the receiving app or destination when saving or sharing a ride, vehicle configuration, video or backup. These files may expose routes, locations, names, notes, included replay photos and captions, and other details. The current app does not automatically trim sensitive route endpoints.
A full personal app backup includes rides, vehicle and setup history, settings, retained safety contacts and message history, and saved replay titles, stop edits, photo copies, event choices, replay ranges and Smooth Stops settings. Photos still attached to a ride are included even when excluded from its replay or outside the selected range. Backup ZIP files are not password protected by the app. Group account/friend setup, authentication keys and group session data are excluded. Downloaded maps, exported videos and imported music are not included. Photo copies are optimized versions, not backups of your full original photo library.
The app disables standard Android cloud backup. A backup you create using Backup & restore is initiated by you. If you choose a cloud drive or another service as the destination, that service receives the file and applies its own practices. Android permissions and provider account access are not restored from a portable backup.
Neuralis cannot control copies held by receiving services, carriers or other people. Review files before sharing and keep backups private.
The public website
The PEV website provides product information, help and downloadable reference material. It is hosted using Duda. Opening a page or downloading a file sends ordinary connection information, such as your IP address, browser information and the requested resource, to the hosting services that deliver it. Website requests are separate from the ride library stored in the app.
The site's typography uses Google Fonts. Your browser requests font files from Google's servers, which receive your IP address and ordinary request information. See Google's privacy policy. Videos are delivered as website media files; the pages do not embed a YouTube or Vimeo player.
Browsing the site does not create a PEV account. Community contributor accounts and uploads are not open. If a contribution service is introduced, its sign-up and submission notices will explain the information requested, what becomes public and the choices available before you participate.
Following a link to Google Play, Tailscale, Spotify or another external site connects you to that provider. Its own privacy practices apply there.
Purchases and support
Google Play handles store purchases and payment details. The app does not ask for payment-card details.
If you email support, Neuralis receives your email address and the information you choose to include. We use correspondence to answer your request, investigate problems and meet applicable obligations, and retain it only as needed for those purposes. You do not need to send a complete ride or backup for an initial request. Avoid including other people's contact details, private invitations or exact routes unless needed to resolve the issue.
Retention, deletion and security
Personal rides, vehicle setups and settings remain until you remove them, replace them through a restore, clear app storage or uninstall. Temporary files and some older incident entries may be cleared during normal use. Deleting a Garage vehicle preserves historical vehicle information in saved rides. Removing a safety contact does not erase earlier message records. Restoring a backup keeps a local recovery copy of the data from before the latest restore.
Deleting a saved ride also removes its replay title and stop edits and its private photo copies. If attachment cleanup cannot finish, the app reports the problem. Removing app copies does not delete original photos, exported videos, backups or copies held elsewhere. Excluding a photo is not deletion. Replacing data through restore or clearing app storage can also remove private replay files; a backup or the recovery copy from a previous restore may retain earlier photos and edits.
Android's app storage protections help restrict access by other apps. Exported backups do not have a separate app password or app-level encryption. No storage or transmission method guarantees complete security.
See Data and deletion for practical removal steps and support-information requests. Neuralis cannot remotely erase data that exists only on your device, in a provider's account or with recipients. You can request access, correction or deletion of personal information you provided to Neuralis; applicable rights depend on where you live. We do not sell your personal information or use it for targeted advertising.
Changes and contact
We may update this policy as the app or website changes. The date above identifies this version. Material changes to sensitive-data use will be explained in the relevant product when appropriate.
Neuralis, LLC. — support@neuralisai.com