Security & Data Sovereignty

All council and resident data is stored exclusively in AWS ap-southeast-2 (Sydney, Australia). JOOVE does not transfer, replicate, or process data in any region outside Australia.

The platform is hosted on Supabase (infrastructure layer) and Vercel (Next.js hosting, edge CDN). Static assets and edge functions may be served from global CDN nodes, but no personally identifiable information (PII) or council data is stored outside AP-SOUTHEAST-2.

At rest: All database storage is encrypted using AES-256 managed by AWS. File uploads (council logos, documents) are stored in Supabase Storage with server-side encryption.

In transit: All connections between clients, edge functions, and the database use TLS 1.3 minimum. HTTP is redirected to HTTPS. HSTS headers enforce secure connections.

The JOOVE Council Platform uses PostgreSQL Row-Level Security (RLS) on all council tables. This means:

• Council members can only access data belonging to their own LGA organisation.
• Role-based permissions: Admin (full access), Editor (data entry, broadcasts), Viewer (read-only analytics).
• All access is enforced at the database level — not just the application layer. A compromised application cannot bypass RLS.
• JOOVE staff access to council data requires explicit service_role credentials, logged in the council_audit_log table.

JOOVE operates in compliance with the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs).

• Resident data shared with councils is subject to a Data Sharing Agreement (DSA) accepted by the council administrator before any data is made accessible.
• Residents have a B2G Data Opt-Out toggle in their account settings. Opted-out residents are excluded from all council analytics and broadcasts.
• Data minimisation: councils see only aggregated and anonymised resident metrics (suburb, activity counts). Individual PII is never exposed.
• Broadcast targeting uses suburb-level data only — no individual profiling.

Daily automated backups are performed by Supabase with a 30-day retention window. Backups are stored encrypted in the same AWS region (ap-southeast-2).

Point-in-time recovery (PITR) is available for the Supabase Pro plan. In the event of data loss, recovery time objective (RTO) is less than 4 hours for the database layer.

In the event of a confirmed data breach or security incident affecting council data, JOOVE will:

1. Notify affected council administrators within 72 hours.
2. Provide a written incident report within 5 business days including scope, impact assessment, and remediation steps.
3. Cooperate with the OAIC notification requirements under the Notifiable Data Breaches (NDB) scheme.

Security inquiries: security@joove.app