Skip to main content
Peopledat Logo

PeopleDat legal

Terms of Service

Effective August 29, 2026

The business agreement for using PeopleDat, including team authority, customer-data responsibilities, verification limitations, billing, integrations, and dispute terms.

Plain-English scope: PeopleDat verifies email addresses; it does not grant permission to contact people or guarantee delivery. Customers control what they submit, who can access it, and how results are used.

1. Agreement and defined terms

These Terms of Service are a binding agreement between Pixel Reef LLC, a Florida limited liability company, doing business as PeopleDat (“PeopleDat,” “we,” “us,” or “our”), and the person or legal entity that accepts them (“Customer,” “you,” or “your”). They govern the PeopleDat website, account, email-verification application, APIs, widget, MCP endpoint, and related services (collectively, the “Service”).

You accept these Terms when you create or use an account, click an acceptance control, purchase the Service, or access a feature that refers to them. If you accept for a company or other organization, you represent that you have authority to bind it. If you lack that authority or do not agree, do not use the Service.

“Customer Data” means email addresses, uploaded or pasted source rows, file and list names, exclusion rules, integration configuration, and other information submitted to the Service for Customer. Verification results, usage records, and account configuration associated with Customer are “Customer Records.”

2. Eligibility and business use

The Service is offered for business and professional use. You must be at least 18 years old and legally able to enter this agreement. The Service is not directed to children or intended for personal, family, or household use. Non-waivable consumer rights still apply if the law treats a particular transaction as consumer use.

If Customer is an agency or service provider, Customer represents that each client has authorized Customer to submit its data, create a client workspace, invite client users, and receive results. Customer remains responsible for its acts and omissions and for instructions it gives PeopleDat on a client's behalf.

3. Accounts, organizations, and authority

Customer must provide accurate account information, keep sign-in methods and credentials secure, promptly remove access that is no longer authorized, and notify PeopleDat at [email protected] of suspected compromise. Customer is responsible for activity performed through its accounts and credentials unless caused by PeopleDat's breach of these Terms.

An organization owns its billing relationship, pooled credits, memberships, and workspaces. Owners control billing, ownership, team access, data, developer settings, and workspace administration. Administrators may manage team and workspace operations but may not access owner-only billing and ownership controls. Contributors may create work and spend credits in granted workspaces; viewers may only view and download permitted records.

Owners and administrators can access every workspace in their organization. Members receive explicit workspace access. Client users can access only their client workspace, while agency owners and administrators retain access to all client workspaces. Customer is responsible for least-privilege access, ownership transfer, spending caps, and periodic access review.

4. What the Service does—and does not do

PeopleDat provides point-in-time email-verification workflows through single checks, lists, lossless imports, exports, teams, agency workspaces, exclusions, schedules, APIs, signed webhooks, aggregate reports, a browser widget, and a hosted MCP endpoint. Feature availability depends on workspace permission, technical limits, and the subscription or PayGo entitlement shown in the Service.

PeopleDat is not a contact database, lead-enrichment service, CRM, outreach sequencer, email sender, consent service, identity service, consumer-reporting agency, or inbox-placement guarantee. It does not determine whether Customer may contact a person. Customer must maintain suppression, unsubscribe, consent, and other source-of-truth records independently.

Verification reflects technical signals available when a request is processed. A status, policy action, reason, score, or technical check is advisory and can become stale. A nullable check can mean it was not performed; it is not the same as a negative check. Results do not prove identity, consent, ownership, engagement, future delivery, or inbox placement.

5. Customer Data and privacy responsibilities

As between the parties, Customer retains its rights in Customer Data. Customer grants PeopleDat and its subprocessors a limited, non-exclusive right to host, copy, transmit, transform, verify, cache, display, and delete Customer Data only as needed to provide, secure, support, and maintain the Service; follow Customer's documented instructions; comply with law; and exercise rights expressly described in these Terms and the Privacy Policy.

Customer represents that it has all rights, notices, permissions, and lawful bases required to submit and use Customer Data and to instruct PeopleDat to process it. Customer must respond to individuals whose data it controls and must not use a verification result to evade an opt-out or revive an address that should remain suppressed. An exclusion is a processing instruction; it does not establish consent or make an unverified address deliverable.

Source columns can contain more than an email address. Customer must minimize what it submits and must not upload passwords, payment-card data, government identifiers, protected health information, biometric data, precise location, information about children, or other regulated or sensitive information unless PeopleDat first agrees in a signed writing that specifically covers that information.

6. Acceptable use

Customer and its users must follow the Acceptable Use Policy, which forms part of these Terms. Among other things, Customer may not use the Service for unlawful surveillance, harassment, unlawful discrimination, credential attacks, address harvesting, abusive messaging, tenant probing, resale of raw results, or circumvention of security, access, rate, spending, or payment controls.

