Skip to main content

cookie

policy

Kids!

This page is for grown ups. It tells grown ups that we send cookies (not the type you eat!) to your computer or mobile to help us make Beano work better and to tell us if Beano has crashed (ooops!!). We hope this is OK but, if not, your grown up can help you get rid of cookies.

Please show this page to your parent or guardian before you use the Beano site. ☺

Cookie policy updated December 2025.

 

Grown Ups!

We use cookies on our site to personalise content and to analyse how our site is being used. The cookies we use are harmless and anonymous, they just help to make the site better by remembering some information about what you or your child have already done on the site.

What are Cookies?

Cookies are small text files that are transferred on to your computer or mobile device by websites that you or your child may visit. Cookies can help make sites work, or work more efficiently by saving user information, as well as to provide information to site owners about how the site has been used. There are different types of cookies we use on beano.com.

Cookies that are used by beano.com are referred to as “first-party cookies” and those that are used by our partners are “third-party cookies”. We do have third party cookies on our site but we take steps to ensure that this content is compliant and does not track our users or receive users’ personal information. If a user clicks out to third party content from our site, we are not responsible for what happens on those sites and we cannot guarantee how they operate. Please check the privacy & cookie policies of any third party site if you visit them.

Persistent cookies remain on a user’s device for the period of time specified in the cookie. They are activated each time that the user visits the website that created that particular cookie.

Session cookies allow website operators to link the actions of a user during a browser session. A browser session starts when a user opens the browser window and finishes when they close the browser window. Session cookies are created temporarily. Once you close the browser, all session cookies are deleted.

So how do we use cookies on our site?

This site uses different types of cookies.

We use cookies to help manage the site and user experience. These cookies may be used to collect analytics of non-personal visitor activity outlines and site preferences, monitor crashes, provide relevant or timely information to you or your child or offer contextual advertisements only.

The law states that we can store cookies on your computer or device if they are strictly necessary for the operation of this site. Necessary cookies help make a site usable by enabling basic functions like page navigation and access to secure areas of the site. The site cannot function properly without these cookies.

Necessary cookies

These cookies are required for beano.com to function properly and for security purposes. Without these cookies, we cannot provide the requested services.

Name: visitor_id
Purpose: Preserves the visitor’s session state across page requests
Expiry: 2 Years
Cookie Type: 1st Party

Name: session_id
Purpose: Preserves the same session state across page requests
Expiry: 2 Years
Cookie Type: 1st Party

Name: country
Purpose: Determines the preferred language and country-setting of the visitor – This allows the website to show content most relevant to that region and language
Expiry: 29 Days

Cookie Type: 1st Party

Name: GRECAPTCHA
Purpose: Used by Google to provide spam protection
Expiry: Session
Cookie Type: 3rd Party

Name: _dc_gtm_UA-xxxxxxxx
Purpose: This cookie is associated with sites using Google Tag Manager to load other scripts and code into a page. Where it is used it may be regarded as Strictly Necessary as without it, other scripts may not function correctly. The end of the name is a unique number which is also an identifier for an associated Google Analytics account.
Expiry: A few seconds
Cookie Type: First Party

Name: OptanonAlertBoxClosed
Purpose: This cookie is set by websites using certain versions of the cookie law compliance solution from OneTrust. It is set after visitors have seen a cookie information notice and in some cases only when they actively close the notice down. It enables the website not to show the message more than once to a user. The cookie has a one-year lifespan and contains no personal information.
Expiry: 365 Days
Cookie Type: First Party

Name: PHPSESSID
Purpose: PHP session cookie associated with embedded content from this domain.
Expiry: A few seconds
Cookie Type: First Party

Name: OptanonConsent
Purpose: This cookie is set by the cookie compliance solution from OneTrust. It stores information about the categories of cookies the site uses and whether visitors have given or withdrawn consent for the use of each category. This enables site owners to prevent cookies in each category from being set in the users browser, when consent is not given. The cookie has a normal lifespan of one year, so that returning visitors to the site will have their preferences remembered. It contains no information that can identify the site visitor.
Expiry: 365 Days
Cookie Type: First Party

__cfruid

This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. It expires at the end of the session. Learn more about Cloudflare cookies

__cfuvid

This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. It expires at the end of the session. Learn more about Cloudflare cookies

__cf_bm

