Privacy
Last updated 2026-11-18.
PingPermit is developing a permissioned human-judgment evaluation service for AI agents. The new public workbench is fictional and unreviewed; it is not a collected human dataset. Existing building-permit reports and subscriptions remain available to current customers. This page explains how we handle inquiries, site activity and existing permit-service information. Questions go to tommy@pingpermit.com.
Human-judgment pilot inquiries and practitioner interest
The local workbench and pilot brief. Choosing a fictional demo action or writing a draft brief stays in your browser. Copying or downloading is local. The Email buttons open your own email app; nothing is sent to PingPermit unless you review and send the message. Do not put real customer or employer-confidential data into a draft.
If you email us. We receive the address, message, and professional or project details you choose to send to tommy@pingpermit.com, through our business mailbox. We use them to respond, assess a proposed evaluation scope or reviewer fit, and handle removal requests. Please do not send private identity documents, customer CRM exports, sensitive personal information, or employer/client confidential materials. An inquiry is not consent to a research dataset or AI training.
Any future paid research. We have not recruited a human review panel or collected human judgments through this prototype. Before asking anyone to perform paid review, we must separately confirm the purpose, participants, compensation, rights, recipients, security, retention, withdrawal limits and appropriate agreements. Training, redistribution, public release and simulation are not included in an evaluation-only inquiry.
What we collect, and why
When you buy a report. The address you looked up, and the email address you give Stripe at checkout — that is where the report and its permanent link are sent. Your card details go to Stripe and never reach us; we see that a payment succeeded, not the number.
When you create an account. Your email address, and whatever else you choose to type on the form: a name, a company, a phone number, the area you work in, a note. The email is where the daily digest and your sign-in link go. Nothing on the form is required except the email.
When you use the site. Your browser stores a random visitor ID (localStorage) and session ID (sessionStorage). Page views and clicks go to our own server with these IDs, the page path, referring site, device category and limited attribution tags; the analytics path excludes query parameters. For a newly seen visitor ID, the server may send the request IP address to ipinfo.io for network information and retain a salted IP hash, network organization and type, approximate city/region/country, first and most recent page paths, visit count and timestamps linked to that ID. These are pseudonymous records, not proof of a visitor's identity, employer or buying intent. Render also processes ordinary request logs, including IP address, user agent and time. We use these records for site measurement and administration, not to claim someone is a qualified buyer. There are no advertising cookies or third-party analytics scripts.
Email we send
Subscribers get a welcome email and the daily digest. Existing pilot users may receive reminders about their remaining access. Each one carries a working one-click unsubscribe, and the digest can be switched off from the top of your feed. Report buyers get the report itself and nothing else.
Earlier permit-business communications used tommy@pingpermit.com. Contact suppression and no-contact requests remain in force; the human-judgment launch does not authorize new unsolicited email campaigns. You can ask us not to contact you again.
Mail leaves through Google Workspace on our behalf.
Permit records are public
Everything in a report or in the feed comes from a city's own published permit records. Where a city names the contractor, applicant or owner on a permit, that name appears as the city published it — we do not add to it, and we cannot change the city's record. If a page about you or your business is wrong, write to tommy@pingpermit.com and we will look at it with you.
Looking up an address sends that address to the city's data portal, because that is where the records live.
Who else sees your data
Stripe processes payments; Render hosts the site and application; a separate managed PostgreSQL database provider stores site and customer records; and Google Workspace handles business email. For the network-information step described above, ipinfo.io receives the visitor's request IP address. Looking up an existing permit record may also contact the relevant public agency's portal, as explained above. We do not sell personal data. A future human-judgment study will require its own reviewed participant and customer data-handling terms.
How long we keep it, and your rights
We keep an existing permit signup while the pilot or subscription exists, and an order while its report link is live — the link is meant to keep working. We retain voluntarily emailed inquiries as needed to respond and document follow-up or no-contact preferences, subject to appropriate deletion requests and necessary records. Analytics event rows record pseudonymous browser/session IDs, time, path, referrer, device and limited attribution information rather than names or emails. Network-profile records can hold the salted IP hash, network organization/type, approximate location and visit history described above. We do not describe those identifiers as fully anonymous. Server request logs are kept briefly by our host.
Email tommy@pingpermit.com to see what we hold about you, correct it, or have it deleted. Unsubscribing from the digest is immediate and needs no email.