Matomo

Matomo says AI providers act under contractual processing agreements and are not permitted to use data for their own purposes or to train general AI models.

Only aggregated website analytics data is shared with the AI tools Matomo uses internally.

Matomo's privacy posture centers on customer control and ownership rather than broad vendor-side model improvement.

Matomo still uses AI services internally for analytics development and insights.

Privacy still depends on whether customers configure identifiers, cookies, and events conservatively.

Customer deployment choices, plugins, and cloud hosting can still introduce additional data flows.

Lead-enrichment and partner data flows in Matomo's own business operations still exist around the service.

Matomo emphasizes privacy-focused analytics and customer control of analytics data.

Aggregated analytics data is the only information described as being shared with AI tools in the reviewed policy.

The policy is explicit about controller/processor terminology and data rights.

Analytics and observability tools can collect identifiers, events, session replays, logs, traces, device data, and usage metadata.

Teams can reduce exposure with masking, consent mode, sampling, log scrubbing, retention controls, and restricted access.

Retention still depends on customer configuration and the wider implementation context.

Opt-out and deletion requests can only be fulfilled where Matomo can identify the user through contact or service use.

Site owners can configure retention and deletion practices.

IP addresses are stored in full form in server logs only for 30 days for security reasons and anonymized on receipt for analytics use.

The policy documents access, correction, deletion, portability, and objection rights.

Self-hosting or tighter customer-controlled deployment can materially improve lifecycle governance.

Customers control deployment, tracking configuration, retention, and data access.

Matomo documents extensive privacy rights, including access, correction, deletion, portability, and objection.

Cookie minimization, IP anonymization, self-hosting, and retention settings give operators real technical choices.

The product's privacy-first orientation is explicit rather than aspirational.

A poorly configured Matomo instance can still collect more visitor data than necessary.

Some visitor controls depend on site owners actually exposing or honoring the available privacy settings.