A small-data promise
Privacy
Key needs a little information to carry an invitation from one person to another. It should not learn more than that job requires.
Last updated August 29, 2026
What Key collects
- Information a sender provides, such as their name, optional email, note, and experience preferences.
- A recipient's choices, response, and optional note after accepting.
- Operational information needed to run and protect the service, such as invitation state, delivery status, security events, rate-limit signals derived from requests, and timestamps for invitation milestones such as a valid open, each choice screen completed, reveal, response, and note completion.
- If paid links are offered, purchase status and provider reference numbers. Key does not receive or store a full payment-card number.
Key does not ask a recipient to create an account or provide their identity. It does not request precise device location. Whoever holds an invitation link may use it, so possession of a link does not prove who a person is.
How the information is used
We use this information to create and deliver invitations, recommend a fitting place, show the sender the invitation's outcome, send requested service emails, fulfill a paid custom URL, prevent abuse, investigate support reports, diagnose where an invitation stopped working, and keep the service reliable.
Milestone timestamps are available only to authorized service operators for support and reliability work. The event trail does not contain the recipient's choice values, note text, identity, precise location, or private link capability. The recipient's path through the choice screens is not shown to the sender. The sender receives the final response and, only after an acceptance, any note the recipient chooses to leave. Key does not sell personal information or use recipient choices for targeted advertising.
Service providers
Key relies on hosting, database, email, payment, and abuse-prevention providers to perform those jobs. The current providers include Netlify, Convex, Resend, Stripe when paid links are enabled, and Cloudflare Turnstile when bot protection is enabled. Those providers process the information sent to them under their own terms and privacy policies.
Private Key capabilities are kept in the # fragment of the shared URL so the web host does not receive that capability in the page request URL. Do not paste or forward a private Key link to anyone who should not be able to use it.
Retention and expiry
The current MVP does not place a fixed expiry date on invitations. A paid custom URL normally remains connected to its invitation until 14 days (14 × 24 hours) after the recipient accepts and opens the door. The public address is then released and may be used for another invitation. An approved retention exception may have no automatic release date. A decline or unanswered invitation does not start the standard clock or silently release the address.
Releasing a custom address does not delete the underlying invitation. Its private Key and sender-status links can continue to work, and payment, security, abuse-prevention, and support records may be kept when reasonably needed for accounting, disputes, safety, or legal obligations. Refunded, disputed, or moderated addresses remain held from reassignment.
Your choices
To ask what information is associated with you, request a correction or deletion, report an exposed link, or raise a privacy concern, use the support form. Share only the information needed to locate the record. Never submit the private fragment after the # symbol. We may need to verify a request before acting on it, and some records may need to be retained for the reasons described above.
Changes
We may update this notice as Key changes. The date above identifies the current version. This page describes the service's present MVP behavior; it is not a claim that the policy has received legal or regulatory approval.