Cookie Policy
Last updated: 27 October 2026. See what changed.
This policy explains the cookies Clarify uses. The short version: inside the service, we use only the cookies needed to sign you in and stay secure. On our public marketing pages and the sign-up form, we also use Google Ads measurement so we can tell which of our adverts led someone to sign up. That measurement never runs inside the signed-in app, and we do not use analytics, session recording or social media tracking pixels anywhere.
What a cookie is
A cookie is a small file a website stores in your browser and reads back on later requests. It is how a website remembers that you are signed in, rather than asking for your password on every page.
Cookies inside the service
All of the cookies below are strictly necessary. The service cannot work without them, so there is nothing to opt out of. They are set by Clarify itself, not by any third party, and they are the only cookies in use once you are signed in.
| Cookie | Purpose | Lifetime |
|---|---|---|
| Authentication | Keeps you signed in and records which workspace you are working in, plus whether you have completed two-factor authentication. Encrypted, and readable only by us. | Until you sign out, or up to 30 days if you chose "keep me signed in" |
| Two-factor sign-in in progress | Set after your password is accepted and before you enter your authenticator code, so we know whose code to check. Removed as soon as sign-in completes. | 5 minutes |
| Remembered device | Set only if you tick "Remember this machine" when entering your two-factor code. Lets you skip the code on that browser next time. Untick the box, or clear your cookies, and the code is required again. | 14 days |
| Anti-forgery token | A security cookie that proves a form submission came from our site. It is what stops another website from acting on your account without your knowledge. | The browsing session |
| Status message | Carries a one-off confirmation message across a page redirect, for example after you change a setting. | Seconds, then discarded |
Advertising measurement on our marketing pages
We advertise Clarify on Google. To know which adverts work, our public pages (the home page, the solution and audience pages, the help centre, these legal pages) and the sign-up form load the Google Ads tag. It records that a page was viewed and, if you reach the "check your email" page after signing up, that a sign-up happened. It does not load on any signed-in page, on the organisation portal, or on a customer's digital card, so nothing about how you use the service, or about any customer's comments, ever reaches Google through our site.
| Cookie | Purpose | Lifetime |
|---|---|---|
| _gcl_au | Set by the Google Ads tag on our own domain. Holds a random identifier so that a sign-up can be matched to the advert that was clicked. | 90 days |
| _gcl_aw, _gcl_gs | Set only if you arrived from a Google advert. Store the click identifier Google attached to the link, for the same matching purpose. | 90 days |
| Google's own cookies | The tag also talks to Google's servers (google.com, googleadservices.com, doubleclick.net), which may read or set cookies on Google's domains under Google's cookie policy. We do not receive those cookies and cannot read them. | Set by Google, up to 13 months |
To opt out, block cookies from google.com and doubleclick.net in your browser, use a tracking blocker, or turn off ads personalisation in Google's ads settings. None of that affects your ability to use Clarify.
The bot check on the demo form
The form that requests a live demo carries a check run by Cloudflare (called Turnstile) so that a script cannot use it to send email in bulk. Most people never see anything; some are shown a small box to tick. The check runs inside a frame from Cloudflare and sets no cookie on our site. Cloudflare receives your browser's network address and the technical signals it uses to tell a person from a script, under Cloudflare's privacy policy. It is on that one form only, never on a signed-in page, and nothing you type into the form goes to Cloudflare.
Fonts
Every page, including signed-in pages, loads the Inter typeface from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). Google's font service sets no cookies and runs no script. Like any web request, it receives your browser's network address and the address of the page you are on, and Google says it does not use those requests to build profiles. If you would rather it did not happen, a content blocker that stops requests to those two hosts leaves Clarify fully usable in your browser's default font.
What we do not use
- No analytics, session-recording or heat-mapping tools, on any page.
- No social media tracking pixels.
- No advertising or retargeting cookies inside the signed-in service.
- No third-party scripts inside the signed-in service. The only third-party request a signed-in page makes is for the typeface described above.
Connecting a Facebook, Instagram, Threads, TikTok, X or Bluesky account sends you to that platform's own sign-in page to authorise us. Those platforms set their own cookies on their own sites, under their own policies. We receive an access token back, not your browsing history.
Managing cookies
You can clear or block cookies in your browser settings. Blocking the strictly necessary cookies will sign you out and prevent you from signing back in; blocking the advertising measurement cookies has no effect on the service. Clearing them all is a safe way to end a session on a shared computer.
Changes
If we add a cookie, or extend where one is used, we will update this page and the date at the top before doing so.
Contact
Questions about this policy: support@clarify.net.au. See also our Privacy Policy.
