Data practices
How I handle territory and property data.
Territory Intelligence involves information about places and properties. This page sets out where it comes from, what I will and will not do with it, what clients agree to, and how to reach me about information I hold.
Last reviewed 16 August 2026
Where this stands today
Rules first, record second
Territory Intelligence launched in August 2026. No client campaign has run yet, so there is no long history to point at.
What follows is therefore the standard that governs the work from the first engagement onward, not a description of a system that has been running for years. I would rather say that plainly than imply an operational maturity that does not exist. Where a campaign needs legal review before it can run, this page says so.
1. Scope
Territory Intelligence may involve public records, licensed commercial datasets, client-provided information, geographic information, property characteristics, permit data, weather information and opportunity indicators derived from those inputs.
2. Roles
There is no single legal role that fits every engagement. Depending on the work and the intended use, WeLead Lab may act as a processor, service provider, contractor or controller. The role is established in the client agreement for that engagement rather than asserted here, because getting it wrong in either direction has consequences.
3. What gets recorded for every dataset
Before a dataset is used in a campaign, I record the following. If I cannot answer these for a source, I do not use the source.
- Source and provider
- Acquisition date
- License or terms
- Permitted uses
- Prohibited uses
- Fields included
- Geographic coverage
- Refresh date
- Accuracy limitations
- Personal-data classification
- Sensitive-data classification
- Client and intended campaign
- Approved channels
- Retention period
- Deletion method
4. Minimization
I collect and deliver only the fields reasonably necessary for the approved campaign. A phone number, email address or personal attribute does not go into a file because it happened to be available — it goes in because the campaign cannot run without it. A neighborhood mail campaign, for instance, usually needs no names at all.
5. Information I will not use
- Medical conditions
- Children’s information
- Precise mobile-device location
- Financial distress or creditworthiness
- Immigration status
- Religious belief
- Sexual orientation
- Biometric information
- Protected-class targeting
- Crime-victim information
- Private insurance information
- Social Security or financial-account numbers
This is not a list I would consider working around for a large enough engagement.
6. Facts, records and inferences are not the same thing
Every campaign distinguishes between a verified public fact, a licensed record, a derived indicator, a hypothesis, and something simply unknown. That distinction is the whole discipline.
A storm-exposure record is not proof of roof damage. A pool-property indicator is not proof that a pool exists or needs service.
Property and market data identifies indicators, not certainty. A home exposed to a storm may not have roof damage, and a property that looks likely to have a pool may not need service. The data tells us where there is a rational reason to look.
7. Security
Files are transferred over encrypted connections, access is restricted to the people who need it for the campaign, accounts holding data use multi-factor authentication, and files are deleted at the end of the agreed retention period. If information is exposed, affected clients are told promptly and told what actually happened.
I am one person, not an enterprise security organization. I describe the controls I actually operate and no more.
8. Channel review
Direct mail, EDDM, canvassing, email, telephone, text messaging and digital audience activation carry different legal, platform and licensing requirements.Possessing data does not authorize every channel. Phone and text are the most restricted; both are reviewed before use, and some campaigns need legal review before they can run at all. Where a source license does not permit a channel, that channel is not used, regardless of what the campaign would prefer.
9. Your rights
If you are a member of the public and want to know whether I hold information about your property, or want it corrected or deleted, or want to know where it came from — email [email protected] or call+1 (512) 336-9618. Tell me the address or the campaign you received, and I will tell you what I have, where it came from, and remove you from future outreach.
I will act on a suppression request whether or not the law obliges me to in your state.
10. What clients agree to
- Use the data only for the approved purpose
- Follow channel-specific law for mail, phone, text, email and canvassing
- Honor suppression and do-not-contact requests
- Keep files secure and restrict who can open them
- Stop using data once it has expired
- Delete it at the end of the agreed period
- Not enrich or combine it for a prohibited purpose
- Not resell or transfer it onward
Limitations
What this page does not do
Laws, provider licenses and local solicitation rules vary by jurisdiction and change over time. This page describes how I work; it is not legal advice, and it does not replace the client agreement for a specific engagement. Some campaigns — regulated calling or texting, sensitive categories, multi-state consumer data — require qualified legal review before activation, and I will say so rather than proceed.
If a signal is only available in certain counties, I will tell you that rather than advertise it as routinely available.
Questions about any of this
Ask me directly. Territory Intelligence explains what the capability does; Privacy covers this website; the client agreement covers a paid engagement.