Skip to content

Security

Built to keep one household's data invisible to every other

No vague promises. Here is exactly how MyVesta stores, isolates, controls and protects your household's information.

Encryption

Data is encrypted in transit with TLS every time it moves between your browser and our servers. At rest, it is encrypted at the storage layer by the database and object-store services we use.

  • All traffic uses modern TLS. We do not serve anything over plain HTTP.
  • File attachments are held in a private bucket that is never publicly readable. Each file is served only to an authenticated member of the household that uploaded it.
  • Database backups and replicas inherit the same storage-layer encryption as live data.
A minimal security dashboard showing a locked vault and encryption status

Household isolation

Every record in MyVesta is bound to a household. Database-level row security makes it structurally impossible for one household to read another's data, because the query layer rejects any request that does not carry the right household identifier and authenticated user identity.

Row-level security by design

Every table that holds household data has a policy that checks the authenticated user's household before a row is returned. There is no global query path that skips this check.

Verified by automated tests

Isolation is not only written into policy. Our test suite repeatedly attempts cross-household access from automated accounts and confirms it is refused.

Access control

Sharing does not mean exposing everything. One owner has full control, and every other member is granted read-only access to the specific categories the owner chooses.

  • One owner

    The owner can invite and remove members, change permissions, export data, and delete the household. Ownership can be transferred when life changes.

  • Read-only members

    Members see only the categories they are granted. They cannot edit, delete, invite others, or change permissions.

  • Per-category permissions

    Access is set category by category, not vault-wide. Medical details can be shared with an adult child without also sharing bank accounts.

  • No anonymous access

    Every request, including shared emergency sheets and calendar feeds, is tied to a verified, signed-in account. There are no public links.

Account security

Strong accounts protect the vault even if a device is lost or an inbox is compromised.

  • Verified email addresses

    Every account must confirm its email before it can create or join a household. Invitations are sent only to the address the owner provides.

  • Twelve-character minimum password

    Passwords must be at least twelve characters and meet complexity requirements. A live strength meter shows whether the one you are typing will hold up.

  • Secure password reset

    Reset links are short-lived, single-use, and sent only to the verified email. Old sessions are invalidated after a reset.

  • Optional app-based two-factor authentication

    Owners can require TOTP-based 2FA for the household, using any standard authenticator app. We do not support SMS-based 2FA because it is weaker.

Accountability

The activity log records who viewed, created, changed, or deleted each record. Every entry shows the person, the action, the time, and what changed. The owner can answer the question "who saw this?" without guessing.

What is logged

  • Views of a record or file
  • New records, uploads and members
  • Edits to fields, permissions and categories
  • Deletions and exports

Your data stays yours

You can leave with everything you brought, or delete it completely. Either way, the choice is yours and the action is immediate.

Export your entire vault

Download a structured file containing every record, custom field and file reference in your household. Use it for backup, migration, or sharing with a lawyer or advisor.

Permanently delete your household

The owner can delete the household, its files, its records and its member accounts at any time. After deletion, we keep only a minimal record that the deletion happened and when.

What we will never do

These are not policy preferences. They are structural limits on how the product is built and how the business is funded.

  • Never sell or share your data

    We do not build marketing audiences, sell lists, or share household information with insurers, brokers, advertisers or data brokers.

  • Never use it to train models

    Your records, attachments and usage patterns are not used to train machine-learning models, ours or anyone else's.

  • Never show you advertising

    MyVesta is funded by subscriptions, not ads. There are no banner ads, sponsored placements, or promoted products inside the vault.

Responsible disclosure

If you find a security issue, please report it privately so we can fix it before it is made public. We respond to well-researched reports within two business days and will credit researchers who ask to be named.

security@myvesta.io

See the rest of how MyVesta works

Read about features, pricing, and the step-by-step setup, or start a free trial and see the controls for yourself.