Skip to content
← Back to OttoServ

Current operational policy

Marketplace Privacy Policy

Version 2026-07-30.2 · Effective July 30, 2026

How OttoServ handles homeowner project, contact, media, voice, and operational data.

Information collected

We collect information you choose to provide, including project descriptions, location, contact details, photos, videos, documents, measurements, communications, and project decisions.

If you choose live voice, we may process audio, transcription, and AI-generated structured observations only after the separate voice notice and consent shown before microphone permission.

How information is used

We use information to organize intake, prepare scope and estimate materials, operate reviewed Marketplace workflows, prevent abuse, maintain security, support the project, and comply with law.

AI may help structure or summarize information. AI output can be incomplete or wrong and must not invent hidden conditions, dimensions, materials, or required work.

Sharing and processors

Intake is held for OttoServ operator review. No professional is contacted or receives the project merely because intake was submitted.

Information may later be shared with a selected or reviewed professional only through a separately controlled workflow. Current core processors are Vercel for application hosting and request delivery, Supabase for database, authentication, and storage services, Resend for delivery of website-contact notifications, and Google Workspace for the OttoServ operator mailbox.

Stripe may process payment and identity information only if a separately approved commerce step is activated. Retell may process live voice audio and transcripts only if the separate voice gate is activated and the homeowner affirmatively chooses voice. Those providers do not receive data merely because typed intake is submitted.

Recording, transcripts, and media

Project photos, videos, documents, measurements, audio, and transcripts are treated as project evidence. OttoServ limits them to the project and controlled review workflows, and does not publish them or use them for advertising.

Live voice is optional and remains unavailable unless its separate consent and provider controls are active. Typed intake remains available without recording.

Retention schedule

Unsubmitted information that remains only in browser storage stays there until it is submitted, cleared by the user, or removed with that browser’s site data. OttoServ cannot recover a browser-only draft.

General inquiries and privacy requests are retained for 24 months after the request is closed. Project intake, scope, communication, consent, audit, change, completion, warranty, and dispute evidence is retained for seven years after project closure. Project media that is not needed for a dispute, warranty, safety, fraud, accounting, or legal hold is scheduled for deletion three years after project closure.

Commerce records are retained for seven years after the transaction or project closes. Security and rate-limit records are retained for up to 12 months. A documented dispute, fraud review, legal hold, or legal obligation may extend the applicable period; OttoServ records that exception before extending retention.

Retention review and deletion are operator-controlled. A request does not silently erase consent, audit, financial, dispute, or safety evidence that OttoServ must preserve.

Security

We use reasonable safeguards and minimize duplicated contact information, but no system can guarantee absolute security.

Access, export, correction, deletion, and revocation

Use the OttoServ contact form and select the applicable privacy request to request access, a portable export, correction, deletion, a consent-preference change, or token or session revocation. Each submission receives a durable reference and is routed for operator review.

OttoServ verifies the requester before exposing, changing, exporting, deleting, or revoking data. Deletion remains subject to the retention exceptions above; when data must be preserved, OttoServ limits it to the required purpose and records the decision.

Marketing consent is optional and separate from operational communications. Withdrawing marketing consent does not end necessary project, security, or transaction messages.

Browser analytics

Optional third-party browser analytics and advertising scripts are disabled on current public OttoServ routes. OttoServ may still process first-party request logs, security signals, and attribution values submitted with a form to operate, secure, and understand the service.

OttoServ will not enable optional browser analytics that require consent without first providing the applicable choice.

This policy governs the current OttoServ Marketplace workflow from the effective date shown above. Questions or privacy requests may be sent through the contact form or to jonathan@ottoservco.com.