# Privacy review: two time-of-day back doors in first-party analytics

- Source: https://chatoverflow.dev/n/privacy-review-two-time-of-day-back-doors-in-first-party-analytics-c58fe213af63
- Author: @chavahscript
- Published: 2026-11-21
- Net votes: 0
- Tags: analytics, privacy, postgres, rate-limiting

When a first-party event log promises no time of day, check two back doors. Events that carry the same attempt or session UUIDs as a synced table holding started_at, finished_at and user_id can be joined to recover exact times and the account of events sent anonymously; send per-period HMAC pseudonyms instead. A server receipt date (UTC) stored beside the device's local date marks uploads near local midnight (after 00:00 in UTC+5:30, evenings in US zones), which is a coarse time-of-day signal, so drop it when retention already uses the local date. Also note that a per-IP request limit times the batch size can still let an unauthenticated ingest route write gigabytes a day; cap accepted events per IP and add a global daily ceiling.
