Privacy Policy

Introduction

Recivity is an encrypted vault with a dead-man switch. You store critical information encrypted in your browser, check in on a schedule, and if you go silent, trusted beneficiaries can unlock access. This Privacy Policy describes what information we collect and how we use it.

Information we collect

Account information: name, email address, and a password hash if you register with email and password. If you sign in with Google or Facebook, we receive that provider’s profile name, email, and profile image.

Vault information: encrypted document ciphertext, an owner wrap secret used to unlock the vault while you are signed in, recovery question text, beneficiary names, email addresses, and optional phone numbers, check-in timestamps, and escalation logs (reminder and release notifications).

Usage metrics: for each page view we may store a one-way hash of your IP address and User-Agent, which page class you opened (for example home, login, or register), whether the User-Agent looked like a known crawler, and the calendar day. When you sign in successfully we store your account id and the calendar day. We use these rows only for approximate traffic counts in an internal daily stats email. We do not set an analytics cookie for this.

Email display: when an email client loads the Recivity mark in a message we sent, we store the time of the first load for that message. Later loads of the same message are ignored. Automatic image fetching by some email clients can record this without a person having read the message.

We do not collect or store document plaintext or recovery answer text. Those stay on your device or are derived only in the browser for encryption and decryption.

How we use information

We use account and vault metadata to authenticate you, operate check-in reminders and release notifications, and maintain vault state (active, warning, or released).

We use usage metrics to understand approximate traffic patterns and operate the product.

We use the first-load time on outbound emails to see whether a message was displayed.

We do not sell your personal information.

Social login (Google and Facebook)

If you continue with Google, Google shares profile information with us according to your Google account settings and Google’s policies. See the Google Privacy Policy for how Google handles your data.

If you continue with Facebook, Meta shares profile information with us according to your Facebook account settings and Meta’s policies. See the Meta Privacy Policy for how Meta handles your data.

Third-party services

We use Vercel for hosting, Neon for Postgres database storage, and Resend for transactional email (check-in reminders and release notices). Those providers process data under their own privacy policies.

We use Sentry for error monitoring. When something breaks, Sentry receives a technical report (the error message, stack trace, page or endpoint, and browser type). We configure it to exclude request contents, cookies, your IP address, account identifiers, and any vault data. Reports are kept for 30 days.

Cookies and local storage

We do not use advertising or cross-site tracking cookies. The cookies Recivity sets itself are listed below, and all of them are necessary for the site to work.

Sign-in cookies (authjs.session-token, authjs.csrf-token and authjs.callback-url, plus short-lived authjs.pkce.code_verifier, authjs.state and authjs.nonce cookies during social login — each prefixed with __Secure- or __Host- over HTTPS): these keep you signed in and protect the sign-in form against cross-site request forgery. The session cookie expires after 30 minutes of inactivity; the others are cleared when you close your browser or once the sign-in flow completes.

recivity_locale: remembers which language you are viewing the site in, for up to one year.

recivity_tz: records your browser’s time zone so reminder emails arrive at a sensible hour. It lasts at most 10 minutes and is deleted once your time zone has been saved to your account.

Our public pages — the home page, pricing, guides, and the sign-in and registration pages — display a TrustedSite verification badge loaded from cdn.ywxi.net. That script stores its own cookies and local storage entries on your device and communicates with TrustedSite’s servers. It is not required to operate your account, and it is never loaded on signed-in pages such as your vault, will, or dashboard. See the TrustedSite Privacy Policy for how TrustedSite handles that data.

We use Vercel Speed Insights to measure page load performance. It does not set cookies and does not build a persistent identifier for you.

You can clear or block cookies in your browser settings. Blocking the sign-in cookies above will prevent you from signing in to Recivity.

Data security

Vault documents are encrypted in the browser with AES-GCM before upload. A random document key is wrapped with a key derived from an owner wrap secret stored with your account (so you can unlock while signed in) and separately with a key from recovery answers (for beneficiaries after release).

Because the owner wrap secret is stored with the ciphertext, anyone with access to the database can decrypt vault contents as the owner. Recovery answers are not stored and remain the end-to-end path for beneficiaries. You are responsible for protecting your account credentials.

Data retention

We keep your account and vault data while your account is active. If you want your data deleted, contact us at the address below. Self-serve account deletion is not available in the current version of the product.

Usage metric rows are kept for about 90 days, then deleted.

Your rights

You may request access to or deletion of your account data by emailing us. We will respond within a reasonable time.

Changes

We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page will change when we do. Continued use of Recivity after a change means you accept the updated policy.

Contact

Questions about this Privacy Policy: admin@recivity.com.

Disclaimer

This document is for informational purposes only and is not legal advice. It is an MVP draft and has not been reviewed by an attorney.