Bring the whole CSV. Keep the whole story.

• Input is CSV or TXT, or pasted addresses. XLSX is export-only.
• CSV and TXT files can be up to 10 MB. CSV supports up to 50,000 data rows; TXT and pasted input accept up to 50,000 valid addresses.
• A CSV can contain up to 200 columns; each CSV cell can contain up to 32 KB.
• Files must be valid UTF-8. A UTF-8 BOM and CRLF line endings are handled.
• CSV quoting, embedded newlines, quoted delimiters, duplicate headers, and headerless sources are supported.
• Do not remove CSV duplicates first unless you intentionally want to remove those original rows.

1. 1

   Upload the CSV

   Choose whether to skip addresses already stored in this workspace, then select the CSV. PeopleDat validates the encoding and hard limits before creating a list.
2. 2

   Preview the first 25 rows

   Inspect how quoted cells, headers, and columns were parsed before anything is saved.
3. 3

   Confirm headers and the email column

   Say whether row one is a header, then select the column that contains the addresses to verify.
4. 4

   Review the estimate

   Check valid unique, duplicate, invalid, missing, excluded, estimated-credit, and storage counts.
5. 5

   Confirm creation and verification

   Choose whether to queue Power verification immediately, then create the list. The workspace retention setting is applied automatically.

During a CSV import, PeopleDat normalizes the chosen address, creates one unique result item, and links every repeated source row to it. When that item finishes, its canonical result appears beside each duplicate in source order.

TXT and pasted input behave differently: the parser stores only the unique valid addresses. It reports duplicate and invalid counts, but those discarded input tokens are not available for row-by-row fan-back or later lossless export.

Workspace deduplication is a separate, explicit option. Turn it on when you want to skip addresses that already exist elsewhere in the active workspace. Because workspaces are the isolation boundary, an address in another client workspace does not leak into or affect this decision.

• 7 days for short-lived operational sources.
• 30 days, the workspace default.
• 90 days for longer review and reconciliation windows.
• Until list deletion when ongoing lossless re-export is required.
• After creation, the success summary and list details show the exact source-data expiry.
• From list details, you can delete source columns immediately or apply a newly extended workspace policy before expiry when offered.

Changing the workspace setting applies automatically to future lists; it does not silently rewrite an existing list’s deadline. After expiry or manual deletion, PeopleDat keeps verification results and aggregates but cannot recreate original non-email source columns. Generated export files follow their own 30-day retention.

While a CSV-backed list still has its source data, CSV and XLSX list exports include every original row and preserved source cell, followed by collision-safe peopledat_* columns for status, action, reason, freshness, mode, billing, and available checks. Formula-like values in both original and appended cells are neutralized before spreadsheet use.

Lists created from TXT or pasted input contain only their stored unique valid addresses, so an export cannot recreate discarded duplicate or invalid tokens. TXT exports are always a deduplicated email-oriented set. Date-range and cross-list exports use a standardized PeopleDat-only schema because source headers cannot be reconciled safely across unrelated files.