Skip to main content

Trust Centre

Data retention

This page helps you understand retention and deletion boundaries. The product earns trust by making its boundaries inspectable, not by asking buyers to accept a black box.

Bounded collection. Explicit permission. No exploitation or authentication attempts.

What this establishes

Understand retention and deletion boundaries

The product earns trust by making its boundaries inspectable, not by asking buyers to accept a black box. This page helps you understand retention and deletion boundaries. The relevant evidence, owner and limit remain available from the same route.

Useful for: security reviewer · privacy reviewer.

In practice

How the claim is checked

01

Every conclusion records scope, source, observation time and evidence state

Begin here when you need to understand retention and deletion boundaries. Stay with the domain, relationship or service state named on the page; the task does not widen silently into a different security or product claim.

02

Unknown, unavailable and not-applicable outcomes remain distinct

Seven PDF publications plus CSV and JSON can be generated from the completed assessment for entitled reports. Open the relevant report evidence when you need to verify the source, observation time, attribution or qualification behind it.

03

Candidates require applicability validation and never become confirmed findings automatically

Complete the step shown on the page, then check the resulting state before moving on. Unknown, unavailable and not-applicable outcomes remain distinct, so absence is never presented as a successful or reassuring result.

04

Methodology changes interrupt trends until comparable evidence exists

Methodology changes interrupt trends until comparable evidence exists. Record the resulting owner, evidence or recovery state where the product provides it, so another person can verify what happened without repeating the task.

What you can rely on

Evidence you can inspect

Trust claims remain bounded by their source and current evidence.

Clear scope

Seven PDF publications plus CSV and JSON can be generated from the completed assessment for entitled reports.

Traceable evidence

The page explains only what the current service state can support.

Honest limits

Unknown or unavailable information remains visible rather than being treated as a positive result.

Important boundary

What this does not mean

Data retention supports one defined outcome: understand retention and deletion boundaries. Domain Signals is not a penetration test, certification, data-residency assessment or prediction of breach likelihood. Missing evidence is not evidence of safety.

Questions answered

Read the conclusion and its limits together

What does Data retention help me decide?

This page helps you understand retention and deletion boundaries.

What evidence sits behind the answer?

Domain Signals keeps the source, observation time and evidence state alongside each conclusion. The relevant report view provides the technical detail when you need to inspect it.

What should I not conclude?

Data retention supports one defined outcome: understand retention and deletion boundaries. Domain Signals is not a penetration test, certification, data-residency assessment or prediction of breach likelihood. Missing evidence is not evidence of safety.

Keep exploring

Useful next steps

The next responsible step

Review the methodology

Review the methodology