RoadPulse privacy policy

Effective 27 October 2026. Updated 9 November 2026. RoadPulse.dev (Randy Galbraith) provides RoadPulse. This policy describes the Android app, its account services and the iOS preview. The full-feature Google Play closed-test candidate includes optional automatic trips, Google navigation and community features. Its advertising and billing SDKs are excluded; it makes no ad requests or purchases. Features require their stated sign-in, permissions and separate sharing choices. Existing accounts keep their earlier sharing choices; an update does not itself enable them.

Google sign-in

Google sign-in requests only your basic identity, email address and profile information through the openid, email and profile permissions. RoadPulse uses this information to authenticate you and associate your RoadPulse account with your private cloud data. It does not request access to your Gmail messages, Google Drive files or contacts. Google passwords are entered with Google, not collected by RoadPulse.

Driving and profile data

When you record a trip, the app uses the phone's location and motion sensors to estimate speed and save trip information on the phone. Saved trips can contain precise route coordinates, times, speed and distance. Your profile can include a display name, selected photo, country, vehicles and route color.

Optional automatic trips and navigation

Automatic trips starts off. If you enable it and grant Android physical activity and precise background location permissions, RoadPulse detects vehicle travel and records location even when the app is closed or the screen is off. Activity signals and fresh GPS confirm travel; detection can miss or delay a trip and cannot distinguish a driver from a passenger. Turn it off in Automatic trips or its notification. Manual recording and navigation remain available without this optional background permission.

When you choose Google destination search or navigation, Google receives search inputs, relevant location or search-area coordinates, and navigation interactions. Its Navigation and Places SDKs also process IP addresses, app/device metadata, SDK identifiers and crash diagnostics to provide and improve Google services. These SDKs have their own processing even when RoadPulse usage analytics is off. Location is used for driving features, not supplied by RoadPulse for ad targeting. Saved private address-book entries and business/personal trip classifications sync with your account when you choose the associated cloud features.

Optional road reports

Sharing a road report requires a separate deliberate action and the displayed consent. A shared report can reveal the selected location, category, time and details to other RoadPulse users; review it before submitting. Reports can be withdrawn and moderated. Reading community reports and offline spoken warnings have separate opt-in controls. A private sample preview is not a published report. These features are supplemental and can be incomplete or inaccurate.

Private cloud copies

When you back up a trip manually, or enable automatic backups while signed in, RoadPulse uploads the completed trip's original data and route to your private RoadPulse account. Profile changes are also saved to that account. Cloud copies are used for backup, restore and your chosen ranking totals. Private navigation recaps can include the original ETA, actual guidance time and arrival outcome, linked to the exact backed-up trip. With ranking participation on, your account’s aggregate time saved and qualifying arrival count can appear on the time-saved leaderboard; individual recaps, addresses and routes stay private. Automatic backups can be turned off in Cloud copies; turning them off does not delete copies already stored. New trip revisions keep earlier copies rather than replacing them.

Optional public rankings

Rankings participation starts off. If you opt in, other signed-in RoadPulse users can see your chosen display name, distance and trip totals, shared territory counts and aggregate time-saved totals for the selected period, and your selected country and optional city label. City and country scopes group participants by their chosen profile location; they do not verify where a trip happened. Your speeds, precise route coordinates, email, vehicles and profile photo are not published by these rankings. You can withdraw from rankings in your profile settings.

Optional territory and clubs

Territory sharing is a separate choice and starts off. Enabling rankings alone does not publish territory. After enabling territory, you can deliberately publish selected completed cloud-backed trips. A separate automatic coarse-tile setting can publish eligible newly completed trips after their private backup is verified. Automatic coarse-tile sharing starts off and does not retroactively publish existing trips. Turning that automatic setting off stops future automatic publications; it does not withdraw earlier shared cells. Withdraw territory sharing itself to remove existing public territory participation. RoadPulse derives coarse grid cells from that trip, approximately one kilometre north to south with widths varying by latitude. Other signed-in users can see those cells, your public display name, territory color, and any associated club name and color. These cells reveal approximate places traveled even though the full route file and individual sample times and speeds are not published.

