Cookie Policy
Last updated: 17 November 2026
Totallister Pty Ltd (ABN 95 155 821 944), trading as Rank Tally at ranktally.com (we, us, our).
On this page
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 a few small entries of our own in your browser's storage, all listed in the table below: while you use our free report, they tie together the steps of a single visit, keep the campaign details and offer name of the link you arrived by, keep the email address you typed so you are not asked again, remember which set of questions you were shown, and remember the report you asked for; one more is set only on our own team's browsers. Everything else that gets stored comes from the tools we use: PostHog, our product analytics, session recording and error-reporting 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, Google Analytics, which Tag Manager loads once you accept analytics cookies, 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_futm (session storage, not a cookie) | Rank Tally | Holds the campaign tags (utm_source and the like) from the link you arrived by, so every step of one visit to our free report is credited to the same campaign | Analytics | Deleted when you close the tab |
rt_lead_email (session storage, not a cookie) | Rank Tally | Keeps the email you typed in this tab, so it is not asked for again | Functional | Deleted when you close the tab |
rt_internal (local storage, not a cookie) | Rank Tally | Set only when one of our own team opens a page of this Website through an internal link, so our visits are left out of the visit counts | Functional | Until removed |
rt_vid (local storage, not a cookie) | Rank Tally | A random number made in your browser, used to split visitors between the versions of our free-report questions. It is not linked to your name or email address | Analytics | Until you clear your browser data |
rt_vid:served (session storage, not a cookie) | Rank Tally | Notes which version of the free-report questions you were shown in this visit, so the steps you take are counted against that version | Analytics | Deleted when you close the tab |
rt_offer (session storage, not a cookie) | Rank Tally | Holds the offer name from the link you arrived by, so the free report you ask for a page or two later still carries it | Functional | Deleted when you close the tab |
rt_reports (session storage, not a cookie) | Rank Tally | Remembers the link to the free report you just asked for, for each business and email address, so asking again does not build a second report | Functional | Deleted when you close the tab |
rt-free-report-wait-started (session storage, not a cookie) | Rank Tally | Holds the time you started waiting for your report, so the progress bar carries on from the same moment when the report page opens | Functional | Deleted when you close the tab |
__cf_bm (cookie, set on hcaptcha.com) | hCaptcha (Intuition Machines) | Set by the spam check on our contact and free-report forms and on the customer portal's sign-up form, 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 | Until you close your browser, or 30 days if you tick “Remember me” when you sign in; cleared when you sign out or clear your browser data |
auth_remember_me (local storage, not a cookie) | Rank Tally | In the customer portal, remembers whether you ticked “Remember me” at sign-in, so your sign-in lasts as long as you chose | Functional | Until you clear your browser data |
rt_report_handover (cookie, set by the customer portal) | Rank Tally | Carries a signed note of the free report you came from while you sign up, so that report's business is added to your new account | Necessary | 48 hours |
rt.selectedLocationId and rt-moved-dismissed:* (local storage, not a cookie) | Rank Tally | In the customer portal, remember which business you picked and which change notices you closed | Functional | Until you clear your browser data |
signupPrefillEmail (session storage, not a cookie) | Rank Tally | In the customer portal, carries the email you typed between the steps of sign-up and sign-in | Functional | Deleted when you close the tab |
signupPlan and signupRef (session storage, not a cookie) | Rank Tally | In the customer portal, carry the plan you picked, and whether you came from a free report, from the sign-up page to the billing page | Functional | Deleted when you close the tab |
tempPasswordEmail (session storage, not a cookie) | Rank Tally | In the customer portal, carries your email from the sign-in step to the choose-a-new-password step when you sign in with a temporary password | Functional | Deleted when you close the tab, or when you set your new password |
help-tour-seen:* (local storage, not a cookie) | Rank Tally | In the customer portal, notes that a page's guided tour has started once for you, so it does not start again by itself. The name includes your email address and the tour's name; the value is the time it started | Functional | Until you clear your browser data |
rt_fbclid (session storage, not a cookie) | Rank Tally | Written only after you accept advertising cookies. Holds the ad-click code from the link you arrived by, so a later free report request can pass it to Meta to measure our ads | Advertisement | Deleted when you close the tab |
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 |
_ga (cookie, set on ranktally.com) | Google (Analytics) | Set by Google Analytics, only after you accept analytics cookies. Tells your visits apart from other visitors' so Google Analytics can count visitors and the pages they view | Analytics | Up to 2 years |
_ga_* (cookie, set on ranktally.com) | Google (Analytics) | Set by Google Analytics, only after you accept analytics cookies. Keeps the state of your current session, so its page views and events are grouped as one visit. The name ends with the ID of our Analytics property | Analytics | Up to 2 years |
__ph_opt_in_out_phc_* (local storage, not a cookie) | PostHog | Written on our public pages when you answer the cookie banner. Records whether you accepted or refused analytics cookies. Until you answer, and after you refuse, PostHog sets no cookie and keeps no identifier in your browser | Necessary | Until you clear your browser data |
ph_phc_* (session storage, not a cookie) | PostHog | Written on our public pages only after you accept analytics cookies. Three entries (ph_phc_*_posthog, ph_phc_*_session_registered_properties and ph_phc_*_window_id) that tie what you do in one tab together as one session, for its page views and session recording | Analytics | Deleted when you close the tab |
ph_phc_*_posthog (cookie, set on ranktally.com and its subdomains) | PostHog | Set by PostHog, on our public pages only after you accept analytics cookies. Holds a random identifier for your browser so PostHog can link your page views, clicks and session recordings on our public pages across visits | Analytics | 1 year |
ph_phc_*_posthog (local storage, not a cookie) | PostHog | Written with the cookie above, on our public pages only after you accept analytics cookies. Keeps the same identifier and the settings PostHog needs to recognise you on your next visit | Analytics | Until you clear your browser data |
_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 |
lastExternalReferrer and lastExternalReferrerTime (local storage, not a cookie) | Meta Platforms | Written by Meta's pixel once you accept advertising cookies. Holds the site you came from and when, so Meta can measure our ads | Advertisement | Until you clear your browser data |
Every entry in the table whose provider is Rank Tally is ours. The other storage entries are written by the provider named beside each.
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. PostHog is the exception: on every page, our public pages and the customer portal, your browser fetches PostHog’s script files from PostHog’s servers (us-assets.i.posthog.com) before you make any choice, so PostHog sees your IP address and the page you are on, whether or not you accept analytics cookies. On our public pages it also receives a cookie-free count of your page views and clicks before you answer the banner and after you refuse.
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: Google Analytics, which counts visitors and the pages they view and sets the _ga cookies above, and Meta's pixel. 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.
PostHog. PostHog (us.i.posthog.com, hosted in the United States) is our product analytics tool. On our public pages and in the customer portal it records page views, when you leave a page, clicks and other events, and the errors your browser hits. On our public pages it may also record sessions: a replay of how you moved around the page. Everything you type into a form is masked in a replay, so we do not see it. On our public pages, before you answer the cookie banner, and after you refuse, PostHog stores nothing in your browser but still counts your page views and clicks without a cookie or any stored identifier, and it does not record sessions. Your answer is kept in __ph_opt_in_out_phc_* in local storage once you give it. Once you accept, it sets the cookie and the local and session storage entries above, so it can recognise you from one visit to the next, and it may record sessions. The customer portal has no cookie banner because PostHog stores nothing in your browser there: no cookie, no local or session storage, and it records no sessions. It still records page views, clicks, other events and errors, and once you sign in it attaches your account id (not your name or email address) to them. See section 3(f) of our Privacy Policy.
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.
(e) To stop Google Analytics and PostHog, refuse analytics cookies in our consent banner, which you can reopen at any time to change your choice, or block cookies, local storage or third-party scripts for this Website in your browser. Refusing analytics cookies on our public pages also keeps PostHog from setting its cookie and storage entries, and from recording your sessions there. In the customer portal PostHog stores nothing in your browser and records no sessions.
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 store in your browser will be reflected in the table in section 3.
7. Contact Us
Use our contact form.