Business purpose
Support B2B prospect research by identifying candidate business addresses, collecting technical signals, and preparing records for human review. It is not a consumer directory, a permission substitute, or an autonomous bulk-sending service.
Evidence model
A result can include company identity, domain, mail-exchange, disposable-domain, role-account, catch-all, or account-response states, depending on configured sources. Each state has a checked time and a known limitation. Unknown is preserved when a provider does not supply a conclusive answer.
Quality boundary
Verification describes observed technical evidence at a point in time. A account can later change, reject, filter, or accept a message differently. Hard-bounce outcomes also depend on list age, sending infrastructure, authentication, recipient policy, and provider behavior.
Human control
People approve target relevance, identity confidence, suppression status, lawful basis, message text, and sending. This review is especially important when inferred email patterns, anonymous visitor records, or regional restrictions introduce uncertainty.
Credential handling
Data-provider and destination credentials belong in a runtime secret store with narrow scopes. They should not appear in prompts, templates, screenshots, or exported prospect records. Operators are responsible for rotation, revocation, monitoring, and incident response.
Data lifecycle
Installation and deletion are separate from downstream retention. Results may exist in agent logs, local files, CRM imports, engagement tools, or provider systems. A responsible deployment maps those stores and documents access, correction, suppression, and deletion paths.