Export Formats

Export your PII scan results in three formats: styled HTML reports for compliance, JSON for integration, or CSV for analysis. Choose the format that fits your workflow.

📄
HTML Report

Professional, printable report with visual risk grades, charts, and formatting. Perfect for compliance documentation, audits, and sharing with stakeholders.

  • Styled, branded layout
  • Print-friendly (PDF compatible)
  • Risk grade visualization
  • Sortable findings table
  • Executive summary
  • Audit trail with timestamps

Best For

Compliance reports, client deliverables, regulatory submissions, board presentations

🔗
JSON

Structured data export with complete metadata. Machine-readable format designed for integration with other tools, dashboards, and automated workflows.

  • Complete metadata included
  • Entity position offsets
  • Severity classifications
  • Scan statistics & timing
  • API usage tracking
  • Integration-ready schema

Best For

API integrations, data warehouses, custom dashboards, automated analysis

📊
CSV

Spreadsheet-compatible export with one finding per row. Easy to import into Excel, Google Sheets, or Looker for filtering, sorting, and analysis.

  • One finding per row
  • Sortable columns
  • Filterable fields
  • Excel/Sheets compatible
  • Entity type grouping
  • Risk severity labeling

Best For

Spreadsheet analysis, team collaboration, data exploration, trend tracking

📋 What's Included in Every Export

All export formats include comprehensive scan data and statistics:

Scan Metadata

Website URL, scan date/time, duration, pages analyzed, API provider used

Risk Grade

A-F compliance score based on PII findings severity and volume

Findings Summary

Total PII instances found, affected pages, entity type breakdown

Entity Types

320+ PII types detected: Email, Phone, SSN, IBAN, Credit Card, etc.

Severity Levels

Critical, High, Medium, Low classifications for each finding

Page Breakdown

Findings listed by page URL with exact line numbers and context

Statistics

Token usage, API calls, detection rates, pages per minute, timing metrics

Audit Trail

Configuration, settings used, detection rules applied, compliance preset

Format Comparison

Feature HTML Report JSON CSV
Printable / PDF ✓ Yes ✗ No ✗ No
Visual Formatting ✓ Charts & Design ✗ No ✗ No
Machine-Readable ✗ No ✓ Fully ✓ Yes
Spreadsheet Import ✗ No ✗ No ✓ Direct
Complete Metadata ✓ Yes ✓ Full Detail ✓ Yes
API Integration ✗ No ✓ Ideal ✗ No
Filtering & Sorting ✓ Interactive ✗ Client-side ✓ Native
File Size Larger (styled) Medium Smallest

🔄 Export Workflow

1

Complete Your Scan

Run a full website scan using piisafe.eu. Enter your target URL, configure detection settings, and launch the analysis. Results appear in real-time as the scanner processes pages.

2

Review Results

View your risk grade (A-F), findings summary, and detailed breakdown by page and entity type. Use the interactive filters to focus on critical findings or specific pages.

3

Select Export Format

Click the "Export" button and choose your preferred format:

  • HTML Report for compliance documentation
  • JSON for API integration and automation
  • CSV for spreadsheet analysis

4

Download & Use

Your file downloads automatically. For HTML, open in a browser or print to PDF. For JSON/CSV, import into your favorite tool: Excel, Looker, Python, API endpoint, etc.

5

Archive & Track

Store your exports for compliance records. Compare reports over time to track remediation progress. Use timestamps to document when PII was discovered and fixed.

📎 Sample Export Data

HTML Report (Rendered Preview)

HTML reports are styled, printable documents with charts and formatted tables.

HTML Report Structure

<!DOCTYPE html>
<html>
<head>
  <title>PII Scan Report — example.com</title>
  <style>/* Branded CSS for printing */</style>
