Data security is a top priority for Route, and Route believes that working with skilled security researchers can identify weaknesses in any technology.
If you believe you've found a security vulnerability in Route’s service, please notify us. We will work with you to resolve the issue promptly.
Disclosure Policy
- If you believe you’ve discovered a potential vulnerability, please let us know by emailing us at route@gerosecurity.com. We will acknowledge your email within 72 hours.
- Provide us with a reasonable amount of time to resolve the issue before disclosing it to the public or a third party. We aim to resolve critical issues within 72 hours of disclosure.
- Make a good faith effort to avoid violating privacy, destroying data, or interrupting or degrading the Route service. Please only interact with accounts you own or for which you have explicit permission from the account holder.
All vulnerability reports must be submitted by email, following the format below exactly.
Send to: the submission email address listed on the Submission Guidelines page
Subject line:
SUBMIT_Report Title
-
TYPE=— the bug type (e.g., XSS, SQL Injection, IDOR) -
ENDPOINT=— the affected endpoint or URL (max 100 characters) -
SUMMARY=— a summary of your finding
![]()
Note on formatting: Reports that do not follow this format — missing subject prefix, missing required fields, or missing attachment — will be rejected and returned to the sender with a request to resubmit correctly. They are not silently discarded, but incorrect formatting will delay review.
Full submission instructions, sample emails, and related workflows (checking report status, appeals, NDAs, etc.) are available on the Submission Guidelines page.
Payouts
Payouts for disclosed vulnerabilities will be made available after the issue has been triaged and the submitter successfully returns the applicable tax form(s).
- US Citizens, Form W-9
- Non US Citizens, Form W-8BEN
Exclusions
While researching, we’d like you to refrain from:
- Distributed Denial of Service (DDoS)
- Spamming
- Social engineering or phishing of Route employees or contractors
- Any attacks against Route’s physical property or data centers
Thank you for helping to keep Route and our users safe!
Changes
We may revise these guidelines from time to time. The most current version of the guidelines will always be updated and available in this article.
Contact
Route is always open to feedback, questions, and suggestions. If you would like to talk to us, please feel free to email us at route@gerosecurity.com.