SECURITY
Vulnerability Reporting and Coordinated Disclosure Policy
Ozion places particular importance on the security of its applications and the protection of its customers' data. If you believe you have discovered a vulnerability, we encourage you to report it confidentially so that we can investigate and, where appropriate, remediate it.
Scope
This policy covers the following applications, together with the associated services operated by Ozion:
Vialto, Viargo, Vigigo
Infrastructure, accounts and services belonging to our customers or third-party providers are excluded unless explicitly stated otherwise. If you are unsure whether an asset is in scope, please contact us before conducting any further investigation.
How to report a vulnerability
Please use our vulnerability reporting page: https://www.ozion.com/security-contact
To help us investigate your report, please include, where possible:
- the application, domain and URL affected;
- a description of the vulnerability and its potential impact;
- the prerequisites and steps needed to reproduce the issue;
- a minimal, non-destructive proof of concept;
- the date of your observation and any relevant technical information;
- a way to contact you.
Do not submit passwords, access tokens or unnecessary personal data. Redact sensitive information in screenshots and logs. If sensitive material is essential to the investigation, contact us first so that we can agree on an appropriate secure transmission method.
Precautions and limitations
This policy establishes a channel for reporting vulnerabilities; it does not grant general authorization to conduct penetration testing against our services or those of our customers.
Without prior written authorization, please do not:
- disrupt service availability or conduct load-testing or denial-of-service attacks;
- attempt brute-force attacks or credential stuffing;
- use social engineering or phishing;
- modify, delete or extract data that does not belong to you;
- install persistence mechanisms or continue exploiting an issue beyond what is strictly necessary to identify it.
If you accidentally access another user's or customer's data, stop investigating immediately, do not disclose the data, and report the situation to us. Use test accounts and test data under your control wherever possible.
Handling reports
We aim to:
- acknowledge receipt within 2 business days of receiving a report;
- complete an initial assessment within 3 business days of receiving a report;
- keep you informed of progress when contact details are available.
The priority and timeframe for remediation depend on factors including the vulnerability's severity, exploitability and impact. We may request additional information or your assistance in verifying a fix.
Coordinated disclosure
Please do not publicly disclose technical details that would enable exploitation before we have had an opportunity to investigate and agree with you on the conditions for disclosure.
We favour coordinating the publication timetable, taking into account risks to users and, where relevant, the deployment of fixes by our customers.
Rewards and acknowledgements
This reporting process is not a bug bounty programme and does not offer financial rewards.
With your prior consent, we may publicly acknowledge your contribution.

