Skip to content

Commit f8c25cb

Browse files
jim-counterclaude
andcommitted
feat: add explanatory boilerplate to admin deletions page
Describes the deletion lifecycle, grace period, anonymisation steps, DSN data persistence, and audit logging for admin context. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 0661c2b commit f8c25cb

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

  • apps/frontend/src/components/views/DeletionAdmin

apps/frontend/src/components/views/DeletionAdmin/index.tsx

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,8 +82,19 @@ export const DeletionAdmin = () => {
8282

8383
return (
8484
<div className='flex flex-col gap-6 p-2'>
85-
<div className='flex items-center justify-between'>
85+
<div>
8686
<h1 className='text-2xl font-bold'>Account Deletions</h1>
87+
<p className='mt-2 text-sm text-gray-600 dark:text-gray-400'>
88+
Users may request account deletion for GDPR/CCPA compliance. Once
89+
requested, a 30-day grace period begins during which the user can
90+
cancel. After the grace period, a background worker anonymises
91+
their data: object ownership is soft-deleted, purchased credits and
92+
pending intents are expired, and PII (username, avatar) is replaced
93+
with a hashed placeholder. Data already stored on the DSN cannot be
94+
removed. All actions are recorded in the audit log.
95+
</p>
96+
</div>
97+
<div className='flex items-center justify-between'>
8798
<div className='flex items-center gap-2'>
8899
<label
89100
htmlFor='deletion-status-filter'

0 commit comments

Comments
 (0)