Privacy at FindMyWeddingDate
The MVP is intentionally minimal. It does not require an account and does not use your birth dates or wedding-date inputs as analytics properties.
Information used for calculations
When you check a date, the two birth dates and wedding date you enter are sent to the FindMyWeddingDate server so the deterministic calculation engine can produce your free result. If you enter a wedding window in the paid Top 3 offer, the current Test 3 interface keeps those form values in the browser for the purchase-intent test and does not calculate or reveal the Top 3 before checkout is available. The current MVP does not intentionally persist those calculation inputs in a customer database.
Browser storage
A random anonymous identifier is stored in your browser’s local storage for funnel measurement. First-touch utm_source, utm_medium, and utm_campaign values may also be stored there when present. Your current form inputs may be kept in session storage so the same browser tab can preserve the dates you entered.
Analytics
FindMyWeddingDate sends a small set of first-party funnel events to its own server. The server removes property names that look like birth dates, wedding or candidate dates, date ranges, guide tokens, checkout session IDs, payment-provider identifiers, email addresses, or IP-address fields before analytics events are logged or forwarded. If PostHog is enabled, the sanitized event, anonymous identifier, campaign attribution, and basic funnel metadata may be sent to PostHog for product analytics. Person-profile processing is disabled for these events.
Purchase-intent testing
During the current Test 3 pre-validation phase, online payment processing is disabled. After a free date check, the site may display a US$9.99 offer to find the Top 3 personalized wedding dates in a selected wedding window. Clicking that purchase CTA records a sanitized top3_purchase_intent_clicked analytics event and then shows a notice that checkout is not open. No card details are requested and no payment-provider request is made in this mode.
Server and provider logs
The application records operational and sanitized analytics logs needed to run and diagnose the service. Hosting, network, analytics, and payment providers may also process technical request data as part of delivering their services.
Contact
Privacy questions can be sent to [email protected].
Effective for Test 3 pre-validation · October 2026