Back to RiderMate

Legal & Privacy

This page contains RiderMate's Legal Terms, Privacy Notice, information about cookies and local storage, and data-protection complaint procedure.

Version 1.1 · Effective

Privacy Notice

RiderMate is the controller of the personal information described in this notice. The business and contact details under “Who provides RiderMate” in the Legal Terms also apply to this Privacy Notice.

Information RiderMate collects

  • Account and profile information: display name, email address, authentication and session information, account identifiers and Rider Profile preferences such as work areas or postcodes, delivery apps and vehicle choices.
  • Rider records: earnings, mileage, expenses, shifts, plans, targets, vehicle costs, tax-related records and assumptions, and other information you choose to enter.
  • Subscription information: selected plan, Stripe customer, subscription, Checkout, invoice, payment-status and refund identifiers, contract status, discount-code references and affiliate-attribution references.
  • Communications: messages and information provided in support, refund, rights-request and complaint communications.
  • Technical and security information: authentication cookies, request and operational logs, error details, browser or device information made available in requests, and security rate-limit data. Limited browser failure reports contain controlled categories, app sections, operations, technical codes and build references, not raw error messages, account identifiers, financial values, passwords or authentication tokens. For unauthenticated rate limiting, RiderMate hashes limited forwarded IP-address and user-agent information rather than using it to locate you.
  • Aggregate usage information: cookie-less Vercel Web Analytics measures page views, page paths, referrers where available, country or region, and browser and device categories. It also counts successful new-shift logging events without shift details, and coarse anonymous, confirmed paid-subscriber or authenticated non-subscriber activity categories where membership status can be verified. These are anonymous visitor estimates and activity counts, not exact counts of unique people or database records. Query strings and fragments are removed from analytics page URLs before transmission. RiderMate does not attach account identifiers, email addresses, billing references or rider records to these analytics.
  • Weather requests: a selected area is mapped to a configured weather zone. Stored weather-zone coordinates or provider location and the required forecast date range may be sent server-side to the weather provider.

RiderMate does not store your payment-card details; Stripe collects and handles those details on its hosted payment pages. RiderMate does not currently collect precise live GPS location or use an IP address to infer your work area. RiderMate does not currently load advertising, behavioural profiling, session replay or fingerprinting, and does not send user records to an external AI service.

How and why the information is used

  • To perform the contract: create and secure your account; save and display your records and preferences; provide planning, forecasting, earnings, export and tax-estimate features; provide RiderMate PRO; administer Checkout, subscriptions, discounts, cancellations and refunds; and respond to service requests.
  • For legitimate interests: prevent abuse and fraud, apply security limits, diagnose faults, keep services reliable, maintain accurate billing state, defend claims and understand operational problems and aggregate usage to improve the service. RiderMate considers the effect on users before relying on these interests.
  • To meet legal obligations: maintain records required for tax, accounting, consumer, payment, fraud-prevention and data-protection purposes, and respond to lawful requests.
  • With consent where it is specifically required: if RiderMate introduces processing that legally requires consent, it will ask first. Withdrawing consent would not affect earlier lawful processing.

Who receives information

  • Supabase provides authentication and session handling, database services, server-side functions, secret storage and parts of the weather-refresh runtime.
  • Vercel hosts RiderMate, runs application and scheduled server functions, routes requests and keeps limited operational logs. It also provides cookie-less Web Analytics for aggregate page-view and usage statistics.
  • Stripe provides hosted Checkout, payment processing, subscription management, refunds and the customer billing portal. Stripe receives information needed for those services, including email, internal user and Checkout references, selected plan, discount or affiliate references, and billing details entered on Stripe's pages.
  • Visual Crossing supplies weather forecasts. It receives the configured weather-zone location or coordinates and forecast date range, but RiderMate does not send it your user ID, email, earnings or shift records.
  • Authentication email delivery providers deliver account and security emails through Supabase. The particular production email-delivery provider is not identified in the application code and can be confirmed on request.
  • Support mailbox providers process emails sent to or from hello@ridermate.app, including support, refund, rights-request and complaint communications. The particular production mailbox provider is not identified in the application code and can be confirmed on request.

RiderMate may also disclose information to professional advisers, insurers, courts, regulators, law-enforcement bodies or another organisation involved in a business transfer where reasonably necessary and lawful. RiderMate does not sell personal information.

RiderMate does not currently use a customer-support tracking SDK, advertising provider, behavioural profiling provider, session-replay provider, separate error-monitoring service or external AI processor. Aggregate Web Analytics uses Vercel; operational console logs are handled within the Vercel and Supabase services described above.

International processing

Some providers may process information outside the United Kingdom. Where UK data-protection law requires a transfer safeguard, RiderMate will use an applicable lawful mechanism, such as UK adequacy regulations or approved contractual safeguards, and take additional measures where appropriate. This notice does not claim a provider region or contractual arrangement that RiderMate has not verified.

How long information is kept

Retention depends on why the information is needed:

  • Core account, earnings, mileage, expense and tax-related records: up to six years after the user's last use where needed for legal, tax, accounting or dispute purposes.
  • Payment, refund, contract and complaint records: up to six years where needed.
  • Accounts that never become paid accounts: normally up to 12 months after last activity.
  • Technical and security logs: only for the shorter period reasonably required for security, troubleshooting and provider operations.
  • Backups: until overwritten through the normal backup cycle.

