Privacy Policy

Effective date: October 17, 2026

Last updated: October 17, 2026

Routes is an app of E-Splice LLC (“E-Splice”, “we”, “us”), the company behind Dragy Moto Lab and Chainline. This policy explains what personal data Routes uses when you use the website at dragymotoroutes.e-splice.com, the Routes iPhone app and the Routes Android app (together, the “app”). It covers how the data is used, who receives it, how long it is kept, and how you can delete it. The iPhone and Android apps run the same app as the website, so everything below applies to them too, except where a section says otherwise.

If you sign in, you use your Dragy Moto Lab account. The Dragy Moto Lab Privacy Policy covers that account, payments and Chainline Pro. This policy covers what Routes adds on top.

1. Summary

Routes works without an account. Your garage, rides, ride plans, offline maps and settings are saved on your device, not on our servers.
Location is used only when you record or follow a ride, or tap “Use my location”, and only if you allow it. The iPhone and Android apps keep using location in the background only while a ride you started is recording. Location stays on your device unless you back up a ride to your account (section 2.4).
If you sign in with a Dragy Moto Lab account, we store your email, optional name, your synced garage and your Pro status with that account.
Maps come from our own map server; routing, place search and weather come from outside services (mainly Stadia Maps). Your device sends them the places or coordinates needed for each request (section 4).
Community is optional and for riders 18 and older. If you join, what you post, the groups and messages you’re in, reports, blocks and push tokens are stored on our Community servers on Cloudflare. Your public profile and Pro badge are off unless you turn them on. Shared routes have their first and last 300 m trimmed by default (section 2.8).
We don’t sell your personal data. We don’t show ads. Routes has no analytics, advertising or tracking code. The website’s sign-in forms use Google reCAPTCHA to block automated abuse (section 4).
You can delete your account at any time in the app (Account › Delete your account in the app), at dragymotolab.e-splice.com/delete-account/, or by email (section 9). You can erase the data on your device from the app.

2. Data we use

2.1 Data saved on your device

Routes saves these in your browser’s storage (local storage and IndexedDB), or in the app’s own storage on iPhone and Android:

Garage: your bikes (make, model, year, engine, gearing, tires and any notes), which bike is active, your rider weight if you enter it, and markers for bikes you deleted so sync can remove them on your other devices.
Rides: rides you record, including the GPS track (positions, and where your device provides them, elevation, time and speed), name, notes, the bike, and distance and time statistics. If ride telemetry is available (section 2.9), each track point also holds heading, GPS accuracy, lean angle and g-forces, and the ride holds its maxima and which sensor they came from.
Ride plans: routes you plan, including their stops and the line between them.
Recording checkpoint: while a ride is recording, its track so far is saved every few seconds, so the ride survives a crash, a closed tab or a dead battery. The checkpoint is removed when you finish or discard the ride.
Offline maps (Pro): map data for areas you choose to save, and the list of saved areas.
Settings: units, map and voice preferences, which kinds of places to show on the map, roads you saved or rode, your Discover location and up to 5 recent locations, the phone-mount calibration for each bike, and your sign-in status if you sign in (section 2.2).
Crash detection and SOS settings (section 2.9): your emergency contacts (name, phone number, call or text), your SOS message and any medical information you enter. These stay on your device and are used only to build an SOS message.
Sync records: which account this device last synced with, and a local copy of your garage if you chose “Use account garage only” when signing in to a different account.

This data is not sent to us, except your garage when you are signed in (section 2.2) and rides you back up (section 2.4). Clearing the site’s data in your browser, clearing the app’s storage, uninstalling the app, or using Erase Routes data on this device (on the Account and Delete account pages) deletes it. If iCloud or Android device backup is on, your phone may include the app’s data in your device backup with Apple or Google, under your Apple or Google account settings.

2.2 Your Dragy Moto Lab account

