Cookies Policy

Cookies Overview

 

. Cookies are small files which are stored on a user’s computer. They are designed to hold a modest amount of data specific to a particular client and website, and can be accessed either by the web server or the client computer. This allows the server to deliver a page tailored to a particular user, or the page itself can contain some script which is aware of the data in the cookie and so is able to carry information from one visit to the website (or related site) to the next.

- Think of a cookie as an identification card that’s uniquely yours. Its job is to notify the site when you’ve returned. While it is possible to misuse a cookie in cases where there is personal data in it, cookies by themselves are not malicious.

. Many websites use cookies. Cookies tell us how often you visit pages, which helps us learn what information interests you. In this way, we can give you more of the content you like and less of the content you don't.

. Cookies let you store preferences and user names, register products and services, and personalize pages. But if you never register or leave personal information at a site, then the server only knows that someone with your cookie has returned to the website. It doesn’t know anything else.

. Clients have an option to present users with a cookie opt-in policy via the TC User Session Type choices in Command Centre under Site Setup Settings.

1. Cookie Session w/Remember Me option. The session is managed with cookies. Allows the user to choose whether the cookies will be permanent cookies or temporary cookies by checking a "Remember Me" box.

2. Cookie Session Temporary: expiring cookies. The session is managed with cookies that will expire when the users browser is closed.

3. Cookie Session Permanent: non expiring cookies. The session is managed with cookies that will never expire, keeping the user permanently logged in with the browser they are using.

4. Server Session: The session is managed with server-side session variables. No login cookies are set, and the users session expires when the browser is closed. (This is the recommended type for optimal use of Candidate Account Simplification, and to keep the site in compliance with the latest data privacy laws).

 

The list of cookies used in Recruiting Marketing Career Sites and their duration in the Recruiting Marketing Career Sites is outlined in the RMK Guide.

Note that customers might come across a cookie : ‘cookie_j2w’ not set to “secure”. We are in the process of performing some infrastructure changes where customer sites are moving to a new backend load balancing mechanism which renders the cookie_j2w obsolete. We have been migrating sites to this new configuration in batches and expect this to be completed shortly.

The cookie used in the new infrastructure is ‘JSESSIONID’ and is secure.

Cookies used in Recruiting Marketing(RMK) Career Sites:

rmk0: The user's encrypted email address, if known. Initially created whenever a new user visits an Recuiting Marketing site and a session is created. Updated when the user provides us with an email address. If SSL mode is turned on for entire site, cookie is sent from the browser to the server using a secure protocol, e.g. SSL.

Type: Persistent or Session

Duration: If Persistent, cookie doesn’t expire. If Session, cookie expires when the session ends.

How to Disable and impact if Disabled: Disable through browsers or computer configurations. User will not be able to log in.

rmk1: The encrypted ID of the user if one exists. Initially created whenever a new user visits a Recruiting Marketing site and a session is created.  Updated when the user logs in or becomes a member and is assigned a user ID. If SSL mode is turned on for the entire site, cookie is sent from the browser to the server using a secure protocol. e.g. SSL.

Type: Persistent or Session

Duration: If Persistent, cookie doesn’t expire. If Session, cookie expires when the session ends.

How to Disable and impact if Disabled: Disable through browsers or computer configurations. User will not be able to log in.

rmk4: Whether or not to prefill the Subscribe box with the user’s e-mail address, in order to avoid the user having to re-enter their email address. Initially created whenever a new user visits a Recruiting Marketing site and a session is created. Updated when the user modifies their Remember Me preference. If SSL mode is turned on for entire site, cookie is sent from the browser to the server using a secure protocol, e.g. SSL.

Type: Persistent or Session

Duration: If Persistent, cookie doesn’t expire. If Session, cookie expires when the session ends.

How to Disable and impact if Disabled: Disable through browsers or computer configurations. User will not be able to log in.

rmk12: A number that indicates if the user has acknowledged the cookies policy banner. If the cookie is not set, then the banner may be presented. If the cookie is set and its value is 1, the banner may be suppressed. This cookie will persist across user sessions, no matter which type of cookies are enabled site wide. Created as a persistent cookie when the user acknowledges the cookies policy banner by either viewing the cookies policy or choose to dismiss the banner.

Type: Persistent or Session

Duration: If Persistent, cookie doesn’t expire. If Session, cookie expires when the session ends.

How to Disable and impact if Disabled: Disable through browsers or computer configurations. User will not be able to log in.

JSESSIONID: Single cookie placed on the users device during their session so the server can identify the user. This replaces the RMK0, RMK1 and RMK4 cookies when the site is configured to use Server Session Cookies. Created as a session cookie whenever a new user visits a Recruiting Marketing site. The value is not updated unless the current session ends, in which case a completely new JSESSIONID cookie is set.

Type: Persistent or Session

Duration: If Persistent, cookie doesn’t expire. If Session, cookie expires when the session ends.

How to Disable and impact if Disabled: Disable through browsers or computer configurations. User will not be able to log in.

LoadBalancer Cookie: Cookie for session stickiness preventing a user from bouncing from one instance to another. Typically issued by F5 once upon new entry to career site, if prior cookie doesn¡t exist.

iNOTE: As new DCs come online, their new Load Balancer cookies will follow this pattern: BIGip-Server-partition-saas_prod-dc<DC number><random key>

Type: Session

Duration: Cookie expires when the browser session ends.

 

i Note: The below cookies are dropped by third-party applications and will only be present if the third-party applications are configured. These cookies may change as third-party applications make changes to their applications without notifying SAP. The Recruiting Marketing Social Sharing widgets may drop third-party cookies on Recruiting Marketing sites where configured. Work with Recruiting Marketing Professional Services for a full list of cookies dropped by the social sharing applications.