Your people. Your privacy.

1. The operator & scope

This policy describes the current rsv-we implementation and planned integrations. Before launch, the operator must add its legal name, mailing address, a working privacy contact, the effective date, and a verified request handling process. This draft has not been reviewed by a California attorney.

2. What information is collected

Account information: you supply a name, email address, and password. We store your account identifier, name, email, a salted password hash, a hashed recovery code, and hashed session identifiers. We do not store plaintext passwords or recovery codes. Email ownership is not currently verified. Host accounts may also have event ownership and Stripe connected-account identifiers. Event information includes titles, descriptions, dates, timezones, locations, prices, Amazon links, checklist items, and optional party images. Uploaded images must be JPG files no larger than 2 MB and 600 × 900 pixels. Image payloads are validated and re-encoded to remove embedded metadata.

Guest information: name, email address, event association, RSVP/payment status, the associated account identifier, and item claims. Payment providers receive the details needed to complete checkout. We store checkout references and payment status, not full card details. Hosting providers may collect technical request, security, and access logs. Google Fonts serves typography and receives technical requests such as IP address and browser information when those font resources load.

3. Why we use it & who sees it

We use information to provide accounts, display invitations, register guests, prevent duplicate item claims, coordinate payments and payouts, investigate errors and fraud, and meet legal obligations. Hosts can view their own guest names, emails, and RSVP status. Other guests see whether an item is claimed, without the claimant’s name or email. Authorized site administrators can view account and event records, manage events, disable accounts, and reset passwords. Administrative actions are recorded in an audit log without passwords.

Anyone who receives a published event link may see its event description and location when the site is public. Confirmed guest information is not a public directory. Hosting and infrastructure providers process information to operate the site; Stripe processes checkout and Connect onboarding; Amazon receives information when you follow its links. These providers have their own privacy policies. We do not automatically opt guests into marketing.

4. Cookies, local storage & ads

Essential authentication and hosting cookies may be used. A secure, HTTP-only session cookie keeps you signed in for up to 30 days. Your RSVPs and claims belong to your account and remain accessible when you sign in from another device. Signing out revokes the current session. Account recovery requires your email and the private recovery code provided at signup; email recovery is not enabled. An administrator can issue a temporary password, which revokes prior sessions and recovery codes and requires a new password at the next sign-in. A new recovery code is issued after that change.

AdSense is not active and no advertising tags load in this version. If advertising is activated later, this policy must identify the actual advertising technologies and their purposes, disclosures, and choices. A consent management platform must be configured where required before tags load. The platform must not represent an in-house banner as Google-certified consent.

5. Retention & security

Event and RSVP records are kept while needed to provide the service, handle host requests, resolve payment issues, and meet applicable legal duties. Account registration counts, event counts, RSVP totals, and simulated payment totals are available to authorized administrators. Page-view analytics and advertising metrics are not collected in this version. A verified retention schedule and deletion process must be finalized before launch. Records are not promised to disappear automatically on a particular date.

We use password hashing, account session checks, request origin validation, authentication rate limits, host authorization checks, and verified payment webhooks. No service can guarantee complete security. Share event links carefully, avoid sensitive content, and keep your password and recovery code private. We do not use card information as an account password.

6. California rights & privacy choices

California residents may have rights to know, access, correct, and delete personal information; limit certain uses of sensitive personal information; opt out of sale or sharing; and receive equal service for exercising applicable rights. The scope of CCPA/CPRA obligations depends on the business and legal thresholds. Other California privacy rules may apply independently.

The current version does not run advertising or sell or share personal information for cross-context behavioral advertising. If that changes, the operator must provide the required opt-out controls and honor applicable Global Privacy Control signals. A cookie button alone does not satisfy every privacy requirement.

A working request channel, identity verification process, authorized-agent process, appeal/contact details where applicable, and response workflow must be configured before public use. Until then live commerce is not enabled and policy text remains a review draft. Do not submit sensitive information in test forms.

7. Children, tracking & changes

The service is intended for users 18 and older. We do not knowingly solicit personal information from children under 13. Hosts should invite adults and avoid collecting children’s names or other sensitive information in event descriptions.

This implementation uses no advertising tracking, analytics tags, or profiling. Nonstandard Do Not Track browser signals do not change essential processing; Global Privacy Control must be treated separately under applicable rules. Updates to actual data practices require an updated policy and appropriate notice.