</head>
<body>
  <div class="report-header">
    <h1>Website PII Scan Report</h1>
    <p>Scanned: example.com</p>
    <p>Date: March 16, 2026 at 14:32 UTC</p>
  </div>

  <div class="risk-grade">
    <h2>Risk Grade: <span class="grade-d">D</span></h2>
    <p>Critical PII exposure detected.</p>
  </div>

  <div class="summary">
    <h3>Scan Summary</h3>
    <table>
      <tr><th>Pages Scanned</th><td>47</td></tr>
      <tr><th>PII Instances Found</th><td>124</td></tr>
      <tr><th>Affected Pages</th><td>23 (48.9%)</td></tr>
    </table>
  </div>

  <div class="findings">
    <h3>Findings by Page</h3>
    <table>
      <tr>
        <th>Page</th>
        <th>Entity Type</th>
        <th>Severity</th>
        <th>Count</th>
      </tr>
      <tr>
        <td>/about</td>
        <td>EMAIL_ADDRESS</td>
        <td>High</td>
        <td>5</td>
      </tr>
    </table>
  </div>
</body>
</html>

JSON Export (Structured Data)

JSON exports contain complete metadata, entity positions, severity levels, and scan statistics.

JSON Report

{
  "report": {
    "version": "1.0",
    "scanId": "scan_26Mar2026_143215",
    "timestamp": "2026-03-16T14:32:15Z",
    "website": "https://example.com",
    "provider": "cloak.business",
    "duration": 284
  },
  "summary": {
    "riskGrade": "D",
    "pagesScanned": 47,
    "piiFound": 124,
    "affectedPages": 23,
    "affectedPagesPercent": 48.9,
    "tokensUsed": 1240,
    "apiCalls": 18
  },
  "findings": [
    {
      "id": "finding_001",
      "page": "/about",
      "entityType": "EMAIL_ADDRESS",
      "severity": "HIGH",
      "confidence": 0.98,
      "value": "john@example.com",
      "context": "Contact our team: john@example...",
      "lineNumber": 42,
      "charOffset": 340,
      "charLength": 16
    },
    {
      "id": "finding_002",
      "page": "/contact",
      "entityType": "PHONE_NUMBER",
      "severity": "HIGH",
      "confidence": 0.95,
      "value": "+49 123 456789",
      "context": "Phone: +49 123 456789 or email",
      "lineNumber": 15,
      "charOffset": 87,
      "charLength": 14
    }
  ],
  "statistics": {
    "byType": {
      "EMAIL_ADDRESS": 56,
      "PHONE_NUMBER": 34,
      "CREDIT_CARD": 12,
      "IBAN": 22
    },
    "bySeverity": {
      "CRITICAL": 12,
      "HIGH": 67,
      "MEDIUM": 34,
      "LOW": 11
    },
    "byPage": [
      {
        "page": "/about",
        "findings": 34,
        "topEntity": "EMAIL_ADDRESS"
      },
      {
        "page": "/contact",
        "findings": 28,
        "topEntity": "PHONE_NUMBER"
      }
    ]
  },
  "config": {
    "preset": "GDPR",
    "language": "en",
    "threshold": 0.85,
    "chunking": "enabled",
    "chunkSize": 50000,
    "totalChunks": 3
  }
}

CSV Export (Spreadsheet Ready)

CSV exports have one finding per row, ready for import into Excel, Google Sheets, or BI tools.

CSV Format (Tab-Separated Values)

Scan ID	Website	Page	Entity Type	Severity	Confidence	Value	Context	Line	Char Offset
scan_26Mar2026_143215	https://example.com	/about	EMAIL_ADDRESS	HIGH	0.98	john@example.com	Contact our team: john@example...	42	340
scan_26Mar2026_143215	https://example.com	/about	PHONE_NUMBER	HIGH	0.95	+49 123 456789	Phone: +49 123 456789 or email	15	87
scan_26Mar2026_143215	https://example.com	/about	EMAIL_ADDRESS	MEDIUM	0.87	contact@example.com	Email us at contact@example.com	89	1240
scan_26Mar2026_143215	https://example.com	/contact	EMAIL_ADDRESS	HIGH	0.99	support@example.com	Support: support@example.com	23	567
scan_26Mar2026_143215	https://example.com	/contact	CREDIT_CARD	CRITICAL	0.96	4532-1111-2222-3333	CC: 4532-1111-2222-3333 (test)	67	234
scan_26Mar2026_143215	https://example.com	/legal/privacy	IBAN	HIGH	0.92	DE89370400440532013000	Bank account: DE89370400440532013000	102	451
scan_26Mar2026_143215	https://example.com	/legal/privacy	BIRTH_DATE	MEDIUM	0.83	01/15/1975	Born: 01/15/1975	156	789
scan_26Mar2026_143215	https://example.com	/team	EMAIL_ADDRESS	HIGH	0.97	jane@example.com	Team lead: jane@example.com	8	145
scan_26Mar2026_143215	https://example.com	/team	PHONE_NUMBER	HIGH	0.94	+49 987 654321	Direct: +49 987 654321	21	312
scan_26Mar2026_143215	https://example.com	/blog/post-1	EMAIL_ADDRESS	LOW	0.71	user123@example.com	See user123@example.com for details	234	4567