An account is optional. When you create one or sign in, Routes talks to the Dragy Moto Lab servers at dragymotolab.e-splice.com. This is the same account you use for Dragy Moto Lab and Chainline. We store:

Account details: your email address, your password (stored hashed, never in plain text), your name if you enter one, and an account ID.
Sign-in sessions: each sign-in creates a session. We keep only a hashed copy of each session token, plus the app type (for example “Routes for Android”), when it was created and when it expires. On the website the session is kept in your browser’s local storage. In the apps it is kept in the phone’s secure storage where available.
Garage sync: while you are signed in, your garage (section 2.1) is stored with your account so it is the same in Routes, Dragy Moto Lab and on your other devices. This includes when each item last changed. When you remove a bike, a small marker (the bike’s ID and the time) is kept for up to 90 days so your other devices remove it too.
Pro status: whether your account has Chainline Pro, where it comes from (website, App Store, Google Play or a trial), and when it renews or ends. Routes reads this to unlock Pro features.

The Dragy Moto Lab servers keep this data. The Dragy Moto Lab Privacy Policy covers it too.

2.3 Location

Routes uses your device’s precise location. It is optional. Routes uses it only for the features below, and only after you allow it in your browser, in iOS or in Android.

Recording a ride: while you record, Routes reads your position, elevation, speed and heading to draw the track and calculate distance and time.
Following a route and spoken cues: your position is used to show where you are on the line and to announce turns.
“Use my location”: adds where you are as a stop in a plan, or (in Discover) finds roads and viewpoints near you.
Crash detection and SOS (section 2.9): while you record or follow a route with crash detection on, your speed and position are checked on your device for a crash, and your last position goes into an SOS message.

Website: location is used only while the page is open and in the foreground. Browsers don’t give websites location in the background.

iPhone and Android apps: when you start recording, the app may ask to use location in the background, so the ride keeps recording while the screen is off or you switch apps. It only does this while a recording you started is running. Android shows a notification for as long as it runs, and iOS shows its location indicator. It stops when you stop or finish the ride. The apps never use location in the background at any other time and don’t track you when no ride is recording.

Where location goes: your position is processed on your device. Recorded tracks stay on your device unless you back them up (section 2.4). When you use “Use my location” in a plan, that position becomes a stop and is sent to the routing services with the rest of your stops (section 4). When you view a map, the map service learns which area you are looking at (section 4). We don’t send your live location to our servers.

You can turn location off at any time in your browser’s site settings, in iOS (Settings › Privacy & Security › Location Services) or in Android (Settings › Location › App location permissions). Routes still works for planning and browsing without it.

2.4 Ride backup (Pro)

Chainline Pro members who are signed in can back up recorded rides to their Dragy Moto Lab account and restore them on another device. When you back up a ride, we store:

the ride’s name, notes, start time, bike, the listed road it was on (if you picked one), the “public” or “private” label, and summary statistics (distance, duration, moving time, elevation gain and loss, average and top speed)
the GPS track, in compressed form: the coordinates of the route and, if your device recorded them, elevation, time and speed along the way
if the ride has telemetry (section 2.9), its maxima only (left and right lean, acceleration, braking and cornering g) and which sensor they came from. The lean and g readings along the track stay on your device.

A ride track is precise location history. It shows where you were and when. We use it only to keep your backup and restore it to your devices. We don’t publish it, sell it, use it for advertising or share it with other users. The “public” label in Routes is only a label, and nothing is made public.

Opting out: backup is optional. When it’s on, rides you finish are backed up automatically. You can turn off automatic backup in Routes (Rides › Ride backup) at any time. Turning it off stops new uploads but doesn’t delete existing backups.
Retention: backups are kept until you delete them or delete your account. There is no time limit, including after Pro ends. If you delete one, a small marker (the ride’s ID and the time) is kept for 90 days so your other devices know it was deleted, then removed.
Deletes win: once you delete a backup, an older copy still uploading from another device won’t bring it back. Only saving the ride again later restores it.
If Pro ends: you can still see, restore and delete your backed-up rides, with no time limit, but you can’t add or update backups.
Limits: up to 5,000 rides and 50 MB per account.
Deleting: delete a backup in Routes (Rides › Ride backup), or delete your account to remove all of them. Deleting a backup doesn’t delete the copy on your device.
Getting a copy: restore a ride to Routes and export it as GPX. You can also ask us for a copy of all your backups (section 10). Our servers don’t create GPX files.

