A data subject access request lands, or an auditor asks what personal data your organization holds, and the honest answer is that years of it are sitting in email. Finding it by reading is not realistic; finding it by uploading the mailbox to a scanning service creates a new privacy problem on the way to solving the old one. This post covers what mailin detects, how it groups the results, how the Data Subject Request workflow produces a report with a redaction pass, and why all of it runs on your own device.
What PII detection finds and how it is grouped
mailin scans an archive on-device for email addresses, phone numbers, Social Security numbers, card numbers, IP addresses and more. Results are grouped by type, and each finding carries its source, meaning the message it came from, and a risk level, so you can work through the higher-risk findings first.
The grouped findings can be exported to CSV. That matters for the audit case as much as the request case: a spreadsheet of what personal data exists, where, and how risky, is something you can hand to a compliance function or work through over several sessions. Treat detection as a scan rather than a verdict. It gives you a list to review, and a person still confirms what each entry is before it is acted on.
Why on-device matters for this particular job
Scanning email for personal data is itself a processing of personal data. Sending the archive to a cloud service to find PII means one more copy on one more server, and one more thing to explain to the data subject. mailin's full-text index and PII scan are built entirely on your Mac, iPhone or iPad. There is no account, the developer collects nothing, and the app contains no code for contacting an email server at all.
Encrypted storage with AES-256 and a Touch ID or Face ID lock are available for archives that need to sit on a shared or portable machine, and everything can be permanently deleted from Settings when the request is closed. The privacy post goes through each of these in detail.
The DSAR email search: finding one person in years of mail
A subject request is usually about a single person, and the search tools do most of the work. Filter by sender or domain to pull everything they sent, then search the full-text index for their name, address or account number across subject, headers and body. Boolean operators combine terms, regex handles identifiers with a known shape, and proximity finds a name near a keyword. Saved searches keep the query so the same person can be re-run when a follow-up request arrives.
Conversation threading via Message-ID, In-Reply-To and References headers matters here because the data subject appears in replies and forwards they never sent. Thread Story reconstructs the whole conversation as a cited timeline, which shows where the subject's data traveled after the first message. If you lean on the AI Assistant or AI Smart Filters to speed this up, remember that AI features can produce inaccurate or incomplete results; verify against the cited emails before anything goes into a response. Search operators are covered in depth in the search post.
The Data Subject Request (DSAR) workflow and report
Data Subject Request (DSAR) is one of the ten Legal / eDiscovery guided workflows in mailin 2.0. Like every workflow it runs step by step in the runner, auto-saves, and files a numbered document in Documents & History that you can reopen, export to CSV, and fold into cross-document reports. Each step can carry the exact emails it relied on, and the optional one-tap sign-off records who completed it and when.
The output is mailin's GDPR data-subject-access report with a redaction pass. The report collects what was found about the subject, and the redaction pass addresses the problem every DSAR response has: the subject's emails are full of other people's personal data, which you are not entitled to disclose. Because the document is numbered and its notes are append-only, the response and the reasoning behind it stay together if the request is questioned later.
Redaction before anything is handed over
mailin's redacted exports either remove personal data or mark redactions on the page, and they draw on the same PII findings described above. The redacted set is what goes to the subject, with third-party identifiers removed. Do a human pass over the redacted output before it leaves; detection is a starting list, not proof that nothing was missed.
For the audit rather than the request, the Retention & Compliance Audit workflow in the same Legal set produces its own numbered document, and the PII CSV export gives it a data inventory to work from.
What this supports, and what it does not claim
PII detection, the DSAR report and redaction support data-subject and records work; they do not make an organization compliant with any regulation, and mailin does not claim otherwise. Whether a response is adequate depends on the request, the jurisdiction and decisions only a person can make.
These features are designed to support common records-integrity and eDiscovery workflows. Admissibility of digital evidence is jurisdiction-specific and depends on factors beyond any single software tool — consult qualified legal counsel for evidentiary use. mailin makes no warranty of fitness for any specific legal or regulatory purpose.
FAQ
Which tier includes PII detection and the DSAR report?
Professional. It includes the GDPR/DSAR report, redaction, Offline Mode with the audit log, and custodians and legal holds, at $9.99 per month, $79.99 per year or $249.99 lifetime.
Is the archive uploaded anywhere for scanning?
No. The scan runs on your device. The only optional network use besides App Store purchase verification is Cloud AI mode, which is off by default, uses your own API key, and sends only excerpts you explicitly choose.
Can I re-run the same request later?
Yes. Saved searches keep the query, and the numbered DSAR document stays in Documents & History, so a follow-up request starts from the previous one rather than from scratch.