Own PostHog project with scrubbed telemetry; privacy policy lists every data flow
The API, console and website report to a PostHog project of their own in the EU, behind a filter that removes media, URLs, keys and addresses; the privacy policy, sub-processor list and DPA annex now name each telemetry flow with its retention.
- The API reports to its own PostHog project (EU region) instead of sharing one with SfwBot
- A deny-by-default filter runs before anything is sent: media, URLs, base64 data, file names, content hashes, API keys, cookies, tokens, e-mail addresses and IP addresses are removed; the provider drops the sender's IP on arrival
- No per-request events exist. The API sends counts per five-minute window (requests, credits, media kinds, levels, status classes, latency buckets); account activity events carry pseudonymous IDs only
- Error tracking and warning-level logs of the API and console with the same removals, kept 90 and 30 days
- Website analytics on sfwapi.dev load only after consent and never on console pages; query strings are stripped from every URL property
- The privacy policy gained rows for account activity events, aggregated API volume, error reports and application logs plus a paragraph on what telemetry never contains; the sub-processor list, the DPA annex and the data handling page say the same