2.5 Purchases

Routes doesn’t sell anything itself. Chainline Pro is sold by Dragy Moto Lab: on the website through Stripe or PayPal, and in apps through Google Play or the Apple App Store, under the Dragy Moto Lab Privacy Policy and Terms. Routes never receives your card or payment details. It only learns whether your account has Pro (section 2.2). The Routes iPhone and Android apps don’t show prices or buy buttons.

2.6 Messages you send us

If you email or call us, we receive your email address or phone number and whatever you tell us, and we use it to answer you.

2.7 Technical data

Like any website, the server hosting dragymotoroutes.e-splice.com receives your IP address, browser type and the pages and files you request. It keeps them in standard server logs for security and troubleshooting. The Dragy Moto Lab servers do the same when you sign in or sync. Routes itself doesn’t collect device identifiers, crash reports, usage statistics or advertising IDs.

2.8 Community

Community (forums, ride groups, chat and direct messages) is optional. You need a Dragy Moto Lab account, you must confirm you are 18 or older, and you must accept the Community Guidelines before you can use it. People under 18 can still use the rest of Routes. Community runs on our own servers on Cloudflare (community.e-splice.com, run by E-Splice). Your Community profile is kept with your Dragy Moto Lab account and is also covered by section 2.10 of the Dragy Moto Lab Privacy Policy.

Your profile

Always shown next to what you post: your username and display name.
Public profile, off by default. If you turn it on, other members can open your profile page and see your avatar, bio, home area (free text such as “Asheville, NC”, never coordinates) and your public threads and shared routes.
Garage showcase, off by default. You can show up to 5 bikes from your garage. Others see only the nickname, year, make, model and a note you add, never gearing, tires, maintenance, notes or rides.
Pro badge, off by default. Other members never see whether you have Pro unless you turn the badge on.
Never shown to other members: your email, account ID, plan or Pro status (unless you show the badge), garage details beyond the showcase, and rides.
Avatars are stored in Cloudflare R2. Routes shrinks the picture to 512×512 before upload, and the server re-encodes it, which strips photo metadata such as GPS. A moderator checks each avatar before others can see it.

What we store

All of this is stored on Cloudflare (Workers, D1, R2, Queues):

Forums: threads, replies, reactions and tags you post.
Shared routes: the route name, the line, and its distance, time, climb and twistiness.
Chat: messages in public channels, ride groups and direct messages (DMs), including route cards, “meet here” map points, replies, reactions and edits.
Membership: which groups and DMs you’re in, your role, mute settings, invites and join requests.
Safety records:
- reports you make, including a copy of the reported content (for a chat message, also the 5 messages before and after it, for context)
- blocks
- automatic filter flags
- the moderation log (who did what, when and why)
- notices sent to you
Push tokens: your device’s push token or browser push subscription, and its platform.
Your Community record: your username, display name, avatar link, Pro status, role, when you joined and were last active, when you accepted the Guidelines and confirmed your age, and any timeout, suspension or ban.

Who can see what

Signed-in members only. Forums and public channels are visible to signed-in Community members. They aren’t public web pages, and search engines don’t see them.
Private ride groups and DMs are visible only to their members. Moderators also see a message in them if someone reports it or our automatic filter flags it.
Not end-to-end encrypted. Chat and DMs are encrypted in transit (HTTPS and secure WebSockets) but not end to end, so our servers can read them.
Group owners and admins can remove messages and members in their own group.
Blocking hides the other person’s content from you and yours from them, stops DMs and invites both ways, and keeps them out of groups you own.

