Conclave Cloud is here! Get started with confidential serverless computing architecture today.
We enjoyed the clarity of the DTCC’s thoughts on Security Token Platforms and the underlying blockchain platforms on which tokens are recorded. Their guidance aligns with our thinking and the design of Corda. This short post provides highlights, and our commentary.
The digital assets market has had a few weeks to digest the DTCC’s whitepaper — and at R3 we are very much aligned with the important conclusions of the paper.
Let’s be clear — this is not a piece discussing whether a particular token is a security or not: that is the purview of the appropriate financial regulator. This was discussing principles for the post-trade processing of financial securities recorded as tokens on blockchains.
So, given that a token in question is a financial security, how should it be treated? And what should you care about if you’re part of the Token Market Infrastructure (TMI)?
Who is TMI? It is Financial Market Infrastructure (FMI), for tokens. Today, the entire TMI is being built out, with tools and platforms for investors (who want to hold the assets), issuers (companies who issue financial security tokens to raise funds for projects and initiatives), and the intermediaries and infrastructure that supports these activities (advisors, asset issuance platforms, exchanges, custody solutions, etc).
We are all TMI.
So what does the DTCC, arguably one of the most successful financial services infrastructure operators in the world, think about tokens? Especially how they are recorded and managed?
We’ve picked out some important and relevant points.
“Existing regulations applicable to the post-trade processing of traditional securities should be applicable to the post-trade processing of tokenized securities. In some cases those existing regulations might not squarely apply.”
Clearly, something is new here. Existing regulations work for existing technologies, but now we have the ability to control assets using digital signatures, and hold these assets digitally, and have guaranteed bilateral and multilateral automation to improve the way we transact and manage assets.
But with new technologies come new risks:
“… those developing policy should determine the legal and other requirements applicable to a Security Token Platform based on the functions it performs and the risks it poses. These risks include custody risk, principal risk, and operational risk.”
Private keys — short strings of text — are crucial to the ability to transact — especially for cryptocurrencies on public blockchains where there is no recourse. For tokens issued by issuers, there may be ways to cancel tokens and re-issue them to parties who have lost private keys. So risks that an investor or a trusted custodian has a private key copied or lost, needs to be managed. This means new operational processes, technologies, and solutions.
Where can we seek inspiration?
“Regulatory principles developed by international standard setting bodies, such as the “Principles for financial market infrastructures,” or PFMIs, can serve as useful guidance.”
“DTCC believes that a Security Token Platform will not attract institutional investors unless these requirements are adequately met.”
Much of the paper is about whether security tokens should be recorded on permissionless networks (eg Bitcoin, Ethereum, EOS, etc) or permissioned networks (eg Corda).
“Because the identities of their users and contributors are unknown, users have not been qualified through any type of anti-money laundering, know-your-customer, or OFAC process.”
This isn’t about the holders of tokens: it is relatively easy to restrict holders to a pre-vetted whitelist of participants, and various token standards are emerging that allow whitelisting in the smart contracts governing what the tokens can and can’t do.
This is regarding who can write to the ledger, and who is paid a fee for doing so. On a permissionless blockchain network, your transaction can be recorded by a pseudonymous actor in a sanctioned country, and you will be paying them a fee to do so. Are you ready to do business with sanctioned actors, even accidentally? Are you also willing to give up control over the recording of transactions to a group of parties who have not committed to any service level agreements, who you can’t sue if things go wrong, and to whom you have no recourse?
“A permissioned network allows for a centralized governance structure and enables assignment of responsibilities to a network operator. Decision-making may be more centralized for certain aspects of the network and more distributed for other aspects.”
Using a permissioned network seems to be the best approach that allows for the benefits of tokens (assured multilateral automation, frictionless transactions) without the uncertainties of using public permissionless networks.
“DTCC believes any platform that provides post-trade processing of security tokens should bear the following post-trade responsibilities. DTCC believes that these responsibilities are also applicable or highly relevant to most crypto assets. These responsibilities derive from specific, relevant international standards as well as specific regulatory requirements in the U.S. and elsewhere:
· Demonstrable Legal Basis
· Identifiable Governance Structure
· Identifiable Risk Management Procedures and Systems
· Identifiable Procedures and Systems to Ensure Settlement Finality
· Security Token Issuance, Custody and Asset Servicing
· Resilience
· Recordkeeping Requirements”
“Because a node on the permissionless network could be located anywhere in the world, the degree to which the governing law would be enforceable may need complex legal logic covering every regional policy to be built into every smart contract and depend on the location of the nodes. For example, even when the Security Token Platform utilizing a permissionless network is governed by the laws of a particular jurisdiction, if a majority of the nodes are located in jurisdictions that would not recognize such laws (or, even more fundamentally, the legal effect of transactions processed on such platform), the platform effectively would not be governed by the law the parties had agreed to.”
“… in a Security Token Platform utilizing a permissioned network, the legal risk associated with foreign parties can be flagged and mitigated in advance.”
In a permissioned network, well-governed business (sub)networks can be created that align with specific legal jurisdictions, allowing for the benefits of tokenised assets while still maintaining a strong legal basis.
“And on a Security Token Platform utilizing a permissionless network, it is not clear the degree to which node operators have legal obligations to other platform participants, such as a duty to continue platform operations or attempt to remedy (or not exploit) discovered platform vulnerabilities.”
Permissionless networks are anarchic and ungovernable by design — that’s how you make an unstoppable world computer. That is their strength, but also makes them inappropriate for financial securities which operate within governed frameworks.
“Additionally, if a Security Token Platform assumes a critical role in effecting securities transactions as well as custody and asset servicing, the question arises as to whether the platform should have in place adequate measures to address possible unavailability or discontinuance of its activities. The nature of these measures would depend on the structure and operations of the particular platform. For example, it is unclear whether the costs of a Security Token Platform configured to leverage a permissionless blockchain would or should include the operation of the permissionless network, which it does not control.”
It is a scary prospect to rely on a permissionless network with fees determined by a market rate, and who you have no recourse to if the network becomes unavailable.
“It is important to financial markets that transactions be considered “final” at some point in time, to ensure they cannot be unwound. Because settlement finality means a transaction cannot be unwound, the point at which settlement becomes final is determined by both the rules of the market (operational finality) and the governing legal framework in the relevant jurisdiction (legal finality).”
One of the principles from the PFMIs is that of finality — the point in time where a token has changed owner, and crucial in the case of a bankruptcy. We have long argued that the “longest chain rule” consensus mechanism of public blockchains do not give finality to a transaction — instead, participants agree that some number of blocks (which changes depending on network activity) is “good enough”. This isn’t good enough.
“It is an open question who would be responsible for the functions automated by a smart contract, particularly if something goes wrong or there is a change in circumstances necessitating a change to the smart contract, and what would be the legal and regulatory status of such person. To the extent that certain asset servicing functions could not be automated by smart contract, such functions would need to be performed by persons with the appropriate legal and regulatory status to do so, but how such persons would interact with the Security Token Platform, especially in a permissionless network, is unclear.”
Smart contracts are crucial — they define how an asset can behave. We believe that smart contracts should be written in well-known and understood coding languages such as Java.
“Therefore, in addition to a risk management framework, it would be prudent for a Security Token Platform to have a business continuity plan in the event of a wide-scale or major disruption.”
And what if the underlying blockchain, where the assets are recorded, were to have an event — say, chain choke from a popular or viral game? In early 2018, pending (unconfirmed) transactions on Ethereum increased sixfold due to Cryptokitties and drove transaction prices up 100x according to some sources.
“A Security Token Platform should demonstrate how it manages the privacy and confidentiality of appropriate records, particularly records that contain users’ personal or proprietary information, while maintaining their accessibility to regulators and appropriate third parties such as external auditors.”
Ah, the privacy vs transparency chestnut. Corda’s design deliberately avoided the “broadcast all the transactions” design of permissionless blockchains in favour of peer-to-peer “need to know” data transmission. This gives Corda the flexibility to send data to the right parties, at the right time.
“Using the post-trade processing responsibilities of today’s FMIs as a guide, such responsibilities for Security Token Platforms should be promulgated in appropriate rules and regulations, assigned to an entity providing post-trade processing services — whether or not it is vertically integrated into the trading platform — and credibly enforced. Otherwise, a Security Token Platform cannot operate in a manner consistent with the public interest.”
Corda was designed so that identified parties can build permissioned business networks to issue, transfer and manage the lifecycle of digital assets. The goals and capabilities that DTCC is recommending are aligned with the very same design inputs that have informed the design of Corda from the start.
It now seems that the crypto industry is starting to understand the benefits of Corda’s design.
If you are involved in building the token market infrastructure or creating a securities token platform, contact digital.assets@r3.com and we’d love to chat about how we can support your business.
Reflections on DTCC’s Guiding Principles for Post-Trade Processing of Tokenized Securities was originally published in R3 Publication on Medium, where people are continuing the conversation by highlighting and responding to this story.
Share
Sign up for our flagship newsletter, The R3 Ledger, to receive the latest R3 news, updates and content. View all our newsletters here.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie | Duration | Description |
---|---|---|
__cfruid | session | This cookie is set by the provider Cloudflare. This cookie is used for load balancing and for identifying trusted web traffic. |
__cfruid | session | This cookie is set by the provider Cloudflare. This cookie is used for load balancing and for identifying trusted web traffic. |
__cfruid | session | This cookie is set by the provider Cloudflare. This cookie is used for load balancing and for identifying trusted web traffic. |
_biz_flagsA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_pendingA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_sid | 30 minutes | This cookie is set by Bizible, to store the user's session id. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_ga_1ECB5XX5W0 | 2 years | This cookie is installed by Google Analytics. |
_ga_1ECB5XX5W0 | 2 years | This cookie is installed by Google Analytics. |
_ga_1ECB5XX5W0 | 2 years | This cookie is installed by Google Analytics. |
_gat_UA-87760032-2 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_gat_UA-87760032-2 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_gat_UA-87760032-2 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
ARRAffinity | This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App. | |
ARRAffinity | 1 year | This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App. |
ARRAffinity | 1 year | This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App. |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
JSESSIONID | session | Used by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests. |
JSESSIONID | session | Used by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests. |
JSESSIONID | session | Used by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
_biz_nA | 1 year | This cookie, set by Bizible, is a sequence number that Bizible includes for all requests, for internal diagnostics purposes. |
_biz_uid | 1 year | This cookie is set by Bizible, to store user id on the current domain. |
bcookie | 2 years | This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page. |
bcookie | 2 years | This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page. |
bcookie | 2 years | This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
language | This cookie is used to store the language preference of the user. | |
language | 1 year | This cookie is used to store the language preference of the user. |
language | 1 year | This cookie is used to store the language preference of the user. |
lidc | 1 day | This cookie is set by LinkedIn and used for routing. |
lidc | 1 day | This cookie is set by LinkedIn and used for routing. |
lidc | 1 day | This cookie is set by LinkedIn and used for routing. |
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie | Duration | Description |
---|---|---|
_BUID | 1 year | This cookie is used to store a universal user ID to identify the same user across multiple clients' domains. |
_BUID | 1 year | This cookie is used to store a universal user ID to identify the same user across multiple clients' domains. |
_BUID | 1 year | This cookie is used to store a universal user ID to identify the same user across multiple clients' domains. |
_gcl_au | 3 months | This cookie is used by Google Analytics to understand user interaction with the website. |
_gcl_au | 3 months | This cookie is used by Google Analytics to understand user interaction with the website. |
_gcl_au | 3 months | This cookie is used by Google Analytics to understand user interaction with the website. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 2 years | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_hjAbsoluteSessionInProgress | 30 minutes | No description available. |
_hjAbsoluteSessionInProgress | 30 minutes | No description available. |
_hjAbsoluteSessionInProgress | 30 minutes | No description available. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjIncludedInPageviewSample | 2 minutes | No description available. |
_hjIncludedInPageviewSample | 2 minutes | No description available. |
_hjIncludedInPageviewSample | 2 minutes | No description available. |
_hjIncludedInSessionSample | 2 minutes | No description available. |
_hjIncludedInSessionSample | 2 minutes | No description available. |
_hjIncludedInSessionSample | 2 minutes | No description available. |
_hjTLDTest | session | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
_ym_d | 1 year | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to store the date of the users first site session. |
_ym_d | 1 year | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to store the date of the users first site session. |
_ym_d | 1 year | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to store the date of the users first site session. |
_ym_isad | 20 hours | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to collect information about the user like his characteristics, behaviour on page and targeted actions. |
_ym_isad | 20 hours | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to collect information about the user like his characteristics, behaviour on page and targeted actions. |
_ym_isad | 20 hours | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to collect information about the user like his characteristics, behaviour on page and targeted actions. |
_ym_uid | 1 year | This cookie is by Yandex.Metrica. This cookie is used to set a unique ID to the visitor and to collect information about how visitor use the website. Thus it help to track the user and the collected informationn is used to improve the site. |
_ym_uid | 1 year | This cookie is by Yandex.Metrica. This cookie is used to set a unique ID to the visitor and to collect information about how visitor use the website. Thus it help to track the user and the collected informationn is used to improve the site. |
_ym_uid | 1 year | This cookie is by Yandex.Metrica. This cookie is used to set a unique ID to the visitor and to collect information about how visitor use the website. Thus it help to track the user and the collected informationn is used to improve the site. |
attribution_user_id | 1 year | This cookie is set by Typeform for usage statistics and is used in context with the website's pop-up questionnaires and messengering. |
browser_id | 5 years | This cookie is used for identifying the visitor browser on re-visit to the website. |
CONSENT | 16 years 5 months 12 days 10 hours | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
CONSENT | 16 years 5 months 12 days 10 hours | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
CONSENT | 16 years 5 months 12 days 10 hours | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
sid | 1 year | The sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time. |
uid | 1 year | This is a Google UserID cookie that tracks users across various website segments. |
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |
anj | 3 months | No description available. |
anj | 3 months | No description available. |
anj | 3 months | No description available. |
ANONCHK | 10 minutes | The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well. |
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
i | 10 years | The purpose of the cookie is not known yet. |
i | 10 years | The purpose of the cookie is not known yet. |
i | 10 years | The purpose of the cookie is not known yet. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
MUID | 1 year 24 days | Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking. |
MUID | 1 year 24 days | Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking. |
MUID | 1 year 24 days | Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking. |
NID | 6 months | This cookie is used to a profile based on user's interest and display personalized ads to the users. |
NID | 6 months | This cookie is used to a profile based on user's interest and display personalized ads to the users. |
NID | 6 months | This cookie is used to a profile based on user's interest and display personalized ads to the users. |
personalization_id | 2 years | This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting. |
personalization_id | 2 years | This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting. |
personalization_id | 2 years | This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
uuid2 | 3 months | This cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements. |
uuid2 | 3 months | This cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements. |
uuid2 | 3 months | This cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | No description available. |
_clck | 1 year | No description |
_clsk | 1 day | No description |
_hjSession_1646283 | 30 minutes | No description |
_hjSessionUser_1646283 | 1 year | No description |
_uetvid | 1 year 24 days | No description available. |
_uetvid | 1 year 24 days | No description available. |
_uetvid | 1 year 24 days | No description available. |
6suuid | 2 years | No description available. |
AnalyticsSyncHistory | 1 month | No description |
AnalyticsSyncHistory | 1 month | No description |
AnalyticsSyncHistory | 1 month | No description |
ARRAffinitySameSite | No description available. | |
ARRAffinitySameSite | 1 year | No description available. |
ARRAffinitySameSite | 1 year | No description available. |
bEkAYwpdRGcM | 1 day | No description |
bEkAYwpdRGcM | 1 day | No description |
bEkAYwpdRGcM | 1 day | No description |
BIGipServer~magenta~mag-c-http-http-xhttpd-http-xhttpd-http-80 | session | No description |
DCMpagecount | session | No description |
DCMpagecount | session | No description |
DCMpagecount | session | No description |
debug | never | No description available. |
gaCookie | 2 years | No description available. |
gaCookie_gid | 1 day | No description available. |
LEAfgqMGWpwUs | 1 day | No description |
LEAfgqMGWpwUs | 1 day | No description |
LEAfgqMGWpwUs | 1 day | No description |
li_gc | 2 years | No description |
li_gc | 2 years | No description |
li_gc | 2 years | No description |
lpv413292 | 30 minutes | No description |
lpv413292 | 30 minutes | No description |
lpv413292 | 30 minutes | No description |
m | 2 years | No description available. |
metrika_enabled | session | No description available. |
metrika_enabled | session | No description available. |
metrika_enabled | session | No description available. |
muc_ads | 2 years | No description |
SM | session | No description available. |
STYXKEY_formcomplete | 9 months 26 days | No description |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |
vary | 1 month | No description |
visitor_id413292 | 10 years | No description |
visitor_id413292 | 10 years | No description |
visitor_id413292 | 10 years | No description |
visitor_id413292-hash | 10 years | No description |
visitor_id413292-hash | 10 years | No description |
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie | Duration | Description |
---|---|---|
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |