The Human-Called standard
We call homeowners who got a contractor's estimate and didn't sign, and ask what happened. Those are real people giving us their time, so here is exactly how we treat them, in plain English, and a public record you can check that we delete what we said we'd delete.
What we promise every homeowner
A real person makes every call. One of our callers dials, listens and talks with you. Software never dials a homeowner on its own.
We tell you the call is recorded and transcribed. The first thing our caller says is "This call is recorded and transcribed by software." You can ask us to stop recording, or end the call, at any point.
It's research, never a sales call. We don't sell you anything on the call, and we never sell your information or share it with advertisers.
Your details are deleted 30 days after the readout. Your name, phone number, the transcript and our link to the recording are deleted 30 days after we present findings to the contractor. The call audio itself is deleted at our phone provider within 72 hours of the call.
De-identified answers are kept only if you agree. If you say yes, we keep your coded answers (the reasons, not your words) with nothing that leads back to you, so we can compare patterns across many contractors. If you say no, nothing is kept.
No AI voices call homeowners. Ever. Software helps us transcribe and organize notes, and a person reviews everything that goes into a report.
The full detail is in how we make calls and our privacy notice.
Proof of deletion
Each time our scheduled deletion removes homeowner details, it adds one entry to a public, append-only record: when it ran, how many records of each kind it deleted, and a fingerprint (hash) that covers the entry before it. If anyone changed or removed a past entry, every fingerprint after it would stop matching, and this page would say so.
The record holds counts only. No names, numbers, addresses, contractors or ids of any kind.
Loading the deletion record…
Check it yourself
Download the whole record as data from /api/public/trust/proofs?all=1. For each entry, oldest first, starting from 64 zeros:
hash = sha256( prev_hash + JSON of { counts, ran_at, run_id, seq } )
The JSON has its keys in alphabetical order at every level and no spaces. Each entry's prev_hash must equal the hash of the entry before it, and seq counts up 1, 2, 3 with no gaps.
Services we use
These outside services handle data for us. Each gets only what it needs to do its job.
Loading…