Skip to main content

Trust Centre

Responsible disclosure

This page helps you report a security issue safely. 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

Report a security issue safely

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

Useful for: security researcher.

In practice

How the claim is checked

01

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

Begin here when you need to report a security issue safely. 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

Use the visible product state and named recovery action. A missing result does not mean that an assessment, payment or account change succeeded; wait for an explicit outcome or contact support with the correlation reference.

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

This page helps you report a security issue safely.

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

Responsible disclosure supports one defined outcome: report a security issue safely. 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 Responsible disclosure help me decide?

This page helps you report a security issue safely.

What evidence sits behind the answer?

This page explains a service or operating state and does not introduce a new assessment conclusion.

What should I not conclude?

Responsible disclosure supports one defined outcome: report a security issue safely. 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

Report a security issue

Report a security issue