Customer may not use a result as the sole basis for an employment, housing, credit, insurance, education, healthcare, legal-services, or other decision that produces a legal or similarly significant effect about a person. The Service is not designed for regulated eligibility decisions.

7. API, MCP, webhooks, reports, and widget

API keys and webhook signing secrets are credentials. Customer must protect them, grant only needed scopes, set appropriate limits, and promptly rotate or revoke exposed credentials. Browser widget site keys and Origin headers are public identifiers, not authentication secrets. Customer may not bypass idempotency, workspace boundaries, rate limits, credit caps, anomaly controls, or other safeguards.

Customer must secure webhook receivers, verify signatures over the exact raw body, prevent replay, and ensure each endpoint remains authorized. Customer is responsible for every system or agent it connects through REST or MCP and for setting explicit maximum credits on billable MCP tools. A connected MCP client may disclose tool inputs or outputs to the client's own model or platform provider; PeopleDat does not control that provider or its terms.

Aggregate report links are bearer credentials: anyone with the token can view the report until it expires or is revoked. Customer must share them only with authorized recipients. If Customer installs the widget, it must give visitors appropriate notice, configure exact HTTPS origins and a daily cap, and use only supported blocking categories. Because widget responses are advisory and fail open during specified error conditions, the widget must not be Customer's only security, consent, fraud, or eligibility control.

8. Fees, subscriptions, taxes, and credits

Prices, credit quantities, billing frequency, and amounts due are shown before purchase. Paid subscriptions renew monthly until canceled. PayGo purchases are one-time purchases. Customer authorizes PeopleDat and Stripe to charge the selected payment method and is responsible for applicable taxes that are not collected by PeopleDat, except taxes based on PeopleDat's net income.

An organization has one pooled credit balance. Active subscriptions and settled PayGo purchases can unlock teammates and live developer features without per-seat billing. Member, key, widget, schedule, and client- workspace caps restrict spending but do not create separate balances or guarantee capacity.

Unknown/provider-failure and policy-excluded results consume no verification credit. Known usable cache hits and other conclusive results consume one normal credit. Credits are contractual units for use of the Service, have no cash value, and cannot be sold or transferred outside the organization. Current renewal, cancellation, refund, failed-payment, and PayGo terms appear in the Billing, Cancellation & Refund Policy, which forms part of these Terms.

9. Third-party services and integrations

The Service relies on infrastructure, verification, payment, email, security, analytics, and sign-in providers identified on the Subprocessors page. PeopleDat is responsible for its selection and use of subprocessors as required by applicable agreements and law, but it does not control third-party services that Customer independently connects, visits, or instructs the Service to contact.

A third-party outage, changed interface, or blocked destination can affect a feature. PeopleDat may replace a provider or integration when reasonably necessary to maintain security, availability, or functionality and will update its disclosures when the change materially affects described processing.

10. Retention, exports, and shared records

A workspace chooses whether encrypted original source columns remain for 7, 30, or 90 days, or until list deletion; 30 days is the default. Once source columns expire, verification results can remain but lossless original-column exports are unavailable. Generated exports expire after 30 days. Other retention periods and deletion limits are described in the Privacy Policy.

Shared lists, jobs, results, exports, audit events, and creator attribution belong to the organization or workspace in which they were created. Removing a person or workspace grant does not delete shared records. Customer must export information it needs before retention expires, a workspace is archived, or access ends.

11. Intellectual property and feedback

PeopleDat and its licensors own the Service, software, interfaces, documentation, branding, and other PeopleDat materials. Subject to these Terms and payment of applicable fees, PeopleDat grants Customer a limited, non-exclusive, non-transferable, revocable right to use the Service during the agreement term for Customer's internal business purposes. No source-code, trademark, patent, or other ownership right transfers.

If Customer voluntarily gives feedback, Customer permits PeopleDat to use it without restriction or payment, provided PeopleDat does not identify Customer publicly as the source without permission. Feedback does not include Customer Data or confidential information.

12. Confidentiality and security

Each party will use the other party's non-public information only to perform or exercise rights under this agreement, protect it with reasonable care, and disclose it only to people who need it and are bound by appropriate confidentiality duties. This does not cover information that is public without breach, already lawfully known, independently developed, or lawfully received without restriction. A legally compelled party may disclose information after giving notice when legally permitted.

PeopleDat uses the safeguards described in the Privacy Policy and security documentation. No online service is risk-free. Customer is responsible for its endpoints, devices, credential storage, integrations, and copies of data exported from the Service. Security concerns should be sent to [email protected] and not publicly disclosed before PeopleDat has a reasonable opportunity to investigate and remediate.

13. Suspension and termination

