Security
How Vyam keeps your work safe
Your plans and files are yours. This is what protects them, said plainly.
Access rules in the database
Who can read or change a project is decided in the database itself, not only in the app. Only the people on a project can see it, and only owners and editors can change it.
No secrets in your browser
The keys that matter, such as the AI key and the database’s service key, live only on the server. The browser holds only what is meant to be public.
Encrypted, and no readable passwords
Data is encrypted in transit (HTTPS) and at rest by our hosting providers. Passwords are never kept in readable form; the sign-in provider keeps only a salted hash.
An AI that is boxed in
The AI only sees what you send it when you ask. Which models can be used is fixed, what comes back is checked before it is used, and you review every plan before it is saved.
Tokens shown once
The access token for a coding agent is shown to you once and kept only as a one-way fingerprint, so even we cannot read it back.
Little code from others
The interface is built from our own code with a short list of well-known open-source packages, pinned to exact versions and checked for known problems.
What we have not done yet
No system is perfectly secure, and Vyam has not yet had an independent security test. We do not claim certificates we do not hold.
If a breach ever puts your data at risk, we will tell you and the authorities as the law requires.
Found a weakness?
Please write to knmnikhil05@gmail.com with the details and give us reasonable time to fix it before you share it. We will not act against good-faith research that avoids harming other people’s data. More in the legal notices and the Privacy Policy.
Plan. Track. Ship.
Describe an idea, get a plan you can edit, and follow it through to launch with your team.