Competition compares the saved completion times of published trips. Current and previous monthly season boards use retained publication evidence. Withdraw territory sharing to remove your published participation; your original private trip copies remain. A chosen club name and color can appear with shared territory and season results. Club invitation codes allow others to join, so share them only with intended members. Club managers can rotate their code, manage the club or disband it; this is separate from application Admin access.

Private friends and community safety

Friends are optional and use a private invitation code; RoadPulse does not upload your phone contacts. Requests show the two members’ profile names. Confirmed friendships and requests are private, and do not share trip routes, addresses or live location. RoadPulse stores the friend connections, blocks, receiving preference and highest confirmed friend count for Crew recognition. Removing a friend or blocking a member closes the connection; earned Crew progress remains.

Before posting or changing community content, accounts must explicitly accept the current community rules. Reporting and blocking remain available without accepting them or enabling public sharing. A community report sends the selected public member, club or road-report identifier and a reason, with a request identifier and time. RoadPulse privately stores the reporter, reported account, captured public label, status and moderation decisions. It does not attach private trips or phone contacts. The RoadPulse Admin reviews these cases and can hide content, restrict participation or restore it. A report does not automatically hide content. Blocks hide public participation between the two accounts and prevent new friend requests; they are private and do not restore friendship when removed.

Community safety reports are removed after 90 days when resolved, or 180 days when still open, except evidence referenced by an active moderation restriction. That evidence stays while the restriction remains active. Scheduled cleanup runs hourly. Blocks and moderation restrictions remain until removed or the associated account is deleted. Account deletion removes associated agreements, reports, blocks and restrictions; a surviving moderation event can retain a decision with a deleted reviewer detached. Older app versions may need to update and accept the rules before new public contributions can be sent. Private trip recording and backups remain available.

Replay and exported cards

Ride Replay reads your saved trip on the phone. Generated trip cards stay in the app's private cache until you choose a recipient through Android's sharing interface. Route outlines are excluded by default. If you include a route, its shape can reveal places traveled. Check the preview and recipient before sharing. An exported image can contain the displayed trip date, distance and speed summary; receiving apps control copies you send to them.

App performance and optional usage analytics

RoadPulse's private Admin dashboard uses aggregate account, sign-in and cloud-copy totals to monitor the service. Optional app usage analytics starts off. If you turn it on in RoadPulse, the app sends a limited set of events, such as a screen being opened, a backup or restore succeeding or failing, and a map request failing. Events can include their type, screen, duration and app version and are linked to your RoadPulse account. They do not contain route coordinates, speeds, sensor readings, email addresses, passwords or free-text error messages.

You can turn optional usage analytics off in the app. This stops new usage reports and clears pending reports on that phone; it does not automatically erase reports already received. Usage analytics are reported for up to 90 days. Expired raw events are removed when that account next sends analytics. The Admin dashboard shows aggregate results. There is no third-party advertising tracker or analytics SDK in this feature.

Advertising and payments

The current Google Play closed-test candidate contains no advertising or billing SDK, collects no Advertising ID and requests no ads or purchases. Google Navigation and Places have their own data processing as described above; turning off RoadPulse usage analytics does not turn that processing off. Advertising is planned, but introducing it requires a separately prepared app release and updated privacy choices and disclosures.

RoadPulse does not pay users to view or click ads. Recognition points have no cash value. The paywall and cash payouts remain off.

Campaign links

When you follow a RoadPulse campaign link, RoadPulse counts the request for that campaign. These are request counts, which can include repeat visits and automated traffic; they are not counts of unique people or app installs. Counts are capped at 10,000 per campaign per day. Campaign counters do not store your IP address, browser details, cookies or the page you came from. Hosting providers can still process ordinary connection logs.

The campaign page opens the app only when you choose. RoadPulse then asks before remembering the campaign. If you agree and sign in, that first campaign can be associated with your RoadPulse account and used in private aggregate marketing reports. This is separate from optional usage analytics. Later campaign links do not replace an account's first recorded campaign. RoadPulse does not send campaign or account data to an advertising network.

Support, feedback and creator inquiry forms

