Privacy Policy

Effective date: September 20, 2026 · TheDigicar LLC

The short version

DragDuro is built to know as little about you as possible. The route viewer, checkpoints, E85 map, and print tools all run in your browser — your GPS position is processed on your device and never sent to or stored on our servers.

We don't store your location, we don't run ads, and we don't sell data. We don't store your IP address either, with one narrow exception: when you request an emailed sign-in code we keep a scrambled (keyed-hash) form of your network address for about 10 minutes, to limit how many codes one network address can request. Its removal after that is best-effort — our database deletes expired records on its own schedule — and our database backups can hold it for up to 35 days (Sections 3 and 9).

If you sign in, here's what actually lands on your profile: your display name and an optional contact phone — plus any map pins you apply for. We do not store your email address on your profile. Instead, so that one email inbox maps to only one DragDuro account, we store a one-way keyed hash of it (never the address itself) on a separate identity record, deleted when your account is deleted; your literal address is kept only where a carve-out requires it: organization/promoter staff records; our audit log of promoter and admin actions, which records the email of the person who acted and, when the action concerns someone else, that person's email too (adding or removing organization staff, creating an organization for its owner, leaving an organization, or placing, lifting or upgrading a restriction on an account by email); and restrictions — if an account is restricted for abuse, the restriction keeps a keyed hash of its address, and a restriction placed by email address also keeps that address and a name, all of which survive account deletion so deleting and re-creating an account can't dodge a ban. See Sections 3, 4 and 9. There are exactly two exceptions to "no location", and both are things you have to deliberately do: flagging yourself as a racer in need (SOS) attaches your position to that flag so other racers can find you, and posting a road report (hazard, police, road condition) attaches the position you're reporting about so other racers know where it is. Both are deleted when the flag or report is cleared.

That's the plain-English gist. The full policy below is what's binding.

1.Who we are & what this covers

This Privacy Policy describes how TheDigicar LLC ("DragDuro," "we," "us") collects, uses, and shares information when you use the DragDuro websites and web applications at dragduro.com, including the route viewer, route maker, E85 station map, print tools, accounts, map pins, and promoter tools (the "Service"). It should be read together with our Terms of Service.

2.What we deliberately do not collect

By design, we do not:

Store your location. Your GPS position is read and processed entirely on your device to snap you to the route line and auto-check checkpoints. It is not transmitted to or retained by our servers. (Two narrow exceptions, both deliberate actions you take: active SOS flags and road reports — see Section 5.)
Store your IP address. Our analytics keeps only a one-way (irreversible) hash of it — see Section 6 — and the only other copy is the short-lived keyed hash kept when you request an emailed sign-in code (Section 3).
Track you across the web. No advertising trackers, no ad networks, no social media pixels, no cross-site profiling.
Sell or rent your personal information. To anyone, for any purpose. We also do not "share" personal information for cross-context behavioral advertising.
Email you for marketing. We send no newsletters and no marketing email, and we don't track whether you open or click any email we send. If you sign in with an emailed one-time code, your address is used purely to deliver that code — and, if you add email sign-in to an account that already exists, one confirmation that it was added. Those emails go out through our transactional email provider, Resend. That's it.

3.What we collect and why

Most of the Service works without an account and without giving us any personal information. If you choose to sign in or use certain features, here is what we collect:

Information	Source	Why we have it
Email address and basic Google account identifier	Google Sign-In (OAuth), when you sign in that way	To create and identify your account. We do not receive your Google password. Not stored on your profile — see below.
A one-way keyed hash of your email address (never the address itself, on your profile)	Computed from whichever address you sign in with, Google or email code	So one email inbox maps to only one DragDuro account, whichever way you sign in. Deleted when your account is deleted.
A scrambled (one-way keyed hash) form of your network address, kept for about 10 minutes (removal is best-effort; backups hold it up to 35 days)	Automatic, only when requesting an emailed sign-in code	To limit how many sign-in codes one network address can request in a short window.
Display name	You	Shown to other racers in the Service.
Contact phone (optional)	You	Shown to signed-in users only — e.g., so racers can reach you if you flag an SOS.
Organization memberships	You / your organization	To associate you with events or groups within the Service.
Map pin applications (business name, type, phone, website, hours, business location)	You	To review and, if approved, display the pin on route maps. Pin details are business information shown publicly on the map.
SOS flag (status, contact info, GPS position at the time of the flag)	You, when you report yourself as a racer in need	Shown to signed-in users so someone can help you. Deleted when the SOS is cleared. See Section 5.
Routes and checkpoints you create or publish	You (route maker / promoter tools)	To provide the route to you and, if published, to other users.
Anonymous usage counts (one-way IP hash, city-level region)	Automatic — see Section 6	To count unique visitors and understand where the Service is used, without identifying anyone.

