Does Named Insured accept credit cards or collect Personally Identifiable Information (PII) or Protected Health Information (PHI) from its customers?
This is application question 4 of 8 on the Coalition Coalition Cyber Policy Application Questions. It is a control question and reaches 9 controls. The wording is the carrier's, quoted verbatim.
Held from the Questions in a Coalition Cyber Policy Application (read 2026-10-11), jurisdiction United States. All Coalition questions.
Answer options on this form: No / Yes.
Facets: control: Does Named Insured accept credit cards or collect Personally Identifiable Information (PII) or Protected Health Information (PHI) from its customers?; population: Personally Identifiable Information
What this question reaches
- ISO 27001:2022 A.5.34: Privacy and protection of personal identifiable information (PII) (direct)
Establishes the privacy practice or notice asked about; it does not establish compliance with every applicable privacy law.
Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared - ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements (supporting)
Establishes the privacy practice or notice asked about; it does not establish compliance with every applicable privacy law.
Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared - ISO 27001:2022 A.8.24: Use of cryptography (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - SOC 2 P1.1: Privacy notice to data subjects (direct)
Establishes the privacy practice or notice asked about; it does not establish compliance with every applicable privacy law.
Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared - SOC 2 P3.1: Collecting personal information consistent with objectives (supporting)
Establishes the privacy practice or notice asked about; it does not establish compliance with every applicable privacy law.
Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared - NIST CSF 2.0 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed (direct)
Establishes the privacy practice or notice asked about; it does not establish compliance with every applicable privacy law.
Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared - NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected (supporting)
Establishes the privacy practice or notice asked about; it does not establish compliance with every applicable privacy law.
Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared - PCI DSS 4.0 Requirement 3: Protect Stored Account Data (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment
Subject: privacy. Owner a broker routes it to: Privacy and records owner.
The same control on other applications
Hiscox Q9, Hiscox Q10, Hiscox Q11, Hiscox Q12, Hiscox Q14, Hiscox Q47, Great American Insurance Group Q5, Great American Insurance Group Q26, Great American Insurance Group Q27, Great American Insurance Group Q28, Tokio Marine HCC Q3, AXIS Insurance Q2.
Map your own answers in the tool. See the Coalition page, the controls index, the island and the answers.