Privacy Policy

Effective: August 15, 2026 · Last updated: September 10, 2026 · ProSVS LLC

What we collect

From service companies (our customers): account and billing details, business configuration, and the operational data the Service manages — schedules, jobs, invoices, and the customer records inside them.

From their customers (end customers): the details needed to book and service a job — name, contact info, service address, job history, and notes your service company keeps. ProService processes this on the service company's behalf.

From website visitors: what you submit on our forms (e.g., early-access requests) and standard server logs.

How we use it

To operate the Service: computing schedules, sending the confirmations/reminders/ follow-ups the service company enables, recovering unpaid balances they ask us to pursue, and improving reliability. We do not sell personal information.

Sharing

With the processors that run the Service, with the third-party systems the service company connects, and when the law requires. Each processor is bound to use data only to provide its service to us. We do not sell personal information.

• Supabase — database, authentication, and server functions.
• Vercel — application hosting.
• Stripe — card and bank (ACH) payment processing.
• Resend — transactional and marketing email delivery.
• Twilio — text messaging.
• Google — maps, drive-time routing, and calendar sync where enabled.
• Browserbase — a hosted browser we use to record a payment into a service company's field-service system, which has no payment API of its own. It sees only the pages needed to enter that payment.
• Anthropic — the model that drives that entry when the page layout changes, and that drafts marketing copy when a service company asks for a draft. It is not used to make decisions about a customer, and no data is used to train it.
• ServiceMonster and Intuit QuickBooks Online — the field-service and accounting systems a service company chooses to connect, under its own agreements with those vendors.

Payments

Card and bank payments are processed by Stripe. Full card numbers and full bank account numbers are entered directly into Stripe's hosted fields and never reach our servers; we receive and store only the card brand or bank name, the last four digits, the amount, and Stripe's own identifiers, so that a payment can be matched to an invoice and to a receipt. Any surcharge is calculated by us and shown before you pay.

Connected accounting systems (QuickBooks Online)

A service company may connect its QuickBooks Online company to the Service. When it does:

• What we access. Accounting data only, under Intuit's com.intuit.quickbooks.accounting scope: company information, customers, invoices and their line items, and the products and services list. We do not request or use Intuit's payroll, payments, or banking scopes.
• What we do with it. Compare what QuickBooks holds against the service company's own records, report the differences to that company, and — only when it instructs us — create or correct an invoice in its QuickBooks company.
• What we store. The connection itself (company id, company name, and OAuth tokens encrypted at rest with a versioned key), the mapping between the two systems' service catalogs, and the invoice numbers and amounts that a comparison found to differ. We do not copy the QuickBooks customer list into the Service.
• How to disconnect. A service company can disconnect at any time from its own settings, or revoke access from inside QuickBooks. Disconnecting deletes the stored tokens; the comparison records that reference invoice numbers are removed on the retention schedule below.
• We do not sell, rent, or share QuickBooks data, and we do not use it to train models or for advertising.

Advertising and measurement

A service company may enable ad conversion measurement on its public booking page. Where it is enabled, Google Ads and Microsoft Advertising tags load on that page and report that a booking was completed, so the company can tell which ads produced work. These tags set and read their own cookies. They run only on the public booking flow — never on the office application, the customer portal, or the payment page.

Retention and deletion

Operational records persist while the service company's account is active — service history is the product. After termination, exports are available for 30 days and data is deleted on our normal schedule. End customers can direct deletion requests to their service company; we assist.

Security

Encryption in transit and at rest, role-scoped access, and least-privilege service credentials. No system is perfect; we notify affected parties of breaches as the law requires.

Contact

micah@prosvs.com · ProSVS LLC, Hailey, Idaho