Raspberry Pi Foundation

Cookie policy

Add Comment

The Raspberry Pi Foundation’s website, like most websites, uses small text files called cookies. This note provides information on what cookies are, which cookies the Raspberry Pi Foundation uses, and how they can be controlled. Our website uses cookies to distinguish you from other users of our website. A cookie is a small file which is stored by your web browser. Cookies provide core functionality (such as the ability to authenticate and log you in to an account), they also help store data on state and and behaviour which can be used to analyse web traffic and visitors. Cookies allow web applications to respond to you as an individual, aiding them to tailor their operations to your needs, likes and dislikes by storing unique information about you. Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website, and allows us to improve our site. By continuing to browse the site, you are agreeing to our use of cookies. We use the following cookies: <ul> <li> Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website such as forums.</li> <li> Analytical/performance cookies. They allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This lets us improve the way our website works, for example by helping us to ensure that users are easily finding what they are looking for.</li> <li> Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you.</li> <li> Targeting cookies. These cookies record your visit to our website, the pages you have visited, and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests. We may also share this information with third parties for this purpose.</li> </ul> Cookie Information General cookies: Cookie Name Purpose Expires __cflb Cloudflare: For load-balancing purposes, a _cflb cookie is set with a unique value on the first response to the requesting client Up to 1 day cookiebanner_accepted, cookiebanner_accepted-legacy, cookieconsent_status Cookie used to prevent us from alerting the user to our cookie policy after the user has dismissed the message the first time Infinite / the year 9999 _ga, _gac_UA-XXXXXXX-X, _gat_UA-XXXXXXX-X, _gid Google Analytics: allows us to analyse user experience on the website Between 1 minute and 1 day pardot, lpvXXXX, visitor_idXXXX, visitor_idXXXX-XXXX Pardot: Cookies set for user engagement and tracking Between session length and 10 years pi_opt_in Pardot: For opting in / out of Pardot tracking 10 years profile, profile.sig Cookies set by Raspberry Pi Accounts in order to identify user sessions 1 week _voucher_app_session, _showcase_session, _pi_redeemer_session Cookies set by Raspberry Pi applications in order to identify user sessions 1 week __stripe_mid Stripe: Used to make credit card payments (eg. donations). Stripe uses a cookie to remember who you are and to enable the Raspberry Pi Foundation to process payments without storing any credit card information on our own servers 1 minute __stripe_sid Stripe: Used to make credit card payments (eg. donations). Stripe uses a cookie to remember who you are and to enable us to process payments without storing any credit card information on our own servers 30 minutes wordpress_XXXX, wordpress_logged_in_XXXX, wordpress_test_cookie, wp-settings-XXXX-XXXX, comment_author_XXXX, comment_author_email_XXXX, comment_author_url_XXXX WordPress: Used to identify user sessions and provide customisation, along with supporting the creation of comments (eg. on blog posts) Between session length and 1 year   CoderDojo Sites: Cookie Name Purpose Expires seneca-login Used to identify user sessions 2 days cookieDisclaimer Whether the user has seen the site-wide notice regarding the use of cookies 1 year canViewYouthForums Whether the user can see the O13 forums On session expiry verifyProfileComplete Whether the user has completed required fields of their profile On session expiry NG_TRANSLATE_LANG_KEY The locale of the users browser, to display the relevant language to them On session expiry   Code Club Sites: Cookie Name Purpose Expires intercom-id-XXXX Intercom: Anonymous visitor identification 1 year intercom-session-XXXX Intercom: Used to identify user sessions, in order to use the support chat functionality 1 week _union_session Used to identify user sessions On session expiry   Forums: Cookie Name Purpose Expires phpbb3_XXXX_k, phpbb3_XXXX_sid, phpbb3_XXXX_u Used to identify user sessions 1 month   Where Hotjar is in use: Cookie Name Purpose Expires _hjClosedSurveyInvites Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. 365 days _hjDonePolls Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. 365 days _hjMinimizedPolls Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site. 365 days _hjShownFeedbackMessage Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show. 365 days _hjSessionTooLarge Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit. Session _hjid Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. 365 days _hjRecordingLastActivity This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records). Session _hjTLDTest When the Hotjar script executes it tries to determine the most generic cookie path to use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, it stores the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. Session _hjUserAttributesHash User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. Session _hjCachedUserAttributes This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. Session _hjLocalStorageTest This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. Under 100ms _hjIncludedInPageviewSample This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site’s pageview limit. 30 minutes _hjIncludedInSessionSample This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site’s daily session limit. 30 minutes _hjAbsoluteSessionInProgress This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. 30 Minutes _hjFirstSeen This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. Session _hjViewportId This stores information about the user viewport such as size and dimensions. Session _hjRecordingEnabled This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. Session   For more information about the individual cookies we use, you can contact us at dataprotection@raspberrypi.org. Please note that third parties (including, for example, advertising networks and providers of external services like web traffic analysis services) may also use cookies, over which we have no control. These cookies are likely to be analytical/performance cookies or targeting cookies. You block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies), you may not be able to access all or parts of our site. We recommend you visit knowcookies.com for detailed guidance. Except for essential cookies, all cookies will expire after we no longer use them.