Trust
Responsible data use
Leead.io is built for teams that need accountable prospect research. AI assists the work, but people remain responsible for how the data is used. This page describes the boundaries and controls that help customers use Leead.io responsibly.
What is appropriate use
- Discovering companies and professionals from publicly accessible sources for legitimate sales, marketing, or recruiting purposes.
- Enriching and qualifying CRM records with source-attributed evidence.
- Maintaining suppression lists, consent records, and opt-out requests in your outreach process.
- Keeping humans in control of approval, outreach, and data retention decisions.
What is not allowed
- Indiscriminate mass harvesting of contacts or companies.
- Collecting data from private, authenticated, or access-controlled sources without authorization.
- Evading CAPTCHAs, rate limits, access controls, or platform terms.
- Using data to harass, stalk, surveil, or send unwanted bulk messages.
- Ignoring suppression lists, opt-outs, or do-not-contact instructions.
- Purchasing, selling, or reselling data in ways that breach source terms or applicable law.
Controls in the product
- Suppression lists — prevent outreach to opted-out or restricted contacts.
- Role-based access — limit who can run discovery, approve records, or execute outreach.
- Audit trail — record major data and outreach actions by tenant and user.
- Human approval — lead proposals, contacts, and outreach actions require appropriate permissions and review.
- Retention settings — configure data retention and suppression policies for your tenant.
Customer responsibility
Leead.io provides technical controls, but customers are responsible for using the platform lawfully in each jurisdiction. You must ensure your outreach, data retention, consent, and suppression practices comply with the laws and platform terms that apply to you. This page is guidance, not legal advice.
Evidence classification
Repository Confirmed — RBAC, audit logging, suppression lists, consent checks, role-based outreach permissions, and retention settings are implemented. Legal interpretation and final customer-facing terms require separate legal review.