Controls you can take to procurement
Sylure is designed for privacy operations where you need fast visibility without widening exposure: validated intake limits, least-privilege roles, evidence minimisation, audit traceability, and policy-driven retention.
Hash-first indexing
HMAC-SHA256
Masked by default
Evidence views
Role-based access
ADMIN / ANALYST / VIEWER
90-day retention
Default lifecycle
Quick answers
Do you store raw identifiers everywhere?
No. Matching is designed to be hash-first (normalised + keyed hashes) and evidence can be masked by default.
Can we delete our data?
Yes. Admins can delete upload bundles on demand. Retention policies also enforce scheduled purge.
How long do uploads live?
Raw bundles are stored in object storage with a default 90-day lifecycle (configurable).
Your data stays under your control
Sylure is built for privacy operations — we optimise for visibility and governance, not long-term storage of raw personal data. Upload bundles can be deleted on demand, and retention defaults to a 90-day lifecycle with a policy-driven purge window.
For legal notices, see privacy notice.
Where bundles live
Upload bundles are stored in object storage (S3) with lifecycle-based expiry and tight access controls.
What we persist
We prioritise metadata plus masked evidence for review. Identity matching is designed to be hash-first to minimise raw-value persistence.
Deletion + lifecycle purge
Admins can delete a bundle at any time. Scheduled purge removes raw bundles and derived outputs when the retention window expires.
Security controls that reduce handling risk
These controls are designed for privacy operations teams who need fast visibility with clear boundaries: bounded intake, least-privilege access, and audit traceability.
Bounded ZIP intake (anti zip-bomb)
Uploads are processed inside strict intake boundaries: 3GB ZIP cap, 20GB uncompressed, up to 250,000 entries, and 100,000 eligible files.
Antivirus scanning
Antivirus scanning can be enabled as a defence-in-depth step. It's designed to reduce handling risk, not to replace your endpoint controls.
Least-privilege roles (RBAC)
Roles support separation of duties: ADMIN, ANALYST, VIEWER. Share dashboards with stakeholders while keeping action controls restricted to authorised users.
Audit traceability
Audit logs capture key actions (Authentication events, Exports, Raw bundle access) so teams can evidence governance controls during review.
Hash-first identity indexing
Identifiers are normalised and indexed using keyed hashes (HMAC-SHA256). This supports DSAR matching while reducing the need to store raw identifiers.
Evidence minimisation
Evidence views are review-focused and can be masked by default to support verification while reducing copy-and-paste sprawl during triage.
Built for data minimisation without losing auditability
Sylure is designed to help teams answer "what personal data do we have, where is it, and what did we do about it?" without unnecessarily persisting sensitive values. Evidence handling is review-focused: enable masked views, limit access by role, and keep traceability for governance.
Hashing & DSAR matching
Identity matching is designed to be hash-first: identifiers are normalised and indexed using keyed hashes (HMAC-SHA256) so teams can search and de-duplicate exposures without turning personal values into plain database fields.
Ingest
Bring exports
Archives, case folders, and logs as ZIP bundles.
Normalise
Canonicalise
Emails, phones, and common identifiers for matching.
Hash
Keyed indexing
Values aren't stored as plain text in the database.
Match
DSAR & mask
Power search and triage with masked evidence views.
Keyed hashing supports matching and de-duplication while reducing raw-data handling. Evidence is intended for verification and governance — not bulk extraction.
Evidence safety principles
- Masking can be applied in the UI and exports (default behaviour).
- Identifier handling is hash-first, supporting search and de-duplication while minimising raw-value persistence.
- Role-based permissions limit who can view evidence, trigger exports, and access raw bundles.
- Reviewer dispositions (e.g. ignore overrides) apply consistently across dashboards, DSAR workflows, and exports.
Masked collaboration
Share findings with stakeholders while reducing exposure. Use masked evidence views for review and sign-off.
Hash-first DSAR workflows
DSAR search and subject matching are designed to run on normalised, keyed hashes — supporting de-duplication and investigation without treating raw values as plain database fields.
Customer-controlled lifecycle
Delete bundles on demand, or rely on lifecycle-based expiry (90 days by default). Prepared uploads expire after ~24 hours to avoid stale intake.
Retention aligned to policy-driven lifecycles
Privacy operations often involve temporary evidence handling. Sylure supports policy-aligned retention so raw bundles and derived outputs don't linger longer than they need to.
Default lifecycle (configurable)
- Default bundle retention in object storage: 90 days, with a 7-day deletion grace window.
- Admins can delete an upload bundle on demand; deletion removes the raw bundle and associated derived outputs.
- Prepared but not scanned uploads expire after ~24 hours.
- When purged, raw bundles and derived outputs are removed while a tombstone record can remain for operational history.
Scheduled purge patterns
Support scheduled deletion of uploaded bundles and associated outputs to reduce unnecessary retention.
Operational transparency
Scan stages and outcomes are tracked so teams can explain what happened, when, and under which controls.
Access controls
Role-based permissions help limit who can view evidence, trigger exports, and access case-level outputs.
Exports for DSAR and stakeholder reporting
Produce shareable outputs without turning the platform into a "raw evidence warehouse". Exports are designed for DSAR operations and stakeholder briefings, keeping evidence minimised and aligning outputs to governance workflows.
Export formats
Reports
Markdown · CSV extracts
DSAR exports
CSV · JSON
Audit logs
CSV
AI (where enabled)
Draft output for human review
Security posture you can brief
If your team asks "what do you store and for how long?", the answer is specific: bounded intake limits, hash-first indexing, masked evidence views, role controls, audit traceability, and lifecycle-based purge (90 days by default).
Documentation
If you need a review pack, we can walk through control boundaries, hashing + masking behaviour, retention and deletion expectations, and representative audit events using your workflow and terminology.
Ready to see controls in action?
We'll walk through intake, evidence handling, RBAC, audit logging, and retention — tailored to your review requirements.