We collect no other categories of personal information. We do not collect precise geolocation (outside an active SOS or a road report you post — see Section 5), biometric data, health data, or payment data (the Service is currently free).

4.Signing in

You can sign in with Google, or with an emailed one-time code — both grant the same account features.

Google. Sign-in uses Google OAuth. When you sign in this way, Google shares your email address and basic profile identifier with us; we use these solely to create and identify your account. Your use of Google Sign-In is also governed by Google's Privacy Policy. We do not receive or store your Google password, contacts, or other Google account data.

Emailed one-time code. Type your email address and we send a 6-digit code, valid briefly, through our transactional email provider Resend. We use the address purely to deliver that code (and, if you later add email sign-in to an account you already have, one confirmation that it was added) — no marketing, no newsletters, and Resend's own open/click tracking is off for these emails. Your address is never stored on your profile; we keep only a one-way keyed hash of it (Section 3), so that one email inbox — with common variations like +tags and, for Gmail, dots, folded together — maps to exactly one DragDuro account no matter which method you use to sign in. An emailed-code sign-in stays valid for up to 12 hours at a time and renews itself while you use the Service; signing out or deleting your account stops it renewing, but a sign-in already issued keeps working until its 12 hours are up.

5.SOS and road reports: the two location exceptions

Everywhere else in the Service, your GPS position stays on your device. Two features are exceptions, and both require you to deliberately tap something — neither happens in the background.

Racer in need (SOS)

If you flag yourself as a racer in need, your device's GPS position at that time is attached to the SOS flag so other signed-in users can see where you are and come help. This is the entire point of the feature, so it cannot work without it.

The position is transient: it exists only as part of the active SOS flag and is deleted when the SOS is cleared (by you, or when your account is deleted).
Your SOS flag — including your display name, any contact info on your profile, and your flagged position — is visible to signed-in users of the Service, and to event promoters via their console.
We do not keep a history of SOS positions and do not use them for any other purpose.

Road reports (hazard, police, road condition)

On a promoter's event you can post a report warning other racers about something on the road. When you do, the position you're reporting about is attached to the report — rounded to roughly 50 metres — along with the type and any note you type. Without a position a report tells nobody anything, so this too is the point of the feature.

A report is anonymous to other racers: your name is not shown on it, and no other driver is told who posted it.
A report is public — anyone using the Service on that event can see it, signed in or not, and it may appear on the event's big-screen display at the venue.
Reports are transient: one expires 30 minutes after it was last confirmed, and the position and your note are deleted as soon as it expires, is cleared, or you remove it.
We keep no history of report content or positions. We do keep simple counts on your account (how many reports you posted, how many were cleared by other racers) so promoters can act on abuse; those counts are deleted with your account.
Which report types exist on an event is the promoter's setting, and reports are not available at all on our unaffiliated demo routes.

6.Analytics: how we count visitors without tracking you

We use a small custom analytics system, not a third-party tracking service. When you visit:

Your IP address is run through a one-way cryptographic hash to produce an anonymous identifier used to count unique visitors. The hash cannot be reversed to recover your IP, and the raw IP address is not stored.
Our content delivery network (Amazon CloudFront) provides a city-level location name (e.g., "Tulsa"), which we save as coarse, aggregate geography. No precise location, no street, no coordinates.

That's it — no analytics cookies, no fingerprinting, no third-party analytics scripts. Like most web infrastructure, our hosting and CDN providers (Amazon Web Services) process IP addresses transiently in order to deliver the site and maintain standard operational logs; we do not use those to identify users.

7.Cookies & local storage

We use cookies and browser storage only for the Service to function — chiefly to keep you signed in and to remember on-device preferences and route progress. Route progress, checkpoint state, and similar viewer data live in your browser's storage on your device, not on our servers. We set no advertising or third-party analytics cookies. If you block cookies/storage, the Service still works, but sign-in and saved progress will not.

8.How your information is shared

We share personal information only as follows:

