Privacy policy

Public-record data only, from two kinds of source: open place data published by Foursquare under the Apache License, Version 2.0, and licensing files published by state boards. The sources, their file dates, their compliance tier, and every modification this site makes are listed on the methodology page.

None of it was collected from the business directly, and none of it was bought. Where a state file publishes a home address because the contractor works from home, a residential screen suppresses the street line, the coordinates, and any personal phone number, and the record publishes with its city only.

A business that claims its listing supplies its own contact details, hours, services, and service area. Those are held separately from public-record data, labeled on the page as provided by the contractor, and removed when the claim is withdrawn.

Server logs, kept for a period this document will state once retention is settled, covering the request path, the response, a truncated network address, and the user agent. They exist to keep the site up and to find abuse.

First-party analytics recording which page was viewed, which hub or profile it was, and where the visit came from. No advertising trackers, no cross-site identifiers, no data broker pixels, and nothing sold or shared for advertising. There is no third-party script on any page of this site.

A removal request and a correction both collect the requester's name, email address, an optional phone number, the stated relationship to the business, and whatever the requester writes in the free-text fields. Each submission is stored with the date and time, the network address it arrived from, and the browser's user agent, as proof of when the request was made and by whom.

That proof exists for one reason: a request to take a record down, or to change what a public record says, is an assertion, and the site has to be able to show what was asserted and when. The email address is used to verify the request and to reply to it. It is added to no list. It is never used to contact the business for any other purpose, and it is never sold, shared, or handed to any contractor.

The response target is five business days. A verified removal is stored as a suppression keyed to the record and to a fingerprint of the business name plus its city, state, ZIP, and county, and that suppression is retained indefinitely, because it is what stops the record from returning with the next data file.

No homeowner request form is live in this release. When one ships it will collect contact details, the property's ZIP code and property type, the trade and the named problem, urgency, whether an insurance claim is involved, and availability windows. Each of those exists to route the request or to gate it, and this document will say which does which before the form goes live.

The property address is not collected beyond what routing needs. Home-service requests are not health data, and nothing on this site collects health data of any kind.

Requests reach only contractors who claimed a listing and supplied their own contact details and their own express written consent, captured separately for calls and for texts, with the disclosure text, the timestamp, the network address, and the user agent stored as proof for five years.

This site never solicits a business at a phone number, mailing address, or email taken from a dataset. The single carve-out is a verification callback or postcard initiated by a claim, which uses the number or address on record for verification only and is logged. No text message is sent to anyone in this release.

Consent is withdrawn by replying to any message, by using the withdrawal link in it, or by writing to the address in the last section. Withdrawal stops routing to that contractor and is recorded with the same proof fields as the consent it revokes.

Contact information is never sold, and it is never sent to a business that did not ask for it. There is no lead sale, no data broker relationship, and no advertising partner.

Processors that hold data on this site's behalf are the hosting platform, the database host, and the messaging provider used for verification. Each is bound by contract to use the data only to provide that service. They are named in the final version of this document.

A homeowner request, once one exists, goes to the contractors the homeowner selected by name, and to nobody else.

A removal and a correction are verified the same way a claim is, and neither requires a claim. The response target is five business days. A removed URL returns HTTP 410 and the record is suppressed from every later release.

Every confirmation states the refresh cycle for the source in question, so a change is not silently overwritten by the next file, and links the upstream source so the record can be fixed at origin as well.

Stated per source and per record type in the final version. What is settled now: consent proof is kept five years, because that is what makes it usable; suppression records are kept indefinitely, because a suppression that expires stops working.

The rights a national directory has to honor, the process for exercising each one, and the identity verification standard for a request are stated in the final version. The removal and correction forms already deliver the two rights people actually use here, and neither requires an account.

Two counters are kept because two legal thresholds turn on them: distinct homeowners whose data is held, and distinct natural persons in the license layer. Both alert at 25,000 and are reviewed before 50,000. The current values are published on the methodology page.

A monitored address for privacy questions, and a named person responsible for them, are stated in the final version. Until then, a removal or correction request filed from a listing reaches a person and gets a reply inside five business days.