PII DO'S AND DON'TS

Most PII exposure is not a sophisticated attack. It is a spreadsheet attached to the wrong email, a customer's card number pasted into a ticket, production data copied into a test database, or a screenshot in a chat channel. These do's and don'ts are the everyday handling rules a security or privacy team can hand to staff, grouped by the places where PII leaks most often.

Zero retention: your data never leaves this browser. Verify it yourself in DevTools.

Loading the PII tools.

About this guide

What Are the Core Rules for Handling PII?

Do

  • Collect only the fields you need, and keep them only as long as you need them.
  • Know the label of the data before you move it (see the sensitivity tiers guide).
  • Use approved, encrypted storage and transfer tools.
  • Mask or tokenize PII before using it outside its home system.
  • Report suspected exposure right away, even if you are not sure.

Don't

  • Don't copy PII "just in case" into personal folders, notes, or devices.
  • Don't send Restricted data by ordinary email or chat.
  • Don't keep exports after the task is done.
  • Don't assume data is anonymous because the name column was removed.
  • Don't try to quietly fix or hide a mistake that exposed PII.

How Should PII Be Handled in Email, Chat, and Tickets?

  • Do send a link to the record in the system of record instead of the data itself.
  • Do double-check recipients and turn off autocomplete for external domains where possible.
  • Do mask values before pasting into a ticket or chat: the masking tool keeps the last four digits so the record can still be found.
  • Don't ask customers to send SSNs, card numbers, or passwords by email or chat.
  • Don't paste full card numbers into tickets; card data has its own rules under PCI DSS.
  • Don't forward long email threads without checking what is quoted below.

How Should PII Be Handled in Logs and Test Data?

  • Do design logging to record identifiers you can look up later, not the PII itself.
  • Do mask or truncate IP addresses, emails, and tokens in application logs where full values are not needed.
  • Do build test data from synthetic values or tokenized copies, never a raw production export.
  • Don't log request bodies, form submissions, or authentication headers in full.
  • Don't leave debug logging on in production.
  • Don't assume a log is harmless: IP addresses are PII under several frameworks (see is an IP address PII?).

How Should PII Be Handled in Spreadsheets, Screenshots, and File Shares?

  • Do delete columns you do not need before sharing a spreadsheet; hiding a column does not remove it.
  • Do crop or redact screenshots before sharing them, and check the browser tabs and notifications in view.
  • Do use a true redaction tool for PDFs and images, such as 2redact; drawing a black box over text in a PDF often leaves the text underneath.
  • Don't share file links set to "anyone with the link" for data with PII.
  • Don't leave tracked changes or comments with PII in documents you send outside the team.

Can You Put PII Into AI Tools?

Treat an AI prompt like an email to an outside party unless your organization has approved the tool for that data. Many AI services keep prompts for a period, and some use them to improve models, depending on the plan and settings.

  • Do check your organization's policy and approved tool list first.
  • Do replace PII with consistent tokens such as [NAME-1] and [EMAIL-1] before pasting; the masking tool does this so the text still makes sense.
  • Don't paste customer records, HR files, medical notes, or credentials into an unapproved AI tool.
  • Don't paste a "test" sample of real data; synthetic examples work just as well for most prompts.

What Should You Do If You Suspect PII Was Exposed?

  1. Stop the spread: unsend if possible, revoke links, and ask recipients not to forward.
  2. Report it to your security or privacy team right away, with what was exposed, to whom, and when.
  3. Preserve evidence. Do not delete logs or messages unless the incident team asks you to.
  4. Let the incident team decide on notification: every US state has a breach notification law, and deadlines can be short.
  5. Afterwards, fix the cause, such as an overly broad share or a logging setting, not just the single event.

Is This Legal Advice?

What Else Is on 2pii?

  • PII scanner: Paste text or open a TXT, CSV, JSON, or Word file and see every SSN, card, email, phone, birth date, address, and labelled name.
  • PII masking tool: Make a masked copy of text: keep the last four digits, replace with labels, or use consistent tokens, per category.
  • PII tier and impact classifier: Pick the data elements and quantity to get a Tier 0-3 rating, an estimated NIST SP 800-122 impact level, and the laws that may apply.
  • What is PII?: The NIST, GDPR, CCPA, and HIPAA definitions side by side, and what "linked" and "linkable" mean.
  • PII examples list: A practitioner list of PII examples sorted into direct identifiers, quasi-identifiers, and sensitive data.
  • PII sensitivity tiers: Public, Internal, Confidential, and Restricted labels mapped to Tier 0-3 and NIST impact levels, with handling rules.
  • PII laws and regulators: Primary-source links for GLBA, HIPAA, COPPA, FERPA, NY SHIELD, CCPA/CPRA, the state privacy laws, and GDPR, each dated.
  • Is an IP address PII?: When an IP address is personal information under NIST, GDPR, CCPA, and HIPAA, and how to handle it in logs.
  • Is an email address PII?: Why a personal email address is direct PII, how work and role addresses differ, and what that means for logs and lists.
  • Is date of birth PII?: Why a birth date alone is linkable PII, why it becomes identifying with ZIP and sex, and how to mask it.
  • Is a ZIP code PII?: When a ZIP code is PII, the HIPAA three-digit ZIP rule, and the combinations that make it identifying.
  • Is a name PII?: Why a full name is PII, when a name alone is low risk, and how context turns a list of names into sensitive data.

Everything is on the 2pii home page. Part of the 2suite.io privacy-first ecosystem.

How Can You Verify That Your Data Never Leaves This Browser?

You do not have to take our word for it. Browser developer tools list every request a page makes, so you can watch 2pii work and confirm that your text is never sent anywhere. The check takes about a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. No text has been opened yet, so none of them can contain your data.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Open the PII scanner, paste some text or open a file, and download the report.
  5. Look at the Network tab again. It is still empty. Scanning, masking, classifying, and saving made no request at all. The tools also show a live counter, read from your browser's own Resource Timing records, of the requests made since your text was opened. For extra proof, turn on offline mode after the page loads: every tool keeps working.

Text you paste or open is held in this tab's memory, checked by code that is already on the page, and handed back to you as a copy or a download. It is never uploaded, never stored in the browser, and gone when you close the tab. The only other request the site can make is the feedback form, and only when you submit it.

The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so even a bug could not send your data elsewhere.

Frequently Asked Questions

Can I email a spreadsheet with customer data?

Only if your policy allows it for that data label and you use an approved encrypted method. A better option is to share a link to the system of record, or a masked copy that includes only the fields the recipient needs.

Is it safe to paste PII into an AI chatbot?

Not unless your organization has approved that tool for that kind of data. Replace names, emails, and numbers with tokens first so the prompt still works without exposing anyone.

Does hiding a column remove the data from a spreadsheet?

No. Hidden columns, rows, and sheets are still in the file and anyone who receives it can unhide them. Delete the data before sharing.

Is a black box over text in a PDF enough?

Often not. Many PDF editors draw a shape over the text and leave the text underneath, where it can be copied. Use a tool that performs true redaction.

What should I do first if I sent PII to the wrong person?

Report it to your security or privacy team immediately, ask the recipient to delete it without forwarding, and let the incident team decide whether notification is required.

Was this helpful?