Privacy Policy
Last updated: November 10, 2026
1. Who We Are
HeyVite is a digital invitation and event-planning service ("HeyVite", "we", "us"). This policy explains how we handle information about hosts, guests and site visitors. We determine how account, billing, security and support information is used to operate the service. Hosts decide which guest details to provide and which event features to use; we process that information to deliver those features. You can contact HeyVite at [email protected].
2. Personal Data We Collect
2.1 Account and Host Data
When you register as an event host, we collect:
- Your name and email address;
- A password hash, if you use password sign-in; we do not store your password in plaintext;
- Passkey public-key credentials and related authentication metadata, if you enable passkeys. We do not receive your fingerprint or face scan; any biometric check is handled by your device or passkey provider;
- Sign-in provider identifiers, name and email if you use an available Google or Apple sign-in option;
- Account preferences, saved contacts and communications you send to support.
2.2 Event and Guest RSVP Data
To generate, customize, and deliver your digital invitation, we collect and store:
- Event details: Title, date, venue, invitation wording, itinerary, sub-events, dress codes, uploaded images and photo albums;
- Guest lists: Names, email addresses, phone numbers, and group relationships (individual, couple, or family classifications);
- RSVP responses: Attendance status, meal preferences, dietary restrictions, guest counts, accompanying guests, and notes/wishes written for the host;
- Mailing addresses if the host enables address collection and you provide one;
- Delivery and invitation interaction records, including first-view time and language preference, to help hosts manage invitations.
2.3 Usage and Telemetry
Requests to the service can include IP addresses, browser/device information, page addresses and timestamps. We use operational logs and security checks to run the service, investigate errors and prevent abuse. Page and feature-usage measurement is described in section 5. Support requests can include the page you contacted us from, your name, email address and message.
2.4 Billing and Transactional Records
Paddle, our Merchant of Record, collects payment details through its checkout and handles them under its privacy notice. HeyVite receives purchase and billing information to activate and manage your access, such as the plan or add-on, transaction and subscription references, purchase date, payment status and billing period. Yearly passes create recurring subscription records; per-event plans and add-ons are one-time purchases.
3. Why We Process Your Data (Legal Bases)
- Providing the service: To manage accounts, create invitations, deliver messages, collect RSVPs and provide the planning features you request. Where applicable, this is necessary to perform our agreement with you or process guest information on the host's instructions.
- Legitimate interests: To secure the platform, investigate errors, prevent abuse and maintain the service, where permitted by applicable law and balanced against your rights.
- Consent: For optional analytics cookies and other processing that requires your consent. You can change your cookie choice in the footer.
- Legal obligations: To meet applicable tax, accounting and legal requirements.
4. Data We Do Not Collect or Use
- We do not sell host or guest list personal information to third parties.
- We do not share your private wedding details or guest lists with advertising networks.
- We do not use your guest lists to train our own machine-learning models. The optional wording assistant is described in section 6.
5. Cookies and Similar Technologies
We use cookies and browser storage for sign-in, protected event access, preferences and measurement. Google Analytics cookie storage is disabled until you accept analytics cookies. That choice does not disable all network measurement: cookieless requests and operational records are described below. You can revisit your choice using “Cookie settings” in the footer.
5.1 Session recording and invitation records
We do not record your screen or reconstruct your visits as session recordings. Usage measurement records page and action information rather than a replay of your screen. Information you submit in forms is processed to provide the requested service.
- Guest routes. Analytics integrations are configured to exclude guest-facing invitation, RSVP and event website routes.
- Invitation records. Separately, interacting with a personal invitation can record its first-view time and language preference for the host. Delivery records and RSVP responses are also part of the event service.
- Submitted content. Our custom analytics events do not include guest-list entries, passwords or the text of your messages.
5.2 Essential and preference storage
Storage used for service features includes:
- Sign-in session: keeps you logged in to your host dashboard after you authenticate. Stored as a secure, http-only cookie and cleared when you sign out.
- Event access: remembers that you entered the correct password for a protected event website or photo album, so you are not asked again on every page. It is scoped to that one event and expires on its own (within about seven days).
- Language preference: when you change language, a preference cookie can remember your choice for up to one year.
- Cookie choice: local storage remembers your analytics-cookie preference so you can review or change it later.
Preference storage can be used before you create an account. It is separate from optional analytics cookies.
5.3 Security cookies (Cloudflare)
Our site runs behind Cloudflare, which may set strictly-necessary security cookies to detect bots and abuse, for example when the Turnstile check runs on our sign-in and contact forms. These protect the platform and are not used to profile you or follow you across other websites.
5.4 Design storage
The Card Studio can save an in-progress design in your browser’s local storage so you can continue editing. Browser storage can be cleared by you or your browser. Saving to an account, uploading media or using an online feature sends the information needed for that feature to the service.
5.5 Analytics
Analytics is used on marketing and host-facing pages to understand page visits and product use. The integrations are configured to exclude guest routes as described above; this is separate from the invitation records used by hosts.
- Cloudflare Web Analytics: cookieless measurement of page visits and performance on eligible pages.
- Google Analytics 4: can send cookieless measurement requests before you accept analytics cookies or after you decline. Declining does not stop these cookieless requests. Google receives page addresses, page titles and request information such as your IP address. Query parameters are filtered to campaign and ad-click identifiers, but the page path and title can include identifiers associated with host-management pages. If you accept, analytics cookies can recognize a returning browser and product milestones such as sign-up and purchase can be reported. Our custom milestone events contain action details such as plan and sign-in method, not guest lists or message text. Ad personalization is disabled.
- HeyVite usage measurement: when enabled, a first-party tracker uses a random tab-session identifier in session storage to group actions. It sends the page path and query to HeyVite to classify the action; the usage record stores the session identifier, action and time. It is separate from Google Analytics. The cookie choice also controls this tracker once applied, though a request already queued or sent may still be processed.
5.6 Managing cookies
Open Cookie settings in the footer to accept or decline analytics cookies. Declining disables permission for Google Analytics cookie storage; it does not remove cookies already stored or stop cookieless measurement. You can clear cookies and other site storage in your browser. Blocking essential storage may prevent sign-in, protected event access or saved preferences from working; declining analytics cookies does not prevent those features.
6. How We Share Data
Information is shared with the people and service providers needed for the features you use. Providers may have their own privacy responsibilities and policies:
- Hosts and authorized collaborators: hosts and authorized co-hosts can access event information and guest responses according to their permissions. Content published in an event website, invitation or shared album is visible according to the selected feature and sharing settings.
- Paddle: processes payments, subscriptions, tax and refund records as Merchant of Record under its privacy notice.
- Email delivery providers: process recipient addresses and message content to deliver invitations, account messages, support replies and requested updates.
- Hosting, storage and Cloudflare services: support the website, databases, uploads, backups, content delivery and bot protection.
- Google or Apple sign-in: if you choose an available provider sign-in option, authentication information is exchanged with that provider.
- Google Gemini: when AI generation is enabled, the optional wording assistant sends the occasion, tone, event title and variation request to Google to generate wording. Information you include in the title is included in that request. When AI generation is not enabled, the assistant uses a curated wording library.
- Google Analytics and Cloudflare Web Analytics: process measurement information described in section 5.
Providers may process information in countries other than your own. You can contact us about recipients and international processing. We may also disclose information where required by law or necessary to address fraud, security incidents or legal claims.
7. Data Retention
- Account and event data: used while your account and events are active, subject to the storage limits of the relevant plan and feature. Hosts can delete guests or events, or request help from support.
- Account deletion: available from Settings → Security → Delete account. It removes account and associated event records from the active database. Upload cleanup and backups are handled separately, so deletion does not mean every copy disappears immediately. Records needed for security, disputes or legal obligations may be retained.
- Billing and support records: retained as needed to manage purchases, resolve support issues or disputes and meet applicable tax, accounting and legal obligations. Paddle separately retains records under its own privacy notice.
8. Your Legal Rights
You can request access, correction, export or deletion of your personal information by emailing [email protected]. Depending on applicable law, you may also have rights to object to or restrict processing, withdraw consent, or complain to a data-protection authority. We may need to verify your identity and will respond within the time required by applicable law, explaining any permitted extension or exception. If your request concerns an event hosted by someone else, we may need to coordinate with that host. Withdrawing consent does not affect processing that was lawful before withdrawal.
9. Security Measures
We use safeguards including password hashing, public-key passkey authentication, randomized invitation tokens and access checks for hosts and authorized collaborators. Private guest-list records are subject to those access controls; information shared through invitations, event websites and albums follows the host's settings. Anyone holding a personal invitation link may be able to view and respond to that invitation, so keep those links private. No security measure can eliminate every risk.
10. Contact Information
For any privacy inquiries, data deletion requests, or questions about this policy, please contact us at:
Email: [email protected]