Owner: Multibook Philippines Inc. · Version 1.2 · Last reviewed 2026-10-20 · Reviewed annually.
Logs acquired
| Log type | Source | Contents |
|---|---|---|
| Audit / activity log | Audit microservice (dedicated DB) | All user and admin actions, logins (success/fail) with IP + user-agent, privileged operations |
| Web access/error logs | nginx on each droplet | HTTP requests, status, client IP, user-agent |
| Application logs | Application containers | App-level events/errors |
| Edge security logs | Cloudflare | WAF events, rate-limit challenges, blocked requests |
| Server/auth logs | OS, Tailscale | SSH/auth, fail2ban, device access |
| Infrastructure monitoring logs | Monitoring service | Server and service health data |
| AI request logs | Application database | Prompt and response content for AI features, plus usage metadata |
| Support tickets | Messaging service database | Tickets, messages and attachments sent to support (a customer record, not an operational log) |
Retention periods
- Audit / activity log: up to 24 months from each event (append-only, partitioned). These logs are not deleted when a workspace is deleted; they are kept until they reach 24 months, then erased.
- nginx web access/error logs: ~12 months (logrotate
rotate 372, daily + compress, on all droplets). - Application (Docker) logs: operational/debug only — security and audit events are captured in the audit database — retained on a rolling basis via the Docker
json-filedriver’s size/file rotation. - Cloudflare edge logs: per plan retention; security events reviewable in the dashboard.
- Server/auth logs: OS default rotation, retained at least 3 months.
- Infrastructure monitoring logs: 30 days.
- Support tickets: resolved or closed tickets are deleted automatically 30 days after closing; open tickets are deleted with the workspace.
- AI request logs: prompt and response content is erased after 90 days; usage metadata (model, token counts, timing, status) is kept.
Integrity & attribution
The audit database is append-only — entries are not editable after write. Privileged operations are attributable to a named account; deployment actions are attributable via GitHub Actions logs.
Provision on request
Operation and security logs (or analysis results) are provided to the customer on legitimate request, subject to the Customer Data Access Policy.