Privacy Policy

1. Who we are, and what this covers

This policy is issued by Mungry LLC, doing business as Verndr (“Verndr,” “we,” “us”), and covers the invitation-only Alpha web applications operated under the Verndr house — including the Verndr vault and Eirvr — together with any desktop client we make available for them. It does not cover third-party sites we link to, or services you connect to a Verndr product (for example, a cloud storage bucket you link to Klarvr), which are governed by that provider’s own privacy terms.

2. The short version

The contents of your vault are encrypted on your device before they ever reach us, using a key derived from your passphrase. We never receive that passphrase and cannot decrypt what you store. A small set of information outside the vault — listed below — is not encrypted, because we need it in ordinary, readable form to operate your account. This policy exists to say plainly what that is, why we hold it, how long we keep it, and who can ask us for it.

3. Information we hold in the clear

The following categories of information are stored without encryption and are readable by Verndr staff and systems when necessary to operate the service:

• Account identifiers. The email address you register with, and any display name you set. We use this to identify your account, deliver invite and account-recovery email, and respond to support requests.
• Operational metadata. Timestamps for account creation, sign-in, and vault activity; the IP address and general device or browser type associated with a request; and error or audit logs generated while operating the service. We use this to secure accounts, investigate abuse, and diagnose faults. What kind of operational metadata can we see? Here’s an example.
• Correspondence. Messages you send to an @verndr.com address, kept for as long as needed to answer them and to keep a record of the exchange.
• Wrapped keys and ciphertext. Your vault contents and the wrapped copy of your vault key are stored on our servers, but not in the clear — see Section 4. We list them here for completeness, since the bytes are retained even though their contents are not readable to us.

4. What stays encrypted, and what that does and does not mean

Files and records you place in a Verndr vault are encrypted with AES-GCM on your device before upload. The key used to encrypt them is itself wrapped with a key derived from your passphrase, which we never receive or store. The practical effect: we cannot read your vault contents, and we cannot recover them for you if you lose your passphrase. Encryption of vault contents is not a claim about the account identifiers or operational metadata described in Section 3 — that information is not encrypted, and is covered by the rest of this policy.

5. Health-related information (Eirvr)

Eirvr applies the same client-side encryption described in Section 4 to the health and wellness records you store in it; we hold the same account identifiers and operational metadata described in Section 3, and nothing more. Eirvr is an invitation-only Alpha and is not currently certified under HIPAA or offered as a business-associate arrangement — see our compliance page for the current status of formal compliance programs.

6. Payment information

This Alpha does not process payments and does not collect card or billing information. When paid plans return, this policy will be updated first to describe what a payment processor collects on our behalf and how long it is kept.

7. How long we keep it

We hold the information in Section 3 for as long as your account is active. If you delete your account, we retain it for 90 days — to allow for account recovery and to investigate any abuse or security incident in progress — after which it is permanently erased from our production systems. Backups that include deleted-account data age out and are overwritten on our normal backup rotation.

8. Who we share it with

We do not sell any information described in this policy, and we do not share it with third parties for their own marketing purposes. This Alpha does not currently run on third-party infrastructure that would make it a recipient of the information in Section 3; if that changes, we will name the provider and what it can access here before the change takes effect. We disclose information described in Section 3 to a third party only where required by valid legal process, or to protect the rights, property, or safety of Verndr, our users, or the public. Because vault contents and wrapped keys are encrypted end to end, we have no capability to produce decrypted contents in response to such a request.

9. Your choices

Contact legal to request a copy of the information described in Section 3, or to request that your account and its data be deleted under the schedule in Section 6. We do not currently operate a formal, automated GDPR or CCPA rights-request process; every request on this Alpha is handled by a person.

10. Children

This Alpha is not directed to, and is not knowingly offered to, anyone under 16. If you believe a child has registered an account, contact legal and we will close it.

11. Changes to this policy

We will update the date at the top of this page when this policy changes, and describe the change here if it materially affects how we handle your information.

12. Contact

Questions about this policy: contact Legal. We do not have a Data Protection Officer.