Upload, classify, discover, report.

Sylure validates bundle intake, maps personal data exposure back to the underlying assets, supports DSAR Discovery workflows and produces governance-ready reporting. Built to be readable for non-technical stakeholders and practical for teams who need evidence, traceability and controlled handling.

What personal data does Sylure detect

Coverage across multiple categories, tuned for UK formats and continuously expanded.

0

File Types Supported

0

GDPR Categories

0+

Personal Data Types

Identity
Contact
Address
Online identifiers
Financial
Identity
Contact
Address
Online identifiers
Financial
Tax & employment
Government IDs
Professional
Health
Demographic
Tax & employment
Government IDs
Professional
Health
Demographic

Supported file types

Upload ZIP bundles containing any mix of these formats.

Spreadsheets

9 formats supported

CSV · TSV · TAB · PSV · XLS · XLSX · XLSB · XLSM · ODS

Documents

6 formats supported

PDF · DOCX · ODT · PPTX · ODP · RTF

Email & Mailbox

3 formats supported

EML · MSG · MBOX

Structured Data

8 formats supported

JSON · NDJSON · JSONL · XML · HTML · HTM · XHTML · SQL

Plain Text

5 formats supported

TXT · LOG · MD · MARKDOWN · RST

Config

8 formats supported

YAML · YML · INI · CFG · CONF · ENV · PROPERTIES · TOML

Email parsing detail

Email receives a full-content scan. In most audits and DSAR responses, the richest personal data evidence sits inside email threads rather than standalone documents. When you upload .eml, .msg or .mbox bundles, Sylure parses each message, decodes the body, extracts addresses from the header block (From, To, Cc, Bcc, Reply-To), and re-feeds attachments through the same detection pipeline applied to standalone uploads. A PDF attached to a forwarded thread is classified identically to one uploaded directly.

MIME transfer encodings (base64, quoted-printable) and HTML data: URLs are decoded automatically, so attachments reach the scanner in their native binary form before extraction runs. Outlook's .msg OLE2 format is supported alongside standard RFC 5322, and .mbox archives are split per-message so each conversation is processed independently.

Platform Walkthrough

From validated intake to DSAR discovery and audit-ready governance. Each module stays tied to the underlying assets.

Validated Intake

Know exactly what was processed and when

Upload ZIP bundles (exports, archives, case folders) and move through a consistent pipeline with guardrails, visible stages and retention-aware lifecycle controls.

  • Start with the data you already have.
  • Size, entry count and extraction limits keep intake predictable.
  • Processing stages visible to reviewers: validation, security checks, indexing.
  • Bundle lifecycle controls support storage limitation and retention posture.

How uploads get processed

Each upload goes through validation, virus scanning, extraction and PII indexing, with lifecycle tracking built in.

Next step

See Sylure on your data

We'll walk through the full platform, covering intake, exposures, discovery, reporting and governance, using your typical bundle shape.