This table lists all cookies used on a standard Eploy candidate portal. Each customer may choose not to use some of the optional features or add new ones of their own.
Eploy uses strictly necessary cookies to make your site works and functional cookies to enhance the overall experience. We also use optional analytics cookies to help us continually improve the service. Users of your Eploy powered candidate portal can continue with these cookies or change them by customising their settings.
Strictly Necessary Cookies
These cookies are essential for the website to function. They enable core functionality such as security and accessibility. Users may disable these by changing their browser settings, but this may affect how the website functions.
Functional Cookies
These cookies are used to enhance the functionality of our websites but are non-essential to their use. However, without these cookies, certain functionality may become unavailable.
Performance & Analytics Cookies
These cookies collect information that is used in aggregate form (to help us understand how websites are being used), to understand how effective marketing campaigns are and to help customise websites for users or to enhance their experience.
| Provider | Cookie | What are they for? | How long do they remain? | Can they be disabled? |
| Strictly Necessary | ||||
| Eploy | ASP.NET_SessionId ASP.NET_AuthId Eploy.Session |
These are session cookies that helps the visitor use the website. It doesn’t capture any personal information. | It's automatically deleted when you shut your browser. | No – it’s essential to make the page work. |
| Eploy | Eploy_CookieConsent | This stores the type of cookies which the candidate has given their consent to store on their PC. E.g. Performance, Analytics etc. | It will automatically expire after 12 months. | No - this cookie is required if the visitor is using the new cookie consent module. If the customer is not using it then it will not be stored. |
| Eploy | CookiesDirective | This records that the visitor confirmed they have read the cookie banner so that it does not appear again. This doesn’t store any other information. This will be replaced by Eploy_CookieConsent. | It will automatically expire after 12 months. | No |
| Functional | ||||
| Eploy | SavedVacanciesCookie | It stores the vacancy ID which is used for keeping a list of saved jobs. It will only store a vacancy ID if the visitor clicks on ‘save job’. | It's automatically deleted when you shut your browser. | Yes - although a visitor won’t be able to save a job without registering first. |
| Eploy | RememberMeCookie | This stores whether or not the visitor has ticked the ‘Remember Me’ option when they log in or register. | It will automatically expire after 12 months. | Yes |
| Eploy | UsernameCookie | This enables the site to remember the visitor’s login name if ‘Remember me’ is ticked. | It will automatically expire after 12 months. | Yes |
| Eploy | CultureSystemCodeID | This is only used for multilingual sites to store the visitor’s culture and set formatting of currency, dates etc. No personal information stored. | It will automatically expire after 12 months. | Yes |
| Eploy | LocalTimezoneVariable | Used to store the visitor’s time zone so dates are formatted and time zones are set to their location. This doesn’t store any other information. | It will automatically expire after 12 months. | Yes |
| Eploy | WebsiteModeID | This is only used when the website has more than one mode (e.g. sites with Graduate Schemes). This doesn’t store any other information. | It will automatically expire after 12 months. | Yes |
| Various | Some websites have the ability to share jobs to social networks. The browser will send information to the specific social site they wish to share content to. The social site will receive the visitor’s ID (on Facebook etc.), the website that they are visiting, the date and time and other browser related information. The names of these cookies changes from time to time. These cookies are only active if this feature is used. |
See the 3rd party pages for more information: |
Yes | |
| Google SSO: SSID | Some websites have the ability to apply for jobs using social profiles, the site will always ask for consent to do this. These will only ever be active if the visitor chooses to use this service and currently only Google applies a cookie. | It will automatically expire after 6 months. | Yes | |
| Dropbox |
Dropbox when uploading from Dropbox Google when uploading from Google One Drive - no cookies |
When uploading a CV or other document the visitor has the option to upload directly from their device or a cloud service like Dropbox. Both Dropbox and Google use cookies for this service, One Drive does not. These cookies are only active if this feature is used. | Yes | |
| YouTube | YouTube yt- |
Some websites embed videos from a YouTube channel, normally using YouTube’s privacy-enhanced mode. This mode may set cookies on a visitor’s computer once they click on the YouTube video player, but YouTube will not store personally-identifiable cookie information for playbacks of embedded videos when using the privacy-enhanced mode. | Read more at YouTube’s embedding videos information page. | Yes |
| Performance & Analytics | ||||
| Indeed | _indeed | Indeed conversion tracker is used by some websites to track the success of advertising jobs with Indeed. When a job seeker navigates to Indeed.com and clicks on a job, a cookie from Indeed.com is placed on their device. | 30 days. | Yes |
| __ga _gali _gat_UA-1036645-1 _gid |
This suite of cookies are managed by Google for analytics. They might be used to collect information about: how many site visitors how visitors use the site where visitors come from, both geographically and from which website |
It will automatically expire after 2 years. |
Yes | |
| _twitter_sess | Some websites may have a Twitter feed displayed, which if clicked allows a suite of Twitter cookies to track where the visitor came from and provides Twitter with details of their Twitter user name (if logged in). | It will automatically expire after 12 months. | Yes | |
Updated 13.08.2021 in line with Eploy version v43