# Data retention (proposed defaults, editable in Admin → Settings)
- Booking chat (Phase 5): closes after booking completion + 24 h; ordinary chats kept 90 days; reported/disputed chats kept until resolution + 365 days; then purged by cron. Access to retained messages limited to staff with `chat.moderate`, audited.
- Email outbox: one-time links are wiped after sending; metadata kept.
- Login attempts: 7 days. Used/expired tokens: 7 days. Read notifications: 180 days.
- Audit logs: kept (security record).
- Backups may hold deleted data for the backup rotation period; do not promise instant permanent deletion.
Have this reviewed against the Kenya Data Protection Act, 2019 before launch.
- Verification documents (ID/permit): kept while the application is active/approved; for **rejected** applications deleted automatically after 90 days (Admin > Settings). They are viewable only by the owner and staff with `providers.review`; staff access is audited. Decide a rule for deactivated providers before launch.
- Premises/service photos are public by design and re-encoded on upload (location metadata removed).
- Customer location (search): used only to rank the current request. Not stored, not logged by the app, not shown to providers. Note: the web server's own access log may record the search URL with rounded (~110 m) coordinates; set a short log retention.
- Geocode cache: stores place-name queries (e.g. 'kasarani') and their coordinates, with no user identifiers.