With other users, as the feature requires. Your display name appears to other racers. Your contact phone is visible to signed-in users only. Approved map pins (business info) are shown publicly on the map. Active SOS flags are visible to signed-in users and to promoters. Routes you publish are visible to users of that route.
With service providers. Our infrastructure runs on Amazon Web Services in the United States — data is stored in Amazon DynamoDB and delivered via Amazon CloudFront. Google provides sign-in. These providers process data only to provide their services to us.
Third-party hand-offs you initiate. If you tap through to Google Maps for navigation, or to an external website (e.g., a vendor's site or the DOE fuel-station data source), you leave the Service and those parties' privacy policies apply. We don't send them your profile data.
Legal and safety. We may disclose information if required by law or legal process, or as reasonably necessary to protect the rights, safety, or property of users, the public, or the Service.
Business transfers. If TheDigicar LLC is involved in a merger, acquisition, or sale of assets, user information may transfer as part of that transaction, subject to this policy's commitments.

We never sell personal information, and we share nothing with advertisers — there are no advertisers.

9.Data retention & deleting your account

Account data (display name, phone, org memberships, and a keyed hash of your email — never the address itself) is kept while your account exists.
SOS positions are deleted when the SOS is cleared.
Map pins are kept while displayed; declined applications may be deleted after review.
Anonymous analytics counts contain no personal information and may be kept indefinitely.
Restrictions survive account deletion. If an account is restricted for abuse, the restriction record keeps a one-way keyed hash of its email address; a restriction placed by email address also keeps that address as it was entered and a display name. These are kept even after the account is deleted, so the same inbox can't dodge the restriction by deleting and re-creating an account.
Audit log. Actions taken by promoters and DragDuro admins are logged with the acting person's email address — and, where the action concerns someone else, with that person's email address too: the staff member added to or removed from an organization, the owner an organization was created for, the member who left an organization, and an account whose restriction by email was placed, lifted or upgraded. The log is kept when accounts are deleted, including the account of anyone named in it.
Sign-in rate-limit records (a keyed hash of your network address, and one of your email address with a count of recent codes and wrong guesses) are kept for about 10 minutes and about 25 hours respectively. Their removal is best-effort — our database deletes expired records on its own schedule — and backups can hold them for up to 35 days.

You can delete your account at any time from the account page ("Danger zone"). Deletion removes your profile, contact info, pins, sign-in methods, and any active SOS. You may first need to leave any organizations you belong to. Residual copies may persist in encrypted database backups for up to 35 days before being purged. If you signed in with an emailed code, a sign-in issued before the deletion keeps working until its 12 hours are up; anything it creates in that window (a map pin, a report, a profile) is not removed by the deletion that preceded it — sign out on every device before deleting if that matters to you, or ask us to remove it. Published routes are event materials and may remain in the Service after account deletion.

10.Security

We use reasonable technical and organizational measures to protect your information, including transport encryption (HTTPS), managed AWS infrastructure, and minimal data collection — the best protection being that we simply don't hold most of the data a breach could expose. No system is perfectly secure, so we cannot guarantee absolute security. If we learn of a breach affecting your personal information, we will notify you as required by law (note: since we never email users, any such notice will be posted prominently in the Service and/or sent to your account email as a one-time legal notice).

11.Your rights & choices

Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of your personal information, and to not be discriminated against for exercising those rights. Because we collect so little, most of this is self-service:

Access/correct: your profile is viewable and editable on the account page.
Delete: use "Delete my account" on the account page, or email us.
Opt out of sale/sharing: nothing to opt out of — we don't sell or share personal information for advertising.
Location: deny the browser location permission and the Service still works; you just won't get position snapping or auto-check. The SOS feature requires location to function.

To exercise any right, email dragduroapp@gmail.com. We will verify requests using your account email and respond within the time required by applicable law. Authorized agents may submit requests with proof of authorization.

12.Children

The Service is intended for users 18 and older and is not directed to children under 13 (or the higher age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will delete it.

13.Users outside the United States

The Service is operated from the United States and data is stored on AWS infrastructure in the United States. If you access the Service from elsewhere, you understand that your information will be transferred to, stored, and processed in the United States, where privacy laws may differ from those of your jurisdiction.

14.Changes to this policy

We may update this Privacy Policy from time to time. The current version, with its effective date, will always be posted at this page. For material changes we will provide prominent notice within the Service. Your continued use of the Service after an updated policy takes effect constitutes acceptance.

15.Contact

Questions or requests about privacy:

TheDigicar LLC
Email: dragduroapp@gmail.com (subject: "Privacy")