Amplitude

The reviewed notice does not provide a clear no-AI-training promise for all behavioral event data.

Amplitude uses collected information to improve and create new products and features.

Amplitude publishes privacy notice coverage for personal data and product analytics services.

Amplitude distinguishes customer end-user data submitted by customers to the product from some of Amplitude's own website and marketing data.

Customers still decide what events, identifiers, and properties they instrument.

Event and profile data can still flow through integrations, service providers, customer users, advertisers, and legal recipients.

Marketing and advertising partners add extra data-sharing paths outside core product analytics.

Amplitude documents privacy rights, processing purposes, and sharing categories.

Customer end-user data is treated separately from many of Amplitude's direct website and marketing interactions.

Customers can control what integrations and exported event flows are enabled.

Some payment and login integrations are clearly named rather than hidden.

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, contracts, exports, backups, and legal obligations.

Analytics exports and partner tools can preserve copies outside the main Amplitude workspace lifecycle.

Privacy rights and deletion request paths are documented.

Customers can manage retention and deletion workflows through the product and privacy processes.

Customer-controlled instrumentation means teams can reduce what ends up retained in the first place.

Amplitude says it will not use collected data for materially different purposes without notice and opportunity to opt out.

Admins can manage access, projects, event data, integrations, and deletion workflows.

Customers control instrumentation and can avoid sending especially sensitive data.

Privacy rights are documented with request paths for several data-use contexts.

Integration and export choices are customer-governed instead of universally forced.

End-user privacy still depends on the customer's instrumentation and consent practices.

Targeted-advertising and website tracking controls are weaker than project-admin controls inside the product.