Is the text I scan uploaded anywhere?
No. The scanner runs in your browser tab and the page shows a live count of network requests since your text was opened. It stays at zero while you scan, mask, and download.
Paste text or open a file to see every Social Security number, ITIN, EIN, payment card, bank number, email address, phone number, labelled birth date, street address, IP address, and labelled name in it. Each finding shows its line, confidence, and the reason it matched, and the report downloads as JSON or CSV.
Loading the PII tools.
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.
F12, or Cmd+Option+I on a Mac, and select the Network tab.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.
A number that merely looks like an identifier is not enough. The scanner validates each candidate: SSNs cannot have a 000, 666, or 900-999 area, a 00 group, or a 0000 serial; card numbers must pass the Luhn check and belong to a known issuer; routing numbers must pass the ABA checksum. A bare nine-digit number is only reported as an SSN when a label such as SSN or Social Security appears just before it on the same line, or when it sits in an SSN column.
When findings overlap, the more specific one wins, so a card number is not also reported as a phone number. Labels only count within the same sentence, so "Born on March 4, 1990. Meeting on 2026-01-05" reports the first date as a birth date and leaves the meeting date alone.
When the text is a table, such as a CSV or TSV export, the scanner reads the header row and uses each column's name as context. Values in columns named dob or birth_date are reported as birth dates, values in ssn columns as SSNs even without dashes, and values in first_name, last_name, patient, or customer columns as names. This catches the bulk exports where most PII leaks happen, without guessing on ordinary text.
The JSON and CSV reports list every finding with its category, line number, character position, confidence, and reason, plus the totals per category. By default the value column is masked, so the report is not one more copy of the PII in your ticketing system. If you need the full values, tick the option first and store the report as Restricted data.
CSV reports guard against spreadsheet formula injection: any cell that starts with =, +, -, or @ is prefixed with an apostrophe.
Those limits are why each result explains itself: the scanner shows you where PII is, and you decide what to do with it.
Everything is on the 2pii home page. Part of the 2suite.io privacy-first ecosystem.
No. The scanner runs in your browser tab and the page shows a live count of network requests since your text was opened. It stays at zero while you scan, mask, and download.
Bare nine-digit numbers are only reported as SSNs when labelled or in an SSN column, because most of them are order, invoice, or account numbers. Numbers written as 123-45-6789 are checked against the SSA issuing rules.
Yes. Open a .docx file and the scanner reads the body text, headers, footers, footnotes, comments, and tracked deletions, using only the browser's built-in decompression.
Medium means the value matched but something makes it less certain: a 555-01XX phone number reserved for fiction, a private IP address, a widely published sample SSN, or a number identified only by its label.
Yes. Download a JSON or CSV report. Values are masked unless you choose to include them in full.