Your servers, your team
The vault runs inside your walls. Neither your data nor the keys to it ever reach us.
Keys stay in your own key service — OpenBao or HashiCorp Vault, in front of your HSM if you have one. We never see them.
Protect · Privacy Vault
Lock it once. Prove it always.
Most privacy vaults lock data away. Ours also proves it is still locked, still deleted when it should be, and only used for the reason you gave.
Built for the Act's duties on security, deletion and access. No tool makes you compliant on its own.
One place for personal data
Keep personal data in one safe place
Most companies keep the same customer's phone number in a dozen places: the app, the CRM, payments, analytics, support tickets and backups. Every copy is one more thing to secure, find and delete.
The vault stores the real data in one safe place. Your other systems get a code instead. Your apps keep working, and only the right people see the real data.
- The real value is kept once, in one protected place.
- Every other system holds a token, so apps and reports keep working.
- Only the people and systems with a reason ever see the real number.
s.8(5): reasonable security safeguards. Penalty schedule: up to ₹250 Cr
Withdrawal
Easy deletion
When someone withdraws consent, the vault handles the deletion: it erases the record, cancels every token that pointed to it and follows up on copies sent elsewhere. Then we test that it worked and keep a dated record.
- Destroy the key the record was encrypted with, so copies in backups become unreadable too.
- Stop every token that pointed to it.
- Chase the copies that were sent elsewhere.
- A signed certificate records which key was destroyed and when.
- Test that it finished, and keep a dated record.
s.8(7): erase when the purpose ends or consent is withdrawn. s.12: right to erasure
Access
Quick answers
When a customer asks what you hold, you search once instead of asking ten teams.
- One search instead of emails to ten teams.
- The same search shows what each piece of data is used for.
s.11: right to access information
Already have a vault?
You don’t have to switch vaults to prove compliance
Use ours, or keep the vault you already have. We connect to it and test it the same way we test ours. You don't have to switch to prove compliance.
- Use ours, or connect the vault you already run.
- Both are tested the same way.
A vault setting is evidence. Only a test can show the rule is met, and that includes our own vault.
Deployment
Three ways to run it, including fully on your servers
Your servers, our team
The vault stays in your data centre. We operate it under named engineers and recorded sessions.
Keys stay in your key service. Our engineers run the vault, but the keys never leave it.
Our cloud
Hosted in India. We name where it runs and who else touches it in the contract.
Separate keys for every customer, held in a dedicated key service in India and rotated automatically.
Do our applications have to change?
A little. Where an app stored the real value, it stores a token instead and asks the vault only when it needs the real value. Most screens and reports work fine with tokens or partly hidden values.
Who can see the real value?
Only people and systems your rules allow, for a stated reason. Everyone else sees a hidden value or nothing. Every look at a real value is recorded in a log that can't be changed.
Can we search on encrypted fields?
Yes, for exact matches and searches on the start of a value, without unlocking the whole table. You can also make sure a value such as an email address is unique.
Is it only for personal data?
No. Any field you declare can go in: bank details, health records, API secrets, contract terms.
Works with
Better together
Every product uses the same map of your personal data, so each one makes the others more useful.
See the vault and the checks together
A privacy vault that checks itself. It keeps personal data in one place, deletes it when consent is withdrawn, and gives you proof that the rules hold.