How This Briefing Works
This report opens with key findings, then maps the gaps between what Matomo discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Full data ownership via self-hosting”
Awaiting scanner verification to confirm runtime behavior matches documented privacy configuration options
pending
“CNIL-approved for cookieless use”
Regulatory approval applies to specific configurations — scanner verification needed to confirm actual deployment settings
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Matomo
- →- If using Matomo cloud, review the Data Processing Agreement for jurisdictional coverage - If self-hosting, ensure the Matomo instance is patched and secured — it becomes part of your attack surface - Enable cookieless tracking mode and IP anonymization for maximum privacy posture - Configure automatic data purging schedules aligned with your data retention policy - Audit installed Matomo plugins for any that introduce third-party data sharing
Negotiation Leverage
- →Matomo's open-source model provides strong negotiation leverage — the self-hosted option is free, meaning cloud pricing negotiations have a credible walkaway alternative. Key questions: (1) For cloud-hosted: What infrastructure and jurisdictions process visitor data? (2) What is the data retention policy, and can it be customized? (3) Are there any analytics features that require data to leave the self-hosted environment? Matomo's open-source foundation means vendor lock-in risk is minimal — data and configuration can be migrated if needed. This is a rare and valuable characteristic in the analytics vendor landscape.
IOC Manifest
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
133 detection signatures across scripts, domains, cookies, and network endpoints