Understanding Risk Grades

Your export includes a risk grade (A-F) based on the volume and severity of PII found:

A
No PII Found
Safe
B
Minimal Risk
< 10 findings
C
Low-Medium Risk
10-50 findings
D
High Risk
50-150 findings
E
Critical Risk
150+ findings
F
Severe Exposure
500+ findings

💡 Integration Examples

Excel / Google Sheets

1. Export as CSV

2. Open File → Open and select your CSV file

3. Use native features to filter by severity, page, or entity type

4. Create pivot tables for trend analysis

Python / Pandas

import pandas as pd
df = pd.read_csv('scan_report.csv')
critical_findings = df[df['Severity'] == 'CRITICAL']
print(critical_findings.groupby('Entity Type').size())

JavaScript / Node.js

const data = require('./scan_report.json');
const critical = data.findings.filter(f => f.severity === 'CRITICAL');
console.log(`Found ${critical.length} critical findings`);

Power BI / Looker

1. Import JSON via REST API or CSV via upload

2. Create calculated fields for severity scoring

3. Build dashboards tracking findings over time

4. Set alerts for critical PII discoveries

Custom Webhooks

Parse JSON exports and send notifications to Slack, Teams, or custom endpoints when critical PII is found

✅ Best Practices

  • ✓ Archive Reports: Keep historical copies of all export reports for compliance and audit trails. Use timestamps to track remediation efforts.
  • ✓ Secure Storage: Store exports in secure locations (password-protected, encrypted, or restricted access). PII reports contain sensitive data.
  • ✓ Regular Scans: Schedule periodic scans to track remediation progress. Compare reports over time to verify fixes.
  • ✓ Share Wisely: HTML reports are ideal for sharing with stakeholders and compliance teams. Use PDFs for printed documentation.
  • ✓ Automate Analysis: Use JSON exports with scripts to automatically flag critical findings and trigger remediation workflows.
  • ✓ Track Metrics: Monitor token usage, scan duration, and findings trends across reports to optimize your scanning strategy.

❓ Frequently Asked Questions

Can I export a partial scan?

Yes! You can select specific pages before launching your scan, or filter findings in the results view and export only critical items.

Are exports encrypted?

Exports are generated in your browser and downloaded to your device. They're not stored on piisafe.eu servers. Use your OS encryption (BitLocker, FileVault) to secure export files locally.

Can I print HTML reports?

Absolutely! HTML reports are print-friendly. Open in your browser and use Ctrl+P (Windows) or Cmd+P (Mac). Choose "Save as PDF" for archival.

What's the file size limit?

Most exports are under 5 MB. Very large scans (1000+ findings) may produce larger files, but all formats are optimized for storage and transmission.

Can I share exports with team members?

Yes, all export formats can be shared. For sensitive data, use encrypted messaging or secure file transfer. HTML reports can be shared as attachments or printed for offline sharing.

Are exports GDPR compliant?

Exports themselves don't contain PII (they only identify where PII exists). However, treat all reports as sensitive documents. Consider data retention policies and deletion schedules for archived reports.

Ready to export your first scan?

Start scanning websites for PII and export professional reports in minutes. No registration required.

Launch Scanner →

📚 Related Documentation

Getting Started

Your first PII scan in 5 minutes. No registration required.

Documentation Index

Browse all piisafe.eu guides, API docs, and resources.

Scanner Guide

Step-by-step tutorial with screenshots and video walkthroughs.

FAQ

Common questions about PII detection, compliance, and APIs.