Legal

Privacy

Information you provide

The marketing site does not run advertising or intentionally use behavioral tracking cookies. The DirtLore app may collect account details, rider-profile information, bike records, setup sheets, maintenance entries, ride notes, track selections, and media that you choose to provide.

If you choose to email DirtLore, we receive the address and information you send so we can respond.

Your data snapshot

While signed in, you can open Account > Data & privacy and download a JSON data snapshot. It combines a bounded snapshot of available DirtLore cloud records with records on that device that are exactly attributable to the signed-in account. Guest records and records belonging to another account are not included.

The snapshot is intended to make your data portable and understandable, but it is not an unlimited archive. Sections have size limits, and the file identifies sections that were truncated. It may include media metadata, but it does not include image, video, or other binary media files. Security credentials, connected-provider tokens, and another person's private information are also excluded.

Community track photos

When you choose a track photo, the app first creates a smaller JPEG copy and excludes the original filename and ordinary embedded EXIF/GPS metadata. That browser-prepared file is uploaded to private incoming storage. DirtLore independently decodes and re-encodes it into a new safety-checked derivative at a separate private review location. The incoming upload is queued for prompt deletion, and only the safety-checked derivative can enter the moderator queue.

While review is pending, the safety-checked derivative, submitted credit, caption, dimensions, and submission time are visible only to you and authorized DirtLore moderators through short-lived access links. If approved, the derivative, credit, caption, and submission date become visible in the public track gallery. Rejected or removed photo files are queued for deletion. A submission that remains pending for 90 days becomes eligible for deletion when cleanup runs.

Signed-in riders can privately report an approved photo. DirtLore stores the report reason, optional details, reporter, photo, time, and moderation result so authorized moderators can investigate abuse and document a decision. Reports do not automatically remove a photo and are not shown in the public gallery.

Rider profile photos and covers

If you add a rider profile photo or cover, the app first creates a bounded JPEG and excludes the original filename and ordinary embedded EXIF/GPS metadata. That copy is uploaded to a private, opaque incoming location. DirtLore then independently decodes, focal-crops, strips metadata from, and re-encodes it into a separate trusted JPEG: 768 by 768 pixels for a profile photo or 1600 by 900 pixels for a cover.

During this first phase, rider profile photos and covers are available only to the signed-in owner through access links that expire after five minutes; they are not added to the public rider-profile response. The incoming copy is queued for prompt deletion after preparation. The active trusted image and its focal point, dimensions, content hash, and processing record remain while you keep that image. Replacing or removing it queues its bytes for deletion and removes its retired metadata once deletion is confirmed. Completed operational cleanup entries, including opaque object paths, become eligible for scheduled purge after 30 days.

Your JSON data snapshot includes rider-photo metadata and focal points, but not Storage paths, access links, or image bytes. Permanent account deletion freezes new rider-photo uploads and removes known incoming and trusted profile images before the account is deleted.

Private Bike Studio photos

If you add a bike photo to Bike Studio, the app creates a bounded JPEG without the original filename or ordinary embedded EXIF/GPS metadata and uploads that copy to a private, opaque incoming location. DirtLore independently decodes, strips metadata from, and re-encodes the complete composition into a trusted private JPEG called Original. Scene edits use that Original as their source and do not overwrite it or generate replacement bike details. The images are not published or added to a public Bike Passport.

Automatic background removal is optional. In the current app, choosing Create my photo runs the cutout model on your device. The first use downloads approximately 200 MB of public model files from Hugging Face and its delivery network. Those files may be cached for reuse; the download provider receives ordinary connection information, but DirtLore does not send it your photo, mask, account details, or private image link. The cutout worker keeps photo data in temporary memory and stops after completion or cancellation. DirtLore does not train models on your Bike Studio photos or send them to an outside inference service in this on-device flow.

The app applies the resulting mask to the saved Original and previews your bike against the background you choose. Saving uploads the mask and rendered scene to DirtLore's private Supabase storage, where they are safety-checked and associated with your photo project. The model removes background pixels; it does not generate replacement bike details. You can keep the Original instead or refine the edges by hand. Reusable scene backgrounds may be AI-generated, but selecting one does not send your bike photo to an image-generation service.

Older supported app versions may offer a separate Photoroom option if it is configured. That option identifies Photoroom and requires explicit consent before sending the metadata-stripped Original for a foreground mask. The current on-device flow does not silently fall back to Photoroom or another outside inference service.

Only the signed-in current custodian can request the Original through an access link that expires after five minutes. The incoming copy is queued for prompt deletion after preparation. The trusted Original and its dimensions and processing record remain while that custodian keeps it. Replacing or removing it queues the bytes for deletion. A custody transfer automatically retires the private Original and does not give it to the next custodian.

