Expected
Privacy Notice
This notice explains how Expected handles information when companies coordinate service visits and customers follow them through a secure link.
Last updated August 19, 2026
1. Scope
This Privacy Notice applies to Expected’s websites, provider and technician workspaces, secure customer visit pages, and related authentication and transactional messaging. A service company may have its own privacy notice for the services it performs. That company controls the customer and visit information it enters into Expected and remains responsible for its own collection and use of that information.
2. Information we handle
Account and company information. We process names, work contact details, organization details, roles, login events, preferences, and company branding supplied by provider owners, administrators, dispatchers, and technicians.
Visit information. We process customer contact details, service and scheduling information, property information, assigned-technician details, visit status, messages, checklist results, work notes, photos, support requests, consent records, and payment status. Restricted property-access instructions are encrypted and are available only through authorized workflows.
Customer access information. A customer can open a high-entropy visit link without creating an account. Sensitive actions require a short-lived phone verification session. We record link, verification, and security events needed to operate and protect that access.
Payment and communications information. Stripe processes card and payout details; Expected receives transaction identifiers, amounts, status, receipts, refunds, and dispute information. Twilio processes transactional SMS delivery and phone verification. We record delivery status and opt-in or opt-out evidence.
Technical information. We may process device and browser data, approximate network information, diagnostics, security events, and privacy-filtered product analytics. We configure monitoring to exclude secure-link tokens, message contents, contact details, addresses, payment secrets, and other sensitive form contents.
3. How we use information
We use information to create and administer workspaces; schedule, assign, communicate, and document visits; show customers who is assigned and what is happening; support payments, receipts, tips, and refunds; send authentication and transactional messages; respond to support requests; prevent abuse; maintain audit history; troubleshoot the service; and comply with legal obligations.
Expected does not use the platform to make automated judgments about a technician’s safety or suitability. The launch product does not perform background screening, business-entity checks, license or insurance verification, government-database checks, or provider-document review.
4. How information is shared
Visit information is shared among the service company, its authorized team members, the assigned technician, and the customer according to their role and the current visit. A customer’s public link returns a limited visit view; messages, work evidence, payment, receipts, and support actions require additional phone verification.
We use service providers to operate Expected, including infrastructure, database and authentication, messaging, payment, error-monitoring, and privacy-filtered analytics providers. They process information for us under their own contractual and security obligations. We may also disclose information when required by law, to protect people or the service, or as part of a business transaction subject to appropriate protections.
We do not sell personal information or use it for cross-context behavioral advertising.
5. SMS and communication choices
Service companies must record the customer’s agreement before sending visit-related text messages. Transactional messages identify the service company and explain how to opt out. Reply STOP to stop text messages from the applicable messaging service; reply START to re-enable them where supported. Opting out of SMS does not cancel a service appointment, so contact the service company directly about scheduling or service changes.
6. Retention and security
We retain information for as long as needed to provide the service, preserve required visit and payment records, resolve disputes, enforce agreements, and meet legal obligations. Retention periods can vary by data type and by the service company’s instructions. Expected uses access controls, row-level authorization, private storage, encryption for restricted access notes, high-entropy revocable links, short-lived verification sessions, signed webhooks, and audit records. No security measure can guarantee absolute protection.
7. Your choices and requests
Provider and technician users can ask their organization administrator to correct workspace information. Customers should contact the service company shown on their visit page to correct visit or customer information, request access, or ask about deletion. You may also contact Expected at privacy@expected.link. We may need to verify a request and may retain information where permitted or required by law.
8. Children, location, and changes
Expected is a business service and is not directed to children under 13. The service is operated from the United States, and information may be processed where our service providers operate. We may update this notice as the product or law changes. We will post the revised date and provide additional notice when legally required.