Cookie policy
Without your consent no Google script is loaded at all. Here is everything this site stores and everything that can end up loading, with the exact condition under which it does.
What we use
| Name | Type | Purpose | Duration |
|---|---|---|---|
| workpay:theme | Local storage | Remembers whether you prefer light or dark | Until you clear it |
| workpay:consent | Local storage | Remembers your cookie decision | Until you clear it |
| workpay:locale | Local storage | Remembers whether you prefer English or Spanish | Until you clear it |
| workpay:v1 | Local storage | The calculations and shifts you choose to save | Until you clear it |
| workpay:audit | Local storage | The change log on the administration page | Until you clear it |
| workpay:draft:YEAR | Local storage | Tax parameters you are editing but have not saved | Until you clear it |
| workpay:session | Local storage | Your account session: keeps you signed in between visits. Only exists if you create an account | Until you sign out or clear it |
| workpay:pkce | Local storage | Temporary verifier for the email-link sign-in. Only exists during that process | Until you finish signing in |
| workpay:migrado | Local storage | A flag that the calculations you had in this browser have already been uploaded to your account, so they are not uploaded twice | Until you clear it |
Accounts and passwords
Subscribing to Premium requires an account: that is what lets your subscription follow you across devices and come back when you sign in. Accounts are handled by Supabase, and your password travels from your browser to Supabase directly. WorkPay never sees, stores or logs your password, which is also why it cannot recover it for you — it can only email you a link to set a new one.
Your session is kept in this browser's local storage, under the workpay:session key in the table above. This site sets no cookies of its own: not for the session, not for measurement, not for anything. The only cookies that can appear in your browser while you are here are Google's, if you accept advertising, and Stripe's while you are on their payment page, which is their domain and not ours.
Advertising (Google AdSense)
The Google AdSense script is not in the HTML of these pages. Our own JavaScript inserts it, and only when five conditions hold at once: advertising is switched on server-side, an AdSense ID exists, you are not a Premium subscriber, you have accepted advertising cookies, and the page has a real ad slot. If any one fails, your browser makes no request to Google at all.
When it does load, Google may set its own cookies to measure and to choose which ad to show you. Those cookies are Google's, not ours, and are governed by their policies.
Ownership of this domain is proven to Google with the /ads.txt file, which is plain text: it executes nothing and stores nothing. That is why their script does not need to load for everyone.
If you have Premium, no advertising is loaded under any circumstances.
Other services we use
Stripe processes Premium payments. It only comes into play if you choose to subscribe: it takes you to its own checkout, where you enter your card. We never see or store your card number.
Supabase stores your account, your subscription and whatever you choose to save. It only comes into play if you create an account.
The AI provider configured on the server analyses payslips you upload to the analyser, which is a Premium feature. It only comes into play if you upload a document.
None of the three loads scripts on these pages or sets tracking cookies just for browsing. The calculators work without any of them.
How to change your mind
Use "Manage cookies" in the footer at any time, or clear the site's storage from your browser settings.