P6: Insufficient Deletion of User Data

P6: Insufficient Deletion of User Data

The delete button removed one copy out of six.

What Is P6: Insufficient Deletion of User Data?

Most delete buttons remove the main database row and nothing else. You'll trace one deletion across a data map and find the copies it never reached: analytics, search, request logs, a CRM vendor and a nightly backup. Then a restore brings the account back and the vendor emails the customer. You'll fan the erasure out to every system, confirm the vendor's delete, tombstone the id for restores, and prove it with a database check and a restore drill.

What You'll Learn in P6: Insufficient Deletion of User Data

P6: Insufficient Deletion of User Data — Training Steps

  1. Delete the Account

    This morning Nadia Okafor, a Pellora customer, deleted her account from the Pellora app. Alice owns privacy engineering, and she wants to know what that button really does. Her staging phone runs the same app build against a staging copy of Nadia's account, so she can walk the exact flow Nadia used.

  2. Open Account & Privacy

    The Account & privacy page holds Nadia's details, her consent record and the Delete account card.

  3. Press Delete

    Deleting an account is two taps: Delete my account, then Delete in the confirmation. The app promises the account and its data are gone.

  4. Open the Data Trail

    Pellora keeps a data map of every system that holds a customer. Nadia is the data subject here: the person the data is about, and the person the deletion is for. Alice opens the map for Nadia's customer record to watch the deletion travel.

  5. One System Cleared

    The deletion request reaches Pellora's production database and the customer row goes. The counter at the top tells the rest of the story.

  6. Pellora's Own Copies

    Three of the remaining copies sit inside Pellora's own infrastructure. Nobody outside the company is involved, and nobody wired them to the delete button either.

  7. Copies Outside Pellora

    Two copies have left Pellora's systems. Hubwell is a processor, a vendor that handles customer data on Pellora's behalf, and it receives a nightly sync for marketing. Stowline keeps 35 days of database snapshots. Alice notes the gap for the platform team. The fix joins the backlog.

  8. The Restore

    A storage fault overnight forced the platform team to restore the production database from the nightly backup. The snapshot was taken before any deletion reached it.

  9. Nadia Writes In

    A message lands in the privacy team's inbox.

  10. Knowledge Check

Security Framework Coverage

OWASP Privacy Top 10

  • P6 Insufficient Deletion of User Data

OWASP ASVS

  • V14.2.7 General Data Protection

CWE

  • CWE-459 Incomplete Cleanup

CIS Controls

  • CIS 3 Data Protection

NIST CSF

  • PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
  • PR.DS Data Security

NICE Framework

  • DD-WRL-003 Secure Software Development
  • OG-WRL-008 Privacy Compliance

GDPR

  • Art. 17 Right to erasure ('right to be forgotten')
  • Art. 19 Notification obligation regarding rectification or erasure

CCPA/CPRA

  • 1798.105 Right to delete personal information