When signed in with a confirmed RoadPulse account, you can deliberately send a Contact, Feedback or Creator inquiry form to support@roadpulse.dev. You choose the optional name, reply email and message. RoadPulse also submits the form category and a request identifier and associates the private request with your signed-in account. No saved trip, route, location, sensor reading or device log is automatically attached.

RoadPulse stores the submitted correspondence, account and request identifiers, creation time, sending status and mail-service receipt privately to handle support, limit repeated submissions and retry the same request without sending duplicate messages. Resend sends the plain-text email from admin@roadpulse.dev to the fixed support address, with your chosen email as the reply address. A mail-service acceptance message is not confirmation that an email arrived in the inbox. You can still choose to review or copy a draft and send it through your own email app.

Referral codes and ambassador applications

You can choose a personal referral code to share with people you invite. It is separate from a club invitation code. When a new account deliberately claims a referral under an open program's displayed terms, RoadPulse records the referring and referred accounts, the code and terms used, the recognition-point rules and attribution and review times. Referral progress can use account confirmation and a qualifying completed cloud backup; publishing territory is not required.

Members see their own code, application and attribution status and aggregate referral counts and recognition points. The RoadPulse Admin reviews applications and referral eligibility using display names, statuses and milestone results. These referral screens do not disclose another member's email address or private trip file. Ambassador applications contain the explanation you choose to submit about helping RoadPulse grow; they remain private for Admin review and do not grant application Admin access.

Recognition points have no cash value and do not grant paid access. Cash-commission tiers and future membership rewards are saved plans only: payouts, billing and membership grants are not connected, and the paywall remains off. An application or referral is not a promise of payment, membership or a partnership. Review the program terms shown in the app before participating.

Service providers

Google authenticates Google accounts. Supabase provides RoadPulse authentication and stores account profiles, private cloud trip copies, submitted support correspondence and private referral and ambassador records, navigation recaps, friend connections and community safety records.
Resend delivers verification and sign-in account emails and the support forms you explicitly send. Support email is forwarded by Cloudflare to RoadPulse's Gmail inbox.
Street maps request visible map tiles from OpenStreetMap. The optional aerial replay map requests visible imagery tiles from the USGS National Map, whose coverage and detail vary. Those requests reveal your IP address and the approximate map area being viewed to the selected tile service; the app does not send it the full trip file. Base-map imagery is not included in exported trip cards.
Vercel hosts the public information, campaign and sign-in return pages. Hosting and authentication services may process ordinary connection and security logs.

Use and sharing

RoadPulse uses account and trip data to operate sign-in, profiles, backups, restore, maps and the navigation, rankings, territory, club, friend, road-report, support, referral and ambassador participation you choose, and to review community safety reports. Google email and profile information is not sold or used for ad targeting, and it is not supplied to an AI model. No AI service is currently connected. These public pages contain no advertising trackers, analytics SDKs, forms or external assets. Campaign request counters are handled by RoadPulse before the campaign page opens.

Retention and your choices

Local trips stay on your phone unless you remove them or clear the app's data. Cloud copies remain separately stored; signing out, removing a local trip or turning off automatic backups does not by itself delete them. To request access to, correction of or deletion of RoadPulse account data and cloud copies, contact support@roadpulse.dev from the account's email address. We will verify account ownership before acting. Signing out does not automatically delete submitted support correspondence, referral records or ambassador applications. You can also contact support to request review or removal of those records; ownership is verified before private information is disclosed or changed. RoadPulse account controls include Close private cloud account. Review the account, sign in again when requested and explicitly confirm deletion. This removes the cloud account and its associated cloud trip copies, profile, XP, account address book, mileage and shared contributions. App Admin accounts require a separate ownership handoff first. A minimal technical deletion receipt and platform security logs can remain for confirmation and security; the receipt contains no email, password or trip content and is detached from the deleted account. That minimal receipt has no automatic expiry. Local trip history, including trips you explicitly restored from cloud copies, local notes and copies already exported to other apps remain on the phone under your control. Remove those separately when desired. To request deletion without installing RoadPulse, follow the account and data deletion instructions.