Cookies
MyWorkLife uses cookies and similar technologies to keep you signed in, protect the platform, and understand how pages perform.
Essential cookies
These are required for core functionality like authentication, session security, protected course access and secure share passcodes.
- Auth.js/NextAuth cookies support sign-in sessions, callback handling and anti-CSRF protection.
mwl_level1_course_accessgives temporary access to the hosted Level 1 course after an eligible launch.mwl_share_*cookies remember a successful passcode for a specific secure share link for a limited time.
Analytics
We use analytics to understand page usage and improve the product. Where possible, analytics events are kept lightweight and focused on product actions (e.g. signup, login, qualification added).
Analytics storage starts denied. If you accept analytics, MyWorkLife may use Google Tag Manager or Google Analytics to measure page use and course journeys. Your choice is stored inmyworklife:analytics-consent, and the banner usesmyworklife:analytics-consent-choice-shown in browser storage so it does not keep reopening.
Email attribution
A marketing link may set a secure, first-party attribution token for up to 30 days so we can understand whether a course purchase followed an email. The token contains no email address and cannot select an arbitrary redirect destination. Marketing emails do not use an open-tracking pixel by default. The cookie name is mwl_marketing_attribution.
Browser storage
Some client-side features use browser storage rather than cookies. Current public checkout and analytics code can use myworklife:checkout-attribution:v1 andmyworklife:purchase-delivery:v1. Logged-in workspace features may also store local interface preferences or draft state, such as account prompts, employment drafts, organisation checkout attempts, billing or credit-purchase state, sidebar state and the last knowledge-base article viewed.
Questions
If you have questions about cookies, contact support via the contact page.
Last updated: