Rovian is a chess platform played over live video and audio. That means a security bug can affect not just data but people’s cameras and microphones. We take reports seriously and would much rather work with researchers than fight them.
📮 How to Report
One address: [email protected] — please put [SECURITY] in the subject line. Contact us before disclosing publicly; let’s fix it first, then tell the story together if you want to.
Reports move much faster when they include:
- Where: the affected URL, endpoint or screen (e.g.
rovian.co/...,realtime.rovian.co, the mobile app). - How: step-by-step reproduction — a sample request/response, screenshot or short video.
- Impact: what can an attacker actually do? (e.g. “I can read another user’s match history”.)
- Your setup: browser/device and the test account you used.
- Your name: how you would like to be credited (or tell us if you prefer to stay anonymous).
Want to send it encrypted? Ask us and we will exchange keys. (Once we publish a PGP key it will be announced in the Encryption field of /.well-known/security.txt — if it is not there, we do not have one yet.)
⏱️ What We Promise You
- We acknowledge your report within 3 business days (a real person, not an autoresponder).
- We share our initial assessment within 10 business days: is it valid, how severe, what we plan to do.
- We keep you updated while we fix it, and tell you when it is closed.
- For serious issues we aim to fix within 90 days. If it will take longer, we will tell you why.
- With your permission, we credit you in the acknowledgements below.
Rovian is built by a small team; we do not run a 24/7 security operations centre. These timelines are ones we can actually keep — and if we cannot, we will write to you.
⚖️ Safe Harbor
Research carried out in good faith and within the rules below is authorised research. If you stay within that scope:
- We will not take legal action against you and will not file a complaint.
- You are not considered to have breached our Terms of Service by the technical steps of your research, and we will not close your account over it.
- If a third party takes action against you, we will confirm in writing that you followed our rules.
To be honest about the limits: this is our commitment, and it cannot waive the rights of third parties or of prosecutors — we can only speak for ourselves. Behaviour outside these rules (exfiltrating data, extortion, harming other users) falls entirely outside this protection.
🎯 Scope
rovian.coand all its pages (web app, API endpoints)realtime.rovian.co— game/chat socket and WebRTC signaling- The Rovian mobile apps (iOS and Android)
- Authentication, session management and authorization flows
- Bypasses of moderation and age-gate protections
Out of scope
- Third-party services we use (Railway, Cloudflare, Sentry, Snap, Google and others) — please report those to their own programs.
- Denial of service (DoS/DDoS), load/stress testing and brute-force attacks.
- Social engineering, phishing, physical attacks and anything targeting our staff.
- Raw automated scanner output with no demonstrated impact (missing headers, version disclosure, SPF/DMARC notes and similar).
- Self-XSS, code the user pastes into their own browser, and unrealistic scenarios (e.g. assuming a fully compromised device).
- Username/email enumeration and similar findings with no standalone impact — though we are glad to hear about them as part of an exploitable chain.
🚧 Rules of Engagement
People play on Rovian with a live camera and microphone. Most of our rules exist to protect that:
- Test with your own accounts. Do not touch real users’ accounts, games or messages.
- If you find you can access another user’s camera, audio or chat, STOP. Do not record, store or share it. Describe what happened in words instead of attaching a screenshot — that is enough proof for us.
- Do not download, copy, delete or modify personal data you can reach. Use the smallest possible proof of access.
- Do not disrupt the service: no DoS attempts, no deleting data, no defacement.
- Do not degrade other users’ experience or spam games and chats.
- Do not share your finding with third parties until it is fixed; after that, we support you publishing it.
🏅 Rewards
We cannot pay cash bounties at the moment. Rovian is a small, early-revenue platform, and we would rather say that up front than promise a bounty we cannot honour and waste a researcher’s time.
What we can offer instead:
- Credit in the acknowledgements below (with a link to your site or profile if you want).
- On request, a signed letter of acknowledgement/reference describing your finding and how you handled it.
- Permanent free premium access to Rovian for critical findings.
- If you like, coordinated publication after the fix (a blog post, support through a CVE process).
When we are in a position to run a paid bounty program, we will announce it on this page and update the scope here.
🚨 Urgent: Child Safety
A suspected underage user or child sexual abuse material (CSAM) is not a “vulnerability report” and is not subject to a 90-day timeline. Report it immediately to [email protected] with the subject “URGENT CHILD SAFETY”; we treat it as our highest priority. Do not download or store the content as evidence — telling us what you saw and where you saw it is enough.
For in-platform harassment, nudity and rule violations, use the report button on the game screen; details are on our Community & Safety page.
🔍 Our Security Posture (no overclaiming)
You will not find an “independently audited” or “security certified” badge on this page. That is deliberate: in security there is no such thing as “passed”. At best an assessment says “on this date, in this scope, using this methodology, we found the following”. What is true today may not be true after tomorrow’s deploy.
Here is the honest picture instead:
- What we have done: an authorised penetration test (July 2026) and regular internal security reviews; a code audit on every security-sensitive change.
- Defences in place: nonce-based Content-Security-Policy, a narrowed
connect-srcallowlist, session validation repeated on every server route, rate limiting, an irreversible device signature against ban evasion, and no automatic recording of normal calls. Normal calls are not automatically recorded. User-triggered moderation evidence and clip features requiring explicit consent are exceptions. Match clips require both players to enable recording consent. See the Privacy Policy for details. - What we do NOT claim: any third-party security certification, ISO/SOC attestation, or a guarantee of being “bug-free”. We hold no such certificate — if we did, we would name the firm, the scope and the date right here.
The real trust signal is not a badge; it is that whoever finds a bug knows exactly where to take it. That is what this page is for.
🙏 Acknowledgements
Researchers who help keep Rovian safe are credited here. The list is currently empty — you could be the first. If you would like your name (and optionally a link) listed, just say so in your report.
The terms of this program may be updated without prior notice; the current version always lives on this page. Machine-readable version: /.well-known/security.txt (RFC 9116).