
Last reviewed: August 2026 | Reading time: 14 minutes
HIPAA vendor management is the programme a covered entity runs to verify, monitor and document the security posture of every Business Associate (BA) that handles Protected Health Information (PHI) on its behalf, for the full life of the relationship. It is required by the Security Rule’s risk management standard at 45 CFR 164.308(a)(1).
It is a separate obligation from executing a Business Associate Agreement (BAA). The BAA is a contract required by the Privacy Rule at 45 CFR 164.504(e). That requirement is met the day a compliant contract is signed. The vendor management requirement is never finished.
Most healthcare compliance programmes are built around the first obligation and assume it covers the second. It does not, and the gap between the two is where nearly every significant Office for Civil Rights (OCR) finding on third-party PHI risk originates. This page covers the ongoing programme. For the point-in-time evaluation of an individual vendor, see the HIPAA vendor risk assessment guide. For the contract itself, see the HIPAA Business Associate Agreement guide.
A signed BAA proves one thing: that a legal obligation now exists. It proves the vendor has agreed, on paper, to implement safeguards, notify you of breaches within 60 days, pass HIPAA obligations to its subcontractors and return or destroy PHI at termination. It proves nothing about whether any of that is happening.
This distinction decides penalty exposure. Consider what each document in a typical vendor file actually evidences.
| What sits in your vendor file | What it proves | What OCR asks for instead |
|---|---|---|
| Signed BAA | The legal obligation exists. 45 CFR 164.504(e) is satisfied. | Evidence of what you did between the signature date and the incident date. |
| Completed security questionnaire | What the vendor chose to tell you. | Independent evidence the stated safeguards exist: audit reports, control evidence, screening results. |
| SOC 2 logo on the vendor’s website | A report exists somewhere. | The SOC 2 Type II report itself, its scope, its exceptions and your documented review of it. |
| Subcontractor clause in the BAA | The vendor promised to bind its own subcontractors. | Confirmation those subcontractor BAAs were actually executed. |
| Annual review calendar entry | A review was scheduled. | Monitoring that detects risk events between reviews, not only at the next one. |
Here is the part most programmes miss: a signed BAA raises your culpability floor. OCR’s penalty tiers escalate with what you knew. An executed BAA is documentary proof you knew the requirement existed. A safeguard gap discovered later is therefore very hard to argue into the “unknowing” tier. The document that satisfied one rule becomes the exhibit that aggravates the other.
An attestation is a self-reported claim: a questionnaire answer, a signed representation, a checkbox. OCR’s position, confirmed repeatedly in enforcement resolutions, is that self-reported claims do not satisfy the risk management standard. The reason is structural, and it has three parts.
Attestations describe intent, not state. A vendor that answers “yes, we enforce MFA” is describing its policy. Whether MFA was enforced on the specific remote access portal an attacker used is a question of state, and questionnaires cannot see state.
Attestations are frozen at a date. A questionnaire completed in January says nothing about the vendor in September. Risk events, a security researcher disclosure, an enforcement action, a financial collapse, a change of ownership, arrive on their own schedule, not on your review calendar.
Attestations cannot report what the vendor does not know or will not say. A BA’s undisclosed cloud dependency, an offshore subcontractor handling PHI, or adverse media in a non-English source will not appear in a self-assessment. Independent screening is the only way this information reaches you. When Neotas analysts rebuild a Business Associate inventory from procurement records, accounts payable data and IT access logs, the true count typically comes out 20 to 40 per cent higher than the compliance register shows. Every one of those unlisted relationships is an unattested, unmonitored PHI exposure.
A Neotas BAA programme gap review compares what your vendor files claim against what independent evidence shows: safeguard verification, adverse media and enforcement screening, and the documentation record OCR requests first. Findings within 5 working days.
Two provisions, two separate penalties. The Privacy Rule at 45 CFR 164.504(e) requires the BAA itself. The Security Rule at 45 CFR 164.308(a)(1) requires ongoing risk management for as long as the relationship lasts. OCR investigates both and can penalise both in the same enforcement action, which is why a breach at one vendor routinely produces two findings against the covered entity: one for the incident, one for the programme that failed to see it coming.
The regulatory direction of travel makes the second obligation heavier, not lighter. HHS published a proposed update to the Security Rule on 6 January 2025 (90 FR 898) that would firm up verification and monitoring expectations for electronic PHI. Its final-rule timing has slipped, but the current Security Rule remains fully in force, and OCR’s audit programme operates today regardless of when the update lands. Waiting for the final rule before building verification is a bet that OCR does not knock first.
Penalty exposure escalates by culpability. According to HHS OCR enforcement data, civil monetary penalties for wilful neglect left uncorrected reach $50,000 per violation with a $1.9 million annual cap per violation category, and figures adjust for inflation each year under 45 CFR Part 102. A vendor management gap across multiple relationships is exactly the pattern the top tier describes: a known requirement, systemically unmet, with no corrective action.
Vendor blind spots are PHI-handling relationships that exist operationally but sit outside the compliance programme’s view. Four recur in almost every inventory rebuild.
Tools adopted outside compliance. Cloud productivity platforms, analytics tools and AI applications onboarded by IT or clinical teams, with PHI use enabled before anyone confirmed a BAA covered it. The violation runs from the first day PHI was shared, not the day the gap is found.
The subcontractor layer. The HITECH Act of 2009 extended BAA obligations to your vendors’ own subcontractors, yet few covered entities have ever confirmed those downstream BAAs exist. The clause in your contract is not the confirmation. Independent, analyst-led investigation of a BA’s dependencies is usually the only way to see this layer, because it is not information any counterparty volunteers. Neotas covers this in the OSINT tools and techniques guide.
Analytics and data vendors under contract pressure. HIPAA changes what an analytics vendor contract must contain: a BAA before any patient-level data flows, minimum-necessary access scoping and de-identification terms that track the regulatory definitions. Shortlists in healthcare routinely exclude vendors that cannot sign a BAA at all.
Terminated vendors with live access. Offboarding that ends the invoice but not the access. HIPAA expects documented destruction evidence: method, scope, date and the named individual who confirmed it. A one-line deletion email is a blind spot filed as a record.
The February 2024 ransomware attack on Change Healthcare exposed the health data of roughly one in three Americans, according to the HHS statement on the incident. It is the largest healthcare data breach in US history, and it is the cleanest natural experiment on attestation ever run.
Every affected covered entity had a signed BAA with Change Healthcare. Most ran annual questionnaire reviews. The contracts were real, the attestations were on file, and none of it surfaced the condition that mattered before the attack did. Security researchers had published warnings about the infrastructure in the months before February 2024. A monitoring programme watching for security disclosures would have seen them. An annual questionnaire cycle structurally could not.
The uncomfortable arithmetic: the covered entities with the most complete paperwork and the covered entities with none had identical outcomes in this breach. Paper does not change breach probability. Verification and monitoring change whether you see risk in time to act, and whether OCR finds a programme or a filing cabinet when it investigates.
Verification replaces “the vendor said so” with “we checked”. The sequence below is the order that reduces exposure fastest.
The gap between 45 CFR 164.504(e) and 164.308(a)(1): the 8 required BAA provisions with the most common drafting deficiency for each, the enforceable-verb test, a 5-level programme maturity scale, and the fourth-party chain Change Healthcare exposed. Written for CPOs, CISOs, General Counsel and CCOs. Use it to brief your board before OCR asks the same questions.
A HIPAA vendor management policy turns the obligations above into assigned, repeatable work. At minimum it should define: the BA inventory and its single accountable owner; the tiering criteria; verification requirements by tier, stating what evidence is accepted and what is not; monitoring scope and alert-handling responsibilities; subcontractor confirmation requirements; offboarding and PHI destruction evidence standards; and the board reporting cadence with four numbers, coverage, verification, monitoring and remediation. The TPRM policy guide sets out the full document structure, and the complete TPRM guide shows where HIPAA obligations sit inside the wider programme.
One design decision matters more than the rest: the policy must state that questionnaires inform tiering but never substitute for verification on the critical tier. Write that sentence into the policy and most of the failure modes below lose their footing.
These are the patterns Neotas analysts and OCR investigators see most often, across health systems of every size.
1. Accepting the badge instead of the report. A SOC 2 seal on a website is marketing. The Type II report, its scope and its exceptions are the evidence. Programmes that never open the report routinely miss carve-outs that exclude the exact systems processing their PHI.
2. Reviewing on the renewal date instead of the risk event. Calendars drive most programmes. Risk does not read calendars. A vendor’s enforcement action in March waits nine months to be noticed by a December review.
3. Assuming a cloud BAA covers everything the platform does. Major cloud providers sign BAAs that cover specific in-scope services under specific configurations. PHI in an out-of-scope service or a misconfigured tenancy sits outside the agreement the file says you have.
4. Scoring questionnaires as if scores were findings. A 94 per cent questionnaire score measures the vendor’s form-filling, not its controls. Treating the score as assurance is how confident programmes arrive at breaches surprised.
5. Offboarding without destruction evidence. Residual PHI access with a former vendor is a live violation. The record must name method, scope, date and the responsible individual. The enhanced due diligence checklist includes the offboarding evidence standard.
Neotas is an intelligence-led third-party risk management provider, rated in the Chartis FCC50 as a leading financial crime compliance technology provider, serving healthcare organisations in the US as a primary market. For HIPAA vendor management specifically, Neotas closes the attestation gap in three ways.
Integrated enhanced due diligence. Independent verification of critical-tier Business Associates: adverse media screening across 200+ languages, corporate record and beneficial ownership research across 198M+ records, and analyst-led OSINT investigation that surfaces what questionnaires structurally cannot, including dependencies a vendor has not disclosed. Delivered through the healthcare TPRM platform.
Continuous monitoring between review cycles. Always-on screening of Business Associates across 40,000+ media sources in 100+ countries, with configurable alerting for adverse media, enforcement actions, sanctions designations and financial distress signals, so material changes reach you when they happen rather than at the next annual review.
Evidence storage and a full audit log. Every screening result, review decision and alert disposition is stored with a complete audit trail, so the documentation OCR requests first, what you did between the signature date and today, is producible on demand rather than reconstructed under investigation pressure.
Third-party risk management using OSINT
How OSINT-enhanced screening surfaced third-party risks that structured database checks and vendor self-reporting missed. [need: one specific outcome figure from the case study]
Third-party due diligence for partnership risks
Independent investigation of a prospective partner’s background ahead of contract, informing the go/no-go decision with evidence the partner had not volunteered. [need: outcome detail]
OSINT for enhanced due diligence
Enhanced due diligence combining open-source intelligence with analyst review to validate self-reported information for a regulated client. [need: outcome detail]
Supply chain risk: modern slavery detection
OSINT investigation into a supply chain surfaced labour-practice risks invisible to questionnaire-based supplier assessment, demonstrating the downstream-visibility method that applies equally to PHI subcontractor chains.
HIPAA vendor management is the ongoing programme of verifying, monitoring and documenting the safeguards of every Business Associate that handles PHI on your behalf. It is required by the Security Rule’s risk management standard at 45 CFR 164.308(a)(1) and continues for the life of each vendor relationship. It is separate from, and additional to, executing a BAA.
No. A signed BAA satisfies the Privacy Rule documentation requirement at 45 CFR 164.504(e). HIPAA also requires ongoing risk management under 45 CFR 164.308(a)(1), which means periodically verifying that the safeguards the BAA mandates actually exist. OCR investigates both requirements and penalises them separately.
It proves a legal obligation exists: the vendor has agreed to implement safeguards, notify you of breaches within 60 days under 45 CFR 164.410, bind its subcontractors and return or destroy PHI at termination. It proves nothing about whether those obligations are being met. That evidence has to come from verification and monitoring.
The four most common are: PHI-handling tools adopted by IT or clinical teams without a confirmed BAA; the subcontractor layer, where downstream BAAs required by HITECH were never confirmed; analytics and data vendors whose contracts lack HIPAA-specific terms; and terminated vendors with residual PHI access and no documented destruction evidence.
Any analytics vendor that accesses patient-level data is a Business Associate and must sign a BAA before data flows. Contracts should also scope access to the minimum necessary, define de-identification against the regulatory standard, and include breach notification and subcontractor obligations. Vendors that cannot sign a BAA are excluded from healthcare shortlists for PHI use cases.
Yes, if real PHI enters the sandbox. The BAA requirement follows the data, not the environment label. If the environment uses only fully de-identified or synthetic data meeting the HIPAA de-identification standard, a BAA is not required, but that de-identification claim itself should be verified rather than assumed.
A vendor risk assessment is a point-in-time evaluation of one vendor’s risk, typically at onboarding or renewal. Vendor management is the standing programme around it: inventory, tiering, verification, continuous monitoring, subcontractor confirmation, offboarding evidence and board reporting. Assessments are events inside the programme; the programme is what 164.308(a)(1) requires.
It is the Security Rule’s security management process standard. For vendor relationships it means assessing and managing the risks Business Associates pose to electronic PHI on an ongoing basis: verifying safeguards, monitoring for changes in risk, and documenting the programme. OCR’s enforcement position is that annual questionnaires alone do not meet the ongoing standard.
Review depth and frequency should follow risk tier. A common structure is annual review for all Business Associates, quarterly review for the critical tier, and continuous monitoring running between cycles so that material events, enforcement actions, breaches, financial distress, are detected when they occur rather than at the next scheduled review.
Yes. Under the HITECH Act, a subcontractor that creates, receives, maintains or transmits PHI for a Business Associate is itself a Business Associate, with direct HIPAA obligations. Your BAA must require the vendor to execute equivalent agreements downstream, in binding language, and your programme should confirm those agreements actually exist for critical-tier vendors.
Compounded exposure. The breach that triggered the investigation is assessed as one violation, and the missing risk management programme is assessed as a separate one. Because the executed BAA proves you knew the requirements, the programme gap is difficult to argue into the lower culpability tiers, where penalties are smaller.
An owned BA inventory, tiering criteria, verification standards by tier stating accepted evidence, continuous monitoring scope and alert handling, subcontractor confirmation requirements, offboarding and PHI destruction evidence standards, and board reporting covering coverage, verification, monitoring and remediation. It should state explicitly that questionnaires never substitute for verification on the critical tier.
No. Questionnaires are self-reported and frozen at a completion date, so they capture what a vendor claims at one moment. The ongoing standard at 45 CFR 164.308(a)(1) expects risk to be managed throughout the relationship, which requires independent verification of critical safeguards and monitoring that operates between review cycles.
A 30-minute conversation with a Neotas specialist will tell you where your programme stands: inventory completeness, verification depth, monitoring coverage and the evidence record. No commitment required.
The point-in-time evaluation this programme runs on: what vendor questionnaires fail to ask, how to structure an assessment that produces evidence rather than scores, and where assessments sit inside the wider management programme.
HIPAA Business Associate Agreement: 8 Required Provisions and Checklist
The contract side of the obligation: all eight provisions required by 45 CFR 164.504(e), the enforceable subcontractor language test, when a BAA is and is not required, and the 5-step programme audit.
Healthcare Vendor Risk Management: Complete TPRM Guide
The full healthcare programme: the 7-stage vendor lifecycle, 7 healthcare vendor categories, 6 risk domains, and how HIPAA, FDA and ESG obligations combine in one operating model.
Healthcare Supply Chain Risk: The 2026 Framework
How PHI and operational risk travel through healthcare supply chains, and the framework for managing concentration and downstream dependency risk across suppliers.
How Neotas conducts vendor due diligence beyond questionnaires: financial health, adverse media in 200+ languages, regulatory standing and beneficial ownership investigation for critical-tier Business Associates.
Enhanced Due Diligence: Platform and Methodology
When questionnaires and contracts are insufficient: how intelligence-led EDD surfaces the risks self-reporting structurally cannot detect, with direct application to healthcare vendor relationships.
Enhanced Due Diligence Checklist
The specific verification checks beyond BAA execution: safeguard evidence standards, subcontractor confirmation steps and the offboarding destruction-evidence record.
What a compliant third-party risk policy must contain, including the monitoring frequency and documentation obligations that satisfy HIPAA ongoing due diligence alongside DORA and OCC standards.
Third-Party Risk Management: Complete Guide
The foundational TPRM reference: lifecycle stages, regulatory requirements, risk categories and maturity model. The pillar this HIPAA vendor management page belongs to.
OSINT Tools and Techniques for Vendor Screening
How open-source intelligence validates self-reported vendor claims: adverse media research, beneficial ownership investigation and enforcement database screening in practice.
Most teams score themselves at level 3. Reviews find level 1. Score your BAA programme against the 5-level maturity scale inside the report, in about 10 minutes.
Neotas Enhanced Due Diligence covers 600Bn+ Archived web pages, 1.8Bn+ court records, 198M+ Corporate records, Global Social Media platforms, and more than 40,000 Media sources from over 100 countries to help you screen & manage risks.
Why a signed BAA raises your penalty exposure when safeguards go unverified, and the 3 decisions that fix it.
vendor risk assessment template
vendor risk assessment template xls
vendor risk assessment questionnaire template
vendor risk assessment template excel
vendor management risk assessment template
bank vendor risk assessment template
free vendor risk assessment template
vendor risk management assessment template
third-party vendor risk assessment template
thirdparty vendor risk assessment template
vendor risk assessment questionnaire template pdf
free vendor risk assessment questionnaire template
vendor risk assessment template equation
vendor risk assessment questionnaire template excel
it vendor risk assessment template excel
vendor risk assessment template pdf
third party vendor risk assessment template
vendor risk assessment template – excel
soc 2 vendor risk assessment template
vendor risk assessment report template
it vendor risk assessment template
free vendor risk assessment template xls
vendor risk assessment template free
vendor risk assessment template xls excel
vendor risk assessment software
customer and vendor risk assessment software
software for vendor risk assessment
compare vendor risk assessment software solutions
vendor risk assessment
vendor management risk assessment
vendor risk assessment software
vendor security risk assessment
vendor risk assessment tools
vendor risk assessment template
automated vendor risk assessment
vendor risk assessment process
3rd party vendor risk assessment
third party vendor risk assessment
customer and vendor risk assessment software
vendor risk assessment checklist
vendor risk assessment questionnaire
information security vendor risk assessment
vendor risk assessment report
vendor risk assessment matrix
third party vendor risk assessment example
risk assessment third party vendor
vendor risk assessment criteria
hipaa vendor risk assessment
vendor cyber risk assessment
vendor risk assessment for banks
vendor risk assessment example
what is vendor risk assessment
vendor risk assessment tool
vendor risk assessment template xls
risk assessment for vendor management
vendor risk assessment questionnaire pdf
nist vendor risk assessment questionnaire
vendor financial risk assessment
vendor risk assessment services
ai vendor risk assessment
what is a vendor risk assessment
vendor due diligence risk assessment
vendor risk assessment policy
how to perform vendor risk assessment
vendor risk assessment program
vendor risk assessment procedure
vendor risk assessment questionnaire template
vendor management risk assessment questionnaire
vendor management risk assessment matrix
vendor risk management assessment matrix
nist vendor risk assessment
vendor risk assessment template excel
vendor risk assessment framework
vendor information security risk assessment
vendor risk assessment servicenow
vendor management risk assessment template
bank vendor risk assessment template
free vendor risk assessment template
risk assessment vendor selection
health risk assessment vendor
healthcare vendor risk assessment
vendor risk assessment form
vendor risk assessment questionnare
vendor risk assessment questions
risk assessment vendor management
vendor risk management assessment template
vendor risk assessment jobs
bank vendor management risk assessment
risk assessment for vendor qualification
vendor risk assessment checklist xls
sample vendor risk assessment
compare vendor risk assessment tools using ai for public procurement contracts.
third-party vendor risk assessment
vendor risk assessment library
vendor risk assessment resume
vendor risk assessment definition
third-party vendor risk assessment template
thirdparty vendor risk assessment template
vendor management risk assessment sample
risk assessment thirdparty vendor
vendor cybersecurity risk assessment
continuous vendor risk assessment
third party vendor risk assessment questionnaire
vendor qualification risk assessment
vendor risk assessment pdf
third-party vendor risk assessment example
vendor risk assessment tools ai public procurement contracts
social media archive services this vendor can also provide risk assessment monitoring
vendor risk assessment best practices
thirdparty vendor risk assessment example
vendor risk assessment scorecard
vendor management risk assessment
vendor risk assessment report sample
vendor risk management assessment
vendor risk assessment audits
cbanc network vendor management risk assessment
vendor risk assessment, reasonable security
vra vendor risk assessment
vendor risk assessment tools tech vendor credibility
vendor risk assessment questionnaire template pdf
sample vendor risk assessment questionnaire
free vendor risk assessment questionnaire template
what is vendor risk assessment process?
vendor risk assessment template equation
vendor risk assessment (vra)
vendor risk assessment process steps
vendor risk assessment methodology
how to do a vendor risk assessment
vendor management risk assessment
risk assessment for vendor management
vendor management risk assessment questionnaire
vendor management risk assessment matrix
vendor risk management assessment matrix
vendor management risk assessment template
risk assessment vendor management
vendor risk management assessment template
bank vendor management risk assessment
vendor management risk assessment sample
vendor management risk assessment
vendor risk management assessment
network vendor management risk assessment
vendor risk management business risk assessment
vendor management risk assessment
risk assessment for vendor management
vendor management risk assessment questionnaire
vendor management risk assessment matrix
vendor risk management assessment matrix
vendor management risk assessment template
risk assessment vendor management
vendor risk management assessment template
bank vendor management risk assessment
vendor management risk assessment sample
vendor management risk assessment
vendor risk management assessment
network vendor management risk assessment
vendor risk management business risk assessment vendor management risk assessment
risk assessment for vendor management
vendor management risk assessment questionnaire
vendor management risk assessment matrix
vendor risk management assessment matrix
vendor management risk assessment template
risk assessment vendor management
vendor risk management assessment template
bank vendor management risk assessment
vendor management risk assessment sample
ffiec vendor management risk assessment
vendor risk management assessment
vendor management risk assessment
vendor risk management business risk assessment
vendor risk assessment
vendor management risk assessment
vendor risk assessment software
vendor security risk assessment
vendor risk assessment tools
vendor risk assessment template
automated vendor risk assessment
vendor risk assessment process
3rd party vendor risk assessment
third party vendor risk assessment
customer and vendor risk assessment software
vendor risk assessment checklist
vendor risk assessment questionnaire
information security vendor risk assessment
vendor risk assessment report
vendor risk assessment matrix
third party vendor risk assessment example
risk assessment third party vendor
vendor risk assessment criteria
hipaa vendor risk assessment
vendor cyber risk assessment
vendor risk assessment for banks
vendor risk assessment example
what is vendor risk assessment
vendor risk assessment tool
vendor risk assessment template xls
risk assessment for vendor management
vendor risk assessment questionnaire pdf
nist vendor risk assessment questionnaire
vendor financial risk assessment
vendor risk assessment services
ai vendor risk assessment
what is a vendor risk assessment
vendor due diligence risk assessment
vendor risk assessment policy
how to perform vendor risk assessment
vendor risk assessment program
vendor risk assessment procedure
vendor risk assessment questionnaire template
vendor management risk assessment questionnaire
vendor management risk assessment matrix
vendor risk management assessment matrix
nist vendor risk assessment
vendor risk assessment template excel
vendor risk assessment framework
vendor information security risk assessment
vendor risk assessment
vendor management risk assessment template
bank vendor risk assessment template
free vendor risk assessment template
An advanced Due Diligence Platform that leverages AI to join the dots between Social Media, Corporate Records, Adverse Media and Open Source Intelligence (OSINT).
Our platform offers the most advanced insights, so you can respond to risks immediately.
With insights spanning global jurisdictions, your business is never in the dark.
Whether you manage a small portfolio or a global enterprise, our platform adapts to your needs
Ready to Transform Your Third-Party Risk Approach?Â
| Cookie | Duration | Description |
|---|---|---|
| AWSALBTG | 7 days | AWS Application Load Balancer Cookie. Load Balancing Cookie: Used to encode information about the selected target group. |
| AWSALBTGCORS | 7 days | AWS Classic Load Balancer Cookie: Used to map the session to the instance. This cookie is identical to the original ELB cookie except for the attribute &SameSite=None; |
| 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-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-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| 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-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-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". |
| CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
| debug | never | Cookie used to debug code and website issues |
| shown | session | Session cookie to control number of times a pop up is shown. |
| 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. |
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| AnalyticsSyncHistory | 1 month | Used to store information about the time a sync took place with the lms_analytics cookie |
| bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
| bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
| lang | session | LinkedIn sets this cookie to remember a user's language setting. |
| lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
| UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
| Cookie | Duration | Description |
|---|---|---|
| li_gc | 2 years | Used to store consent of guests regarding the use of cookies for non-essential purposes |
| rl_anonymous_id | 1 year | Generates an unique anonymous Id to identify a user and attach to a subsequent event. |
| rl_user_id | 1 year | to store a unique user ID for the purpose of Marketing/Tracking |
| Cookie | Duration | Description |
|---|---|---|
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gat_gtag_UA_107495977_1 | 1 minute | Set by Google to distinguish users. |
| _gat_UA-107495977-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
| _gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| 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. |
| CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
| Cookie | Duration | Description |
|---|---|---|
| _fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
| fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
| YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
| yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| 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. |