Security
What actually protects your account today, stated without embellishment, including the things we have not built yet.
Last updated 4 September 2026
Your password
We never store your password. It is put through bcrypt, a deliberately slow one-way hash, and only the result is kept. Nobody at SnapVitals can read your password, and a stolen database would not reveal it.
Sign-up and password reset enforce the same complexity rules, so a reset can never weaken an account below what registration demands. Changing your password signs out every other device.
Failed sign-ins take the same amount of time whether or not the email exists, so response timing cannot be used to discover which addresses are registered.
Sessions
Signing in issues a short-lived access token and a longer-lived refresh token. Refresh tokens are stored only as hashes, and each purpose, session, password reset, email confirmation, uses a separately namespaced hash, so a token minted for one flow cannot be replayed against another.
Confirmation and reset links are single-use and expire.
Your data in transit and at rest
All traffic is over HTTPS with a certificate that renews automatically. The database and cache are reachable only from the application server itself, they are not exposed to the internet.
Everything you can see is scoped to your own account at the database query level, not merely hidden in the interface, so another user cannot reach your meals by guessing an address.
Abuse limits
Sign-in, registration, password reset and AI analysis are all rate limited. Accounts must confirm their email address before they can sign in, which keeps invented addresses from consuming paid AI capacity.
Administrative access is restricted to a specific address list enforced on the server. Hiding an admin link in the interface is not treated as security.
What we have not built yet
SnapVitals is built and run by one person, and is in beta. Being straight about the limits:
- There is no two-factor authentication. Your password is the only thing protecting your account, so use one you do not reuse elsewhere.
- We have not had an external security audit or penetration test.
- Your food photographs are processed by Google’s AI outside India, under Google’s terms rather than ours.
- We hold health information, weight, age, what you eat. Please weigh that before deciding what to record.
Reporting a vulnerability
If you find a security problem, please tell us before telling anyone else. Email hello@snapvitals.app with enough detail to reproduce it. We will acknowledge within 72 hours and keep you updated until it is fixed.
We will not pursue legal action against anyone who reports a genuine issue in good faith, provided you do not access, change or delete data belonging to other people, do not degrade the service for others, and give us reasonable time to fix it before publishing.
We are too small to pay bounties. We will credit you if you would like to be credited.
If we are breached
If a breach affects your personal data, we will notify you and the Data Protection Board of India as the Digital Personal Data Protection Act, 2023 requires. We will tell you what happened, what data was involved, and what to do about it, without waiting until we have a comfortable explanation.
What you can do
- Use a password you do not use anywhere else
- Confirm your email address so you can recover the account
- Sign out on shared devices
- Remember you can log meals by typing instead of photographing - that path never sends an image anywhere