Location in Community

Shared routes: the first and last 300 m of a shared route are trimmed off by default, so your start and end (often your home) aren’t shown. You can turn the trim off each time you share. A shared route is visible to whoever can see the post or message it’s in.
“Meet here” points: these are locations you choose to share, visible to whoever can see the message.
Event meeting points (when events are available): the exact pin is shown only to riders who RSVP, the organiser and moderators. Everyone else sees only the general area.
Community never receives your live location.

Moderation and reports

Every post, message, route name and profile text goes through an automatic word filter. Content the filter catches is blocked, held for a moderator, or allowed and flagged.
You can report any post, message, profile or group. Reports go to our moderators, who aim to review them within 24 hours. They can hide or remove content, warn, time out, suspend or ban an account, and the person gets a notice with the reason.
Credible threats and child-safety content are removed and reported to the authorities as the law requires.

Push notifications

If you turn notifications on, the iPhone and Android apps use Google Firebase Cloud Messaging (FCM), which delivers to iPhones through Apple Push Notification service. The website uses web push through your browser’s push service (for example Google, Mozilla or Apple).
A notification carries the sender, the group and a short preview. DM previews are hidden (“New message”) unless you turn previews on.
Notifications never include your location.
Push tokens are deleted when you turn notifications off, when they stop working, or when you delete your account.

How long we keep it

Your content stays until you delete it or your account. When you delete your own message, thread or reply, its text, shared route and reactions are erased from our servers right away. Only an empty “deleted” placeholder (with no content) stays, so conversations still make sense. If someone has an open report about it, the copy in that report is kept until a moderator closes the report, then erased.
Content a moderator or group admin removes is hidden from members but kept, so it can be reviewed or restored, until the group or thread is deleted or the author deletes their account.
Deleted groups: a group’s chat history is erased 30 days after the group is deleted, so a mistaken delete can be undone.
Reports: reports stay until they’re handled, then are deleted 90 days after they’re closed.
Moderation log: kept for 2 years.
When you delete your account, Community removes, within minutes:
- your messages, threads, replies, reactions and shared routes
- your memberships, invites, blocks, reports you filed, notices, push tokens, avatar and Community record

A thread that others replied to stays, with your opening post replaced by a “removed” note. Your DMs are closed and their history erased after 30 days. Groups you own pass to another member, or are deleted if no one is left. Copies of your content in reports about you are cleared. The moderation log keeps your account ID and the actions taken for up to 2 years. Server backups that still contain your data roll off within about 30 days.

2.9 Ride telemetry, crash detection and SOS

Telemetry sensors. Routes can show and record lean angle and g-forces. In order of preference, it uses a Dragy, RaceBox or RaceChrono device you connect over Bluetooth, your phone’s motion sensors (only after you tap to allow them; iPhone asks for permission), or your GPS speed and heading alone. The readings are processed on your device and saved with the ride (section 2.1). Bluetooth and motion data are never sent to us or to any service. Your browser or phone handles the Bluetooth pairing; Routes only receives the device’s name and its readings.

Crash detection is off until you turn it on. While it is on and you record or follow a route, Routes checks your phone’s motion sensors and GPS speed on your device for a hard impact or sudden stop followed by no movement. Nothing is sent while it watches. If it detects a crash, or you hold the SOS button, it sounds an alarm and counts down so you can cancel. If you don’t cancel:

Emergency contacts: Routes prepares a text with your message, the time, your name if you are signed in, your medical information if you added it, and (if you allow it) a link to your last position. Your phone’s Messages or Phone app opens and you or someone with you sends it. Routes can’t send texts by itself today, and we don’t receive your contacts.
Group ride (Community, section 2.8): if you are in a group ride and turned on “Alert my group ride”, the alert (type, your position and its accuracy, the time, and the impact, speed, lean and battery readings) is sent to our Community servers, which notify the riders in that group.
Location link: the link (dragymotoroutes.e-splice.com/sos) carries your position in the part of the address after “#”, which browsers don’t send to our server. Anyone you send it to can see that position. It is a snapshot, not live tracking.

