Skip to content
REVMAPPED
Menu

REVMAPPED / privacy

PRIVACY NOTICE

Who is responsible

Darren Bewley trading as REVMAPPED is the controller of personal information used to operate REVMAPPED. Contact: 50 Furness Avenue, St Helens, WA10 6QE, United Kingdom. Email privacy@revmapped.com for privacy and deletion requests, or support@revmapped.com for assistance. This notice covers the Android and iOS apps, www.revmapped.com, support correspondence and the private tester questionnaire. Version 24 September 2026.

Current beta

The current app beta is free. Separately offered website Founders pre-orders, when enabled, are optional purchases for future access. Questionnaire submissions remain disabled. Live emergency-contact SMS and voice alerts are enabled for beta, subject to your separate setup, opt-in, contact agreement and number verification.

Information you provide

Account information can include your email address, username, profile, account identifier and sign-in credentials. Passwords and verification codes are handled through the authentication service; never send them to support. Information you choose to add can include motorcycles and registration details, photos, notes, fuel and maintenance records, emergency-contact details, group/connection activity, shared posts, comments, reviews and reports. Only provide information about someone else where you have a proper reason to do so and have told them how it will be used.

Ride recording and precise location

When you start a recording, the app uses permitted GPS and motion inputs to record the route and estimate speed, distance, altitude, orientation, lean, acceleration, braking and related statistics. Background location lets a ride continue while another app is open or the screen is locked. Raw high-frequency sensor processing takes place on the phone; processed telemetry and precise coordinates can be included in saved rides. Granting a phone permission does not mean every feature shares that information, and does not amount to consent to unrelated purposes.

Local storage and cloud services

Ride recordings and app settings are stored on the phone. Cloud account/profile functions and features you use communicate with our backend. Choosing ride or garage backup uploads the relevant records and selected media, including precise ride coordinates. A private cloud backup is different from a masked share card. Some features need an account, internet access or a permission; if you decline these, the dependent feature cannot work. Cloud profiles, connected services and information deliberately sent to us are not local-only data.

Sharing and the limits of masking

You choose whether to publish content, connect with riders or share live group positions through the available controls. Recipients may copy or share what they receive. Endpoint masking reduces the detail shown near a ride’s start and finish; it does not anonymise a route or guarantee that a home, workplace or person cannot be identified. Repeated journeys, landmarks, photos and other details can reveal locations. Inspect every export before sharing. Account exports and selected external files may contain exact coordinates. Removing image metadata does not remove faces, number plates or identifying scenery.

Maps, route searches and weather

Mobile street maps load directly from OpenFreeMap, which receives your IP address and the requested map areas. Route searches, destinations and waypoints are processed through our location services and Geoapify. Requested weather uses location through WeatherAPI. Viewed map areas and query coordinates may reveal where you are interested in travelling. These requests are separate from publishing a ride. Route and weather information is not an assurance of safe or lawful access.

Live groups, assistance and emergency contacts

When enabled by your choices, group or assistance features disclose the relevant position, identity and activity to the permitted audience. Stop sharing using the feature controls; ending a ride, leaving a group and expiry rules also affect availability. Do not use the app to track someone without their knowledge. Live emergency-contact alerts are available during beta after separate setup, opt-in, contact agreement and number verification. An uncancelled alert sends precise latest or last-known coordinates and accuracy/time information independently of social masking through your selected SMS/voice channels. Twilio processes the recipient phone number and alert content. These alerts do not dispatch emergency services. You can turn detection off in Emergency contact settings.

Notifications and diagnostics

Notifications use an account-linked device token and relevant event identifiers through Supabase, Expo and Apple APNs or Google FCM when configured and permitted. Your notification choices and device settings affect delivery. We also process service requests, security events, error codes, delivery status and operational usage to operate, protect and troubleshoot the service. You can deliberately export or send diagnostic information; review files before sharing. The mobile code currently contains no advertising SDK or automatic user-event analytics integration. This does not mean our hosting, API or email providers keep no technical logs.

Private tester registration

The private tester registration page collects your name, email address, name shown on Facebook and whether you use Android, iPhone or both. We use these details to match you against the owner-selected tester list, verify your mailbox, communicate the selection decision and administer beta access and the free year of Pro. A shared group link does not grant access. Registration is reviewed by Darren; other testers cannot see your details. Verification links expire after 30 minutes. Unverified registrations are scheduled for removal after 7 days and declined registrations after 30 days. Approved registration details are kept through testing and free-year administration, then reviewed for deletion; account, purchase and legally required records are handled separately. Requests to correct or withdraw registration can be sent to support@revmapped.com. These service messages do not subscribe you to marketing. Founders checkout separately verifies your email before checking membership, to avoid duplicate purchases and public membership lookups.

Tester questionnaires and support

