Privacy Policy
Last updated 29 September 2026
SignalHarvest is run by Sebastián Fernández in Asheville, North Carolina. It reads building-permit filings published by county and city governments in western North Carolina and shows contractors the projects near them that have no builder attached yet.
What we collect
- Public records. Permit filings as the county publishes them: address, work described, filing date, permit number, and whatever owner or applicant contact the county chooses to publish. We do not add to this from private sources.
- Your account. If you sign up or open a shared link, we store the email address you gave us, which leads you looked at, and which contacts you unlocked.
- Correspondence. If you email us, that thread is stored so we can answer it.
How we use Google user data
SignalHarvest connects to one Google account — signalharvestdb@gmail.com, our own outreach mailbox — so that mail sent to contractors and their replies stay on one record. No customer ever connects their own Google account, and we never ask you to.
- gmail.compose — to write and send outreach mail from that mailbox, and to save drafts for review before sending.
- gmail.readonly — to read replies to that outreach so a conversation can be matched to the right contractor.
From each message we store only the envelope — sender, recipients, subject, timestamp, thread id — and a short snippet used to match the reply to a contractor. Message bodies and attachments are not stored. Nothing from that mailbox is shared with any other customer, sold, or used to build any profile.
SignalHarvest's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to develop, improve, or train generalised AI or machine-learning models.
What we never do
- We do not sell or rent your information.
- We do not use Google user data for advertising.
- We do not let humans read that mailbox except to operate and support the service.
Who else touches the data
Only the vendors that make the product run, and only for that purpose: Google (mail), Vercel (hosting), Resend (notification email), Clerk (sign-in), Twilio (checking whether a published phone number is still in service), and Anthropic (drafting outreach copy, where our prompts are excluded from model training). Our database runs on a server we control in Germany.
How long we keep it
Permit records are kept as long as they are useful, which is a matter of months. Account and correspondence data is kept while the account is open and for twelve months after. Disconnecting the Google account stops all access immediately; revoking it at myaccount.google.com/permissions does the same from Google's side.
Your choices
Write to signalharvestdb@gmail.com and ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. We answer in writing within 30 days.
A note on permit records: the owner names, addresses and phone numbers in them are published by the county as public record. We can remove you from our copy, and we will on request, but we cannot remove you from the county's.
Changes
If this policy changes in a way that matters, the date at the top changes and anyone with an account is emailed.
Contact
Sebastián Fernández · SignalHarvest · Asheville, North Carolina · signalharvestdb@gmail.com