RMPDS Cookie Policy
(Version February 2021)
1. Introduction
Rocky Mountain Poison and Drug Safety (RMPDS) may use our own and third-party cookies (“Cookies”) in connection with your use of our Websites or Services. We also work with third parties to help better serve you, and may use our own and their pixels, web beacons, tags, scripts, local shared objects such as HTML5, advertising identifiers (including mobile identifiers such as Apple’s IDFA or Google’s Advertising ID), software development kits (SDKs) and similar technologies (“Other Web Technologies”) into our: (a) (i) websites, portals, applications (including mobile applications), channels, software, and widgets (including as embedded on sites owned by third parties), and (ii) social media pages and channels (collectively, the “Websites”); and (b) any services, features, media, functions, content, tools, and links contained in or offered via the Websites (collectively, the “Services”), including when they serve you content on our Websites. For example, when using our Websites or Services, you may encounter embedded content, or you may be directed to other websites.
Cookies and Other Web Technologies collect and transmit information about you, such as your use of our Websites or Services; your browser type, search preferences, IP address; and the date and time of your use. Cookies and Other Web Technologies may have unique identifiers, and reside, among other places, on your computer or mobile device, in e-mails we send to you, and on our Websites.
2. Types and Purposes of Cookies and Other Web Technologies
We use both session-based and persistent Cookies and Other Web Technologies. Session-based Cookies or Other Web Technologies exist only during one session and disappear from your device when you close your browser or turn off your device. Persistent Cookies or Other Web Technologies remain on your computer or device after you close your browser or turn off your computer.
The following table sets out the different categories of Cookies or Other Web Technologies that our Services use and why we use them. The lists of third-party providers of Other Web Technologies are intended merely as illustrative and should not be viewed as a comprehensive list.
3. Managing Cookies
While you have choices about Cookies and Other Web Technologies, deleting, blocking, or disabling Cookies or Other Web Technologies can affect the functionality of our Websites and Services and may prevent you from accessing certain features.
You may be able to disable Cookies or Other Web Technologies through your browser settings. Please follow your browser’s instructions to determine what choices you have available to you through your browser. Please note that disabling a Cookie or Other Web Technology or category of Cookies or Other Web Technologies does not delete the Cookies or Other Web Technologies from your browser unless manually completed through your browser function. For more information, please visit: https://www.allaboutcookies.org/manage-cookies/.
Similarly, your device may provide you with choices about Cookies and Other Web Technologies via your device settings. For example, you can also restrict the collection and/or use of advertising IDs on your mobile device. For more information, please visit: https://www.networkadvertising.org/mobile-choice.
With respect to Cookies or Other Web Technologies used by third parties, we do not necessarily have access to or control over the Cookies or Other Web Technologies third parties use. Some third parties may permit you to opt out of their Cookies or Other Web Technologies directly. Please see the links provided in the table above for more information about the availability of any such opt-out option. Additionally, you may be able to opt out of some of such third party’s practices by visiting the following links: Network Advertising Initiative and Digital Advertising Alliance.
4. "Do Not Track" Requests
RMPDS may track its users over time as they browse third-party sites in order to provide intelligent, customized advertising, and RMPDS currently does not recognize Do Not Track (“DNT”) signals from web browsers, as the Internet industry is still working on DNT standards and solutions.
In addition, some third parties may collect your information when they serve you content on our Websites. This enables them to tailor what they present to you over time. Many web browsers allow you to set the DNT signal so that third parties (particularly advertisers) know you do not want to be tracked. Please review your web browser’s internet options for more details.
1. Introduction
Rocky Mountain Poison and Drug Safety (RMPDS) may use our own and third-party cookies (“Cookies”) in connection with your use of our Websites or Services. We also work with third parties to help better serve you, and may use our own and their pixels, web beacons, tags, scripts, local shared objects such as HTML5, advertising identifiers (including mobile identifiers such as Apple’s IDFA or Google’s Advertising ID), software development kits (SDKs) and similar technologies (“Other Web Technologies”) into our: (a) (i) websites, portals, applications (including mobile applications), channels, software, and widgets (including as embedded on sites owned by third parties), and (ii) social media pages and channels (collectively, the “Websites”); and (b) any services, features, media, functions, content, tools, and links contained in or offered via the Websites (collectively, the “Services”), including when they serve you content on our Websites. For example, when using our Websites or Services, you may encounter embedded content, or you may be directed to other websites.
Cookies and Other Web Technologies collect and transmit information about you, such as your use of our Websites or Services; your browser type, search preferences, IP address; and the date and time of your use. Cookies and Other Web Technologies may have unique identifiers, and reside, among other places, on your computer or mobile device, in e-mails we send to you, and on our Websites.
2. Types and Purposes of Cookies and Other Web Technologies
We use both session-based and persistent Cookies and Other Web Technologies. Session-based Cookies or Other Web Technologies exist only during one session and disappear from your device when you close your browser or turn off your device. Persistent Cookies or Other Web Technologies remain on your computer or device after you close your browser or turn off your computer.
The following table sets out the different categories of Cookies or Other Web Technologies that our Services use and why we use them. The lists of third-party providers of Other Web Technologies are intended merely as illustrative and should not be viewed as a comprehensive list.
Table 1. Cookies on our Website
| Type of Cookie or Other Web Technology | Purpose | Who Serves the Cookie (for example) |
|---|---|---|
| _ga | Registers a unique ID that is used to generate statistical data on how the visitor uses the website | Google Analytics |
| _gat | Used by Google Analytics to throttle request rate | Google Analytics |
| _gid | Registers a unique ID that is used to generate statistical data on how the visitor uses the website | Google Analytics |
| Cookies_on | 1. When a visitor loads a page from the site the script checks if cookies_on variable has been passed to it as a cookie. 2. If it has been passed, the script tries to get Session ID (SID) from the request. 3. Depending on session mode the script is getting SID differently. |
Table 2. Mandatory Cookies Needed for Chat Sessions with Poison Centers
| Cookie Name | Category | Description | Cookie Type | Expiry (Session or Time Based) | Single / Multi-Sub Domain Cookie | Usage (which fields it captures) |
|---|---|---|---|---|---|---|
| egain-last-request-id | Strictly Necessary Cookie | This cookie enables successful re-connection of chat in undocked window when the chat window is closed after network disconnect and reopened again after network reconnect. | Session | Session | Single Domain | last request id for a bosh session (chat messaging session) required to reconnect to same bosh session |
| egain-last-success-request-id | Strictly Necessary Cookie | This cookie enables successful re-connection of chat in undocked window when the chat window is closed after network disconnect and reopened again after network reconnect. | Session | Session | Single Domain | last successful request id for a bosh session (chat messaging session) required to reconnect to same bosh session |
| egSubDomainSupportConfig | Strictly Necessary Cookie | This cookie is used to store configuration required to enable docked chat across multiple sub-domains under top level domain | Session | Session | Multi Sub-Domain | Stores the multi sub domain support related configuration such as support required, parent domain, cookie path, secure attribute for cookies |
| egSessionId | Strictly Necessary Cookie | This cookie enables re-connection to ongoing docked chat session after page refresh or page navigation. This is used in case docked chat is enabled across multiple sub-domains under top level domain | Persistent | 1-hour expiry time | Multi Sub-Domain | chat session id |
| egChatInProgress | Strictly Necessary Cookie | This is used to store value of in progress state of a chat in case docked chat is enabled across multiple sub-domains under top level domain. This will be used in case docked chat is enabled across multiple sub-domains under top level domain |
Persistent | 1-hour expiry time | Multi Sub-Domain | Chat in progress status |
| EgainLastRequestId | Strictly Necessary Cookie | This will be used in case docked chat is enabled across multiple sub-domains under top level domain | Persistent | 1-hour expiry | Multi Sub-Domain | This is used to set last request id sent in a bosh session (chat messaging session) |
| egChatStateBeforeUnload | Strictly Necessary Cookie | This is used to store chat state data when the parent page which opened popped out chat unloads. This value will be used in case docked chat is enabled across multiple sub-domains under top level domain |
Persistent | 1-hour expiry | Multi Sub-Domain | This is used to store chat state data when the parent page which opened popped out chat unloads |
| egTabId | Strictly necessary cookie | This is used to uniquely identify the browser tab required for docked chat functionality. This value will be used in case docked chat is enabled across multiple sub-domains under top level domain | Session | Session | Multi Sub-Domain | This is used to uniquely identify browser tab required for docked chat handling across multiple tabs |
| egChatWindowState | Strictly Necessary Cookie | This value is used to determine the docked chat window is in minimized or maximized state in case docked chat is enabled across multiple sub-domains under top level domain | Persistent | 1-hour expiry time | Multi Sub-Domain | chat window state whether maximized or minimized |
| egFetchFromStorage | Strictly Necessary Cookie | This is used to determine whether the sensitive data such as session id to be stored and fetched from web storage instead of sending and retrieving from chat application URL. This will be used in case docked chat is enabled across multiple sub-domains under top level domain |
Persistent | 1-hour expiry time | Multi Sub-Domain | This is used to store configuration value for the data such as session id to be read from storage or from URL |
| egAwaitingEvtDone | Strictly Necessary Cookie | This is used to store value for captured event after the customer has filled in their details and is awaiting to chat with an agent | Session | Session | Single Domain | Indication of event capture for customer awaiting to chat with an agent |
| X-egain-ban-visitor | Strictly Necessary Cookie | Cookie set by application for banning chat customer. It is conditionally set by application based on criteria. | Persistent | Configurable in admin console (Time range - 1 hour to 168 hour) | Single Domain | User's browser session |
| egSystemMsg | Strictly Necessary Cookie | This is used to store message id for a chat system message sent. This value will be used in case docked chat is enabled across multiple sub-domains under top level domain | Persistent | 1-hour expiry | Multi Sub-Domain | This is used to store message id for a chat system message sent |
| egAgentMsg | Strictly Necessary Cookie | This is used to store message id for a chat message sent by an agent. This value will be used in case docked chat is enabled across multiple sub-domains under top level domain |
Persistent | 1-hour expiry | Multi Sub-Domain | This is used to store message id for a chat system message sent by an agent |
| egChatInitiateData | Strictly Necessary Cookie | Stores values required to initiate chat in case docked chat is enabled across multiple sub-domains under top level domain | Persistent | 1-hour expiry time | Yes | This is used to store values such as entrypointid, locale, templatename, serverURL, Video chat parameters, post chat attributes etc. which are used to initiate chat |
3. Managing Cookies
While you have choices about Cookies and Other Web Technologies, deleting, blocking, or disabling Cookies or Other Web Technologies can affect the functionality of our Websites and Services and may prevent you from accessing certain features.
You may be able to disable Cookies or Other Web Technologies through your browser settings. Please follow your browser’s instructions to determine what choices you have available to you through your browser. Please note that disabling a Cookie or Other Web Technology or category of Cookies or Other Web Technologies does not delete the Cookies or Other Web Technologies from your browser unless manually completed through your browser function. For more information, please visit: https://www.allaboutcookies.org/manage-cookies/.
Similarly, your device may provide you with choices about Cookies and Other Web Technologies via your device settings. For example, you can also restrict the collection and/or use of advertising IDs on your mobile device. For more information, please visit: https://www.networkadvertising.org/mobile-choice.
With respect to Cookies or Other Web Technologies used by third parties, we do not necessarily have access to or control over the Cookies or Other Web Technologies third parties use. Some third parties may permit you to opt out of their Cookies or Other Web Technologies directly. Please see the links provided in the table above for more information about the availability of any such opt-out option. Additionally, you may be able to opt out of some of such third party’s practices by visiting the following links: Network Advertising Initiative and Digital Advertising Alliance.
4. "Do Not Track" Requests
RMPDS may track its users over time as they browse third-party sites in order to provide intelligent, customized advertising, and RMPDS currently does not recognize Do Not Track (“DNT”) signals from web browsers, as the Internet industry is still working on DNT standards and solutions.
In addition, some third parties may collect your information when they serve you content on our Websites. This enables them to tailor what they present to you over time. Many web browsers allow you to set the DNT signal so that third parties (particularly advertisers) know you do not want to be tracked. Please review your web browser’s internet options for more details.