The private questionnaire uses a personal invitation and invited email address to control access. The form covers rider/phone profile, optional experience feedback and bug reports. If enabled, submitting sends your answers and email to REVMAPPED support through Resend; mailbox copies and delivery records are separate from the open browser form. We do not use a public list of invited emails. An invitation link is a secret: anyone who receives it and the matching email may be able to use it. Do not forward it. Unsent answers stay in the open page and may be lost when it reloads. Do not include passwords, payment information, medical details, precise home/work addresses or information about other people that is not needed.

Purposes and lawful bases

For UK GDPR purposes, we use information necessary to provide the account and features you request on the basis of performance of our contract with you or steps you request before it. We use necessary security, abuse-prevention, service-operation and support information for our legitimate interests in running a reliable, safe service and resolving problems, balanced against your rights. We use optional beta research responses for our legitimate interests in evaluating and improving the invited beta; you can decline optional questions and object to that processing. Where a feature or communication specifically relies on consent, we ask separately and you may withdraw it. We process information when needed to comply with a legal obligation. These bases do not authorise unrelated advertising, selling your location or collecting unnecessary information.

Your right to object

You may object to processing based on legitimate interests for reasons relating to your situation by emailing privacy@revmapped.com. We will stop unless applicable law permits continued processing on compelling grounds or for legal claims. If we ever use your information for direct marketing, you can object to that use at any time. Beta invitations, support replies and essential service messages are not permission for unrelated marketing.

Recipients and service providers

Information may be processed by Supabase for authentication, database, storage and application services; Vercel for website hosting and delivery; OpenFreeMap for mobile map display; Geoapify for route planning and place searches; WeatherAPI for requested weather; Resend for transactional email and configured questionnaire delivery; and our Namecheap Private Email service for support correspondence. Expo, Apple and Google provide configured notification/distribution services. Twilio processes opted-in SMS/voice emergency-contact alerts and contact verification during beta. Other riders and chosen recipients receive only what the relevant sharing flow makes available to them. Professional advisers or authorities may receive information where necessary and legally justified. Stripe processes separately authorised website payments, refunds and payment-risk checks. We receive order references, purchaser email, payment status and membership allocation; card details are entered on Stripe-hosted checkout rather than stored by REVMAPPED. Resend delivers order confirmations, release announcements and personal early-access invitations. A pre-order does not create an app account; account setup opens 24 hours before public release.

International processing

Providers and their support or subprocessors may process information in the United Kingdom, the EEA, the United States and other operating locations. A London database or European sending region does not guarantee that all processing stays there. UK law requires an appropriate basis for restricted transfers, such as an applicable adequacy decision or approved contractual safeguards. You can ask privacy@revmapped.com for the recipient locations and a copy or explanation of the safeguards relevant to your information, with confidential details removed where justified. Our provider-contract and transfer assessment is part of the release review; this notice is not a claim that choosing a hosting region completes it.

How long information is kept

Saved ride and garage records are retained for the account/features you use until you delete them or the account, subject to necessary legal, security and rights-protection exceptions. Local copies remain under your device controls. Operational cleanup currently removes expired live locations, nearby-presence entries after five minutes, assistance coordinates after closure/expiry, hazards seven days after expiry, API-action records after two days, completed push-queue entries after seven days, and stale push tokens and operational feature-usage records after ninety days. Unreferenced media becomes eligible for cleanup after seven days. Scheduled processing may not happen at the exact expiry instant. These periods do not describe independent provider logs or backups.

Support, invitations and retained exceptions

We retain support and questionnaire material only for as long as needed to manage the beta, investigate the issue, answer follow-up requests and meet applicable legal or record-keeping needs. Relevant factors include whether a case is open, whether a response is needed for an unresolved defect, and whether a specific legal claim or obligation requires preservation. Invitation access can be revoked independently of records already received. A limited record may remain to document security incidents, rights requests, moderation decisions or a valid purchase/Founder allocation. Deletion from an active system may precede expiry from restricted backup or processor copies. Ask us about the retention criteria or status for your particular records; no universal immediate-erasure promise is made.

Your rights and requests

Depending on the information and lawful basis, you may request access, correction, erasure, restriction, or a portable copy, object to relevant processing, and withdraw consent where it is used. These rights have legal conditions and exceptions. We may ask for proportionate information to verify your identity; do not send identity documents unless requested through an appropriate route. We normally respond within one month of receiving a valid request, with any legally permitted extension explained. Requests are normally free; we will explain if a lawful exception applies. You can complain to the Information Commissioner’s Office at ico.org.uk/make-a-complaint or 0303 123 1113. You do not have to complain to us first. Other mandatory rights and your local supervisory authority may apply where you live.

Deletion, security and changes

Cloud account deletion is available in the app’s Privacy & data controls; web requests can be made using /delete-account or privacy@revmapped.com. Logging out, uninstalling, deleting local data and deleting a cloud account are different actions. Export anything you want to keep first. Device security, access restrictions and encrypted network connections help protect information, but no app can guarantee perfect security; keep your phone and sign-in details secure. We do not use REVMAPPED to make solely automated decisions with legal or similarly significant effects about you. Material changes to this notice will be identified with a new version and brought to your attention appropriately before relevant new processing starts.