Customer may stop using the Service at any time and may cancel a paid subscription as described in the Billing Policy. PeopleDat may restrict or suspend access when reasonably necessary to address a material violation, abuse, a security risk, suspected fraud, nonpayment, legal requirement, or threat to another customer or the Service. When practicable, PeopleDat will give notice and a reasonable opportunity to cure.

PeopleDat may terminate this agreement for an uncured material breach or if it discontinues the Service. Upon termination, Customer's right to use the Service ends. Sections that by their nature should survive—including accrued payment duties, confidentiality, ownership, disclaimers, indemnity, liability limits, dispute terms, and retention obligations—remain effective.

Customer may lose access to lists, results, and exports after termination and should download needed records beforehand. Termination does not require PeopleDat to delete shared or financial records sooner than the Privacy Policy, a legal hold, or applicable law permits.

14. Disclaimers

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE AND RESULTS ARE PROVIDED “AS IS” AND “AS AVAILABLE.” PEOPLEDAT DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. PEOPLEDAT DOES NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, COMPLETELY SECURE, OR THAT A RESULT WILL PREDICT DELIVERY, INBOX PLACEMENT, ENGAGEMENT, IDENTITY, OR CONSENT.

These disclaimers do not exclude an express written commitment in an order form or a warranty, right, or remedy that applicable law does not permit the parties to exclude.

15. Customer indemnity

To the extent permitted by law, Customer will defend PeopleDat and its officers, members, employees, and contractors against a third-party claim arising from Customer Data, Customer's collection or use of an address or result, its messaging or widget practices, its integrations, or its material violation of these Terms or another person's rights, and will pay finally awarded damages and reasonable settlement amounts.

PeopleDat must promptly notify Customer, allow Customer to control the defense and settlement, and provide reasonable cooperation at Customer's expense. Customer may not settle a claim in a way that admits fault by PeopleDat or imposes a non-monetary obligation on PeopleDat without written consent.

16. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, GOODWILL, BUSINESS OPPORTUNITY, OR DATA, EVEN IF ADVISED THAT SUCH LOSS WAS POSSIBLE.

EXCEPT FOR CUSTOMER'S PAYMENT OBLIGATIONS, CUSTOMER'S INDEMNITY OBLIGATIONS, OR A PARTY'S FRAUD, WILLFUL MISCONDUCT, OR MISAPPROPRIATION OF THE OTHER PARTY'S INTELLECTUAL PROPERTY, EACH PARTY'S TOTAL AGGREGATE LIABILITY ARISING OUT OF THE SERVICE OR THESE TERMS WILL NOT EXCEED THE GREATER OF US$100 OR THE AMOUNT CUSTOMER PAID OR PAYABLE TO PEOPLEDAT DURING THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY.

The exclusions and cap apply to the extent permitted by law, regardless of the theory of liability, and do not limit rights or remedies that cannot lawfully be waived.

17. Governing law and disputes

Florida law governs these Terms without regard to conflict-of-law principles. The state courts located in Hillsborough County, Florida, and the United States District Court with jurisdiction over that county have exclusive jurisdiction over disputes arising from these Terms or the Service, and each party consents to that jurisdiction and venue. Either party may seek temporary or injunctive relief in any court with jurisdiction to protect confidential information, security, or intellectual-property rights.

Before filing a claim, a party will give the other written notice and allow 30 days for good-faith informal resolution, unless delay would cause material harm or a limitations period would expire. These Terms do not require arbitration and do not contain a class-action waiver.

18. Changes and general terms

PeopleDat may update these Terms to reflect service, legal, or security changes. Material changes will take effect prospectively after reasonable notice through the Service or the account email. If Customer does not agree, its remedy is to stop using the Service and cancel renewal before the change takes effect. Changes do not retroactively alter an accrued payment or claim.

Neither party is liable for delay caused by events beyond its reasonable control, except payment obligations. Customer may not assign these Terms without PeopleDat's written consent; PeopleDat may assign them with a merger, reorganization, sale of substantially all relevant assets, or by operation of law. If a provision is unenforceable, it will be limited to the minimum extent necessary and the remainder will continue. Failure to enforce a provision is not a waiver.

These Terms, the Billing Policy, Privacy Policy, Acceptable Use Policy, and any signed order form or data- processing addendum are the complete agreement about the Service and replace earlier discussions on that subject. A signed order form controls over these Terms for its commercial terms; an executed data-processing addendum controls for its covered processing; and the Billing Policy controls for purchase mechanics.

19. Legal notices and contact

Legal notices to PeopleDat must be sent to [email protected] and must identify the sender, organization, account, and subject of the notice. PeopleDat may send notices to the organization owner's account email or through a prominent Service notice.

Pixel Reef LLC · Florida, United States