Privacy
Effective October 6, 2026
Booking a detail means telling us where you live and letting someone come to your home. Working as a detailer means handing us documents that decide whether you get paid. This page describes what we do with both, as the product actually works today — not what we intend to build.
Where something is not built, this page says so rather than leaving you to assume it. We expect to update this page as Dripbase grows, and the date above changes when the substance does.
What we collect
- If you book a detail
- Your name, email address and phone number. The address of the car, including anything you tell us about gates, parking or where the outdoor tap is. Your vehicle’s make, model, year, color, license plate and any notes you add. What you booked and what it cost. Reviews you write. A profile photo, if you choose to add one.
- If you apply to detail
- Your name, email, phone and home ZIP code, your experience and equipment, and what you tell us about your current work and insurance. If you go on to be vetted: your driver’s license, insurance certificates, a background check result, photos of your rig, and your training and assessment results.
- If you detail: where you are on the way to a job
- Only after you tap “On my way” on a job, and only if you allow location while the app is in use. The app then sends your position about every fifteen seconds, including while it is in the background, until you start the job, drop it, it is cancelled or you sign out. We keep one point per job — the latest — with its accuracy, your direction of travel and the time. Each new point replaces the last, so there is no trail. Once the customer has been shown where you are, we also keep the last point they were shown from well away from where the trip began, which is what they keep seeing if you head back that way. We also keep a point we placed at random within a few hundred metres of where the trip began, which is used to hide the area around it (see below); a later trip that begins near the same place uses the same point. Your real starting place is not stored. Each such point is deleted once no trip has begun near it for 180 days, and all of them are deleted when you delete your account. The full story is in the section on detailer location.
- If you detail: your Google Calendar busy times
- Only if you connect Google Calendar, and only the times you are busy, not what the events are. The Google Calendar section below has the details.
- If you never make an account
- Asking us to cover your ZIP code stores your email and that ZIP. Asking for a sign-in code stores the address you typed, even if you stop there. Submitting the detailer interest form stores everything on it.
- When you use the site
- Our hosting provider records ordinary web server logs, which include IP addresses. See the section on cookies below for what is stored in your browser.
Who can see your address
Detailers deciding whether to take your booking see the city, state and ZIP code, how far away it is, and your car’s make, model, year and size. They do not see your street address, the coordinates, your license plate, your car’s color, or the access notes you saved with the address.
The detailer who accepts the job sees the full address, the map coordinates we worked out from it and those access notes, because they have to find your car. When the job ends, they stop seeing them. There is deliberately no grace period.
We work out those coordinates after you book, by sending your street address, city, state and ZIP code to Mapbox (see below). We do not send the apartment or unit line. The coordinates are stored on the job, frozen like the address, and once stored the point is not changed. If Mapbox cannot be reached, your booking still goes through and the job simply has no coordinates.
One exception worth knowing about. The “Notes” box on the booking form is sent to every detailer who is offered the job, before anyone accepts — unlike the access notes saved with your address, which are not. If something should only reach the person actually coming, put it in your address’s access notes.
Detailer location on the way to a job
When a detailer taps “On my way”, the detailer app asks for their location while the app is in use, and shares it with us until they start the job, drop it, it is cancelled, or they sign out. It keeps sending while the phone is in another app, such as a maps app, and never asks for “Always” location permission. Our server also refuses any point for a job that is no longer on the way.
Who can see it. Only the customer whose job it is, and only in a limited way. They are not shown the detailer’s position until the detailer is within about 5 miles of the job’s address, in a straight line, and never if we could not place that address on a map. They are never shown it while the detailer is within about 1.6 kilometres (a mile) of a point close to where the trip began, which is usually the detailer’s home or the last customer’s address. On each trip, the first time the customer is shown either the detailer’s position or an arrival time, the detailer is also past a further random distance of up to about 3.2 kilometres (two miles): part of it chosen once, and kept secret, for each point trips begin near, and part chosen for that trip, so where they first appear does not show exactly how far away that point is. If a detailer the customer can already see heads back toward where the trip began, the map stops following them at that distance and keeps showing the last place it showed from further out, with the time it was taken and no direction of travel, until they are that far away again. The detailer sees their own location in their own app. Another customer, or a detailer who is not on the job, cannot read it.
Arrival time. While the detailer is on the way, the customer is also shown a rounded arrival time, such as “about 15 minutes”. It is always rounded up: to the next 5 minutes under half an hour, to the next 10 up to an hour, and “more than an hour” beyond that. It is worked out only from positions outside the area around where the trip began (the first one, also past that trip’s random distance), and only from a position less than three minutes old. While the map is holding a detailer’s last place, the arrival time is not updated either, and it is gone within three minutes. When there is no recent drive time, no arrival time is shown.
How long we keep it. The latest point is deleted when the job leaves “on the way” — when the detailer starts it, drops it or it is cancelled. We keep no history of where a detailer has been. What we do keep is, for each place a detailer’s trips have begun, a point we placed at random within a few hundred metres of it — never the place itself — so the same area is hidden on every trip from there. Each is deleted once no trip has begun near it for 180 days, and all of them when the detailer deletes their account.
Maps. On an iPhone, the Dripbase booking app shows the detailer on an Apple Maps map. Apple draws the map; we place the pins on your phone and do not send Apple coordinates, and Apple’s own privacy policy covers what it receives to draw the map. On Android, the map is drawn by Mapbox. We place the pins on your phone and do not send Mapbox their coordinates, but to draw the map your phone asks Mapbox for the map of the area on screen — around your home and, once shown, your detailer — so Mapbox can tell which area you are looking at, along with your phone’s IP address and basic device details. We switch off Mapbox’s optional usage reporting, and the app never asks for your phone’s location. Mapbox’s own privacy policy covers what it receives.
Your profile photo
Adding a profile photo is optional. If you add one, it is stored privately and never served from a public web address — each view uses a link that expires in minutes and requires you to be signed in. We show it to the detailer assigned to your job, so they know who to look for, and to our staff, the same as everything else on this page. Other customers never see it, and neither does a detailer who is only offered the job.
Removing your profile photo deletes the stored file. If our storage can’t confirm that right when you ask, nothing changes and your photo stays — we would rather say so than call it removed while it is not. Replacing it deletes the old file the same way; if that first try does not go through, we retry automatically within the hour rather than leaving it in place.
Payments
We never see your card number. It goes to Stripe, our payment processor, through a form Stripe hosts. What we keep is the card’s brand, its last four digits and its expiry date, so you can tell one saved card from another. Stripe receives your name, email, and the amount and description of each charge.
Detailers are paid through Stripe as well. Stripe collects the bank details and the identity and tax information it requires to pay you and to issue your 1099-NEC, including your date of birth and full Social Security number — we never hold any of those. What we store is the Stripe account identifier, whether payouts are enabled, and whether Stripe has your tax ID.
Detailer documents and checks
Licenses, insurance certificates and assessment videos are stored privately. They are never served from a public address: each view creates a link that expires in five minutes. Only you and our staff can open them. Customers never see a document — at most they see which types of check a detailer has passed.
Background checks and license verification are done by our staff reading what you send us. We do not use a background-check or identity vendor today, and no third party runs a check on you on our behalf.
Google Calendar
Detailers can connect a Google Calendar so we stop offering them jobs at times they are already busy. It is optional: nobody has to connect one to work on Dripbase. This section is about detailers only.
- What we ask Google for
- One permission:
https://www.googleapis.com/auth/calendar.freebusy. It lets us ask Google when you are busy. We get a start time and an end time for each busy stretch. We do not get event titles, descriptions, attendees or locations, and this permission does not let us read them. - What we use it for
- To keep job offers away from your busy times. A busy time becomes a block of time off, and we do not send you offers that overlap it. If a new busy time overlaps an offer you have not answered yet, we withdraw that offer. Nothing else uses it: not pricing, not your tier, not advertising. We do not yet warn you when a busy time overlaps a job you have already accepted, and your calendar never cancels an accepted job.
- What we store
- The start and end of each busy block, with no text. A record of the connection: that it is on, the permission you granted, when it last synced and the last error code, if any. A short log entry when a connection is made or removed, or a sync changes your blocks, which holds counts, not your busy times. And your Google refresh token, the key that lets us keep asking. It is encrypted before it is stored (AES-256-GCM) and is not written to our logs. The short-lived access token Google gives us for each sync is held in memory for that sync and is not stored.
- How often, and how far ahead
- About every 15 minutes while the connection is on, for the next 90 days. Each sync replaces the upcoming blocks with what Google currently reports.
- Who sees it
- You, in your settings, see that your calendar is connected and the upcoming busy times we imported, each as a start and an end. Customers never see your busy times or that you have a calendar connected. Our staff can reach busy blocks only through our database, and do so only when needed for security, to follow the law, or because you asked us for help. We do not give it to anyone else. The companies that host our database and servers store it on our behalf, as listed below, and Google receives our requests for it.
- How to stop it
- In the detailer app, open Settings, then Calendar, and choose Disconnect. We tell Google to cancel the permission, delete the stored token, and delete every busy block we imported, including ones that have already ended. If Google cannot be reached, we still delete our copy, and you can finish by removing Dripbase under third-party access in your Google Account. You can remove it there at any time yourself.
- If Google cuts us off
- If you remove Dripbase from your Google Account, Google stops answering us. We delete the stored token, keep the busy times that start in the next 7 days so the coming week stays protected while you reconnect, delete the ones that start later, delete the ones that have already ended, and ask you to reconnect.
- If you delete your account
- We cancel the permission at Google, delete the stored token and the connection record, and delete every busy block we imported, past and upcoming, the same as disconnecting.
- What we keep
- While your calendar is connected, a busy time that has ended is kept for 30 days and then deleted. Each holds a start and an end and nothing else. When you disconnect or delete your account, busy times that have ended are deleted straight away. If you remove Dripbase from your Google Account instead, they are deleted the next time we check your calendar and find the permission gone, and never later than 30 days after they end.
Dripbase’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain words, about what we get from Google Calendar:
- We use it only to keep job offers away from your busy times.
- We do not sell it.
- We do not use it for advertising.
- No person at Dripbase reads it, except where needed for security, to follow the law, or with your consent.
Who else receives your information
We do not sell your personal information, and we do not share it for advertising. These are the companies that handle it so the product can work:
- Stripe
- Payments and detailer payouts, as described above.
- Vercel
- Hosts the site and the API, and stores job photos and detailer documents. As our host it processes every request, including IP addresses.
- Mapbox
- Turns an address into a point on a map, and works out how long a drive will take. When you book, your street address, city, state and ZIP code are sent to Mapbox, and the point it returns is stored on the job. While a detailer is on the way, their current position and the job’s point are sent to Mapbox to get the drive time, so we can tell you roughly when they will arrive. We keep the latest drive time with the detailer’s latest position, and delete it with that position when the job is no longer on the way. Your name, phone number and email are not sent. On Android, Mapbox also draws the map in the booking app, as described above. Mapbox’s own privacy policy covers what it does with a request.
- Resend
- Sends our email. It receives the address we are writing to and the contents of the message, including sign-in codes.
- Anthropic
- Powers the answer box in our Help Center. If you use it, your question is sent to Anthropic along with our published help articles. It is not connected to your account, and nothing about your bookings is sent with it — so please don’t type anything into it you would not want to send to another company.
- Statsig
- Decides which version of a feature you see. Signed in, it receives an account identifier, your role and, for detailers, your tier. Signed out, it generates a random identifier stored in your browser. We never send it your name, email, phone or address.
- Runs Google Analytics on our public pages, and only if you say yes. It receives the page you are on, the page you came from, your IP address and a random identifier stored in a cookie — see the section on cookies below. If you are a detailer and connect Google Calendar, we also ask Google for your busy times — see the Google Calendar section.
- A managed database provider
- Stores everything described on this page, on our behalf and under our instructions.
We will also disclose information if the law requires it, or to protect someone’s safety.
Cookies and what is stored in your browser
Dripbase itself sets no cookies. When you sign in, your session is kept in your browser’s local storage and sent back to us on each request. It lasts seven days. Signing out removes it. The help chat panel also remembers when it last opened, so it does not reopen on you.
Statsig, described above, stores a random identifier and its own bookkeeping in your browser. It does not set a cookie in our setup.
Google Analytics runs only if you say yes. The first time you visit a public page, a banner asks whether we can count your visit. Until you answer yes, Google Analytics does not load at all: no request goes to Google and no cookie is set. If you say no, or ignore the banner, it stays off and the site works exactly the same. We use it to see which pages people land on and where they arrived from.
If you say yes, Google sets two cookies on our domain:
- _ga
- A random identifier that lets Google Analytics tell one visitor from another. It lasts two years.
- _ga_ followed by an ID
- Remembers your current visit, so page views are counted as one visit rather than several. It lasts two years.
Two more limits apply either way. Google Analytics runs only on our public pages, never on the booking, signup or account pages. And Google’s advertising features are switched off, so it is not used to build an advertising profile of you.
Your answer is saved in your browser’s local storage, not a cookie, so it applies to this browser only, and clearing your site data asks you again. You can change it here at any time. Changing it deletes the two cookies above and turns analytics off until you answer again. We do not have a separate response to a browser “Do Not Track” signal; the banner is how you choose.
How long we keep things
Be aware that we currently delete very little. Bookings, charges, refunds, payouts, reviews, job photos, detailer documents, staff decisions and the notes behind them are all kept as a record of what happened. Records of a job do not change when you later edit a saved address or a price changes — what a job charged and promised is frozen when it is booked.
The same is true of information from people who never finished signing up: a ZIP coverage request, a sign-in code sent to an address, or a detailer interest form is kept. We have no automatic clean-up of old records, and building one is on our list.
Three exceptions. Device tokens for push notifications are deleted when you sign out of a device or when an account is closed, because keeping one means keeping a live key to someone’s phone. A profile photo you remove or replace is deleted from storage, as described above, not kept. And a detailer’s live location is deleted when the job leaves “on the way”; the randomly placed points near where their trips began are deleted 180 days after the last trip from near them, or with their account. The map coordinates on a job are kept with the address, as part of the record of the job.
Google Calendar is the one place where a detailer can make us delete something themselves: disconnecting removes the stored Google permission and every busy time we imported. While a calendar is connected, busy times are deleted 30 days after they end.
What you can do today
Signed in, you can:
- See and change your name
- Change your password
- See your saved addresses, vehicles and cards, and add more
- See your bookings and what you were charged
- Sign out of one device, or of all of them
- Delete your account
What we cannot do yet
These are being built. Until they exist, this page describes how we handle your data rather than being a place to act on it:
- Download a copy of your data
- Ask us to erase your history
- Change your email address or phone number
- Remove a saved address, vehicle or card
- See the before and after photos of your own job
You can delete your account in Account › Data & privacy, and our staff can do it for you. Deleting it means you can no longer sign in or book, and the email address cannot open a new account. It does not erase the history: your past jobs keep the name, contact details and addresses on them, a review you wrote is part of a detailer’s standing, and a payment is a financial record we have to keep. We would rather say that plainly than call it a deletion and quietly keep the rows. Your conversations with Dripbase support are kept, so our staff can still see them. Any that are still open are closed, except a safety report, which stays open until our staff close it. No one can reply on any of them afterwards.
Marketing
We do not send marketing. The messages we send are about a specific booking or your account — that it was confirmed, that someone is on the way, that it is done, or a code to sign in with. If that ever changes, we will ask you first, and this page will say so before it happens.
Children
Dripbase is for adults. It is not intended for anyone under 18, and we do not knowingly collect information from children. If you believe a child has given us information, tell us and we will remove what we can.
How to reach us
Questions about anything on this page, or about your own data, go to privacy@getdripbase.com. A person reads it. We are a small team in Phoenix, Arizona, so expect a reply in days rather than minutes.
Changes to this page
When how we handle your data changes, this page changes in the same release, and the effective date at the top moves. We do not quietly broaden what we collect.
Signed-in customers can also read the shorter version at Data & privacy in their account.