This Cookie Statement was updated on May 5, 2026.
This Cookie Statement describes how SAP (hereinafter also “We”, “Our”) uses cookies and similar technologies to collect and store information when you visit SAP Partner Portal. SAP’s Privacy Statement applies in addition to this Cookie Statement. SAP’s Privacy Statement informs you about the way SAP uses, stores and protects personal data collected. It also informs you of your data protection rights and how to exercise them. We recommend that you read SAP’s Privacy Statement: https://partneredge.sap.com/en/public/privacy-policy.html(opens in new tab)
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 at perform a similar function to cookies. These include inter alia web beacons, clear gifs, and social plug-ins. These are often used in conjunction with cookies to help a website owner understand its users better.
What are first party Cookies?
SAP’s websites contain first party Cookies. 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?
The difference between a first party cookie and a third party cookie relates to who places the cookie on your device. SAP sometimes allows third parties to place Cookies on your device. 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. For more information about these Cookies, please click the “Cookie Preferences” link in the footer of the webpage.
Analytics and Digital Marketing in the United States of America
In the United States SAP routinely works with third party analytics and digital marketing providers who facilitate and support SAP (and partner) marketing activities including targeted communications. These activities may involve the sharing of limited Personal Information (personal identifiers and contact information, your interests and interactions with SAP, professional/employment information) for those specific business purposes. In addition to the above, SAP may also share your personal data with other third parties, or for other business purposes, with your explicit consent. SAP endeavors to recognize common opt-out preference signals at a browser level, and frictionlessly exclude you from marketing cookies and associated tracking.
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 this SAP Web presence?
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 technical features on SAP Partner Portal. 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 SAP Partner Portal.
When tracking and evaluating the usage behavior of users of the Web Presence by means of cookies or similar technologies includes the processing of your personal data, SAP is conducting the processing based on the following legal permissions:
SAP differentiates between Required Cookies that are absolutely necessary to enable technical core functionalities, Functional Cookies that allow SAP to analyze the site usage, and Advertising Cookies that are used to serve ads relevant to your interests.
| Name | Description/Purpose | Persistent | LifeSpan |
|---|---|---|---|
| IDP_SESSION_MARKER_accounts | Marker used by SCI to support SSO, JWT login | N | Session |
| country | Data associated with a country detected by ip | 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 |
| JSESSIONID | Used to communicate with SCC | N | Session |
| PEP_PRM_PROD | Store encrypted access token for connection to PRM and exists only for authenticated users. | Y | 1 hour |
| PEP_PRM_REFRESH_PROD | Store encrypted refresh token for connection to PRM and exists only for authenticated users. | N | Session |
| PEP_IDS_PROD | 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 |
VCAP_ID |
Technical routing cookie automatically set by SAP BTP/Cloud Foundry infrastructure to maintain session affinity. Ensures all requests during a session are directed to the same application server instance for session continuity. |
N |
Session |
renderid |
Helps to evenly distribute server load by recording information about the server you interacted with |
N |
1 week |
botinfo_sap |
Used by the system to recognize bots, ensuring a secure and efficient user experience |
Y |
1 year |
ak_bmsc |
A cache is used by the website to optimize the response time between the visitor and the website |
Y |
1 month |
bm_mi |
This cookie is leveraged by the system to recognize bots, ensuring a secure and efficient user experience |
N |
Session |
bm_sv |
Cookie used by Akamai Botman Manager to help differentiate between web requests generated by humans and web requests generated by bots or other automated processes |
Y |
1 year |
TAsessionID |
Retains a TrustArc session ID to collect and record cookie consent decisions |
Y |
15 days |
cmapi_cookie_privacy |
TrustArc sets this cookie to manage the display of the cookie consent pop-up and to retain the selected settings |
Y |
1 year |
cmapi_gtm_bl |
TrustArc sets this cookie to manage the display of the cookie consent pop-up and to retain the selected settings |
Y |
3 months |
optout_domains_pc |
When the optout_domains_pc cookie is set, and the user switches to a subdomain with no consent or conflicting consent, the user’s opt-out preference is respected across subdomains. |
Y |
391 days |
kndctr_#_AdobeOrg_cluster |
Allows the website to determine the number of specific user-visits for analysis and statistics. |
N |
1 day |
kndctr_#_AdobeOrg_identity |
Used for internal analytics by the website operator. |
Y |
13 months |
QSI_SI_#_intercept |
Used to store user settings during the current session. |
Y |
2 days |
| Name | Description/Purpose | LifeSpan |
|---|---|---|
AMCV<id> |
Adobe Site Catalyst cookie |
Session |
AMCV_MCMID |
Stores a unique visitor ID to track users for marketing and analytics purposes. |
Session |
mbox |
Adobe Target session |
2 years |
at_check |
Adobe Audience Manager sets this temporary cookie to check if the cookie read/write capability is enabled on the browser |
1 year |
_mkto_trk |
Store Adobe Marketo Munchkin info and send to SMC |
2 years |
kndctr_###_identity |
Stores identity-related information required for data routing and processing within the Edge Network. |
395 days |
kndctr_###_consent |
Stores and manages user consent preferences in connection with Adobe Experience Platform services. |
180 days |
kndctr_###_consent_check |
A session-scoped helper cookie that prompts the Edge Network to revalidate consent server-side after the TTL expires. |
2 hours |
kndctr_###_cluster |
Stores the Edge Network region serving the user’s requests to ensure proper routing. If a user’s IP address changes during the cookie lifetime, routing may be updated to the nearest region. |
30 minutes |
kndctr_###_personalization |
Stores session information used by Adobe Target for content personalization. |
395 days |
_gd_visitor |
6sense uses this cookie for collecting information on the user’s visit such as the number of visits, average time spent on the website, and the pages loaded for displaying targeted ads. |
400 days |
_gd_svisitor |
6sense uses this cookie as a long lived unique identifier of the user. It is either correlated to the 6suuid or a unique value. |
400 days |
_gd_session |
6sense uses this cookie for collecting information on users’ visits such as the total number of visits, average time spent on the website, and pages loaded. |
4 hours |
6suuid |
A third-party unique identifier for the visitor that is managed by 6sense. |
1 year |
_gcl_au |
Google Tag Manager uses the cookie to store ad click information, enabling conversion tracking beyond the landing page |
3 months |
client |
The SAP Next Generation Data Service uses this cookie to capture the visitor’s ID for building a personalized browsing experience |
1 year |
session |
The SAP Next Generation Data Service uses this cookie to capture the session ID for building a personalized browsing experience |
1 year |
s_ecid |
Contains a copy of the Adobe Experience Cloud ID |
Session |
s_pers |
Adobe Analytics uses this cookie to retain ongoing analytic data. |
1 year |
s_plt |
Set to track the time that the previous page took to load |
Session |
s_pltp |
Provides page name value (URL) for use by Adobe Analytics |
Session |
s_sess |
Adobe Analytics uses this cookie to retain temporary analytic data |
1 year |
| Name | Description/Purpose | LifeSpan |
|---|---|---|
__spdt |
Used by Spotify to store browsing behaviour to enable targeted advertising and measure advertisement performance |
10 months |
_clck |
Used by Microsoft to persist a user ID across sessions to track behavior over time |
1 year |
_clsk |
Used by Microsoft to connect multiple page views into a single session recording |
1 day |
_fbp |
Meta uses to track visitors across websites and collect information to provide customized ads |
3 months |
_uetsid |
Used by Microsoft to store a session ID for tracking user interactions on a website. |
2 hours |
_uetvid |
Used by Microsoft to store a visitor ID to track users across sessions. |
Session |
_twpid |
Used to track user behavior for advertising and marketing purposes via Twitter. |
390 days |
How can you manage and delete cookies?
SAP provides you with the option to adjust your preferences for Functional and Advertising Cookies when such cookies are placed on your device. In such a case, 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 using your browser settings, most browsers allow you to refuse or accept all cookies or only to accept certain types of cookies. The process for the management and deletion of cookies can be found in the help function integrated in your browser.
If you wish to limit the use of cookies, you may not be able to use all the interactive functions.