Privacy Policy

Effective October 14, 2026

This policy covers OnBaseRide, a rideshare for verified service members and their dependents, on the web and as an installable app. It explains what personal data is collected, why, who it is shared with, how long it is kept, and the rights you have over it. It is written to meet the EU General Data Protection Regulation (GDPR), Portugal's data protection and electronic communications laws, and United States federal and state privacy laws.

Who is responsible for your data

OnBaseRide is operated by Erica Thompson (Brave Haven), the controller of your personal data. For anything about your data, email hr@bravehaven.io. No data protection officer has been appointed, because one is not required at this size.

The short version

What we collect, why, and for how long

Your account

What
Email address and password (held by Supabase Auth, which stores only a hash), whether you have confirmed your email address, display name, and profile photo if you add one. If you sign in with Google, GitHub or LinkedIn, the name and email address that provider shares
Why we are allowed to
Contract: needed to provide the service you signed up for (GDPR Art. 6(1)(b))
How long we keep it
For as long as you keep your account. Ask us to delete it and it is deleted within 30 days

Confirming you are military-affiliated

What
Whether ID.me verified your military status, the group it reported (for example "Service Member"), and when. Nothing else ID.me knows about you is passed to or kept by OnBaseRide
Why we are allowed to
Contract: needed to provide the service you signed up for (GDPR Art. 6(1)(b)): OnBaseRide is only open to the military community
How long we keep it
For as long as you keep your account. Ask us to delete it and it is deleted within 30 days

Matching and running rides

What
The installation the ride belongs to, pickup and drop-off addresses, the pickup time you choose (now or scheduled up to 30 days ahead), other ride times, the driving miles and the price worked out from them, status, and which rider and driver are on the ride. To price a trip, the two addresses are sent to Mapbox, which returns the driving distance; the map coordinates it returns are used once and not kept. A price you do not use is deleted after 15 minutes, or when you next check a price. A driver sees a ride's pickup, drop-off and pickup time before accepting it. A driver who posts a commute gives its meeting point, destination, departure time and seats, and every verified member can see them until it leaves, so the meeting point should be a public place, never a home. A commute's meeting point and destination are sent to Mapbox to price it the same way
Why we are allowed to
Contract: needed to provide the service you signed up for (GDPR Art. 6(1)(b))
How long we keep it
For as long as you keep your account. Ask us to delete it and it is deleted within 30 days. Paid rides are kept as payment records

Finding addresses near you ("Use my location")

What
Your device's location, only when you tap "Use my location" and your browser asks you and you allow it. We send it to Mapbox to find the nearest address and to sort suggestions nearest you. Once you have allowed it, the home screen also uses it to find the installation nearest you and say whether rides are open there; that is worked out in your browser and never sent anywhere
Why we are allowed to
Consent (GDPR Art. 6(1)(a)): you tap the button and allow it in your browser. You can say no, or turn it off in your browser settings, at any time
How long we keep it
We do not store it. It stays in the open page only and is gone when you leave or reload it, and it is never logged

Paying for rides and paying drivers

What
Payment status, amounts (the cost share, card processing and the total), and Stripe IDs. Drivers set up payouts on Stripe's own pages, where Stripe collects their identity and bank details directly
Why we are allowed to
Contract: needed to provide the service you signed up for (GDPR Art. 6(1)(b)), and legal obligation: tax and accounting law (gdpr art. 6(1)(c))
How long we keep it
As long as tax and accounting law requires, up to 10 years

Launch waitlist

What
Email address and an optional note. A copy of each signup made on the website (the email address, the note and the time) is also sent to our task list in Todoist, so we can track replies to it
Why we are allowed to
Consent (GDPR Art. 6(1)(a)). You can withdraw it at any time
How long we keep it
Until launch in your area, or until you ask us to remove you. The Todoist copy is kept until its task is deleted

Protecting sign-up, rides, payments, place lookups and verification from bots (Vercel BotID)

What
When you register, ask for a new confirmation link, ask to reset your password or set a new one, pay for a ride, post a commute, look up an address, see Sarge's places near your installation, set up driver payouts, start military verification, join the launch waitlist, or, on the demo site, start a guest account or have sample drivers move your demo rides along: signals from your browser and request that Vercel BotID uses to tell people from automated bots, such as browser and device characteristics and how the request was made. We receive only a verdict: person or bot
Why we are allowed to
Legitimate interests (GDPR Art. 6(1)(f)): keeping the service usable and protecting it from abuse
How long we keep it
We keep nothing. Vercel processes the signals to return the verdict

Protecting password log in from bots (Cloudflare Turnstile)