Crash detection is not an emergency service. It works only while the app is open and running, your phone is on and has signal, and it can miss crashes or raise false alarms. Call 911 (or your local emergency number) when you can.

2.10 Send to Dragy Moto Lab (Pro)

If you are signed in with Chainline Pro, you can send a ride to Dragy Moto Lab to view it there. Routes sends the ride (name, start time, bike, statistics, the GPS track and, if it has them, the lean and g readings along it) to your Dragy Moto Lab account at dragymotolab.e-splice.com, where the Dragy Moto Lab Privacy Policy covers it. You can also export the ride as files and share them yourself. Nothing is sent unless you tap Send.

3. Cookies and local storage

Routes doesn’t set cookies. It uses your browser’s local storage and IndexedDB (or the app’s storage) to save the data in section 2.1 and your sign-in session. These are needed for the app to work and are not used for tracking.

On the website’s sign-in, create-account and password-reset screens, Google reCAPTCHA may set its own cookie (such as _GRECAPTCHA) and use similar storage for security. The Dragy Moto Lab website uses its own cookies when you visit it, for example when you reset your password or delete your account there. Its policy describes them.

4. Third-party services

Routes contacts these services directly from your device when you use the related feature. Each one receives your IP address, your browser or app’s standard request details, and the data listed here. Each handles it under its own privacy policy. None of them receives your name, email or account.

Map tiles: our own map server (tiles.e-splice.com, run by E-Splice on Cloudflare, with map data from Protomaps and OpenStreetMap). It receives the map area and zoom level you are viewing or saving offline. The map’s fonts and icons are served from dragymotoroutes.e-splice.com. Routes doesn’t contact the OpenStreetMap tile servers.
Aerial and Satellite map views: Stadia Maps (tiles.stadiamaps.com, satellite imagery © CNES, Airbus DS and PlanetObserver), with USGS The National Map (basemap.nationalmap.gov, U.S. Geological Survey) as the fallback. Only when you pick Aerial or Satellite, they receive the map area and zoom level you are viewing. The imagery isn’t saved for offline use.
Routing: Stadia Maps (api.stadiamaps.com, Stadia Maps, Inc.) plans Twisty and Direct routes. Route requests send the coordinates of your stops (start, waypoints, destination, including “My location” if you added it) and your route options (for example how much to avoid highways, tolls, ferries or unpaved roads). If Stadia Maps fails or is busy, the same request goes to a free fallback, one at a time and only as far as needed:
- FOSSGIS Valhalla (valhalla1.openstreetmap.de, run by FOSSGIS e.V.), for Twisty routes
- OSRM (router.project-osrm.org), for Twisty and Direct routes
- BRouter (brouter.de) plans off-road lines. Off-road routes go only to BRouter.
Place search: Stadia Maps, with Photon (photon.komoot.io, by komoot) as the fallback when Stadia Maps fails. They receive the text you type in search, the approximate centre of the map you are looking at (to rank nearby places first), and, when you drop a pin, its coordinates, to look up a place name.
Nearby roads and viewpoints (Discover): Overpass API (overpass-api.de, run by FOSSGIS e.V., with OpenStreetMap data). Only when you pick a Discover location, it receives the area around that place (a box of map coordinates). Results are kept on your device for up to 7 days.
Places on the map (fuel, food, hospitals and more) come from our own map server (above) and don’t contact any other service. Toll sections come with the route from the routing service.
Weather and elevation: Open-Meteo (api.open-meteo.com). It receives the coordinates of the first stop of a plan or road for the current weather, and points sampled along a line to work out its climb.
Google reCAPTCHA (v3): used only on the website’s sign-in, create-account and password-reset screens, to tell people from automated abuse. Its script loads only on those screens. Google receives your IP address, browser and device details, cookies, and how you interact with the page, and returns a score that is sent with your request to Dragy Moto Lab. It is not used in the iPhone or Android apps. Use of reCAPTCHA is subject to Google’s Privacy Policy and Terms of Service.
Community (only if you use it, section 2.8): our Community servers on Cloudflare (community.e-splice.com, run by E-Splice on Cloudflare Workers with D1, R2 and Queues). They receive and store what you post and send in Community, your group memberships, reports, blocks and push tokens.
Push notifications (Community, only if you turn them on): Google Firebase Cloud Messaging (FCM) in the iPhone and Android apps, which uses Apple Push Notification service on iPhone. On the website, your browser’s own web push service (for example Google, Mozilla or Apple) is used. They receive your device’s push token and the notification text (section 2.8).
Dragy Moto Lab (dragymotolab.e-splice.com, also E-Splice): accounts, garage sync, Pro status, ride backup and password reset, as described in section 2.
Payments: handled by Dragy Moto Lab through Stripe, PayPal, Google Play and Apple (section 2.5), never by Routes.

