This Cookie Policy explains how Simpson Soft UK Limited (“we”, “us”) uses cookies and similar technologies on workframe.online and in the Workframe app. It should be read with our Privacy Policy.
In short: Workframe uses strictly necessary cookies to sign you in, keep your session secure and remember which Workspace you are using. With your permission, our website also uses one optional cookie to record how you found Workframe. We do not use advertising cookies or tracking cookies from other companies.
1. What cookies are
Cookies are small text files that a website stores on your device. They let the site recognise your device between pages and visits. Similar technologies, such as local storage, work in a comparable way; this policy covers them too. “First-party” cookies are set by the site you are visiting; “third-party” cookies are set by another domain.
2. How we use cookies
Under the Privacy and Electronic Communications Regulations, cookies that are strictly necessary to provide a service you have asked for do not need consent. Most cookies Workframe sets fall into this category. Without them you could not sign in or use the app securely.
We use one optional cookie, workframe_source, only if you choose Accept in the cookie banner on our website. You can change your choice at any time with Cookie settings at the bottom of any page on our website.
3. Cookies we use
| Cookie | Set by | Purpose | Duration |
|---|
| __Secure-neon-auth.session_token | Workframe (first party, via our authentication provider Neon Auth) | Keeps you signed in and identifies your session securely. HTTP-only and secure. | Until you sign out or the session expires |
| __Secure-neon-auth.session_data | Workframe (first party, via Neon Auth) | Briefly caches session details so pages load quickly without weakening security. | A few minutes, renewed while you are active |
| Sign-in state cookies (names beginning __Secure-neon-auth) | Workframe (first party, via Neon Auth) | Protect the “Continue with Google” sign-in flow against forgery and return you to the right page. | A few minutes, during sign-in only |
| workframe_active_org | Workframe (first party) | Remembers which Workspace you last opened if you belong to more than one. We check it against your actual memberships on every request; it never grants access by itself. | 12 months |
| Security cookies such as __cf_bm | Cloudflare (first party, on workframe.online) | May be set by our network provider to distinguish people from automated traffic and protect the service from attack. | Up to 30 minutes |
| workframe_consent | Workframe (first party) | Remembers whether you accepted or declined the optional cookie below, so we do not ask again on every page. | 12 months |
| workframe_demo | Workframe (first party) | Keeps you in your private demo workspace and remembers which demo person you are viewing as. Set only when you start the demo. HTTP-only and secure. | 24 hours |
| workframe_calculator | Workframe (first party) | Carries the full-time days per week, holiday allowance and leave year start you entered in the pro-rata holiday calculator to the Workspace you create, so it starts with them. Set only when you choose to set the calculator up for your team; it holds those figures and nothing about you. HTTP-only, and deleted when your Workspace is created. | 48 hours |
Optional cookie (only with your consent)
| Cookie | Set by | Purpose | Duration |
|---|
| workframe_source | Workframe (first party) | Records how you first reached our website: the website that linked to us, any campaign tags in the link (such as utm_source), the first page you visited and when. If you then start a trial, we save this with your new Workspace so we can see which websites and campaigns bring new customers. It is not used for advertising and is not shared with other companies. | 30 days |
We do not store personal data in local storage or session storage.
4. Third-party pages
When you subscribe or manage billing, you are taken to secure pages hosted by Stripe (checkout.stripe.com and billing.stripe.com). Stripe sets its own cookies there for payment processing and fraud prevention, as described in Stripe’s Cookie Policy. If you choose “Continue with Google”, Google’s own sign-in pages and cookies apply, as described in Google’s Privacy Policy. We do not control these cookies.
5. Managing cookies
You can block or delete cookies through your browser settings. If you block the strictly necessary cookies above, you will not be able to sign in to Workframe or stay signed in. Signing out removes your session cookies.
You can withdraw consent for the optional cookie at any time with Cookie settings at the bottom of our website. Choosing Decline deletes it.
6. Changes to this policy
If we introduce any other cookies that are not strictly necessary, we will update this policy first and ask for your consent before setting them. The effective date at the top shows when this policy last changed.
Questions: support@workframe.online.