Syndigo Cookie Notice for the Content Experience Suite (CES)

Effective Date: November 14, 2023

Introduction and Scope

This Cookie Notice (the “Notice”) is designed to assist you in understanding how and why Syndigo LLC (“Syndigo”, “we”, “us”, “our”) uses cookies and other similar technologies (“Tracking Technologies”) to collect certain information, including information considered as personal data on the Content Experience Suite (formerly Context Experience Hub or CXH) platform (the “Website”).

We use Tracking Technologies to allow our Website to operate, to authenticate your log-in credentials, to display media content to you, and to secure the Website. This Notice does not apply to Tracking Technologies that may be active on our Website following your visit to other websites.

To the extent that information collected by the Tracking Technologies constitutes personal data (on its own or if combined with other information), our Privacy Notice shall apply to the processing of such personal data, as defined in the Privacy Policy.

Cookies and Other Tracking Technologies

A “cookie” is a small text file stored on your device (computer, phone, tablet, etc.) that contains information about your browser, device, and online activity. This information often consists of a string of numbers and letters that uniquely identifies your device.

We use both session and persistent cookies on our Website. Session Cookies are deleted when you close your browser. Persistent cookies may remain after you close your browser, but they have an expiration date.

Some of the cookies placed on your device through our Website are first-party cookies, because they are placed directly by us. Other are third-party cookies, meaning that they are placed through our Website by third parties. Please refer to the privacy policies of these third parties to learn more about the way in which they collect and process information about you.

Our Website also employs “local storage” and “session storage”, which enables our Website to store information locally on your device. In particular, we use’s analytics services, which are based on local storage. Pendo allows us to analyze your use of the Website and to present you with guides and notices.  You can read’s privacy notice here.

Opting Out; How We Respond to Do Not Track Signals and Global Privacy Control

You have the right to opt out or reject the use of non-essential Tracking Technology. To do this you can alter the configuration of your browser to reject certain types of Tracking Technologies. You can set your browser to send a “Do Not Track” (“DNT”) signal or set up Global Privacy Control (“GPC”). For more information on GPC, please visit: We will not yet respond to your GPC signals. Please note that our Website does not respond to DNT signals received from web browsers.  For more information about how to manage and delete cookies in your browser, please visit  Note, if you reject certain Tracking Technologies, you may not be able to access and use all of the features on our Website.

The Tracking Technologies We Use on Our Website

Strictly Necessary Tracking Technologies: The following Tracking Technologies are necessary for the Website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you that amount to a request for services, such as setting your privacy preferences, logging in, or filling in forms. You may be able to set your browser to block or alert you about these Tracking Technologies, but if you block them, some parts of our Website will not work.

NameConsent Manager TagProviderPurposeDuration
.ADAuthCookie, .ADAuthCookie_domain, .ADAuthCookie_devAuth, .auth_en_authSyndigoSyndigo (first-party cookie)To enable user authentication.Session
.auth_en_uatSyndigoSyndigo (first-party cookie)1 week
XSRF-TOKENSyndigoSyndigo (first-party cookie)To ensure site security by preventing cross-site request forgery attacks.Session

Performance Tracking Technologies: The following Tracking Technologies allow us, among other things, to count Website visits and traffic sources so we can measure and improve the performance of our Website. They help us to know which pages are the most and least popular and see how visitors move around the Website. If you do not allow these Tracking Technologies, we will not know when you have visited our Website and will not be able to monitor its performance.

NameConsent Manager TagProviderPurposeDuration
None currently in use.

Functional Tracking Technologies: Functional Tracking Technologies enable the Website to provide enhanced functionality and personalization. They may be set by us or by third-party providers whose services we have added to our pages. If you do not allow them, then some or all of these services may not function properly.

NameConsent Manager TagProviderPurposeDuration
None currently in use.

Targeting Tracking Technologies: Targeting Tracking Technologies may be set through our Website by our advertising partners (or set directly by our advertising partners). They may be used by those companies to build a profile of your interests and show you relevant advertisements on other sites. They do not store personal data, but are used to develop personal data about you, such as to uniquely identify your browser and internet device. If you do not allow these, you will experience less targeted advertising.

NameConsent Manager TagProviderPurposeDuration
None currently in use.

Local Storage and Session Storage

We use local storage and session storage on the CES platform which enables our Website to store information locally on your device.

currentCompanySyndigoHolds the ID of the currently selected accountAs long as the user allows. Data will be cleared when the user clears her browser.
cxh:page-sizeSyndigoPreference for max number of records returned for a data page (such as product index)
ljs-hideLocalize (Third party) See Localize Privacy Notice and Information about Local StorageTo determine whether or not localize.js is active on the webpage.As long as the user allows. Data will be cleared when user clears browser.
ljs-source-langTo source the language ID of the webpage.
ljs-cacheThis is the version number of the currently cached translation dictionary.
ljs-langTo determine the currently selected language of the webpage
ljs-visistTo determine the number of pageviews
QqOxaJvigUDKtsettingsProject settings ([Project Key]settings)
pendo_tabldPendo (Third-party)   See Pendo’s Privacy Notice  Unique ID Pendo generates to represent that tab of the browser.As long as the user allows. Data will be cleared when user clears browser/closes the tab.
pendo_cdPendo uses this to detect cloned browser tabs.
_pendo_accountId.ff928d67-c3bb-4949-45bc-d33ef7be75d8This is used to identify and record the visitor’s account ID that will be used in Pendo like Guide delivery and analytics. If disabled, the account ID will not be recorded with events or xhr events until the user has been identified again. This could cause issues with analytics and Guide delivery.100 days
_pendo_meta.ff928d67-c3bb-4949-45bc-d33ef7be75d8This stores a hash of the current metadata so that Pendo can see when it is changed and update it. If disabled, metadata events may be sent too frequently to the point where Pendo may have complications tracking when metadata changes happen.
_pendo_visitorId.ff928d67-c3bb-4949045bc-d33ef7be75d8This is used to identify and record the visitor information so the information is used in Pendo analytics and Guide delivery.  If disabled, VisitorID is central to all analytics and Guide delivery. The visitorID will not be recorded on any Guide events (i.e. dismiss, advanced, or in segmentation) or usage data until the user has been identified again
pendo_guides_blocked.ff928d67-c3bb-4949-45bc-d33ef7be75d8This is used when Pendo detects that the visitor has an ad blocker in their browser which is essentially preventing Pendo from reliably sending events.  Pendo then shutsdown guide loading.Has a 30 minute TTL for when the guides are blocked and a 4 hour TTL for when the guides are not blocked.

With regards to Localize local storage listed above, a dictionary cache string will be saved for each language that you select in the Localize widget, along with the source language. The name of the variable will be the Project Key followed by the language ID. This caches the source and target language phrases in the browser to increase performance. If any of the source or target language changes, this data will be automatically refreshed with the new data.

Changes to this Notice

If we make any material change to this Notice, we will post the revised Notice to our Website and update the “Effective Date” above to reflect the date on which the new Notice became effective.

Contact Us

If you have any questions about this Notice, send us an email to or contact us by postal mail at:

141 W. Jackson Blvd., Suite 1375
Chicago, Illinois 60604

Please allow up to four (4) weeks for us to reply.