Preview privacy notice

Last updated October 6, 2026.

This private development preview requires a final legal business identity, privacy contact, vendor review and approved retention policy before public launch.

Information in the preview

Requests collect contact information, ZIP, service needs, timing preferences, scope and optional photos. Partner applications include business and qualification statements. Service records include assigned account emails, scope, timing notes, checklist entries, concerns, resolutions, photos and operator reviews. Do not submit payment details, access codes, identity documents, health information or unrelated sensitive material.

Who can see a service record

The operator and assigned provider can access the working record. An assigned customer sees the job’s scope and timing note, approved summaries and specifically approved photos. Customer accounts can record a concern. The site’s owner-only access remains in place until participants are explicitly granted access. Photo files are stored privately and checked for access on each request.

Photo permission and timestamps

Ask permission before operational photos and avoid faces, private documents and personal items. Marketing use requires separate permission. A customer may decline photos; an alternative observation can be recorded. Uploads are resized for review and do not preserve original image metadata through the normal upload form. Keep original evidence securely when needed. A recorded timestamp reflects receipt by the system, not independently verified capture time.

Automation and optional AI

Rules flag missing checks and draft progress updates. Optional AI drafting is disabled until configured. For checklist update drafts, only the service category and structured checklist/evidence status are sent to the configured OpenAI service; names, contact details, free-text notes and photos are excluded from that feature. Separate relationship summaries and lead-conversation coaching can send relevant CRM contact details, saved conversation text, website evidence and an operator-supplied reply to OpenAI when enabled and requested. These are different workflows; do not enter unrelated sensitive information. AI requests use store:false, which is not a promise of zero provider retention. A human must approve every customer-facing update. Gmail sending is not implemented. Reviewed missed-call text recovery can use Twilio when configured and explicitly enabled; it begins paused. Stripe Checkout is available only when configured for a separately approved order. Provider payouts and automatic refunds are not implemented. Advertising trackers are not used.

Optional AI planning conversation

The owner-only AI concierge preview is disabled until securely configured. If enabled, it asks for permission before sending your conversation text to OpenAI. Unlike checklist-only drafting, this feature sends the free-text messages you enter, previous turns, and public SRVCS service guidance. Do not enter contact details, access codes, payment data or sensitive information. Chat is held in page memory; moving your own details into a request is optional and submission is a separate step. API requests use store:false; this is not a promise of zero provider retention. Vendor retention and data settings require review before public launch.

Connected services and business research

Google Workspace connections can import authorized mailbox history into the private CRM. Read-only access logs messages; the separate optional mailbox-management authorization permits archive and Trash actions. CRM exclusion changes SRVCS records without deleting Gmail messages. Twilio connections can import call and text history and track reviewed recovery messages. Stripe handles checkout and payment information directly; do not enter card or bank details into ordinary SRVCS forms. When connected, Apify searches business listings and Firecrawl reads public websites for business and contact evidence. Public business contact details and their source links can be saved for review; a listing does not establish consent to marketing, provider qualification, or a customer relationship. Vapi connection inspection does not itself activate voice calls. Each vendor’s policies and account settings govern its own processing.

Contact preferences

Request consent allows discussion of that request when communication is activated. It does not authorize automated marketing calls or texts. Future communication, payment and analytics tools require disclosures and consent reflecting the tools actually used.

Correction and deletion

Contact hello@getsrvcs.com for access, correction, deletion or communication-preference requests. Include the reference number rather than additional sensitive information. Activity entries preserve corrections as subsequent entries; operator-assisted deletion is separate and must respect applicable retention duties. A final legal business identity and approved retention schedule remain launch requirements.

Hosting

The site uses database and private object storage supplied through its hosting platform. Authentication cookies may control access. A public release requires a notice that accurately identifies the business, vendors, purposes and applicable privacy rights.