Your booking data.

Effective September 20, 2026. LocalService is operated under the Trinity River AI name. Contact team@trinityriverai.com.

What we collect

We process service searches, postal code, requested time, service options, vehicle details you supply, customer name and email, service address, notes, booking state, and payment resource identifiers. Please avoid including sensitive information in booking notes.

How it is used and shared

We use these details to match services, obtain provider approval, process customer-approved test payments, and manage bookings or support requests. Authorized operators and the selected provider need booking details to coordinate service. Supabase stores records; Vercel hosts the application; Stripe hosts Checkout and processes payments. AI platforms such as Meta Muse receive the responses to requests they make on your behalf and apply their own privacy policies.

LocalService does not receive or store raw card numbers. Stripe handles payment information. Muse-native payment tokens are not accepted in this pilot. We do not sell booking information or use it for targeted advertising.

Retention and your choices

Booking, audit, idempotency and payment reference records are retained during the pilot for reconciliation and support. Automatic deletion is not yet enabled. Request access, correction or deletion by email; we will verify your request and explain any records that must be retained for transaction, security or legal reasons. Rate-limit counters expire and are removed during subsequent requests. Application logs contain request identifiers, route names, response status and timing, not request bodies or authorization credentials.

Protection

Server credentials stay server-side. Booking access requires both connector authentication and a booking-specific secret. Database tables deny public access. No system can guarantee absolute security; send suspected issues to our support contact.