What
Being set up, not yet switched on. Once it is, when you open the log in page to sign in with an email and password, a Cloudflare Turnstile check runs on that page. Cloudflare receives your IP address and signals from your browser, such as browser and device characteristics and how the check was completed, to tell people from automated bots. We, and Supabase, which runs our sign-in, receive only a single-use token saying whether the check passed. Signing in with Google, GitHub or LinkedIn and registering do not use it
Why we are allowed to
Legitimate interests (GDPR Art. 6(1)(f)): protecting accounts from automated password guessing. It is a security check, not analytics, so it runs without asking first
How long we keep it
We keep nothing. Cloudflare processes the signals to return the result

Running and securing the site

What
IP address, browser and device type, pages requested, and time of request, in server logs. When the server hits an error, an error report goes to Sentry: what failed, where in the code, the page address without its query, and the time. Email addresses and long numbers are removed from it first, and it never includes your IP address, cookies or what you typed
Why we are allowed to
Legitimate interests (GDPR Art. 6(1)(f)): keeping the site working and protecting it from abuse
How long we keep it
Server logs: no more than 30 days, then deleted automatically by our host. Error reports: 30 days, then deleted by Sentry

Limiting repeated registration, confirmation-link, password reset and demo guest attempts

What
A one-way hash of your IP address, and of the email address you register or ask for a password reset with, with a count of attempts in the current hour; on the demo site, also a count of guest accounts started from your IP address. Never the address itself
Why we are allowed to
Legitimate interests (GDPR Art. 6(1)(f)): stopping automated sign-up and email flooding
How long we keep it
Deleted automatically after one day

Limiting repeated requests from signed-in accounts

What
A one-way hash of your account ID, with a count of requests in the current hour, for price quotes, address suggestions, Sarge's places, posting commutes and, on the demo site, sample driver activity
Why we are allowed to
Legitimate interests (GDPR Art. 6(1)(f)): stopping abuse and keeping metered map services within their monthly limits
How long we keep it
Deleted automatically after one day

Understanding how the site is used (only if you accept)

What
When each page was viewed, the page address, the referring site, approximate location (country, region, city), browser, operating system, and device type. No cookies. Visits are told apart by a hash of the request that Vercel discards after 24 hours, so the data is not tied to you
Why we are allowed to
Consent (GDPR Art. 6(1)(a)). You can withdraw it at any time
How long we keep it
Vercel keeps it for our plan's reporting window, and may keep it longer. Withdrawing consent stops any further collection

The demo site

demo.onbaseride.com is a demonstration of OnBaseRide for investors and partners. It runs separately, with its own database, and its payments are Stripe test payments that move no money. If you create an account there, your email address is handled exactly as this policy describes. The demo app at demo-app.onbaseride.com uses the same demo. If you choose "Try as a rider" or "Try as a driver" on either, you get a guest account with a made-up address that receives no mail; it holds no personal data and is deleted after a day. Every demo page says it is a demo, and search engines are asked not to list it.

Cookies and similar technologies

These are strictly necessary for the site to work, so they do not need your consent:

Vercel Web Analytics sets no cookies. Its script is loaded only if you choose Accept analytics; until then nothing about your visit is sent to it. You can change your choice at any time with Analytics settings at the bottom of every page. If your browser sends a Global Privacy Control signal, we treat it as a refusal and do not ask.

Who we share it with

We use these service providers (processors). Each may use your data only to provide its service to us, under a data processing agreement:

You may also use these services, which are responsible for your data themselves:

We do not sell personal information and do not share it for cross-context behavioral advertising. We would disclose data to authorities only where the law requires it.

International transfers

Our providers store or process data in the United States. For transfers of personal data from the European Economic Area, the UK, or Switzerland, we rely on the EU-U.S. Data Privacy Framework (and its UK and Swiss extensions) where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses in the provider's data processing terms.

Automated decisions

Whether you can request or offer rides depends on ID.me's verification result. If you think ID.me got it wrong, email us and a person will review it with you.

Your rights

In the European Union, the UK, and Switzerland

You can complain to a data protection authority. In Portugal that is the Comissão Nacional de Proteção de Dados (CNPD), www.cnpd.pt. Elsewhere, contact the authority where you live or work. We would appreciate the chance to put things right first.

In the United States

Depending on your state (including California, Colorado, Connecticut, Virginia, Texas, and others with comprehensive privacy laws), you may have the right to know what personal information we collect and how we use it, to access it, to correct it, to delete it, and to opt out of its sale, of targeted advertising, and of profiling. We do none of those three. We will not treat you differently for using any of these rights. You can use an authorized agent, and if we turn down a request you can appeal by replying to our answer.

How to make a request

Email hr@bravehaven.io and say what you would like. To protect your account, we will ask you to confirm the request from the email address on it. We answer within one month (GDPR), or within 45 days for US state privacy law requests, and tell you if a complex request needs longer. Requests are free.

How we protect it

Children

OnBaseRide is only for adults: our terms require you to be at least 18. We do not knowingly collect personal data from anyone younger. If you believe a child has given us personal data, email us and we will delete it.

Changes to this policy

When this policy changes, we update this page and its effective date, and email account holders about significant changes.