Cutout masks, saved scene images, placement and brush-correction recipes, processing status, and automatic-cutout consent records are stored privately with the photo project. You can choose the Original again, select a saved composition, or discard compositions. Failed and discarded outputs are queued for deletion. Replacing or removing the Original, transferring the bike, or deleting the account also retires related cutouts and compositions. Short-lived processing leases prevent a late result from restoring a retired image.

Your JSON data snapshot includes Bike Studio project, edit, recipe, and consent metadata, but not Storage paths, access links, content hashes, provider receipts, or image bytes. Permanent account deletion freezes new Bike Studio work and removes known incoming, Original, mask, and scene images before the account is deleted.

Large brush recipes have a separate snapshot limit, with any truncation identified in the download. Short-lived processing counts help prevent abuse and limit legacy paid cutout usage; replacing a photo does not reset those counts. Account deletion removes their account association, while recent unlinked counts remain briefly to protect the service-wide processing limit. Cached public model files contain no rider data and can be removed by clearing this site's browser storage.

Ride files and connected devices

On Android, Ride Mode records precise phone GPS location, time, accuracy and speed after you choose Start Ride. Recording uses a foreground service and may continue with the screen off until you finish, reach the recording limit, or the operating system stops it. Memory Saving Mode omits GPS points below 5 mph. Optional read-only Stark connectivity can add available bike speed, motor RPM, battery level and health, voltage, temperature and mode measurements. We do not include the bike's Bluetooth address or vehicle identifier in uploaded recordings. These measurements are experimental and depend on firmware.

Phone recordings are stored in DirtLore's private storage on the recording device, then uploaded to your account through Supabase when DirtLore is open and online. They remain private and can be viewed on another device signed in to the same account. Cloudflare delivers the application; MapTiler supplies requested map areas as described below. Ride Mode does not send these measurements to an AI or advertising service. You can export an individual recording with its GPS and bike measurements, edit its optional ride details, or delete it. Account deletion removes cloud recordings and attempts to clear the account's recordings on the current device; it cannot remotely erase another phone's local copies. Revoking location permission prevents further GPS recording.

You may choose to import an activity file or connect a supported training provider. A ride import can include session identifiers, device and sport information, timestamps, duration, distance, calories, timestamped GPS routes and altitude, manual and automatic laps, pauses, heart rate and other available sensor samples, statistics, zones, training load, recovery and benefit reports, and related session metadata. DirtLore preserves the original Polar session responses and normalized private records so it can process available data without discarding its source. Provider values with unspecified units are not presented as standardized speed, power, or cadence by guessing. Uploaded FIT bytes are parsed for the review and are not retained by default.

Connecting Polar starts an import of the previous 90 calendar days. While the connection remains enabled, DirtLore periodically checks Polar Flow for workouts, including when the app is closed; you can also request a sync in the app. A completed Polar workout is saved as a durable private ride and can be opened without first choosing a bike, venue, or lap source. DirtLore may provisionally suggest one currently owned bike or a uniquely matched catalog venue when the available evidence supports it; optional confirmation controls the precise ride-day and session association. When route quality supports it, DirtLore can privately estimate a repeated loop, laps, and sectors from GPS. Ambiguous recordings remain without invented laps. The imported source and private GPS-derived results are retained with the ride, and DirtLore-calculated values remain labeled separately from Polar data.

A Polar connection requests the permissions devices:read, sports:read, and training_sessions:read to import workouts and interpret their device and sport information. Supported workout details may include session-associated test results, comments, physical information, strength-training results, and hill splits when Polar supplies them. DirtLore does not request separate sleep, daily-activity, test-library, route-library, or profile permissions for this feature. Polar remains responsible for Polar Flow and its own handling of your information.

GPS routes and heart-rate information are private account data by default. DirtLore does not publish a rider's location or connected activity merely because it was imported.

If you separately enable Include route preview when sharing a recorded ride card, your accepted friends can see a sampled GPS path showing where you rode. For a grouped track day, the thumbnail represents the latest shared moto; it does not reveal private motos. This option is off by default, including on older shares. You can turn it off in the ride's sharing controls or make the ride private to stop future access. Removing or blocking a friend also stops their future access. Original activity files, heart rate, setups and notes are not included in these previews.

Garmin Connect

Garmin connectivity is available for early testing. We ask for your authorization before connecting your Garmin account or receiving its activity data.

With your permission, DirtLore associates Garmin activities with your identifiable DirtLore account and maintains a private ride history. Available information may include Garmin user and activity identifiers, device and sport details, activity files, timestamps, GPS coordinates, altitude, duration, distance, speed, laps, heart-rate samples, and related activity statistics. Availability depends on your device, recording and permissions. Access uses the Activity API, without separate daily-health, sleep or women's-health access, and without historical backfill.