This cookie is set by HubSpot's CDN provider and is a necessary cookie for bot protection. It expires in 30 minutes. Learn more about Cloudflare cookies

__hs_opt_out

  • This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.
  • This cookie is set when you give visitors the choice to opt out of cookies.
  • It contains the string "yes" or "no".
  • It expires in 6 months.

__hs_do_not_track

  • This cookie can be set to prevent the tracking code from sending any information to HubSpot.
  • It contains the string "yes".
  • It expires in 6 months.

__hs_initial_opt_in

  • This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
  • It contains the string "yes" or "no".
  • It expires in seven days.

__hs_cookie_cat_pref

  • This cookie is used to record the categories a visitor consented to.
  • It contains data on the consented categories.
  • It expires in 6 months.

__hs_gpc_banner_dismiss

  • This cookie is used when the Global Privacy Control banner is dismissed.
  • It contains the string "yes" or "no".
  • It expires in 180 days.

__hs_notify_banner_dismiss

  • This cookie is used when the website uses a Notify consent banner type.
  • It contains a boolean value of True.
  • It expires in 180 days.

hs_ab_test

  • This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
  • It contains the id of the A/B test page and the id of the variation that was chosen for the visitor.
  • It expires at the end of the session.

hs-messages-is-open

  • This cookie is used to determine and save whether the chat widget is open for future visits.
  • It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity.
  • If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes.
  • It contains a boolean value of True if present.
  • It expires in 30 minutes.

hs-messages-hide-welcome-message

  • This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.
  • It contains a boolean value of True or False.
  • It expires in one day. 

__hsmem

  • This cookie is set when visitors log in to a HubSpot-hosted site.
  • It contains encrypted data that identifies the membership user when they are currently logged in.
  • It expires in seven days. 

hs-membership-csrf

  • This cookie is used to ensure that content membership logins cannot be forged.
  • It contains a random string of letters and numbers used to verify that a membership login is authentic.
  • It expires at the end of the session.

hs.superstore.laboratory.<id>

  • It contains an offline cache of cohorts that a user got assigned for HubSpot Product experiments.
  • It doesn't contain personal identifiable information or information that can identify your device or hardware
  • HubSpot experiments are anonymous and aren't attached to user sessions. However, if tracking consent is given, specific experiments might be tied to identifiable user sessions.
  • The individual contents of this storage entry expire automatically upon specific dates determined by HubSpot Product. Often, these are 48 hours.
  • It can't be manually removed and is automatically created whenever conditions are met.

<id>_key

  • When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again.
  • The cookie name is unique for each password-protected page.
  • It contains an encrypted version of the password so future visits to the page will not require the password again.
  • It expires in 14 days.

Performance cookies

Performance cookies enable us to test changes to our website in order to improve overall the user experience. They also provide functionality to gather anonymous feedback from users and aggregate user behaviour to These cookies do not collect any information that could identify you.

Some of our performance cookies are managed for us by third parties. However, we don’t allow the third party to use the cookies for any purpose other than anonymously reporting usage statistics.

Name: _ga

Purpose: This cookie name is used by Google Analytics. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. reports.

Expiry: 2 years

Cookie Type: First Party

Name: _gat_gtag_UA_xxxxxxxxxx

Purpose: Used by Google Analytics to throttle request rate via Google Tag Manager

Expiry: 1 Day

Cookie Type: First Party

Name: _gid
Purpose: This cookie is used by Google Analytics. The cookie is used to store information of how visitors use a website, The data collected includes the number visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 1 Day
Cookie Type: First Party

__hmpl

  • It contains metadata regarding tracking events that HubSpot collects throughout the user's journey at HubSpot.
  • It's stored either on the Browser's Session Storage or Local Storage based on the presence or lack of tracking consent.
  • It doesn't contain personal identifiable information or information that can identify your device or hardware.
  • It can't be manually removed and is automatically created whenever conditions are met.

hublytics_events_53

  • This browser storage entry is used by HubSpot Product to temporarily store tracking events created by HubSpot Product until they get dispatched over the network.
  • It's stored either on the Browser's Session Storage or Local Storage based on the presence or lack of tracking consent.
  • It doesn't contain personal identifiable information or information that can identify your device or hardware.
  • It can't be manually removed and is automatically created whenever conditions are met.

