Last updated: September 2026
The short version: CodeVault stores the code you save and almost nothing else. This page explains exactly what that means, in plain language — no legalese, no surprises.
Only what CodeVault needs to work. When you create an account we store your username and email, plus a scrambled (hashed) version of your password. We never see or store your password in plain text — not even briefly.
Everything else is the content you choose to save: a snippet's title, description, code, language, tags, and whether it's public or private.
Every snippet is private by default. Only you can see it. Nothing about a private snippet is shown to anyone else.
If you flip a snippet to public, it appears in the public library and anyone can view it. You can switch it back to private at any time — but keep in mind that something already viewed or copied may have been saved elsewhere.
The hosted demo runs on Vercel and stores data in MongoDB Atlas — both see only encrypted data in transit and at rest, and neither reads your snippets. If you self-host CodeVault (it's open source and you're welcome to), no third party is involved at all.
Passwords are hashed with bcrypt, sessions are token-based rather than stateful, and access tokens expire quickly by design. No system is perfect, but if we ever found a real issue affecting your data we'd disclose it openly — the project is public.
If something here is unclear or you want a specific piece of your data removed, open an issue on GitHub or email sainrahul374@gmail.com.