Back to overviewSECURITY

Responsible vulnerability disclosure

If you discover a security issue, this page explains how to report it in a way that protects users, preserves trust, and gives Omnilyzer a fair chance to investigate and respond.

Responsible disclosure

If you discover a security issue, this page explains how to report it in a way that protects users, preserves trust, and gives Omnilyzer a fair chance to investigate and respond.

Why this page matters

Responsible disclosure

Use the standard security mailbox for most reports and the emergency mailbox when the risk is active or urgent.

Chapter 01

What to include in a report

Affected URL, page, or feature area.

Clear reproduction steps, impact summary, and any supporting evidence.

Whether the issue appears active, exploitable, or time-sensitive.

Chapter 02

Expected disclosure behavior

Avoid destructive testing, denial of service, or unnecessary access to customer or personal data.

Do not publicly disclose the issue before Omnilyzer has had a reasonable chance to review and respond.

Use the emergency route when there is an ongoing or urgent security risk.

Cookie notice

KEEP EXPLORING

Useful systems begin with a better question.

Start a conversation