Privacy Policy

1. Who We Are

HeyVite is a premium digital invitation and RSVP management platform ("HeyVite", "we", "us"). We are the data controller for the personal data processed through our website and invitation builder, except where our hosts upload guest details, in which case we process that data on the host's behalf to deliver the event's communication.

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;
• Your password hash (we use secure encryption and never store plaintext passwords);
• Passkey biometric identifiers (WebAuthn credentials and challenges), if you choose to enable passwordless login.

2.2 Event and Guest RSVP Data

To generate, customize, and deliver your digital invitation, we collect and store:

• Event details: Title, date, venue, message to the couple, itinerary, sub-events, dress codes, and uploaded cover images;
• 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.

2.3 Usage and Telemetry

We collect standard audit logs, IP addresses, session timestamps, and device headers when you access our host dashboard or guest RSVP portals. This is strictly to prevent abuse, secure the platform, and provide guest-access security features.

2.4 Billing and Transactional Records

Paid upgrades are processed securely by Paddle, our Merchant of Record. Payment-card details and full billing addresses are collected and stored by Paddle under their own privacy standards. HeyVite receives a limited transaction record (including the purchased tier, country and last 4 digits of the card) to activate your premium features.

3. Why We Process Your Data (Legal Bases)

• Performance of a Contract: To host your customized invitation web page, email invitation links, authenticate your login sessions, and track guest RSVPs.
• Legitimate Interests: To secure the platform against fraud, prevent inappropriate language via our profanity filters, and monitor platform performance.
• Legal Obligations: For billing records, financial taxes, and corporate accounting 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 read or parse your guest data to train machine-learning models.

5. Cookies and Similar Technologies

We keep cookies to the strict minimum needed to run the service. We do not use advertising or cross-site tracking cookies. Our baseline analytics is cookieless (Cloudflare Web Analytics, see 5.4). We also use Google Analytics on our marketing pages. It runs in a consent-aware mode: until you accept it on the cookie banner it stores nothing on your device and cannot recognise you or link your visits together, and you can change your mind at any time from the “Cookie settings” link in the footer. Decline, or simply ignore the banner, and no analytics cookie is ever set.

5.5 Session recording

When you accept optional analytics, we may record how pages are used, clicks, scrolling and navigation, and replay them to find where the interface is confusing. This is a reconstruction of the page, not a video of your screen or your camera, and it is subject to these limits:

• Never on guest pages. No recording runs on an invitation, RSVP or event website, exactly as with our other analytics.
• What you type is never captured. Every form field is masked before anything leaves your browser, on every page, including passwords and messages.
• Guest details are hidden. On the host dashboard and event management pages all on-screen text is masked, so a recording shows layout and behaviour rather than any guest’s name, email or reply.
• Short retention. Recordings delete themselves automatically: seven days for dashboard pages, fourteen for everything else.
• Only we can see them, through an authenticated admin page. They are never shared or sold.

Decline analytics, or ignore the banner, and nothing is recorded at all. You can change your mind at any time from “Cookie settings” in the footer.

5.1 Essential cookies we set

These first-party cookies are set only when you actively sign in or open a password-protected event, and are required for those features to work:

• 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).

We set no cookies of our own on our public marketing pages. A visitor who never signs in, and who does not accept optional analytics, receives no cookies from us.

5.2 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.3 Similar technologies

If you try the Card Studio before creating an account, your in-progress design is saved in your browser’s local storage, on your own device, so a refresh never loses your work. It stays on your device and is not sent to us until you choose to save.

5.4 Analytics

We use two analytics tools, and neither one ever runs on guest-facing invitation, RSVP, or event pages. A guest opening an invitation is not measured by us at all.

• Cloudflare Web Analytics (always on, no consent needed): a privacy-respecting, cookieless tool that measures aggregate page views on our marketing pages, which pages are visited and roughly where visitors come from, without cookies, cross-site tracking, or personal data.
• Google Analytics 4: runs on our marketing pages in a consent-aware mode. Before you accept, it measures visits without storing anything on your device: no cookies, and no way to recognise you or connect one visit to another; Google does receive the page address and, as with any web request, your IP address. Only once you accept does it set first-party cookies to recognise a returning browser. It reports page views and a few product milestones (an account created, a plan purchased) to Google (Global) so we can see which pages and guides are useful. Ad personalisation is turned off. We report the page address without its query string, keeping only standard campaign tags (utm_*, and ad-click ids) so we can tell which link brought you here; nothing else from the address is sent, so a sign-in or password-reset link never reaches Google. Milestones carry the shape of the action only (which plan, which sign-up method), never your name, email, or anything about your event or guests. To withdraw consent, open Cookie settings in the footer and choose Decline; the script stops loading on your next page view, and you can clear the cookies it set in your browser settings.

5.5 Managing cookies

You can clear or block cookies at any time in your browser settings. Because the cookies we set ourselves are essential to signing in and keeping your session secure, blocking them may stop parts of the dashboard or protected event pages from working. Optional analytics cookies can be blocked with no effect on the site at all.

6. How We Share Data

We share data only with trusted sub-processors necessary to run the platform services:

• Paddle: Transaction processing and tax collections (Global).
• Google Workspace (SMTP relay): Delivering invitation emails, welcomes, and host OTP codes (US/Global).
• Cloudflare: CDN, DNS management, and Turnstile bot protection (Global).
• Google (Gemini API): Powers the optional guest-concierge chat and the AI wording assistant. When you use those features, the relevant event details and guest first names are sent to Google at request time to generate the reply (Global).
• Google Analytics: Aggregate visitor measurement on our marketing pages, in the consent-aware mode described in 5.4 (no cookies and no recognition of you unless you accept). No guest, event, or guest-list data is ever sent to it, and it does not run on invitation, RSVP or event pages (Global).

7. Data Retention

• Account Data: Retained as long as you maintain an active account.
• Event & Guest Records: Hosts can delete individual guests or a whole event directly from the dashboard. You can also permanently delete your entire account (with all its events, guest records, RSVP logs, uploads and messages) yourself, from Settings → Security → Delete account (it takes effect immediately). Prefer we handle it? Email [email protected] and we will complete the deletion within 30 days.
• Billing Records: Retained up to 7 years to satisfy mandatory tax and audit requirements.

8. Your Legal Rights

Regardless of where you reside, you can request to **access, correct, export, or permanently delete** the personal data we hold about you by emailing our support desk at [email protected]. We will verify your identity and respond to your request within 30 days.

9. Security Measures

We implement strict technical safeguards, including TLS 1.2 or higher for data in transit, argon2id/bcrypt hashing for account credentials, cryptographically randomized invitation and RSVP tokens to prevent guessing or URL scraping, and access controls that keep each host’s guest list visible only to that host.

10. Contact Information

For any privacy inquiries, data deletion requests, or questions about this policy, please contact us at:
Email: [email protected]