Modd uses a small number of cookies and similar technologies (like localStorage) to keep you signed in and remember your preferences.
Strictly necessary
- Session token — keeps you signed in between visits.
- CSRF token — protects form submissions.
Functional
- Onboarding preference — your account remembers that you have seen the first-run tour, with localStorage used only as a browser fallback.
- UI preferences — remembers sidebar state and theme choices.
- Hosted checkout — Dodo Payments may use cookies or similar device information to secure checkout, prevent fraud, manage subscriptions and support payment recovery. Dodo Payments identifies itself and provides its privacy information before you confirm a payment.
No advertising cookies
We do not use cookies for advertising. Payment and recovery technology is used for those service functions, not to build advertising profiles for Modd.
Cookieless traffic and action totals
Vercel Web Analytics counts page views and provides aggregate information such as page, referrer, country, browser and device type. It does not place third-party cookies or attach the data to an account. Before a page path is sent, Modd removes query strings and fragments, replaces report and other opaque identifiers, and excludes authentication callbacks and administrator pages.
Modd also increments daily aggregate totals when an active public shared result loads and when its “Get your free report” link is selected. The aggregate counter table stores only the action and fixed campaign labels such as LinkedIn or other. It does not store the shared-result link, an account or visitor identifier, name, company, role, score, CV or job content, query string, referring URL, IP address or user agent. The counters operate without cookies and are not tied to a person.
Optional product and campaign measurement
If you allow measurement, PostHog records privacy-filtered page views, clicks, form interactions without field values, dead clicks, page exits, scroll depth, web performance metrics and privacy-filtered session replays in addition to the cookieless totals above. Replay is limited to public, legal and sign-in pages plus the authenticated workspace while you add inputs or wait for processing. It keeps ordinary interface text and styling visible, but masks all form values, filenames, role excerpts, account details and errors, redacts potentially private element attributes, and blocks images in your browser before upload. Replay stops before a completed report is shown. Report, result, dashboard and welcome pages are excluded. We do not send CV or job-description text, typed values, emails, error messages, query strings, URL fragments, console logs, network contents or full referring URLs. PostHog uses first-party localStorage for an anonymous browser identifier and stops capturing and persisting data when you withdraw consent.
We also use first-party localStorage for up to 30 days to remember how you first reached Modd. We keep only standard campaign labels (source, medium, campaign and content), an optional referral code, the referring site's hostname and the privacy-filtered landing path.
After you register, this first-touch record is attached to your account so we can understand which sources lead to registrations, reports and purchases. It remains until you delete your account or withdraw measurement consent below. Declining does not affect your use of Modd. If you withdraw while signed out, account-level removal completes when you next sign in on the same browser.
Controlling cookies
You can clear cookies and localStorage at any time from your browser settings; doing so will sign you out. Your account-level onboarding preference is retained, and you can replay the tour at any time from Account.
Current choice: not chosen