EN DE FR ES TR IT NL PT JA ZH-CN

Security

Responsible disclosure policy.

Data security is a top priority for FileWave. If you believe you have found a vulnerability in a FileWave service or product, tell us so we can work with you to resolve it promptly.

Security contactGood-faith testingNo public disclosure before resolutionISO 27001 trust context

Operational value

Route security reports clearly and responsibly.

How to report a vulnerability

Email security@filewave.com with the affected URL, IP address, service, or product location; steps to reproduce; your contact information; and whether you want to be identified in a vulnerability resolution report.

Disclosure expectations

Do not disclose the vulnerability publicly or to a third party before it is confirmed and resolved by the FileWave Security Team. Make a good-faith effort to avoid privacy violations, data destruction, service interruption, or degraded service.

Research boundaries

Please avoid distributed denial of service, spam, social engineering or phishing of FileWave employees or contractors, and attacks against FileWave physical property or data centers.

What FileWave helps with

How responsible disclosure works.

Send details

Include reproduction steps, affected service or product, and your preferred contact method.

Protect users

Only interact with accounts you own or where you have explicit permission.

Coordinate disclosure

Give FileWave time to verify and resolve the issue before any public disclosure.

Written acknowledgment

FileWave does not generally offer monetary rewards, but valid reports may receive written acknowledgment.

Common questions

Common questions about vulnerability reporting.

Where should I report a FileWave security vulnerability?

Email security@filewave.com with the affected service or product, steps to reproduce, contact information, and disclosure preference.

Does FileWave run a paid bug bounty?

FileWave does not generally offer monetary rewards for vulnerability reports, but valid reports may receive written acknowledgment after review and verification.

What testing is out of scope?

Avoid DDoS, spam, social engineering, phishing, physical attacks, privacy violations, data destruction, and service interruption.

Security reporting

Clear reporting helps FileWave act quickly.

When researchers share enough detail to reproduce and validate a security issue, FileWave can route the report to the right team and keep the follow-up focused.