Cookie Policy

This page lists the cookies realtreasury.com sets, what each is for, and how long it lasts. It is meant to be checkable against what your browser actually shows you. If you find something here that we have not listed, tell us and we will either explain it or remove it.

1. The Short Version

We use two kinds of cookie. Essential ones keep the site working and are always on. Analytics and marketing ones tell us which pages get read, which companies visit, and how LinkedIn ads perform. In the US they are on unless you turn them off in cookie settings or your browser sends a Global Privacy Control signal; elsewhere we ask first.

We do not sell what these cookies collect. When they are on, LinkedIn, Apollo and HubSpot receive data about your visit, as described in section 3. When they are off, no analytics or marketing cookie is set and the LinkedIn, Apollo and HubSpot tags do not load. Google Analytics still sends Google a cookieless signal for each page you view, which includes the page, your IP address and your browser type.

Manage cookie preferences

2. Essential Cookies

These are set because the site cannot run without them: they keep it secure, stop bots submitting our forms, remember the cookie choice you made, and record which country’s cookie rules apply. We do not ask consent for these, and turning them off in your browser will break parts of the site.

Name	Set by	Purpose	Expires
rt_consent	Real Treasury	Remembers whether you accepted or rejected analytics cookies	12 months
rt_consent_gpc	Real Treasury	Records that you allowed analytics cookies while your browser sent a Global Privacy Control signal	12 months
rt_region	Real Treasury	Stores your country so we know which cookie rules apply	30 days
__cf_bm	Cloudflare	Distinguishes people from bots	30 minutes
_cfuvid	Cloudflare	Applies rate limits per visitor	Session
cf_clearance	Cloudflare	Records that you passed a security challenge, so you are not asked again. Only set if you are challenged.	Up to 1 year
cf_chl_*	Cloudflare Turnstile	Holds the state of the “are you human” check on our forms	Session
wordpress_test_cookie, wp-settings-*	WordPress	Sign-in and admin preferences. Only set for our own logged-in staff, never for visitors.	Session to 1 year

We also store one item in your browser’s local storage, rt_consent_at, which is the date and time you made your cookie choice. We keep it so we can show when consent was given if you ever ask.

If you register to watch one of our recorded webinars, that page also stores rtg_<webinar>_access in local storage. It remembers that you registered, so the video plays on your next visit without asking again.

3. Analytics and Marketing Cookies

Outside the US, these are set only after you accept them. Until then Google Analytics loads in a mode that stores nothing on your device, and the LinkedIn, Apollo and HubSpot tags do not load at all. In that mode Google Analytics still sends Google a cookieless signal for each page you view (the page, your IP address and your browser type), with no identifier that links one visit to another. If you reject, or never answer, it stays in that mode and the other three tags never load; if they are on and you turn them off, we delete the Google Analytics and HubSpot cookies below, and the LinkedIn and Apollo tags stop loading from the next page you open. Cookies those two tags have already set stay in your browser until they expire or you clear them.

Name	Set by	Purpose	Expires
_ga	Google Analytics 4	Distinguishes one browser from another so repeat visits are not counted as new people	2 years
_ga_<property id>	Google Analytics 4	Keeps the state of your current visit	2 years
__hstc	HubSpot	Recognizes a returning browser and records your first, last and current visit times	6 months
hubspotutk	HubSpot	Visitor ID	6 months
__hssc	HubSpot	Counts pages viewed in the current visit	30 minutes
__hssrc	HubSpot	Tells HubSpot whether you have restarted your browser	End of session

LinkedIn Insight Tag. Measures how LinkedIn ads perform and lets site visitors be reached with LinkedIn ads. LinkedIn sets its own cookies, listed in LinkedIn’s cookie table, and uses the data under its cookie policy.

Apollo website tracker. Matches a visit to the company it likely comes from, so we can see which organizations read our material. Apollo handles that data under its privacy policy.

HubSpot. We use HubSpot to manage our contacts and understand how visitors use our site. HubSpot acts as our processor under its privacy policy.

Google acts as our processor for this data. It is governed by Google’s privacy policy, and you can also opt out at the browser level with Google’s opt-out add-on.

When analytics cookies are on, we store rt_src in your browser’s session storage. It records how you reached the site (the campaign tags on the link you followed, the first page you landed on, and the referring site’s domain) so that a form you submit records where it came from. It is cleared when you close the tab. When they are off, it is not stored.

4. Embedded Content

Some pages embed a video from YouTube. We use YouTube’s privacy-enhanced (no-cookie) player, which does not set YouTube’s cookies when the page loads, though the player may still keep some data in your browser’s local storage. Once you press play, YouTube may set its own cookies under Google’s policy. Pages that link out to LinkedIn or a vendor’s website hand you over to that site’s own cookie practices, which this policy does not cover.

5. Changing Your Mind

Use the cookie preferences control on this page or on our Privacy Policy. Your choice is remembered for 12 months, after which we will ask again.

You can also manage cookies in your browser directly — every major browser lets you block or delete them, usually under Settings → Privacy. Blocking essential cookies will stop our forms working.

6. Contact