Use every part of PeopleDat with confidence.

1. 1

   Open your secure sign-in link

   Enter your email on the sign-in page. PeopleDat emails a time-limited link—there is no password or one-time code to copy.
2. 2

   Choose the workspace

   Your account starts with a personal organization and a default workspace. If you have invitations, use the workspace switcher to enter the right team or client workspace.
3. 3

   Add the source

   Open Lists. Use CSV when you need every source row and column preserved; use TXT or paste for a simple list containing only unique valid addresses.
4. 4

   Review before spending

   For CSV, preview the source, choose the email column, and review duplicate, invalid, missing, excluded, storage, and estimated-credit counts before creation. TXT and paste create the email-only list directly; review the success counts before starting verification separately. The workspace setting determines CSV source retention, and the exact expiry appears after creation.
5. 5

   Verify and export

   Start the durable job, leave the page if you wish, then return to review canonical verdicts and create a CSV, XLSX, or TXT export.

• Overview: balance, recent activity, and next actions.
• Lists: sources, results, retention, reruns, and exports.
• Jobs: durable verification and export progress.
• Analytics: usage, verdict mix, and workspace attribution.
• Automations: exclusions, schedules, and notifications.
• Developer: API keys, webhooks, widget keys, and MCP.
• Team / Clients: invitations, roles, workspace grants, and caps.
• Billing: credits, subscription, PayGo, invoices, and portal access.
• Settings: workspace preferences, retention, and account controls.

Organizations own membership, billing, and the pooled credit balance. Workspaces isolate lists, jobs, keys, webhooks, schedules, reports, widgets, and usage. Your active workspace is a preference; the server rechecks authorization on every protected operation.

1. 1

   Choose CSV or TXT, or paste addresses

   Use CSV for lossless row-and-column preservation. Use TXT or paste for an email-only list. Files can be up to 10 MB; CSV supports up to 50,000 rows excluding an optional header, and TXT/paste accept up to 50,000 valid addresses.
2. 2

   Preview CSV rows

   For CSV, preview 25 rows, confirm whether row one is a header, and choose the email column. CSV is limited to 200 columns and 32 KB per cell.
3. 3

   Review CSV classifications

   Before creating a CSV-backed list, see counts for valid unique, duplicate, invalid, missing, excluded, estimated-credit, and stored rows.
4. 4

   Choose deduplication and set retention

   Optional workspace deduplication skips already-known addresses without provider work or charge. Owners and admins set the default CSV source-retention policy in Settings before importing.
5. 5

   Create and verify

   For CSV, choose whether to queue Power verification immediately, then confirm creation. TXT and paste create the email-only list directly; start verification separately after reviewing the success counts.

Read the lossless import guide →

Jobs move through queued, processing, and terminal states. The worker retries bounded transient failures, and a database sweeper recovers pending work if a queue wake-up is lost. You can safely leave the page while a durable job runs.

Detailed rows may include nullable checks for syntax, domain mail acceptance, SMTP connectivity, deliverability, catch-all, disposable, role account, free provider, inbox full, disabled, spam-trap, and MX records. A blank or null check means it was not performed; it does not mean false.

Results can be filtered by verdict, action, verification signal, exclusion, creator, source, and date. Exact-email lookup is supported. PeopleDat does not promise substring searching over encrypted addresses.

• CSV: for a CSV-backed list with retained source data, every original row plus collision-safe peopledat_* result columns.
• XLSX: the same lossless CSV-backed data in a spreadsheet workbook; email-only lists cannot recreate discarded input tokens.
• TXT: a deduplicated, email-oriented file for simple workflows.
• Saved filters: reuse verdict or action selections for list exports.
• Cross-list exports: use a standardized PeopleDat schema because source headers differ.
• Formula safety: original and appended cells are neutralized against spreadsheet formula injection.

If preserved source columns have expired or were deleted immediately, verification results remain available but lossless original-column exports do not. Download generated files before their 30-day export expiry.

Reports show verdict counts and percentages, reason breakdowns, recommendations, checked date, verification mode, and privacy-thresholded top domains. They never include addresses, source columns, row downloads, or direct result APIs.

The complete bearer URL is revealed once, defaults to seven-day expiry, and can be revoked immediately. Anyone with the URL can open it until expiry or revocation, so share it only through an appropriate private channel.

Read the private report guide →

Clients invited to a client workspace cannot see the parent workspace, other clients, agency billing, or members without access to that workspace. Archiving a workspace disables new work, keys, widgets, schedules, and report links without deleting history.

Read the teams and client workspace guide →

• Exclusions: exact email, domain, or TLD rules apply before provider work and cost zero credits.
• Schedules: rerun a list every 30, 60, or 90 days at a chosen local time and timezone.
• Hard caps: a scheduled run starts only if the full estimate fits its maximum and the available balance.
• No partial runs: if the cap or balance is insufficient, nothing is verified and the run is recorded as skipped.
• Change reports: see newly invalid, newly risky, recovered, unchanged, and excluded records.
• Notifications: receive privacy-safe in-app or email summaries for the events you choose.

Read the automations guide →

• REST API: synchronous single checks, durable bulk jobs, results, exports, credits, and usage.
• Signed webhooks: terminal job/export and low-credit events with HMAC verification and retry diagnostics.
• Browser widget: Quick-mode form advice with exact HTTPS origin allowlists, hard caps, and fail-open behavior.
• Hosted MCP: balance, usage, jobs, estimates, single verification, and bounded bulk tools for compatible assistants.
• Test keys: deterministic, provider-free scenarios that never consume credits.
• OpenAPI 3.1: machine-readable contract at /openapi.json.

• A known cache hit remains billable because it returns a usable conclusive result.
• Unknown/provider-failure results and policy exclusions use zero credits.
• Credits are reserved atomically, attributed to workspace/member/user/key/source, and restored with the same attribution on refund.
• Subscription and PayGo entitlements fund one organization pool; agency caps limit individual client workspaces.
• Preserved CSV source rows default to 30 days and can be configured to 7, 30, or 90 days, or until list deletion.
• Generated exports remain for 30 days. Security/API audit events remain for two years, and FINANCIAL-class audit entries use a seven-year cleanup window.
• Primary subscription, purchase, Stripe-event, wallet, and credit-ledger rows are outside automated retention cleanup; their deletion timing is handled separately under the approved financial policy and applicable legal holds.

Owners manage payment methods, invoices, renewal, and cancellation through Dashboard → Billing. Current allowances and PayGo prices are always shown on Pricing; contractual details live in the Billing Policy.