Skip to content

Privacy

Operational information, handled plainly.

ValetLoop supports established dry cleaners running property-specific residential pickup programs. This notice describes the operational information needed for that bounded workflow.

What we handle

ValetLoop handles cleaner account and support contacts, organization and property configuration, resident household and contact details, schedule choices, consent, requests, manifests, audit and notification records, and provider identifiers needed for billing or email delivery. Supabase Postgres is the application source of truth. Published property pages contain cleaner-approved program fields, not household or contact data.

Why and with whom

We use this information to operate the portal, validate resident actions, show activity to the authorized cleaner, and produce a property-grouped manifest or CSV handoff. Cleaner subscription billing is handled through Stripe when configured; Stripe remains the provider-side source for its invoices and billing events. Transactional email is queued through the notification outbox and delivered through Resend when configured, with consent and opt-out controls. Local fixtures and adapters document the flow but do not establish live provider activation. Resident garment-care payments are outside ValetLoop.

The POS Switch Navigator is a separate anonymous, transient assessment. It uses only coarse event categories for product measurement; names, email, company, customer data, report contents, credentials, and raw URLs are not sent to analytics. Assessment state stays in the visitor’s browser session, reports are not saved to a cloud account, and optional property-plan or correction forms are private submissions rather than public content.

Retention and choices

The current operations policy lists recommended defaults, not legal approval: active product records while the account or property is active; audit, subscription, recurrence, and correction records for 7 years after last activity; notification and provider-delivery records for 24 months; failed or abandoned public-intake records for 90 days; support submissions for 24 months after closure; resident contact and household data deleted or anonymized 30 days after account or property deletion, subject to an approved legal hold; management-token hashes through expiry or revocation plus 30 days; application logs for 30 days and security logs for 180 days; export and deletion request records for 24 months without exported payloads; and daily backups retained 35 days with monthly recovery points for 12 months. Exact periods, legal holds, cancellation grace, and anonymization remain subject to founder and legal approval.

Cleaner account owners can download a redacted export or request deletion review from Settings. A confirmed deletion review remains cancellable during a 30-day review window and does not itself delete data. Any deletion operation must check legal holds and record boundaries for providers, storage, analytics, and backups; provider-side copies and backups may follow their own retention windows. Use Support for a correction or data request; residents can also contact the cleaner using the support details on their property page.

Terms · Support · Home