__hstc

  • The main cookie for tracking visitors.
  • It contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
  • It expires in 6 months.

hubspotutk

  • This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
  • It contains an opaque GUID to represent the current visitor.
  • It expires in 6 months.

__hssc

  • This cookie keeps track of sessions.
  • This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
  • It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
  • It expires in 30 minutes.

__hssrc

  • Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
  • If this cookie does not exist when HubSpot manages cookies, it is considered a new session.
  • It contains the value "1" when present.
  • It expires at the end of the session.
 Deleting cookies

You can delete cookies already stored on your computer:

  • In Internet Explorer 11 click on “Tools”, point to “Safety” and then select the “Delete browsing history”. Click on the “Cookies and website data” checkbox and then choose “Delete”.
  • In Microsoft Edge click on the three dots icon in the top right-hand corner and select “Settings”. Under “Clear browsing data” select “Choose what to clear” and select the checkbox next to “Cookies and saved website data” then click on “Clear”. If you wish you can turn the “Always clear this when I close the browser” setting to “On”.
  • To delete cookies from a particular website in Firefox, click on the three lines icon and choose “Options”. In the “Privacy & Security” panel go to the “History” section and in the drop menu next to “Firefox will” choose “Use custom settings for history”. A cookies window will appear when you click “Show Cookies”. In the Search field type the name of the site whose cookies you want to remove. Select the cookies you wish to remove and click “Remove Selected”. Click “Close” to close the Cookies window and the “about:preferences” page. To delete all cookies, open the cookies window as above and click “Remove All Cookies”.
  • In Google Chrome click on the three dots icon in the top right-hand corner, select “Settings” and find “Advanced” near the bottom. Under “Privacy and security” click on “Content settings”. Click on “Cookies” and Under “All cookies and site data” select “Remove All”. Confirm by clicking on “Clear all”.
  • On Safari on Apple OS X click on the Safari menu, then select “Preferences” from the drop-down. Go to the “Privacy” tab. Click the “Remove All Website Data” button to remove all stored website data and click “Remove Now” to confirm. To remove stored data by individual site, click on the “Details” button and select the sites with the stored data you wish to remove. Click “Remove” and then “Done”.
  • For Opera selecting “Settings”, “Preferences”, “Advanced” and then “Cookies” and checking the “Delete new cookies when exiting Opera” and closing Opera when you have finished browsing will ensure the cookie information is kept in the browser.

Blocking cookies

Most browsers allow you to refuse to accept cookies. For example:

  • In Internet Explorer 11 you can refuse all cookies by clicking “Tools”, “Internet Options”, select the “Privacy” tab and, locate “Advanced” under Settings and choose if you want to allow, block or be promoted for first and third-party cookies.
  • In Microsoft Edge click on the three dots icon in the top right-hand corner and select “Settings”. Locate “View advanced settings”. In the “Cookies” section you will find a drop-down menu where you can select “Block only third-party cookies” or “Block all cookies”. You will then have to re-start Microsoft Edge.
  • In Firefox you can block all cookies by clicking “Tools”, “Options”, and unchecking “Accept cookies from sites” in the “Privacy” box.
  • In Google Chrome you can adjust your cookie permissions by clicking on the three dots icon in the top right-hand corner of your browser screen, selecting “Settings” from near the bottom of the drop-down list, then clicking on “Advanced” near the bottom. This should open options. In the “Privacy” section, click “Content Settings” and disable cookies by selecting “Block site from setting any data”. Click “Done” to save your preferences.
  • On Safari on Apple OS X click on the Safari menu, then “Preferences” then “Privacy”. Under “Accept Cookies” unselect the “Always allow” option.
  • For Opera choose “Settings”, “Quick Preferences” and uncheck “Enable Cookies”. Blocking all cookies will, however, have a negative impact upon the usability of many websites. If you block cookies, you may not be able to use certain features on our website (log on, access content, use search functions).

 

Control Google Analytics cookies

A lot of sites use special types of cookies from Google Analytics to track the traffic on a site and what users do on the site. You can stop being tracked by ALL Google Analytics cookies across ALL sites on your computer or mobile device by visiting https://tools.google.com/dlpage/gaoptout.

One last thing...

Websites we link to are not covered by this policy. So if you or your child click on a link and access someone else’s site, they might collect and use information about you and your child in a different way to us.