This policy explains how OneForce Care uses cookies and similar technologies (such as browser local storage and on-device app storage) on our marketing website, on the web platform, and in the OneForce Care Worker App. It works alongside our Privacy Policy. It is published by Wondertree Studios Pty Ltd (ACN 699 886 498, ABN 82 699 886 498) of Level 10, 387 George Street, Sydney NSW 2000, Australia.
We keep this deliberately minimal: none of our surfaces set tracking, advertising or cross-site cookies, and we do not run analytics scripts on the marketing website.
1. What cookies and local storage are
Cookies are small text files a website can ask your browser to store and send back on later requests, often used to keep you signed in or remember preferences. Local storage is a similar browser feature, but it is only ever read by the site that set it and is never automatically sent to a server with each request. App storage is the equivalent on a phone: data the app keeps on the device itself.
The practical difference matters for privacy. A cookie travels with every request, which is why cookies are the traditional building block of cross-site tracking. Local storage does not travel anywhere unless the application deliberately reads it and sends it.
2. Our marketing website
Our marketing website (this site) does not set any cookies, and does not use any analytics, advertising or cross-site tracking scripts. There is no tag manager, no advertising pixel, no session-replay tool and no third-party font or script loaded from another domain.
Because we set nothing, there is no consent banner to click through. We would rather earn the trust than ask for the consent.
When you submit a contact or demo-request form, the information you type is sent to us to action your enquiry; see our Privacy Policy for how that information is handled and how long we keep it. Our web server records ordinary request logs, including IP address and browser type, which we use to operate and secure the site.
3. The OneForce Care web platform
The platform does not use cookies. Instead, it uses your browser’s local storage for a small number of essential, functional purposes:
| What is stored | Why | What happens if you clear it |
|---|---|---|
| Your signed-in session | So you do not have to log in again every time you open the platform. This is essential to the application working and cannot be provided another way. | You are signed out and must log in again. |
| Your display theme | So the interface renders in light or dark mode as you last chose, without a flash of the wrong style. | The theme resets to the default. |
| Your active organisation | If your account has access to more than one provider workspace, we remember which one you last worked in. | You are asked which workspace to open. |
| Table and view preferences | Some data tables remember which columns you last chose to show, or which view you last used, purely for convenience. | Tables return to their default columns and views. |
None of this data is used for advertising, is shared with ad networks, or is used to track you across other websites or apps. Nothing in the list identifies you to anyone other than the platform you are already signed in to.
4. The Worker App
The Worker App stores data on the device itself, not in a browser. It keeps your signed-in session, your display preferences, and a local copy of the shifts, tasks and notes you need so the app keeps working when the signal drops and syncs when it returns. It also holds a push-notification token so shift notifications can reach your phone.
Location is read only for the specific events the app tells you about: recording a travel leg, and, where your employer has enabled the on-site check, confirming you are at the shift’s starting address when you clock in. The app does not track your location in the background between those events. Push notifications, location and camera access are permissions you grant on the device and can withdraw in your phone’s settings, though withdrawing them stops the related feature working.
Signing out of the app clears the locally stored session and cached records for that account.
5. Third-party pages and content
A few flows hand you over to a page we do not control, and that page may set its own cookies under its own policy:
- the signing page where a document sent for signature is completed; and
- the authorisation screen of an accounting provider such as Xero, when you connect your organisation.
Two features also load content from a mapping provider into the platform page itself, rather than sending you elsewhere: address suggestions as you type into an address field, and the map shown when a travel leg is reviewed. That provider may set its own storage under its own policy when it loads.
We set no cookies of our own in any of these, and we receive no tracking data from them. Where a flow leaves the platform, the platform tells you.
6. Managing cookies and local storage
Because we do not set cookies, there is nothing to manage there. You can inspect or clear local storage at any time through your browser’s developer tools or privacy settings, and you can clear app storage by signing out of the Worker App or clearing the app’s data in your device settings.
Note that clearing local storage for the platform will sign you out and reset your saved preferences, since those functions rely on it. Browser settings that block all storage will stop the platform from being able to sign you in at all.
Most browsers also send a “do not track” or global privacy control signal. We do not need to act on one, because we do not track you in the first place.
7. Changes
We may update this policy if what we use changes. If we ever introduce analytics or any non-essential storage, we will update this page before it goes live and describe exactly what it does. The “last updated” date above reflects the latest version.
8. Contact
Questions about cookies, local storage, or what the app keeps on your device? Email hello@oneforce.com.au.