Privacy

Privacy policy

Effective May 23, 2026. We collect what we need to book your clean, and nothing else. We never sell your data.

The short version

1. What we collect

You give us: name, email, phone, home address, home details (size, bedrooms, etc.), service preferences, payment method (via Stripe — we never see the card number), SMS consent, and messages you send to Clean Kasa.

Automatic: IP address, device + browser fingerprint (for fraud prevention), pages visited (for product improvement). We do not use third-party advertising trackers.

2. How we use it

To match you with a cleaner, communicate about your booking, charge for the visit, and send the receipt. To investigate complaints or quality issues. To improve the product.

3. Who we share it with

The cleaner assigned to your booking sees: your first name, last initial, address, home details, and any visit notes. They do not see your email, full name, or payment method.

Stripe processes payments. Their privacy policy: stripe.com/privacy.

Resend sends our transactional email.Twilio sends our SMS reminders, booking updates, cleaner job offers, verification codes, and support replies. Both see your email/phone but not your payment details.

We do not sell personal information. We do not share mobile phone numbers, SMS consent records, or mobile opt-in information with third parties for marketing or promotional purposes.

4. How long we keep it

Booking records: 7 years (for tax + dispute purposes). Communication threads: 3 years. Payment records: as required by Stripe (10 years). Marketing emails opt-in only; opt out anytime.

5. Your rights

Request a copy of all data we hold about you, request deletion, or correct inaccurate information from your account page or by texting Clean Kasa at (415) 779-7513. We respond within 30 days.

California residents: CCPA rights apply. We do not sell your information; opt-out is automatic. Use the same contact option above to request the specific categories of data we hold.

6. Security

All data is encrypted in transit (TLS 1.2+) and at rest. Payment data is tokenized by Stripe — we never see it. Operator + cleaner access is gated by email/password authentication with a per-request Content-Security-Policy nonce; sessions are HttpOnly cookies scoped to the operator portal.

7. Changes

If we update this policy, we'll post the updated version here at least 14 days before the change takes effect.