Cookie Policy
This website uses cookies, including cookies used for analytics and performance measurement, to enhance your browsing experience, serve personalized content, understand how our website is used, and improve its functionality. By using our site, you consent to our use of cookies as described below. If you do not agree to the use of cookies, you may choose not to visit the site, delete cookies after visiting, or use your browser’s anonymous browsing mode. Please see the section below on managing your cookie preferences for more information.
This Cookie Policy provides information about how and when Technical Safety BC uses cookies and other similar tracking technologies on this website, including aggregated analytics information to evaluate and improve site performance. We may update our Cookie Policy at any time and any changes made will appear here and become effective immediately. Your continued use of this website is taken as confirmation that you agree to any such changes.
What Is a Cookie?
A cookie is a very small file that is placed on an internet user's hard drive. It is generated by a web server, the hardware (computer) or software (computer program) that helps to deliver web content via the Internet. The information the cookie contains is set by the web server and it can be used by the web server whenever the user visits the site. A cookie can be thought of as an internet user's identification card, which tells a website when the user has returned.
Cookies cannot access the user's hard drive, so a cookie can't read other information saved on the hard drive, or get a user's email address etc. They only contain and transfer to the web server as much information as the users themselves have disclosed to a website.
What Does a Cookie Look Like?
Below is the content of a typical cookie from our website:
SESS6af0e18ca4b960f4be24e42a92c67d36 f06i799dmu3v74c20d3cso1a03
technicalsafetybc.ca/
1536 2562317056
30381064
4226980396
30376407*
These codes will only make sense to our web server.
Cookies Used by This Site
We use the following types of cookies:
Strictly Necessary Cookies: These cookies are essential for the operation of our website, enabling you to log into secure areas.
Analytical/Performance Cookies: These cookies help us understand how visitors use our website by tracking and recording their behavior, such as the pages they visit and how they navigate the site. This information helps us improve our website's functionality and ensure users can find what they need easily. These cookies do not collect personal information.
Functionality Cookies: These cookies recognize you when you return to our website. They allow us to personalize content, assist with viewing videos, and remember your preferences.
Targeting Cookies: These cookies track your visits to our website, including the pages you've viewed and the links you've clicked. We use this information to make our website more relevant to your interests and to display targeted ads across the internet.
You can find more information about the specific cookies we use and their purposes in the table below:
| Cookie | Description |
|---|---|
| .ASPXAUTH | Used with Absorb LMS to identify if the user is authenticated. |
| __cf_bm | Used with CloudFlare to read and filter requests from bots. |
| __ControllerTempData | Used with ASP.NET MVC and ASP.NET Core to store temporary data across subsequent HTTP requests. |
| __hssc | Used with HubSpot to keep track of sessions. |
| __hssrc | Used with HubSpot to determine if the visitor has restarted their browser. |
| __hstc | Used with HubSpot as the main visitor tracking cookie. |
| __RequestVerificationToken | Used with ASP.NET and ASP.NET Core to prevent Cross-Site Request Forgery (CSRF) attacks. |
| __Secure-ROLLOUT_TOKEN | Used with the ASP.NET framework, to protect against Cross-Site Request Forgery (CSRF or XSRF) attacks. |
| _absorb_ui_session | Used with the Absorb LMS to maintain a user's active browsing session. |
| _ehq_uid | Used with the Engage platform to create a unique identifier used for tracking user identity and sessions on a website. |
| _engagementhq_v3 | Used with the Engage platform to secure access to the site with an encrypted user token. |
| _fbc | Used with Facebook to store information about a users last visit to the site. |
| _fbp | Used with Facebook to store and track visits across websites. |
| _ga | Used with Google Analytics to store and count pageviews. |
| _gcl_au | Used with Google Adsense to store and track conversions. |
| _pin_unauth | Used with Pinterest to store the user's usage history. |
| _pinterest_ct_ua | Used with Pinterest for marketing and conversion tracking purposes. |
| _rdt_uuid | Used with Reddit to help build a profile of your interests and show you relevant ads. |
| _Secure-1PAPISID | Used with Youtube to profile users' interests and deliver relevant, personalized ads on Google properties and websites that use Google services. |
| _Secure-1PSID | Used with YouTube to build a profile of a user's interests for personalized advertising across Google services. |
| _Secure-1PSIDCC | Used with Google to build a profile of a user's interests for displaying relevant and personalized ads. |
| _Secure-1PSIDTS | Used with Google to maintain user sessions across Google services. |
| _Secure-3PAPISID | Used with Google on third-party websites (like YouTube) to personalize ads by tracking user preferences and behaviour. |
| _Secure-3PSID | Used with YouTube to build a profile of a user's interests for personalized advertising across Google services. |
| _Secure-3PSIDCC | Used with Google/YouTube to help secure your login session. |
| _Secure-3PSIDTS | Used with Google/YouTube for advertising and analytics to track user interests and activity for personalized ads. |
| ajs_anonymous_id | Used with Altassian Jira Servicedesk to store a user's last visit. |
| ajs_user_id | Used with Altassian Jira Servicedesk track a known user across multiple visits. |
| APISID | Used with Google to store user preferences and information when viewing pages with Google-hosted content, such as YouTube or Google Maps. Also, works as a security cookie to authenticate users. |
| ar_debug | Used with Atlassian Jira Servicedesk to store a user's last visit. |
| ASP.NET_SessionId | Used with our online services portal ASP.NET application, to affiliate a unique session ID with the user. This cookie will contain the user's session ID and will expire at the end of the user's session (i.e. when the browser is closed). |
| attempt-ids | Used with Absorb LMS for session management to track a learner's progress within a specific course attempt. |
| cs-lytics-audiences | Used with Contentstack to synchronize a user's audience membership data and flow information to Contentstack's edge network for real-time, personalized web experiences. |
| cs-lytics-flows | Used with Contentstack to synchronize user flow membership data from Lytics to Contentstack. |
| cs-personalize-manifest | Used with Contentstack to store a list of all active personalized experiences and their corresponding variants activated for a user. |
| cs-personalize-user-uid | Used with Absorb LMS for session management to track a learner's progress within a specific course attempt. |
| current_language | Used with the Engage platform to store a user's preferred language. |
| derived_epik | Used with Pinterest when the Pinterest tag reports a match identified without using cookies. This happens with tracking tools like enhanced match. |
| epik | Used with the Pinterest JavaScript tag. It is based on information sent from Pinterest with promoted traffic to help identify the user. |
| guest_id | Used with Twitter (now X) to uniquely identify and track a user as a guest when they interact with embedded Twitter content. |
| guest_id_ads | Used with Twitter (now X) to collect information on user behaviour and interactions across multiple websites to optimize advertisement relevance, specifically when the user is logged out of the platform. |
| guest_id_marketing | Used with Twitter (now X) to collect behavioural information and track visitors to improve personalized advertising. |
| has_js | Used with our web content management system to remember whether your browser has JavaScript enabled. The information it stores is in the form of a 1 or a 0. |
| HSID | Used with Google Ads for fraud prevention. |
| hubspotutk | Used with HubSpot to store and track a visitors identity. |
| IDE | Used with Google DoubleClick to provide ad delivery or retargeting. |
| idle-timeout | Used with Absorb LMS to end a user's session after a period of inactivity. |
| jwtToken | Used with Absorb LMS to maintain a user's authentication. |
| ki_r | Used with Qualaroo to store a user's referring website. |
| ki_s | Used with Qualaroo to store dynamic variables from a user's browser. |
| ki_t | Used with Qualaroo to store the time of a user's visit. |
| ki_u | Used with Qualaroo to store a unique user ID. |
| loggedin | Used with our Design Registration Portal to keep users logged in. |
| next-i18next | Used with Next.js to store a user's preferred language. |
| NID | Used with Google Ads to provide ad delivery or retargeting or store user preferences. |
| participant_fe | Used with Engage to correctly load the login, registration, and reset password pages. |
| personalization_id | Used with Twitter (now X) for advertising and user engagement tracking across different websites and devices. |
| pfe_ideas | Used with Engage to correctly load the ideas tool. |
| remember_user_token | Used with Engage to remember a user once they login, and to extend a user session for up to 2 weeks. |
| SAPISID | Used with Google Ads to display personalized advertisements on Google sites, based on recent searches and previous interactions. |
| seerid | Used with Lytics to track visitor activity and preferences for analytics, personalization, and marketing purposes. |
| seerses | Used with Lytics to track visitor sessions. |
| SESS6[32 character random string] | Used with our web content management system to recognise that subsequent page requests originate from the same web browser. |
| SID | Used with Google Ads to provide ad delivery or retargeting or provide fraud prevention. |
| SIDCC | Used with Google Maps to provide the identification of trusted web traffic. |
| SSID | Used with Google and YouTube to store user preferences, manage secure sessions, and collect information for personalized advertising. |
| SSL_SESS6[32 character random string] | Used with our web content management system to recognise a person who has created an account and has logged into our website as an authenticated user. |
| unexpected_redirect | Used with Engage to differentiate between new and old pages being browsed across a site. |
| unexpected_thunder | Used with Engage to store user details (ID, Type) to identify a user. |
| unexpected_visit | Used with Engage to report on the last visited tracking for home and hub page visits. |
| VISITOR_INFO1_LIVE | Used with YouTube to provide ad delivery or retargeting, store and track a visitor's identity or store and track interaction. |
| VISITOR_PRIVACY_METADATA | Used with YouTube to store your consent for embedded videos, ensuring your privacy choices are respected when you watch content on third-party websites. |
| x-ms-cpim-cache | Used with our online services portal for maintaining the request state of a user and keeping them authenticated and logged in |
| x-ms-cpim-csrf | Used with our online services portal to prevent Cross-Site Request Forgery. |
| x-ms-cpim-sso | Used with our online services portal to maintain SSO sessions. This cookie is set as persistent, when Keep Me Signed In is enabled. |
| x-ms-cpim-trans | Used with our online services portal for tracking the transactions (number of authentication requests to Azure AD B2C) and the current transaction. |
| YSC | Used with YouTube to store and track interaction with their property. |
Managing Your Cookie Preferences
Most internet browsers allow you to change your cookie settings. These options are typically found in the "Options" or "Preferences" menu of your browser. Alternatively, the "Help" section of your browser can provide further instructions. Generally, you can block cookies by enabling the setting that allows you to refuse all or some cookies.
Some cookies are essential for the website to function properly. By using our site, you are automatically opting into these essential cookies.
Further Information
For more details about cookies, including how to view, block, manage, and delete them, please visit www.allaboutcookies.org.