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. After you enter a valid email, we also save that email with the journey and advertising attribution needed to send one private resume link if you remain inactive for 10 minutes and have not started a trial or purchased. 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 and session replay, including pages and screens viewed, interaction timing, navigation, exits, resumes, assessment selections, personalized results, plan choices, pay-button taps, checkout and payment outcomes, performance, errors, experiment assignments, complete rendered experiences and interactions, text entered into first-party fields, URLs and attribution parameters, journey and session identifiers, campaign information, and other properties supplied by the product. Card or wallet details are entered in a Stripe-controlled checkout surface and are not part of this replay.
Advertising measurement
When advertising measurement is enabled, the browser and server send matching Meta PageView, QuizStarted, Quiz25, Quiz50, Quiz75, ViewOffer, AddToCart, and Jolly events with shared identifiers so Meta can count each event once. AddToCart means you pressed See my plan on the offer screen. When you press the first Pay now button, the browser and server send matching InitiateCheckout events with the same deduplication method. Meta may receive the page URL, which names the experiment topic, along with standard event, customer-information and product parameters available at the time of the event. These can include your IP address, browser or device information, Meta cookies or identifiers, journey external ID, checkout-email match information, selected amount and currency, assessment or personalization context, and product information. Those details may allow Meta to recognize a browser and infer interest in the topic. Fields are normalized or hashed where Meta requires it. After Stripe verifies a payment, our server sends Meta a Purchase event. Meta may receive the stable event identifier and source URL plus standard event, customer-information and product parameters available at the time of the event, including the browser user agent, IP address, Meta fbp and fbc identifiers, journey external ID and a normalized SHA-256 hash of the checkout email. Card and wallet details remain in Stripe's payment surface and are not sent to Meta. Until measurement is configured, no Meta event is sent.
Payments
Payments are processed by Stripe. Card or wallet details are entered in Stripe-hosted checkout or Stripe's embedded payment element and are never seen by us. From the payment we keep the identifiers and information needed to reconcile, fulfill, cancel and refund the subscription, the amount, the plan, and the email address Stripe collects. When advertising measurement is enabled, the event and customer-information parameters described above are 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. An inactive-journey recovery record is suppressed when checkout is verified, can be stopped from its email link, and is kept only for recovery, attribution and delivery auditing. 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. The one saved-plan email includes an unsubscribe link that stops that reminder without affecting a purchase. 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.