Map data: Protomaps © OpenStreetMap contributors (openstreetmap.org/copyright). Routing & search © Stadia Maps. Full credits are on the About page. Links to other websites (for example Dragy Moto Lab) open those sites, and their own policies apply. When you use Share on a ride, the text goes to the app or contact you choose, and GPX export saves a file on your device for you to use as you like.

5. How we use data

To provide Routes: save your data, plan and record rides, sync your garage, back up rides, and unlock the Pro features your account includes. The legal basis, where one applies, is performance of our contract with you.
To keep the service and your account secure and prevent abuse, for example sign-in rate limits and session revocation (legitimate interests).
To answer your messages (contract or legitimate interests).
To meet legal obligations.

We don’t use your data for advertising. We don’t build profiles, and we don’t make automated decisions that have legal or similarly significant effects on you.

We don’t sell or rent personal data, and we don’t share it for cross-context behavioral advertising. Data goes only to:

Dragy Moto Lab, which runs your account (also E-Splice).
Other Community members, only what you post in Community and what your profile settings show (section 2.8). Moderators see reported and flagged content.
Hosting providers for dragymotoroutes.e-splice.com, dragymotolab.e-splice.com and Community (Cloudflare), which store the site, the account database, server logs and backups.
The services in section 4, which your device contacts directly when you use those features.
Authorities, when the law requires it, or to protect our rights, our users or the public.
A successor, if the business is sold or merged, under this policy.

7. Security

All traffic between the app and our servers uses HTTPS, which is encrypted in transit. Passwords and session tokens are stored only as hashes on our servers. Short-lived access tokens are kept only in the app’s memory. Sessions end when you sign out, change or reset your password, or delete your account, and you can sign out on every device from the Account page. Data on your device is protected by your device’s own security, so use a screen lock. No system is completely secure, but we work to protect your data.

8. How long we keep data

Data on your device: until you delete it (section 2.1).
Account details and synced garage: until you delete them or your account. Markers for deleted bikes are removed after 90 days.
Ride backups: until you delete them or your account, with no time limit (also after Pro ends). Markers for deleted rides are removed after 90 days.
Sign-in sessions: access tokens expire after 1 hour. Sessions expire 60 days after last use, or sooner when you sign out, change your password or delete your account.
Server logs and backups: only as long as needed to keep the service secure, fix problems and meet legal obligations. Backups are overwritten on a rolling basis; after you delete your account, backups that still contain it are purged within about 30 days.
Community: see section 2.8. In short: until you delete it or your account. Deleted groups are erased after 30 days, closed reports after 90 days, and the moderation log after 2 years.
Orders and payments: as described in the Dragy Moto Lab Privacy Policy.
Third-party services: under their own policies.

