LegaSafe Vault
Get started

Security

LegaSafe Vault
Razor Crest LLC d/b/a LegaSafe Vault
Effective: September 27, 2026
Related: Privacy · Terms

This page says how we protect vaults today, without marketing language we cannot defend.

What we actually do

  • Accounts through Supabase Auth (email/password or Google). Signed-in sessions last four hours, then you sign in again.
  • Passwords are stored by the auth provider, not in our app as plain text. Reset uses a one-use 6-digit code by email or confirmed text, good for 10 minutes.
  • File storage is a private bucket. Downloads use time-limited signed URLs. We do not mean for vault files to be public on the open web.
  • Database access uses row-level rules so one family does not read another family’s rows in the ordinary product path.
  • Pages run on HTTPS.
  • After a completed release, the product locks writes so cards are not quietly edited.
  • Operators can see notice facts (name, email, phone, date of birth, status). They cannot download customer files in the ordinary admin tools.
  • Death notice starts a 7-day pending release you can abort. Assigned files stay sealed until that wait ends.

Encryption and keys

  • At rest and in transit. Our storage provider encrypts the database and stored files at rest with AES-256. Pages and downloads travel over HTTPS.
  • Who holds the keys. The provider manages those encryption keys. You do not hold them, and we do not keep a separate set of our own.
  • What that means. The app has to be able to read your files to show them to you and to release them to your Legacy Stewards. A person with the highest level of access to our hosting accounts could in principle reach them too. We limit that access, and our admin tools do not offer file downloads.
  • Short links. When you or a Legacy Steward opens a file, the app makes a link that works for about a minute.
  • Passwords and account numbers. We recommend you do not store them here. Write down where they are kept instead.

Why we do not use owner-only keys

Some products give only the owner the key, so that not even the company can open a file. We looked at that and chose not to build it, on purpose, because of what this product is for.

  • The point is that your family can open your papers. A vault exists for the day you cannot speak for yourself. If only you hold the key, the papers are readable only while you can still unlock them.
  • A lost key cannot be recovered. With owner-only keys, a forgotten passphrase, a lost device, or a death without sharing the key means the files are unreadable for good. We could not help your family, and no reset could bring them back.
  • The workarounds add steps that must be done before they matter. Keys can be split or shared with your Legacy Stewards, but each person has to set that up in advance. We expect many families would not finish, and an unopenable vault is a worse failure than one we manage.
  • Features need the server to read your files. Search, previews, the Last Wishes and Emergency Print Card PDFs, and release to your Legacy Stewards all depend on it.
  • The cost is trust. You rely on us and our providers to protect the keys and limit access, which is why this page says plainly that the product is not zero-knowledge.

If you need a file that only you can open, encrypt it yourself before you upload it, and write down where the key is kept. We cannot recover it for you or your family. We have not built owner-held keys. If we offer them later as an option, we will explain the trade-offs above in the same plain words.

What we do not claim

  • Not zero-knowledge. Servers that run the app can process file bytes. That is how search, thumbnails, and release work. If you need a product where even we cannot mathematically open a file, this is not that product.
  • Not HIPAA certified. Not SOC 2 certified as of this date. Do not store records on the assumption that we are a covered clinic or a audited enterprise.
  • Not “bank-level” as a slogan. Banks are examined under rules we are not under.
  • Not a guarantee. Hosts fail. Phones get stolen. Stewards forward email. An emergency print card can be copied.

Your job

  • Use a password only you know. Do not share it.
  • Confirm texts if you want release alerts on the phone.
  • Name Stewards on purpose. Free includes one.
  • Treat the printed emergency print card link like a house key.
  • Keep original signed papers where you said they are. The vault holds copies.
  • If you close the account, understand the vault is hidden, not wiped.

Processors

Hosting and mail run on third parties (today: Supabase, Vercel, Stripe, Resend, and our SMS provider). Their security pages apply to their systems. A failure there can affect us.

Incidents

If we learn of a breach that requires notice under law, we will notify affected accounts at the email on file and, where required, regulators. Email support@legasafevault.com if you think your vault was opened by someone who should not have it.

Changes

We will date this page when the practices change in a way you would notice.