Acceptable Use Policy

You may submit an address or source row only when you have a lawful and authorized reason to process it.

• Do not harvest, scrape, buy unlawfully obtained lists, or generate addresses for indiscriminate checking.
• Do not submit passwords, card data, government identifiers, health data, biometric data, precise location, information about children, or unrelated sensitive information.
• Do not use PeopleDat to determine whether a person belongs to a protected or sensitive group.
• Agencies must have each client's authority before submitting client data or inviting client users.

PeopleDat does not send campaigns and a verification result is not permission to contact someone. You remain responsible for every message sent through another service.

• Do not support spam, phishing, fraud, harassment, threats, impersonation, malware, or deceptive activity.
• Honor consent, suppression, unsubscribe, and do-not-contact instructions independently of verification.
• Comply with laws that apply to your messages, including sender identification, disclosures, postal-address, and opt-out requirements.
• Do not use a deliverable result to override a complaint, unsubscribe, or other reason an address should not be contacted.

You may not use PeopleDat as a consumer report or as the sole basis for a decision about employment, housing, credit, insurance, education, healthcare, legal services, public benefits, or another matter that produces a legal or similarly significant effect. A result does not prove identity, consent, ownership, honesty, or risk.

• Do not access another organization, workspace, list, result, report, key, widget, webhook, or account without authorization.
• Do not probe, scan, overload, disrupt, benchmark for competitive publication, reverse engineer protected controls, or test vulnerabilities without written authorization.
• Do not bypass authentication, idempotency, exclusions, rate limits, credit caps, spending controls, origin restrictions, anomaly pauses, or payment safeguards.
• Do not hide automation, create accounts or keys to evade a limit, or use compromised credentials.
• Do not upload malicious files or send a webhook to a destination you are not authorized to operate.

You may integrate PeopleDat results into your own authorized internal workflow or customer service. You may not resell raw PeopleDat output, create a competing verification database, publicly benchmark the Service without a reproducible and fair methodology, remove required report attribution, or represent PeopleDat as endorsing you or your decisions.

API keys, webhook secrets, report tokens, and MCP credentials must be protected. Public widget site keys may be embedded only on configured origins and within the caps set for that widget.

PeopleDat may investigate suspected misuse and may limit, suspend, or terminate affected access when reasonably necessary to stop harm, protect another tenant, preserve security, comply with law, or enforce the Terms. When practicable, PeopleDat will give notice and an opportunity to cure. Serious, repeated, or intentional abuse may result in immediate action.

Report suspected abuse to [email protected]. Include the relevant workspace, request, or event identifier where available, but do not email credentials, full lists, or unrelated personal data.