Privacy Policy
Last updated: August 17, 2026
Invitease collects only the information needed to create, manage, activate, and share digital invitation pages during launch.
Information we store
We store account email addresses, invitation details, RSVP submissions, payment status, and basic page view counts. RSVP information is visible to the invitation owner.
Payments
Midtrans processes hosted Premium checkout details under its own privacy practices. Invitease stores payment references, status, method, and notification audit data needed to verify payment and activation, but does not collect card or wallet credentials. Manual payment proof may be sent through WhatsApp or other payment tools outside Invitease, which also apply their own privacy practices.
Done-for-You setup
When you request Done-for-You setup, event details, contact information, wording, links, images, and revision feedback may be shared through WhatsApp. Invitease uses those materials only to communicate about, prepare, review, and publish the requested invitation. WhatsApp applies its own privacy practices to information sent through its service.
Template setup callback requests
When you ask Invitease to set up a selected template, we store your name, canonical WhatsApp number, selected template, site language, request status, and timestamps. We also store a one-way 64-character network fingerprint derived with a server-only secret from Netlify's trusted connection IP header. We do not store the raw IP. The fingerprint is used only to prevent abusive submissions. Access is limited to authorized Invitease admins, who use the request to contact you about that invitation and manage the callback queue.
Analytics and advertising measurement
On marketing pages, Invitease offers optional Google Analytics, Google Ads, and Meta Pixel measurement. Before you choose, Google Ads may receive limited cookieless signals with advertising-click identifiers redacted; Google Analytics and Meta Pixel do not receive Invitease page-view events. If you allow measurement, Google Analytics and Meta Pixel receive marketing-page paths and basic browser or device information, while Google Ads and Meta Pixel may store cookies and receive payment-conversion information to connect a purchase with an earlier advertising click. Invitease does not measure invitation pages, authentication, dashboard pages, or private payment-detail pages with these services. Payment conversion data contains the value, currency, a random transaction reference, and a generic confirmation-page location, not private payment URLs, invitation content, RSVP responses, or payment credentials. Ad personalization and Google signals remain disabled. You can remove or change the stored choice through your browser cookie settings.
First-party product measurement
After login, Invitease records whether an account first reaches the invitation creator, reaches the template picker, selects a template, and begins filling in the invitation form. These account-linked events do not contain invitation content, contact details, browser information, or full URLs, are not sent to Google or Meta, and are removed when the account is deleted. Invitease uses them only to understand where the creation flow is abandoned.
Data access
Dashboard data is protected by account login. Public invitation pages are accessible only when an invitation is active and unexpired.
Images and guest content
Uploaded images and event content are used to render the invitation page selected by the invitation owner. RSVP submissions are collected for the invitation owner and should only include information needed for the event.
Deletion requests
To request deletion or correction of invitation data or a setup callback request during launch, contact Invitease through WhatsApp or the direct message channel used during onboarding. Invitease deletes callback contact data when it is no longer needed for the request or when a valid deletion request applies, subject to legal or abuse-prevention needs.