Self-service account deletion removes your RiderMate account and the product data covered by that process. RiderMate and its providers may still retain payment, refund, contract, fraud-prevention, security, complaint and other records where legally required or reasonably necessary. Stripe may retain transaction records under its own legal obligations and retention rules. Account deletion therefore does not promise erasure of legally required transaction records, and backups age out through their normal cycle.

Your UK data-protection rights

Depending on the circumstances, you may have the right to ask for access to your information, correction, deletion, restriction of processing, an objection to processing, or transfer of information in a portable form. You may also withdraw consent where processing relies on consent and complain to the Information Commissioner's Office.

You can start self-service account deletion from Settings, under Billing, or from an authenticated restricted-account screen. Self-service account deletion does not include a data-export offer; the existing Shift History CSV export remains a separate feature. This does not automate every data-protection right or override records RiderMate must retain. Manual deletion and other erasure requests, and requests for access, correction, restriction, objection or portability, may be sent to hello@ridermate.app. RiderMate may need to verify your identity and will respond without undue delay and within the applicable legal timeframe, normally within one month. The law permits more time in limited circumstances; if that applies, RiderMate will explain why.

Security and your choices

RiderMate and its providers use technical and organisational measures intended to protect information, but no internet service can guarantee absolute security. Keep your account credentials private and contact RiderMate promptly if you suspect unauthorised access. After confirmed account deletion, RiderMate attempts to remove that account's RiderMate storage and authentication session from the browser or installed PWA where deletion is completed. It cannot remotely clear local state on another browser or device, downloaded exports, browser history or password-manager entries; clear RiderMate site or PWA data on those devices yourself. Clearing browser or installed-PWA storage may also remove local preferences or unfinished signup information, and some locally dismissed items may return.

Cookies and Local Storage

RiderMate uses first-party browser storage to operate accounts and app features. It does not currently use advertising cookies, behavioural profiling, session replay or cross-site tracking. No cookie banner is used for the storage described here.

Vercel Web Analytics is cookie-less. RiderMate does not enable its optional account-identification or analytics-cookie features. Vercel uses an anonymous visitor hash derived from incoming request information and discards it after 24 hours. The Web Analytics disclosure was updated on 12 October 2026; this does not change the Legal Terms version or existing acceptance records.

Necessary authentication storage

Supabase authentication uses first-party cookies with names based on the RiderMate Supabase project, commonly shaped like sb-<project-ref>-auth-token. A session may be split across cookie chunks, and a temporary PKCE verifier may be used for sign-in, password recovery or other secure authentication flows. This storage is necessary to sign you in, maintain your session and protect authentication flows.

Unfinished signup information

Local storage may temporarily hold unfinished onboarding information under ridermate.pendingSignupProfile. It can contain the account identifier, email address, display name, selected work area, vehicle and apps so RiderMate can safely finish onboarding after an interruption. RiderMate removes it when the related onboarding flow completes or is cleared, but browser storage may otherwise retain it until it is removed by RiderMate or by you clearing site data.

Rider Insights and Dashboard preferences

Rider Insights uses persistent local storage containing an opaque user namespace and a limited rotation history of up to 20 insight identifiers, families, purposes and dates. It does not store the underlying earnings or tax amounts in that history. RiderMate preserves this information so recently shown insights can rotate sensibly across visits.

Dashboard To Do dismissals also use persistent local storage, namespaced by an opaque authenticated-user value, stable task key and occurrence key. This prevents a different RiderMate user in the same browser from inheriting the dismissal and allows the same occurrence to remain dismissed on that browser or device. It does not synchronise across browsers or devices, and clearing browser or PWA storage may make a dismissed action return.

Temporary Catch-Up storage

Session storage may use a key containing your authenticated account identifier and Catch-Up setup revision, with a random mutation identifier stored as its value for concurrency checks and idempotency. It lasts for the browser-tab session and helps prevent duplicate or stale Catch-Up updates.

Offline application files

RiderMate's service worker uses the browser's Cache Storage for offline support. The current RiderMate cache, ridermate-offline-v2, stores only the self-contained offline page. Older RiderMate offline-cache versions are removed when the service worker updates. The cache remains until it is updated, removed by RiderMate or cleared through browser or PWA storage controls. RiderMate does not create an IndexedDB database.

Storage on hosted provider pages

Third-party services may use their own cookies or similar storage when you visit pages they host. For example, Stripe Checkout and the Stripe customer portal may use storage for payments, fraud prevention, security and session continuity. That storage is governed by the provider's own information presented on its hosted service.

Data Protection Complaints

If you have a concern about how RiderMate has used your personal information, email hello@ridermate.app. Include enough information to identify your account and explain the concern, but do not send passwords or full payment-card details.

RiderMate will acknowledge the complaint within 30 days, investigate it fairly, and provide an outcome or a progress update. RiderMate may ask for further information or proof of identity where reasonably necessary. Raising a complaint does not affect your other rights.

You also have the right to complain to the UK Information Commissioner's Office. Information about making a data-protection complaint is available at ico.org.uk. You do not have to complete RiderMate's complaint process before contacting the ICO.