Third Parties Code of Conduct

Cepal Hellas is committed to ethical business practices and operations across its entities and jurisdictions of operation. The Board of Directors and Senior Management of the Company apply a “zero-tolerance” approach to any incidents of misconduct or illegal activity, regardless of whether these incidents originate from employees of the Company or third parties that the Company cooperates with or is represented by.

The Company is committed in maintaining the highest standards of integrity, transparency and responsibility across all its activities, in full compliance with all applicable laws and regulations.

The Third Parties Code of Conduct describes the fundamental expectations of the Company on integrity and ethical business practices from all the Third Parties the Company collaborates (i.e., customers, suppliers, sub-contractors, representatives, intermediaries, consultants, etc.). Any Third Party that engages with the Company must comply with all applicable laws and regulations, as well as the requirements and principles set throughout this Third Parties Code of Conduct.

To access the Code of Conudct, please click the following link.

Third Parties Code of Conduct

Necessary cookies

PIX_COOKIES_STATISTICAL

PIX_COOKIES_NECESSARY

PIX_COOKIES_FUNCTIONAL

PIX_COOKIES_CONSENT

Functional cookies

Statistical cookies

Google Analytics

Created under the Regime of Pixelocracy.

Αναγκαία cookies

PIX_COOKIES_STATISTICAL

PIX_COOKIES_NECESSARY

PIX_COOKIES_FUNCTIONAL

PIX_COOKIES_CONSENT

Λειτουργικά cookies

Στατιστικά cookies

Google Analytics

Created under the Regime of Pixelocracy.

Name	Description	Duration	Data type
_hjClosedSurveyInvites	Hotjar cookie that is set once a visitor 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	Boolean true/false
_hjDonePolls	Hotjar cookie that is set once a visitor 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	Boolean true/false
_hjMinimizedPolls	Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.	365 days	Boolean true/false
_hjShownFeedbackMessage	Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.	365 days	Boolean true/false
_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	UUID
_hjRecordingLastActivity	This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).	Session	Numerical Value (Timestamp)
_hjTLDTest	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	Session	Boolean true/false
_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	Hash
_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	JSON
_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	Boolean true/false
_hjIncludedInPageviewSample	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.	30 minutes	Boolean true/false
_hjIncludedInSessionSample	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit.	30 minutes	Boolean true/false
_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	Boolean true/false
_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	Boolean true/false
hjViewportId	This stores information about the user viewport such as size and dimensions.	Session	UUID
_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	Boolean true/false
_ga	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	1 day	HTTP
_gat	Used by Google Analytics to throttle request rate	1 day	HTTP
_gid	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	1 day	HTTP