Terms of service
The final terms will define the service relationship, customer responsibilities, scope acceptance, and approved job-action process.
Status: Approved policy text is not included in this preview.
Legal and policies
Policy topics, with final terms still to be approved.
Customers should see the relevant policy in plain language near the decision it governs, with a durable record of the version accepted for a booking or job action.
Informational preview only
This page is a product information architecture preview. It does not publish final legal terms, request agreement, or replace the approved policies that must be presented before booking and other protected actions.
What each approved policy must cover
The summaries below describe required topics without inventing contract language, deadlines, fees, warranties, or other business rules.
Privacy
The final notice will explain collection, use, sharing, retention, account access, and applicable privacy-request paths for customer and property information.
Status: Approved policy text is not included in this preview.
Scheduling and cancellation
The final policy will distinguish requested dates from confirmed appointments and explain approved cancellation or schedule-change rules.
Status: Approved policy text is not included in this preview.
Payment authorization
The booking flow will present approved consent for processor-hosted card setup and later authorization or capture before the customer agrees.
Status: Approved policy text is not included in this preview.
Communication consent
The final disclosure will cover required job communications, channel preferences, and a separate choice for any marketing communication.
Status: Approved policy text is not included in this preview.
Provider disclosures
The job-specific experience will show the approved fulfillment and provider-role disclosure at the stage where assignment is confirmed.
Status: Approved policy text is not included in this preview.
Accessibility
The final statement will describe accessibility support and an approved way to report a barrier or request assistance.
Status: Approved policy text is not included in this preview.
Customer-facing privacy boundaries
These product safeguards come from the application and security plans; they are not a substitute for the final privacy notice.
- Full addresses and sensitive record identifiers do not belong in public URLs.
- Customer photos and job documents remain private and require controlled access.
- Card details belong in processor-hosted fields, not application storage.
- Marketing consent remains separate from required transactional communication.
- Protected customer actions require verified, purpose-limited access.