ISC · Security and Confidentiality and Privacy · 9 practice questions
CPA Privacy Retention: Delete When Your Notice Says
Keeping personal information beyond the privacy notice's deletion deadline is a privacy failure unless law requires longer retention. Below: follow a retailer's closed-account records from account closure through a missed deadline and correction.
Try one first
Hint
Separate the obligation to protect information from unauthorized access from the obligation to handle personal information according to stated retention and disposal commitments.
Answer B. Privacy concerns include whether personal information is collected, used, retained, and disposed of according to the entity's stated commitments. The company promised deletion within 90 days but retained closed-account data for more than a year, which supports a privacy (retention/disposal) deficiency. The controls described (encryption and restricted access) and the absence of unauthorized disclosure mean the facts given do not by themselves demonstrate a confidentiality failure.
Why not A: This is tempting because personal data are involved, but confidentiality specifically concerns protection from unauthorized access or disclosure. Here the data were encrypted and access was limited, so the evidence points to noncompliance with retention commitments (privacy) rather than a confidentiality failure.
Why not C: While plausible at first glance, privacy and confidentiality are distinct. The retention beyond the stated 90 days clearly supports a privacy issue; however, the described protections argue against a confidentiality deficiency based on the information given.
Why not D: Incorrect because privacy obligations include adherence to stated retention and disposal commitments; a breach or disclosure is not required for a privacy deficiency. Encryption and lack of a breach do not excuse failure to follow the privacy notice.
The timeline
- Day 0A customer closes an online retail account.
The retailer's privacy notice promises deletion of closed-account personal information within 90 days unless law requires longer retention. No legal requirement applies.
- Day 90The promised deletion deadline arrives.
The retailer must delete the closed-account records by this deadline. Keeping them beyond it violates the privacy retention commitment.
- More than one year after closureInternal audit finds the records still retained.
Names, addresses, email addresses, and birth dates remain encrypted and accessible only to authorized personnel. No unauthorized access or disclosure occurred. The supported finding is a privacy retention deficiency.
- After the reviewRemove the overdue records and correct the deletion process.
Secure disposal addresses the missed privacy promise. Stronger encryption alone would leave the over-retention unresolved.
Key points
- Remember: encryption protects retained data, but it does not make keeping that data past the promised deadline acceptable.
- Account closure starts this retailer's retention clock, not the date internal audit discovers the records.
- The notice permits legally required retention, but no legal requirement applies here.
How the exam traps you
- No deficiency exists because the records stayed encrypted and no breach occurred. The missed deletion deadline violates the privacy commitment even without unauthorized access.
- Both privacy and confidentiality automatically failed because the retained records contain personal information. Over-retention establishes the privacy failure. These facts alone do not establish a confidentiality failure.
Question 2
Hint
Focus on privacy as more than just protecting data from unauthorized access. Ask whether the organization still needs this personal information for the purpose it originally disclosed.
Answer C. Privacy principles require that personal data be collected, used, and retained only for the stated purpose. Here the DOB was collected solely for age verification and there is no legal or business need to keep it, so the appropriate treatment is secure deletion or irreversible de-identification. This approach minimizes ongoing privacy risk and aligns retention with purpose.
Why not A: This is tempting because encryption and access controls protect confidentiality, but those safeguards do not justify indefinite retention. Data minimization and purpose limitation require disposal or de-identification once the stated purpose is satisfied.
Why not B: Voluntary provision of data does not override retention limits tied to the original purpose. If the only purpose was age verification and no further need exists, keeping the full DOB in the master file is not appropriate.
Why not D: Sharing for analytics would expand processing beyond the stated purpose. Unless the data are truly de-identified or a valid legal basis and notice/consent exist, repurposing the DOB for analytics is not consistent with the stem.
Question 3
Hint
Separate confidentiality safeguards from privacy commitments about permitted purpose and retention.
Answer C. The privacy notice limits both the purpose for which the images were collected (identity verification) and their retention period (deleted 30 days after approval or denial). Encryption and limited internal access protect confidentiality but do not authorize a secondary use or extended retention that conflicts with the lender's stated commitment. Because no legal exception applies, the appropriate response is to stop the proposed training use, contain access to reduce risk, and securely dispose of the images in accordance with the notice.
Why not A: This is tempting because strong confidentiality controls exist, but it is wrong: privacy commitments govern permitted purpose and retention. Internal access controls don't authorize a new operational use or cure retention that exceeded the stated period.
Why not B: Updating the notice prospectively does not justify data already retained in violation of the existing retention commitment. The organization should correct the retention failure and stop any incompatible secondary use now rather than relying on a future notice change.
Why not D: This correctly rejects the proposed secondary use but is still wrong because it leaves improper over-retention unaddressed. Promised deletion is the controlling commitment and possible future usefulness is not a valid basis to retain the images when no exception applies.
Question 4
Hint
Distinguish unauthorized access or disclosure (confidentiality) from repurposing or retaining data beyond what the privacy notice permits (privacy).
Answer D. Privacy concerns whether the organization honored its commitments about collection, permitted uses, retention, and disposal of personal information. The privacy notice limited use to underwriting/fraud screening and required deletion of declined-applicant data within 90 days; copying those SSNs and income documents and keeping them for 18 months to support marketing is repurposing and excessive retention contrary to the notice. Encryption and logs address confidentiality (protection against unauthorized access) but do not justify repurposing or prolonged retention, so this is primarily a privacy exception.
Why not A: This scenario primarily indicates an access-control issue (excess privileges after a role change), which is a confidentiality concern because it risks unauthorized access. Because the access occurred within the promised retention period and there is no evidence of repurposing or extended retention, it does not primarily show a privacy-use/retention violation.
Why not B: This describes an unauthorized disclosure to bystanders (improper exposure of information), which is primarily a confidentiality breach rather than a privacy-use/retention violation. The core issue is failure to prevent disclosure, not misuse or extended retention contrary to the privacy notice.
Why not C: Authorized users accessed the files by an approved secure method and the paper copies were promptly and properly disposed of, so this does not show repurposing or excessive retention under the privacy notice. It also does not describe an unauthorized disclosure, so it is not clearly a confidentiality exception either.
Question 5
Hint
Decide whether the core problem is how data is being collected and retained versus who can access data after collection.
Answer B. The primary deficiency is that the app's collection, permitted uses, and retention conflict with the company's published privacy commitment. The most direct remediation is to change the app's behavior (stop continuous background collection), obtain affirmative user consent for any secondary analytics use, and enforce the promised 24‑hour deletion. Technical controls and governance improvements are helpful but do not by themselves stop improper collection or excessive retention.
Why not A: This is tempting because aggregated analytics and discarding raw traces reduce identifiability and stored detail. However, it still relies on collecting raw, fine‑grained location data before aggregation and does not prevent continuous background collection or guarantee timely deletion, so it fails to address the root over‑collection/over‑retention problem.
Why not C: Suspending analytics and doing a PIA is a prudent, administrative response and pauses the secondary use while the issue is assessed. But it is temporary and procedural, this approach does not directly reconfigure the app to stop continuous collection or immediately enforce the promised deletion, so it is not the most direct fix.
Why not D: Elevating and monitoring privacy violations improves detection and governance and helps ensure remediation when issues are found. It is nonetheless reactive: these changes do not themselves stop the app from collecting and retaining data contrary to the privacy commitment and therefore do not most directly remedy the defect.
Question 6
Hint
Distinguish protections against who can see data (confidentiality) from rules about what the data may be used for (privacy/purpose limitation).
Answer C. Privacy includes restrictions on collection, use, and retention consistent with a privacy notice, not just protections against disclosure. The notice limited birthdates to age verification and deletion thereafter unless retention was required; marketing's later use for targeted advertising without consent or authorization is inconsistent with that stated purpose. Therefore the core problem is a privacy issue (purpose mismatch), even though encryption and access controls addressed confidentiality.
Why not A: This distractor tempts because internal handling and access controls suggest confidentiality was preserved. It fails because privacy also governs permissible uses of personal data; internal non‑disclosure does not authorize a use that contradicts the company's stated purpose without consent or other authorization.
Why not B: This is tempting because birthdates are identifying and protecting them matters. It is incorrect because the stem describes confidentiality controls; the dispute arises from an improper purpose (using retained birthdates for marketing), which is a privacy (purpose/usage) concern rather than solely a confidentiality failure.
Why not D: This distractor appeals by invoking technical safeguards and deletion to reduce harm. It fails because encryption or later deletion do not retroactively authorize a use that contradicts the stated privacy purpose; the unauthorized marketing use itself raises a privacy issue even if security measures and deletion mitigate risk.
Question 7
Hint
Treat privacy and confidentiality separately: privacy includes promised handling across the data lifecycle (including retention/disposal); confidentiality concerns whether client-designated materials were limited to authorized client users (client-level authorization), not just platform authentication.
Answer D. The provider's public privacy notice promised deletion within 90 days; retaining SSNs and addresses in production for 14 months without a legal basis violated that privacy commitment because retention and disposal are covered by privacy promises. Separately, client contracts required uploaded strategic-planning files to be treated as confidential; sending Client A's attachment to a user employed by Client B who lacked client-level authorization was an unauthorized disclosure and therefore violated the confidentiality commitment. Platform authentication alone does not substitute for client-level authorization under a client confidentiality obligation.
Why not A: This is tempting because platform authentication suggests legitimate access, but confidentiality commitments turn on whether the recipient was authorized to view that client's confidential file. An authenticated user from another client who lacks client-level authorization receiving Client A's file is an unauthorized disclosure and breaches the confidentiality commitment.
Why not B: This is tempting because the disclosure is a clear confidentiality problem, but it wrongly assumes privacy is implicated only by unauthorized access. Privacy commitments commonly include lifecycle obligations (collection, use, retention, disposal); keeping applicant PII beyond the promised retention period without legal basis itself violates the privacy notice.
Why not C: This is tempting for those who focus on misuse or harm thresholds, but the question asks whether the provider's stated commitments were met. Both retention beyond a stated deletion period and disclosure to a user without client-level authorization can violate contractual or policy commitments regardless of subsequent misuse or demonstrable harm.
Question 8
Hint
Decide whether the facts describe an exposure/unauthorized-access event or a deviation from stated retention/disposal commitments.
Answer B. Privacy includes collection, use, retention, and disposal of personal information in accordance with an entity's stated policies. Northbay's retention of rejected applicants' Social Security numbers past the posted 60-day disposal period is a failure of its retention/disposal commitment and therefore a privacy issue. Because the facts explicitly state there was no unauthorized access or disclosure, there is no direct evidence of a confidentiality breach.
Why not A: This is tempting because Social Security numbers are highly sensitive and confidentiality concerns focus on preventing exposure. It fails here because the scenario shows no unauthorized access or disclosure and instead demonstrates noncompliance with a retention/disposal promise, which is a privacy (policy/retention) issue rather than a confidentiality breach.
Why not C: This choice is plausible since retaining data contrary to policy can raise both kinds of concerns. It is incorrect because the question asks which issue is most directly raised; the facts show a retention/disposal policy violation without any evidence of a confidentiality failure, so privacy is the primary issue.
Why not D: This distractor appeals to the mistaken notion that privacy issues only arise from breaches. It fails because privacy also concerns whether an organization follows its announced collection, retention, and disposal practices; retaining data longer than stated can itself violate privacy even absent a breach.
Question 9
Hint
Focus on the difference between protecting data that should be kept and deciding whether the data should still be kept at all.
Answer C. Privacy involves limiting collection, use, retention, and disposal of personal data to what is necessary. Because the birth dates are no longer needed, deleting them (including backups) most directly reduces privacy risk by implementing data minimization and appropriate disposal. The other choices strengthen confidentiality but do not address unnecessary retention.
Why not A: Encryption is a strong measure to protect data confidentiality (prevent unauthorized disclosure), but it does not resolve the privacy issue of keeping personal information longer than necessary.
Why not B: Restricting access supports confidentiality through least-privilege, yet if the data is no longer necessary, merely limiting access does not eliminate the privacy risk of unnecessary retention.
Why not D: Confidentiality agreements help govern proper handling and deter misuse, but they are governance measures that do not address the privacy concern of retaining data that should be disposed of.
Common questions
Is retaining customer data too long a privacy or confidentiality issue?
Here, it is a privacy issue because the retailer missed its promised deletion deadline. Encryption, restricted access, and no unauthorized disclosure do not establish a confidentiality failure.
Does encryption allow a company to keep personal data past its privacy notice deadline?
No. Encryption protects the data but does not extend the promised retention period.
What should a company do after missing its privacy notice deletion deadline?
Identify and securely dispose of the overdue records when no legal retention requirement applies. Correct the deletion process so future records are removed within the promised period.
Watch it solved
A full CPA ISC task-based simulation on Confidentiality and privacy, worked step by step.
Data Classification & Privacy Compliance | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Confidentiality and privacy
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.