Delete Data After Account Closure
Added 2026-10
Delete Data After Account Closure — Chinese original prompt
用户注销账号后，系统只把状态改成已注销，数据仍留在 [表数量] 张表里。请梳理一份删除路径：哪些数据必须物理删除、哪些可以匿名化保留、哪些因合规要求需要留存一定期限，并说明备份与日志里的副本怎么处理。输出：表与字段的处置清单、删除任务的执行方式、失败重试与审计记录。
Site original
Chinese original
Example
Sample input
用户注销后只改了状态位，个人信息还留在十几张表，梳理一条删除路径。
The output should include
- 标明必须物理删除与可匿名化的
- 合规留存项单列并说明期限
- 说明备份与日志里的副本怎么办
Replace these placeholders 1
Swap the bracketed parts for your own details before sending.
[表数量]
How to use
备份里的数据也要覆盖，否则「已删除」只是在前台看不见。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.