Customer Security Explanation (FTC v. Wyndham Worldwide Corp.)¶
Use this to explain a security topic or incident to customers in clear, non-technical language; supports notification obligations and trust.
Purpose¶
This explanation translates technical and legal context from FTC v. Wyndham Worldwide Corp. into clear customer-facing language, focusing on what happened, what protections are in place, and what customers should do. It supports transparent communication while remaining aligned with counsel-reviewed facts.
Hallucinated writing examples¶
Scenario: In an illustrative period following the Third Circuit Wyndham decision and the stipulated injunction (time), the Security Director (role) prepares a customer security explanation (type) for leadership stakeholders (audience).
CUSTOMER NOTICE — DATA SECURITY INCIDENT
What Happened: Prior incidents involved unauthorized access in environments associated with payment-card data. Wyndham has implemented remediation and governance measures in response to legal and regulatory proceedings.
What Information Was Involved: Potentially affected information related to payment-card transaction contexts described in prior disclosures. Wyndham continues customer support through official communication channels.
What We Are Doing: We are strengthening connectivity governance, access controls, monitoring, and assessment-driven remediation across relevant systems.
What You Can Do: Monitor account statements, report suspicious activity, and rely on official Wyndham channels for updates. Additional support information is available at [URL].
Document-type guide: Customer Security Explanation
Writing tips: Writing best practices — Customer Security Explanation