CloseCheck collects nothing.
That is not a posture, it is how the thing is built. There is no account, no server that holds your work, no analytics and no advertising or tracking SDK of any kind.
What stays on your device
Saved files and their checklists, your name and contact details if you choose to add them to reports, your language and role preferences, and whether you have seen the intro. On the web these live in your browser's local storage; in the iOS app they live in the app's own container. Clearing your browser data, or deleting the app, deletes them. Nobody else can see them, including us — there is nowhere for them to go.
The one network request
If you type a street address and press Look up, that address is sent to the United States Census Bureau geocoder so it can be resolved to a city and county. That request is optional — picking the jurisdiction from the list or searching by name never sends anything anywhere, and gives the same answer. We do not store the address, log it, or attach it to any identifier. The Census Bureau's handling of the request is governed by their own policy.
The ordinance data
The whole dataset ships inside the app and the page. Looking up a jurisdiction is a local operation: no request is made, so no record exists of which properties you checked.
Links out
Every requirement links to the issuing agency's own page so you can verify it. Those are ordinary links to other organisations' websites, and what happens once you follow one is covered by their policies, not this one.
Children
CloseCheck is a professional reference tool with no content directed at children, and since it collects nothing it collects nothing from anyone of any age.
Changes
If this ever stops being true — if a feature genuinely needs a server — this page will say so before that feature ships, not after.
Last updated 10 August 2026. Questions: closecheck@tcclss.com