This is still the old unused V7.0.4 test route. It now saves account deletion requests into the real sb_account_deletion_requests queue. The current live Profile Settings URL is untouched.
sb_profiles fields for this signed-in user. Deletion requests write only to sb_account_deletion_requests. Real Auth deletion stays server-side through the Edge Function later.@username
RoleUsing old V7.0.4 test page first.
Supabase Auth state.
Current user row from sb_profiles.
Only profile text/avatar/banner URL fields.
Writes request row, not Auth deletion.
Magic links use shouldCreateUser:false to avoid public signup.
No account loaded yet.
These controls save locally as a draft preference payload and can be exported. They do not write unknown database columns.
Downloads profile/account summary without browser tokens or Supabase session secrets.
Saves a real request row for owner/admin review. It does not call Auth delete from the browser.
Real Auth deletion must be done server-side by Edge Function later. This page never uses a service-role key.
Waiting.
Waiting.
Waiting.
Waiting.
V7.12.300.16 Profile Account Centre TEST — old V7.0.4 route, real delete-request queue, current live profile URL untouched, no schema/RLS/storage policy/live promotion.
Choose image, preview, upload to the existing image bucket, then save the public URL to the current sb_profiles row.
This creates a real request row in sb_account_deletion_requests. It does not delete Auth users, storage objects, profile rows, messages or content.