Cookie Policy
Last updated: 26 September 2026
Totallister Pty Ltd (ABN 95 155 821 944), trading as Rank Tally at ranktally.com (we, us, our).
1. Introduction
(a) This policy explains how we use cookies and similar technologies (including local storage) on the Website, and how you can control them.
(b) A cookie is a small file stored on your device when you visit a website, and local storage works in a similar way. Cookies are what let a website keep you signed in, remember what you have chosen, or measure how it is used. Section 3 says which of them we actually set.
2. Types of Cookies
These are the categories a cookie can fall into. We do not set every category — the cookies we actually use are listed in section 3.
Necessary — Required to enable the basic features of this site, such as providing secure log-in or recording your consent preferences. These cookies do not store any personally identifiable data.
Performance — Used to understand and analyse the key performance indexes of the Website, which helps in delivering a better user experience for visitors.
Functional — Help perform certain functionalities such as sharing the content of the Website on social media platforms, collecting feedback, and other third-party features.
Advertisement — Used to provide visitors with customised advertisements based on the pages you visited previously, and to analyse the effectiveness of ad campaigns.
Analytics — Used to understand how visitors interact with the Website. These cookies help provide information on metrics such as the number of visitors, bounce rate, and traffic source.
3. Cookies and Similar Technologies We Use
We set no cookies of our own on this Website — ranktally.com. We keep two small entries in your browser's storage while you use our free report: one ties together the steps of a single visit, and one remembers which set of questions you were shown. Everything else that gets stored comes from the tools we use: our error-tracking tool on every page, the spam check on our contact and free-report forms, the cookie consent banner Google Tag Manager shows on our public pages, Meta's advertising pixel on our public pages, which sets its cookies under our domain, and — when you sign in — the customer portal, which needs cookies to keep you signed in. The Google business picker on the free-report form, and the map behind the grid on your report, store nothing at all — but your browser does contact Google to draw them. Here is everything:
| Name / key | Provider | Purpose | Type | Duration |
|---|---|---|---|---|
rt_fsid (session storage, not a cookie) | Rank Tally | A token our server signs, holding an identifier for one visit to our free report, sent with each step we record — pages reached, questions answered or skipped, buttons clicked — so the steps of that visit can be counted together | Analytics | Deleted when you close the tab |
rt_lead_email (session storage, not a cookie) | Rank Tally | Holds the email address you typed on the first step of the free report, so the next step can show it to you | Functional | Deleted when you close the tab |
rt_quiz (local storage, not a cookie) | Rank Tally | Remembers which set of questions you were shown on our free report, so you see the same set if you come back | Functional | Until you clear your browser data |
__cf_bm (cookie, set on hcaptcha.com) | hCaptcha (Intuition Machines) | Set by the spam check on our contact and free-report forms, to tell automated traffic from people | Necessary | 30 minutes |
| (nothing stored) | Google (Maps and Places) | Draws the business picker on the free-report form, and the map behind the grid on your report. We measured it setting no cookie and writing nothing to your browser — but your browser loads it from Google directly, so Google receives the data described under the table | Necessary | — |
CognitoIdentityServiceProvider.* (cookies) | Amazon Web Services (Amazon Cognito) | Keeps you signed in to your account, and lets our servers load your data as you | Necessary | Refreshed while you stay signed in; cleared when you sign out or clear your browser data |
cookieyes-consent (cookie, set on ranktally.com) | CookieYes | Remembers the choices you made in our cookie consent banner, so only the scripts you agreed to run and the banner does not ask again on every page | Necessary | 1 year |
_fbp (cookie, set on ranktally.com) | Meta Platforms | Set by Meta's pixel to recognise your browser across visits, so Meta can measure our ads | Advertisement | 90 days |
_fbc (cookie, set on ranktally.com) | Meta Platforms | Set by Meta's pixel when you arrive from one of our ads, recording that ad click so Meta can measure it | Advertisement | 90 days |
The only entry written to your browser's local storage is rt_quiz, on the version of our free report that asks you questions.
What is loaded from somewhere else. The spam check, the business picker and the map on your report are not files we serve — your browser fetches them from the provider, which means the provider sees your IP address and the page you are on, whether or not it stores anything. On our contact and free-report pages that is hCaptcha (js.hcaptcha.com, api.hcaptcha.com and its asset hosts). On the free-report page it is also Google (maps.googleapis.com, places.googleapis.com, maps.gstatic.com and Google's font servers), and when you type a business name into the picker, what you type is sent to Google to fetch the suggestions. Once your report is ready, its page loads Google the same way to draw the real map behind the grid (maps.googleapis.com and its map tiles from maps.gstatic.com): that tells Google your IP address and the page you are on, and nothing else — there is nothing to type into a map. Our landing page loads none of them.
Google Tag Manager and our consent banner. Our public pages load Google Tag Manager from www.googletagmanager.com. Tag Manager sets no cookie of its own: it shows the CookieYes consent banner, loaded from cdn-cookieyes.com, and runs the analytics and advertising scripts configured in it only for the categories you agree to there. Until you choose, those scripts are told consent is refused and do not run. Your choice is kept in the cookieyes-consent cookie above, and you can change it at any time from the banner. Google and CookieYes both see your IP address and the page you are on when they load; neither is loaded on your report or on the links in our emails.
Meta pixel. Once you consent to advertising cookies, our public pages load Meta's pixel from connect.facebook.net. It sets the _fbp and _fbc cookies above and sends Meta the events described in section 3(d) of our Privacy Policy.
When you start a subscription or open the billing portal, we send you to Stripe's own pages to pay. Stripe sets its own cookies there, under Stripe's privacy policy. We do not load Stripe's scripts on this Website.
4. Third-Party Cookies
The providers listed above set their own cookies, or receive data, when you use a form on this Website, visit our public pages or sign in to the customer portal. Their handling of that data is described in their own privacy policies. See our Privacy Policy for the full list of third-party services we use and where they process data.
5. How to Control Cookies
(a) You can control and delete cookies through your browser settings — including blocking cookies entirely or deleting them at the end of each session. Blocking necessary cookies may stop parts of the Website working.
(b) Browser instructions: Google Chrome | Apple Safari | iOS Safari | Microsoft Edge | Firefox
(c) Most providers also offer their own opt-outs — see the provider's privacy policy linked from the table above.
(d) To stop Meta's pixel, refuse advertising cookies in our consent banner, or block cookies or third-party scripts for this Website in your browser. You can also control how Meta uses activity from our pages for ads in your Facebook ad preferences.
6. Changes to This Policy
We may update this policy from time to time by posting the updated version on the Website. Material changes to what we track will be reflected in the table in section 3.
7. Contact Us
Use our contact form.