← ClaudeAtlas

popia-kitlisted

POPIA privacy and security guardrails for South African apps, plus a read-only database check. Use when building or changing anything that handles personal information, before publishing, or when asked for a POPIA, privacy or security review.
VenusOne-Lee/popia-compliance · ★ 13 · AI & Automation · score 73
Install: claude install-skill VenusOne-Lee/popia-compliance
<!-- Generated from adapters/_core.md by scripts/build_adapters.py. Edit the core, not this file. --> # POPIA privacy and security guardrails These rules apply whenever you build, change or review anything that touches personal information of people in South Africa: forms, sign-ups, accounts, CRM, analytics, marketing, AI features, uploads, payments. They come from POPIA (Protection of Personal Information Act 4 of 2013) and its Regulations as amended 17 April 2025. Engineering guidance, not legal advice. Full skill, scanner and references: https://github.com/VenusOne-Lee/popia-compliance ## Always apply when writing code 1. **Minimise (s10).** Every field needs a purpose. Don't collect SA ID numbers unless a law (FICA, tax, payroll, credit) or the core service requires it. Prefer date of birth or an age check. 2. **Lock down access (s19).** Enable row-level security on every Supabase/Postgres table holding personal information, with owner-scoped policies. Never `using (true)` for select/update/delete. Firebase rules compare `request.auth.uid` with the owner. Storage buckets with uploads are private; serve via short-lived signed URLs. 3. **Keep secrets server-side (s19).** No `service_role`, admin or secret keys in client code or in `VITE_`, `NEXT_PUBLIC_`, `EXPO_PUBLIC_`, `REACT_APP_` variables. Derive user identity from the verified session or JWT, never from the request body. 4. **Encrypt (s19).** HTTPS everywhere with HSTS. Field-level encryption or tokenisation for