9. Delete your account and data

You can delete your account from the website, the iPhone app or the Android app. Deleting it permanently removes your Dragy Moto Lab account (used by Routes, Dragy Moto Lab and Chainline), including your email, name, password, synced garage, maintenance log, ride backups, Community profile, posts and messages (section 2.8), and every sign-in session. It also cancels any Chainline Pro subscription bought on the website. There are three ways:

In the app: while signed in, go to Account › Delete your account in the app, or open dragymotoroutes.e-splice.com/app/delete-account/. Type DELETE, enter your password and confirm. Your account is deleted right away and you are signed out on every device. Afterwards Routes offers to erase the data saved on your device too.
On the website: go to dragymotolab.e-splice.com/delete-account/, sign in and confirm.
Ask us: email support@e-splice.com from the address on your account with the subject “Delete my Routes account”. The Delete account page can prefill this email for you. We will delete the account and confirm by email, usually within 7 days and always within 30 days.

Server backups are kept for up to about 30 days after deletion, then purged as they rotate out.

If you subscribed through Google Play or the App Store, cancel the subscription there too, because deleting your account doesn’t cancel store subscriptions. When you delete in the app, Routes tells you if a store subscription is still set to renew and shows these steps:

Google Play: Profile › Payments & subscriptions › Subscriptions
iPhone: Settings › your name › Subscriptions

Order amounts and dates are kept without your personal details, as described in the Dragy Moto Lab Privacy Policy.

Data saved only on your device isn’t on our servers. To delete it, use Erase Routes data on this device (on the Account and Delete account pages), clear the site’s data, or uninstall the app. To remove just ride backups, delete them in Routes. To remove just your synced garage, delete the bikes while signed in.

10. Your rights

Wherever you live, you can:

Access and export: see your garage, rides and plans in the app and export rides and plans as GPX files. You can also ask us for a copy of the account data we hold, in a machine-readable format: your account details, garage, maintenance log, ride backups (ride details and the compressed GPS tracks), and your Community profile, posts and messages.
Correct: edit your name and garage in the app. You can ask us to correct anything else.
Delete: delete individual items, your device data or your whole account (section 9).
Withdraw consent: turn off location (section 2.3), turn off ride backup, or sign out at any time.
Object or restrict: object to or ask us to restrict some processing.

California residents (CCPA/CPRA) have the right to know what personal information we collect, use and disclose, and to access, correct and delete it. We don’t sell or share personal information for cross-context behavioral advertising, and we don’t use sensitive personal information (such as precise location) for anything other than providing the features you ask for. We won’t discriminate against you for using your rights. You can use an authorized agent, and we may need to verify your request, usually by email from the address on your account.

If you are in the EU, UK or a similar region (GDPR), you also have the right to data portability. Where we rely on consent (location), you can withdraw it at any time. You can also complain to your local data protection authority.

To use any of these rights, email support@e-splice.com or call (601) 487-8979. We respond within the time the law requires, normally 30 days (45 days for California requests).

11. Children

Routes is meant for adult riders and is not directed to children. You must be at least 18 (or the age of majority where you live) to create a Dragy Moto Lab account, and Community is only for riders 18 and older (section 2.8). We don’t knowingly collect personal data from children under 13 (or the minimum age in your country). If you believe a child has given us personal data, email support@e-splice.com and we will delete it.

12. International users

We are based in the United States. Our servers and the services in section 4 may process data in the United States, the European Union and other countries. Where required, we rely on appropriate safeguards for these transfers. By using Routes from outside the United States, you understand that your data may be processed there.

13. Changes to this policy

We will post any changes on this page and update the effective date. If the changes are significant, we will tell you in the app, or by email if you have an account, before they take effect.

14. Contact

E-Splice LLC
P.O. Box 180662
Richland, MS 39218
Email: support@e-splice.com
Phone: (601) 487-8979
Website: dragymotoroutes.e-splice.com