Legal
Privacy Policy
Last updated August 29, 2026
This policy explains what DetailHive collects and how we use it. It is a product privacy policy, pending lawyer review.
Who we are
DetailHive is shop software for auto detailers, operated at detailhive.io. Questions about this policy go through our Contact page at detailhive.io/contact.
What we collect
Account
Name, email, and a password handled by our auth provider, or identifiers from Apple or Google sign-in. Optional two-factor authentication (authenticator app, or an email code if the shop owner turns that on). Session tokens so you stay signed in. Password reset email is not 2FA.
Shop profile
Shop name, booking slug, phone, address, hours, services, branding, payment methods you list, and similar settings you enter. For carrier SMS registration we may collect legal business name, EIN or tax id, and tax street address — including during Pro checkout, not only from a later identity form. We do not publish those on the booking page.
Bookings, clients, vehicles, and photos
Client names, contact details, appointment times, notes, job photos, inventory counts, mileage logs, and any VIN a shop records on a client or booking. That VIN and matching job history stay scoped to that shop. Vehicle-spec lookup is not part of the public website today.
Communications
When a shop uses email, SMS, or voice, we process the metadata and content needed to deliver that message or call — for example, numbers, timestamps, reminder text, and receptionist audio. When the AI receptionist is on, inbound call audio is streamed to xAI. Some shops use Telnyx AI Assistant as a fallback. SMS may go out through Telnyx or SignalHouse, depending on the shop’s line. Auto-reply is not on unless the shop turns it on. The shop is responsible for end-customer SMS consent; DetailHive does not collect that consent for the shop.
Payments
Subscriptions are billed separately on Stripe to the shop owner. Job card payments go through DetailHive’s Stripe platform account and are then transferred to the shop’s connected Stripe account. We keep payment records Stripe shares with us (status, amounts, customer ids). We do not store full card numbers.
Contact form and feedback
The site contact form and the in-app feedback form do not require a shop login. Contact may collect name, email, optional phone and shop name, and a message, then email a confirmation to the address the person typed. Feedback may collect a message plus optional shop name and email so we can follow up.
Device tokens
If a shop owner uses the iOS app, we may store a device token so we can send push notifications about the shop.
How we use it
- Provide the product: accounts, booking pages, shop dashboards
- Bill DetailHive subscriptions and help shops take card payments
- Deliver support when you write us
- Meet 10DLC and carrier requirements when a shop texts
- Run the AI receptionist only on that shop’s calls, when the shop enables it
- Send reminders, review requests, or weather alerts if the shop enables them
We do not sell personal information. Mileage logs can show IRS rates for deduction estimates. That is not tax advice.
Who processes data for us
We use these companies to run DetailHive:
- Supabase — database and authentication
- Vercel — hosting the app
- Stripe — subscriptions and shop card payments
- Telnyx — shop phone, SMS, and Telnyx AI Assistant fallback
- SignalHouse — SMS on some shop lines
- Resend — booking emails, the contact-form ticket and confirmation, and feedback mail
- xAI — inbound call audio when the receptionist is on
- Apple and Google — optional sign-in
Those companies process data so the feature you turned on can work.
What we publish on a booking page
A public booking page can include shop hours, social links, tax rate, accepted payment methods, and the shop Stripe account id used for checkout. Street, ZIP, Venmo handle, and EIN are omitted from that public page by design.
Shops and their client data
For client, booking, VIN, and photo records a shop stores, the shop decides what to collect and why. DetailHive is the service that hosts and processes that data so the shop can run its business. Other shops must not see it.
If you are a client of a detailing shop, start with that shop for questions about your appointment or your information. You can also reach DetailHive through Contact.
Cookies and sessions
We use cookies and similar storage for sign-in and to keep a session open with a refresh token. If 2FA is on, a new device may need a second factor. We do not use that session data to sell ads.
Retention
We keep account and shop data while the account is active. After an account closes, we may keep billing records, security logs, and other records we must keep. Job and client records stay with the shop’s account until the shop deletes them or asks us to close the account. We may keep call transcripts and summaries on the shop call log while the account is active. Device tokens stay while the app is installed or the account is active.
Security
We take reasonable steps to protect the data we host. No method of storage or transmission is guaranteed to be secure.
Children
DetailHive is built for shop businesses. It is not directed at children under 13. We do not knowingly collect personal information from children under 13.
Your rights
Shop owners can review and update much of their account and shop data in the app. People in the United States can contact us to access or delete account data. Use Contact if you cannot do it from the account.
We do not claim certification under GDPR, CCPA, or similar laws. If a request applies to client records a shop controls, we may need that shop to help complete it.
Changes
We may update this policy. The date at the top of this page will change when we do. See also our Terms of Service.
Contact
Operator: DetailHive, detailhive.io. Contact: detailhive.io/contact.