Privacy requests
Owner onlyCustomers’ data requests under RA 10173. Each must be answered within 30 days of the request (§22, D45, D79).
Owner access only
Privacy requests involve a customer’s full record, so only the Owner handles them (§5.1, §22). Staff can log a request from the customer’s profile.
| Request | Customer | Received | Due | Status |
|---|
No requests here.
Implementation notes for Cursor
Entities: PrivacyRequest (business_id, customer_id, type access/correction/erasure, source portal/staff, created_at, due_at = created + 30 days, status open/completed/rejected, outcome_note, handled_by_staff_id).
Key states: Open list sorted by due date; overdue in red. Access builds the JSON + CSV export (profile, bookings, receipts, memberships, messages) and emails a 7-day signed link. Correction edits named fields. Erasure anonymises the profile (name becomes “Deleted customer”, contact, notes and tags cleared); receipts and payments are kept for tax records. Every action logs privacy_request.* to the Audit Trail.
Forbidden inventions: no Manager or Staff access; no hard delete of receipts, payments or bookings; no export by email attachment.
Governs: §22, §5.1 (D79), D45, PLAN-226.