Understanding Logical Deletion and Data Compliance in Backend Services
The article explains how many backend services use logical deletion—simply flagging or masking user data instead of physically removing it—to appear compliant with standards like China's GB/T 35273, while highlighting risks such as continued e‑bike control, fraud detection challenges, and missed logout handling.
When a user deletes an account, many apps only mark the account as deleted (logical deletion) rather than physically removing data. This article describes a case where an e‑bike app still controls the vehicle after showing a “account deleted” message, illustrating typical backend practices.
It explains three common approaches: simply flagging the account, flagging plus data masking, and forgetting to log out the user. The discussion references Chinese standard GB/T 35273 , which defines deletion as making personal information unretrievable, and allows logical deletion to meet compliance.
The article also notes that physical deletion may cause issues for fraud detection and legal accountability.
Java Tech Enthusiast
Sharing computer programming language knowledge, focusing on Java fundamentals, data structures, related tools, Spring Cloud, IntelliJ IDEA... Book giveaways, red‑packet rewards and other perks await!
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.