supabase-data-handling

# Supabase Data Handling ## Overview GDPR and CCPA compliance with Supabase requires a layered approach: Row Level Security (RLS) for tenant data isolation, `supabase.auth.admin.deleteUser()` for right-to-deletion requests, SQL-based data exports for subject access requests, PII detection across database columns, automated retention policies using `pg_cron`, and point-in-time recovery for backup/restore. This skill implements every compliance requirement using real Supabase SDK methods and PostgreSQL features. **When to use:** Implementing GDPR right-to-deletion, responding to data subject access requests (DSARs), auditing PII in your database, configuring automated data retention, setting up tenant isolation with RLS, or planning backup/restore procedures. ## Prerequisites - `@supabase/supabase-js` v2+ with service role key for admin operations - Supabase project on Pro plan (for `pg_cron` and point-in-time recovery) - Understanding of GDPR Articles 15-17 (access, rectification, erasure) - Database access via SQL Editor or `psql` for schema changes ## Instructions ### Step 1: RLS for Data Isolation and PII Column Management Configure Row Level Security to ensure users can only access their own data, and identify which columns contain PII. **Tenant isolation with RLS:** ```sql -- Enable RLS on all tables containing user data ALTER TABLE public.profiles ENABLE ROW LEVEL SECURITY; ALTER TABLE public.orders ENABLE ROW LEVEL SECURITY; ALTER TABLE public.documents ENABLE...