Terms & Conditions.
The terms for using our site and working with us. We are a small, early team, and most of what we publish is here to help the cybersecurity community get AI-ready. We have kept this in plain English, with the formal detail living in the engagement letter for any paid work.
By using ryvane.ai or working with us on a paid service, you agree to the terms below. If any of them don't sit right with you, please don't use the site or hire us, and there are no hard feelings. We are a small, early team, and much of what lives here, our research and writing, is shared freely to help the cybersecurity community get AI-ready. These terms cover the website and that free content; any paid work is governed in detail by a separate engagement letter, which takes precedence over anything stated here.
01, About these terms
Who we are.
Ryvane is a small, early-stage team with a simple mission: to share what we learn and help the cybersecurity community become AI-ready. "Ryvane" refers to Ryvane Pvt. Ltd., the entity that runs this website and offers our research, audit, and training work. "We", "us", and "our" mean the same thing, and "you" means anyone who visits the site, reaches out, or works with us.
Because we are still finding our feet, these terms may change as we grow. The "Last updated" date above shows when the current version went live, and continuing to use the site after a change means you are okay with the new version.
02, The website
What you can and can't do here.
Sharing is the whole point. You are welcome to read, link to, and pass around anything we publish, including the Journal, the methodology page, and any open research notes. A credit back to us is appreciated, but never required.
You agree not to:
- Use the site in any way that breaks applicable laws or that we'd consider abusive
- Attempt to break into, probe, or stress-test our infrastructure without prior written permission
- Scrape the site for the purpose of redistributing content commercially without our agreement
- Misrepresent yourself, your company, or your intent when reaching out via our contact channels
The site is provided "as is". We are a small team doing our best to keep things accurate and current, but we can't promise it is free of typos, the occasional technical hiccup, or something that has gone out of date.
03, Engagements
How paid work actually starts.
Nothing on this website is a binding offer to provide services. We start every paid engagement with a friendly scoping conversation, then a written engagement letter that lays out scope, deliverables, timeline, fees, confidentiality, and anything else relevant to the work. We would rather be upfront and move at the right pace than over-promise.
That engagement letter, not this website, is the contract that governs the work. If anything in these site terms conflicts with it, the engagement letter wins.
04, Intellectual property
Who owns what.
The Ryvane name, logo, branding, and the content on this website are ours. Anything we build for you in an engagement (reports, exploit scripts, evaluation harnesses, and code written specifically for you) is yours once the engagement is paid in full, subject to the engagement letter.
We do keep the right to reuse the general knowledge, techniques, and methods we develop, as long as they never expose your confidential information, since teaching and sharing is core to why we exist. If we ever want to write publicly about a class of vulnerability we found, we agree the disclosure path with you in the engagement letter, never on our own.
05, Confidentiality
What we keep private.
Anything you share with us about your systems, your team, your security posture, or your business, whether in writing, on a call, or through shared infrastructure, is confidential. We treat it that way by default, and we put it in writing for paid engagements through the engagement letter or a separate non-disclosure agreement.
We don't name clients publicly without their written permission. We don't share findings between clients. We don't use findings from one engagement to win another.
06, Limitation of liability
Reasonable limits.
The website and everything we share for free (blog posts and open research included) come without warranties of any kind. We publish them in good faith to help the community learn, but to the extent the law allows, we can't be liable for any indirect, incidental, or consequential loss from using the site or relying on free content. Please use your own judgement before applying anything to a production system.
For paid engagements, the limitation of liability is whatever the engagement letter sets out, usually capped at the fees paid for that engagement.
07, Governing law
Where disputes are handled.
These terms are governed by the laws of India, and any dispute about the use of this website falls under the exclusive jurisdiction of the courts in Bengaluru, Karnataka. A paid engagement may name a different governing law and venue in its engagement letter, and that takes precedence. Honestly, we would always rather sort out any concern with a conversation first.
08, Contact
Questions about these terms.
If anything here is unclear, or you would like a copy of our standard engagement letter or NDA template, just write to hello@ryvane.com and we will get back to you. We are always happy to talk.
A privacy policy is on the way. Until it's published, our short version is: we don't sell data, we don't run third-party analytics that track you across sites, and we only collect what we need to answer your messages or run an engagement. Ask us anything if that matters to you.
Where AI security gets practiced.
Audits, research, and training from the team building the field's working toolchain.
LEARN MORE