We use this information to display your rides and maps, calculate clearly labeled GPS-based lap estimates where recording quality permits, summarize available heart-rate zones, prevent duplicate imports, and associate rides with the bikes and tracks you choose. These calculations are not official race timing or medical advice. Garmin imports are private by default. Sharing a ride card with Friends requires your separate action. If you enable public profile statistics, saved Garmin rides may contribute to those summaries. Garmin GPS routes stay private unless you separately enable Include route preview for a shared ride card as described above. Heart-rate traces, setups and notes stay private.

The service providers are Supabase for backend processing, authentication, database and private file storage; Cloudflare for application hosting, delivery and security, including connection callback requests and incoming Garmin activity deliveries; and MapTiler for map and satellite imagery. MapTiler receives map-area or tile requests and ordinary connection information, which can reveal the area being viewed; it does not need your Garmin activity file, heart-rate samples or account credentials. Providers may use infrastructure subprocessors to deliver their services. We do not send Garmin activity records to a separate analytics or advertising service. Proton processes support emails, including any activity information you choose to include in a message to us.

We do not sell Garmin data or use it for behavioral advertising. Service providers process information to deliver their services to DirtLore. Garmin data and information derived from it are not used to train, evaluate or improve AI models, or submitted to AI assistants or AI analysis services. DirtLore's separate bike-photo background-removal feature does not require Garmin activity data.

You can withdraw Garmin sharing permission in your Garmin Connect account. DirtLore also provides a disconnect control that requests removal of its Garmin registration and stops future imports. If authorization has already expired, you may need to remove DirtLore from Garmin Connect settings as well. Disconnection alone will not erase previously imported rides. Garmin records are included in DirtLore's account export and deletion workflows. The per-ride Garmin export includes the original received activity data; the instant account snapshot provides a bounded summary. Unprocessed delivery data is removed after eight days, and temporary connection attempts expire after ten minutes and are purged daily. You may request access, correction, export, restriction or deletion by emailing support@dirtloremx.com; we may verify account ownership before acting. Corrections to original device recordings may need to be made in Garmin Connect, while DirtLore ride labels and associations can be corrected separately. Garmin data will be kept while needed for your private ride history, unless you request deletion or applicable obligations require otherwise.

We will update this notice before introducing additional Garmin uses or processors and obtain any required consent. Garmin separately controls information in Garmin Connect under its own privacy notice: https://www.garmin.com/privacy/connect.

How information is used

We use this information to provide Bike Passports and durable private ride records, display routes and lap reviews, produce labeled GPS-derived estimates, suggest a bike or venue when the available evidence supports it, associate a ride with the bike and track you confirm, prevent duplicate imports, secure accounts, troubleshoot the service, and comply with applicable obligations.

DirtLore practice-lap estimates are not official race timing, navigation, or safety information.

Hosting information

Our hosting and security providers may process ordinary technical request information such as IP address, browser type, requested page, and timestamps to deliver and protect the website. Their handling of that information is governed by their own policies and applicable law.

Sale and advertising

DirtLore does not sell personal information and does not use connected activity, precise location, or health information for behaviorally targeted advertising.

Connections, retention, and deletion

You can disconnect a supported provider to delete DirtLore's stored connection tokens and stop future imports. Disconnecting does not automatically erase activities already stored in DirtLore. Completed Polar workouts saved as private rides, together with their private GPS-derived results, are not deleted after 30 days merely because optional bike, venue, or lap-source confirmation has not occurred. Temporary or incomplete import state may be cleaned up when it is no longer needed. Imported activities and correspondence are retained only while reasonably needed for the service, security, legal obligations, or a request you make.

You can permanently delete the signed-in account from Account > Data & privacy. Account deletion removes profile information, rider profile photos and covers, private Bike Studio photos, rides and activity imports, social activity, connected-service credentials, and known private uploads. It also removes records on the current device that are exactly attributable to that account. Guest records and records for other accounts on the device are left alone.

To preserve bike and transaction integrity, DirtLore may retain bike history, custody and transfer records, purchases, and archived photographer drops and assets under a private, non-authenticatable “Deleted rider” record. Identifying profile fields and attributable free-form text are removed from those retained records. A one-way hash of a former username is reserved for 90 days to help prevent immediate impersonation, then becomes eligible for the next scheduled cleanup.

Account deletion cannot reach local records stored on another device. You must clear the account's DirtLore data on each other device where it was used. For individual deletion requests or help with an inaccessible account, follow the instructions on our Delete My Data page.

Changes

We may update this policy as DirtLore develops. The effective date at the top will change when material revisions are published.

Contact

Questions about privacy can be sent to support@dirtloremx.com.