Privacy
The short version: we save your progress, question selections, and journey activity so you can resume and so we can improve the product.
Assessment and fulfillment
We save assessment answers, including safety answers, journey choices, progress, and the exact screen reached in this browser so the journey can resume after an ordinary exit or reload. If you continue to checkout, the complete answer set and journey choices are also stored with the order so we can build the product you are buying. Scores and generated results are recomputed when needed.
What we do record
We use PostHog to record product analytics, including pages and screens viewed, anonymous interaction timing, navigation, exits, resumes, plan choices, pay-button taps, checkout and payment outcomes, performance, errors, and experiment assignments. For each assessment selection, including safety questions, the structured answer event sends only the authored question ID, numeric option position, time from the screen view to selection, and selection change count; that event does not contain option text or raw advertising click IDs. Separately, PostHog session replay is configured for 100% of sessions without surface or input masking. Replay records the complete rendered experience and interactions, including question and selected-answer text, safety selections, personalized results, generated schedules, Baby pattern, goal and plan-style choices, signature canvas marks, plan selection, order review, first-party payment states, and text entered into first-party fields such as refund or cancellation email confirmation. Card details are entered on Stripe's separate site and are not part of this replay. Recorded URLs have query strings and fragments removed, so raw advertising click IDs are excluded. Events carry anonymous journey and session identifiers, timestamps, build and journey versions, and limited campaign labels from the link you arrived on. We do not identify PostHog visitors with their checkout email, although replay can contain an email typed into a first-party field as described above.
Advertising measurement
When advertising measurement is enabled, this site loads the Meta pixel and sends one standard PageView event. Meta may receive the page URL, which names the experiment topic, along with your IP address, browser or device information, and Meta cookies or identifiers. Those details may allow Meta to recognize a browser and infer interest in the topic. After Stripe creates a real checkout session, our server sends Meta an InitiateCheckout event. After Stripe verifies a payment, our server sends Meta a Purchase event. Both server events contain the amount, currency, stable event identifier, source URL and, when available, the browser user agent, IP address, and Meta fbp and fbc identifiers. We do not send Meta your assessment answers or options, score, result profile, safety reason, personalized result, checkout email, phone number, name or address. ViewContent, automatic event capture and advanced matching stay off. Until measurement is configured, no Meta event is sent.
Payments
Payments are processed by Stripe. Card details are entered on Stripe's own page and are never seen by us. From the payment we keep the identifiers needed to reconcile, cancel and refund the subscription, the amount, the plan, and the email address Stripe collects. Assessment answers are stored in our separate fulfillment record and are never placed in Stripe metadata. When advertising measurement is enabled, the limited browser IP, user agent, fbp and fbc information described above is also stored with the order so a failed server event can be retried. Stripe processes your payment data under its own privacy policy.
Cookies and storage
We use browser local storage for assessment progress, answers, journey identifiers, attribution, experiment assignments, and pending exit delivery so an ordinary reload or exit can resume at the exact screen. PostHog session replay uses the anonymous identifiers and complete-experience recording described above. If advertising measurement is enabled, the Meta pixel sets its own cookies.
Retention
Product analytics events and session replays are retained while the experiment runs and for the reporting period that follows. Order and payment records, including the limited advertising match information when measurement is enabled, are retained as long as tax and financial rules require. The separate fulfillment record is deleted after an unpaid checkout is verified as expired, when an order is refunded, or after fulfillment is completed. Closing or cancelling the browser checkout alone does not delete it because payment confirmation can arrive later.
Your choices
Exits retain progress so you can resume at the exact screen you reached. Write to assistant@wayd.social from the address used at checkout to ask what we hold or to request deletion of the separate fulfillment record. Financial order records may be retained where required.
Contact
Privacy questions go to assistant@wayd.social. Do not repeat assessment details in a support message because the fulfillment record is linked to the order reference already.