www.sap.com
Open in
urlscan Pro
2a02:26f0:6c00:296::1e22
Public Scan
URL:
https://www.sap.com/corporate/en/legal/privacy/cookies.html
Submission: On October 17 via manual from IN — Scanned from DE
Submission: On October 17 via manual from IN — Scanned from DE
Form analysis
0 forms found in the DOMText Content
Javascript must be enabled for the correct page display Skip to Content * Products * Industries * Services and Support * Learning * Community * Partner * About Try & Buy Contact Us Contact Us Contact Us * SAP Privacy Statement COOKIE STATEMENT This Cookie Statement describes how SAP.com uses cookies and similar technologies to collect and store information when you visit SAP.com websites. WHAT ARE COOKIES AND SIMILAR TECHNOLOGIES? Cookies are small files placed on your device (computer, tablet or smartphone). When you access a website, a cookie is placed on your device and it will send information to the party that placed the cookie. There are other technologies that perform a similar function to cookies. These include web beacons and clear gifs. These are often used in conjunction with cookies to help a website owner understand its users better. When SAP sends you newsletters or other messages SAP uses these technologies as follows so that SAP can track email open and click rates: In order to determine a user's ability to receive HTML e-mail in addition to whether or not an e-mail has been opened, SAP includes a "web beacon" in the majority of HTML e-mail messages SAP sends. A web beacon (a small .gif image) is activated when an HTML e-mail is opened via a request for the image on our servers. This capability helps SAP send e-mail in a format that users can read and enables us to track the aggregate number of e-mails opened. The web beacon does not collect any personal data. WHAT ARE FIRST PARTY COOKIES? SAP’s websites have first party cookies and allow third parties to place cookies on your device. The difference between a first party cookie and a third-party cookie relates to who places the cookie on your device. First party cookies are cookies that are specific to the website that created them. These cookies enable SAP to operate an efficient service and to track patterns of user behavior to SAP’s website. WHAT ARE THIRD PARTY COOKIES? Third party cookies are placed on your device by a third party (i.e., not by SAP). While SAP allows third parties to access SAP’s website to place a third-party cookie on your device, SAP does not retain control over the information supplied by the cookies, nor does SAP retain access to this information. This information is controlled wholly by that third party according to the respective privacy policy of the third party. To access more information about these cookies, please click the “Cookie Preferences” link in the footer of the webpage. WHAT IS A SESSION AND WHAT IS A PERSISTENT COOKIE? Our websites may place session and persistent cookies on your device. Whereas the difference between a first party and third-party cookie relates to the party controlling the initial placement of the cookie on your device, the difference between a session and a persistent cookie relates to the length of time the cookie lasts. Session cookies are cookies that typically last for as long as you are using your browser, or browser session. When you end your browser session, the cookie expires. Persistent cookies, as the name implies, are persistent and will last after you close your browser. This allows for quicker and often more convenient access to our website. WHAT COOKIES ARE USED ON SAP WEBSITES? SAP wants you to be in a position to make an informed decision for or against the use of cookies which are not strictly necessary for the website’s technical features. If you elect to reject cookies used for advertising, you will be shown advertising that is less targeted to your interests. This will still allow you to use all of the functionality of the website. SAP differentiates between Required Cookies that are absolutely necessary for the website’s technical features, Functional Cookies that allow SAP to analyze the site usage, and Advertising Cookies that are used by advertising companies to serve ads relevant to your interests. Required Cookies Required Cookies are required to enable core site functionality. These cookies allow SAP to provide you a secure log-in and to remember your log-in details, to establish and maintain your shopping cart, and to make sure the website looks consistent. Functional Cookies Functional Cookies allow SAP to analyze site usage so it can measure and improve its performance. These cookies collect information on how a website is used – for example which pages a visitor opens most frequently and whether they receive error messages from a page. These cookies do not save any information that permits identification of the user. The collected information will be aggregated and thus will be analyzed in a non-attributable way to a specific person. These cookies are used exclusively to improve the performance of a website and thus the user experience. Advertising Cookies Advertising Cookies are used by advertising companies to serve ads that are relevant to your interests. These Cookies allow you to share pages with social networks and to post comments. Further, to serve ads relevant to your interests. WHAT FIRST PARTY COOKIES ARE ON SAP.COM? Required cookies Name Description/Purpose Persistent LifeSpan ONEDX_IDS Store login status and exists only for authenticated users. It contains encrypted info about user name, session index, and different user data: last name, c-number, e-mail, etc. N Session IDP_SESSION_MARKER_accounts Marker used by SCI to support SSO, JWT login Y Session IDS_autoLoginChecked Stores whether a user has checked the Remember me checkbox on the logon page (SAP Lumira Cloud) N Session cmp-parameters Stores parameters received from the campaign form Y 15 min countryCode Stores country code selected from country selector Y 30 days localeCode Stores locale selected from country selector Y 30 days locale Stores locale N Session country Data associated with a country detected by ip N Session <formName> Specifies if requested gated page (TYP) is accessible, i.e. appropriate campaign was registered successfully Y 45 days user-in-gating-flow Flag to check if the user in gating flow to provide appropriate functionality during redirects N Session gated-asset-id Flag to check if the user in gating flow to provide appropriate functionality during redirects N Session crm_code Flag to check if the user in gating flow to provide appropriate functionality during redirects N Session requestToAssetFromTYP Cookie to prevent open TYP by direct link N Session compatibilityPopup To prevent double popup appearance about compatibility browser (IE only) Y 30 days sc_add_event Produce checkout Y 365 days SAP.TEXTONLY Text only view. Cookie removed after turn off text view. N Sessions submittedCampaignForm Use data from already submitted campaign instead of asking the user to submit the gated form again. Contains last 5 submitted campaigns Y 300 days CampaignLandingPage Contains the path to the campaign information, will be passed to SMC N Session campaigncode Contains the path to the campaign information, will be passed to SMC N Session url_id Contains the path to the campaign information, will be passed to SMC N Session analytics_url_id Contains the path to the campaign information, will be passed to SMC N Session useractivated The flag that user finished account activation N Session CodeTrackingCookie Create multiple cookies Based on global/settings/ctrackingcodesettings.define. Typically, record the value in url_id and external referrer. N Session QSI_HistorySession Qualtrics creates to accumulate each full URL that a visitor visits in a session N Session notice_behavior Define scenery for user N Session notice_gdpr_prefs Store user selection from cookie banner Y 1 year notice_preferences Store user selection from cookie banner Y 1 year BIGipServer~<>renderid BIGIP Related to support sticky session Y 30 min Functional cookies Name Description/Purpose Persistent LifeSpan event1ContactUs Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1Newsletter Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1CampaignEP Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1Basic Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1CampaignLP Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1Premium Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1ProfileUpdate Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1ProfileUpgrade Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1Subscribe Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session event1Upgrevent1ContactUsade Contains timestamp + English alphabet symbols pended to rich length in 20 symbols. Used for event1 serialization. N Session DBLiveEngage Assumption: Flag that session should be shared only once Y 30 min LPVID Live Person visitor ID Y 30 min LPSID_{Liverpson Account ID} Live Person Session ID N Session mbox Adobe Target session Y 30 min _sdsat_demandbase Demandbase data N Session s_pers Tracking Cookie Y 30 days s_sess Tracking Cookie N Session s_referrer Adobe Site Catalyst cookie. store referer N Session AMCV<id> Adobe Site Catalyst cookie. N Session SAP.TTC Conversion cookie that checks when the user first visits the site Y 90 days client Tracking Cookie Y 2 years session Tracking Cookie N Session _gcl_au set by google ad services Y 3 month HOW CAN YOU MANAGE AND DELETE COOKIES? SAP provides you with the option to adjust your preferences for Functional and Advertising Cookies, and you can access preferences at any time by clicking on the “Cookie Preferences” link in the footer of the webpage. You can also block and delete cookies by changing your browser settings. To manage cookies, most browsers allow you to refuse or accept all cookies or only to accept certain types of cookie. The process for the management and deletion of cookies can be found in the help function integrated in the browser. If you wish to limit the use of cookies, you may not be able to use all the interactive functions of our website. Last revised: March 10, 2020 Enlarge View table HOW IS YOUR EXPERIENCE WITH THIS PAGE? QUICK LINKS * Why SAP * Intelligent Enterprise * Small and Midsize Enterprises * SAP Trust Center * SAP Insights * SAP Community * Developer * Support Portal ABOUT SAP * Company Information * Worldwide Directory * Investor Relations * Careers * News and Press * Events * Customer Stories * Newsletter SITE INFORMATION * Privacy * Terms of Use * Legal Disclosure * Copyright * Trademark * Sitemap * Text View * Cookie Preferences CONTACT US Germany 0800/5 34 34 24 Or see our complete list of local country numbers Contact Us FIND US ON * * * * * * Back to top