On this page
What the dated primary record establishes
The Federal Trade Commission’s June 2024 Avast final order names UK, Czech and U.S. group entities. The complaint alleges that browsing information was sold after products promised protection against tracking. The companies neither admitted nor denied the allegations apart from specified jurisdictional facts.
The final order bans specified third-party advertising disclosures of browsing information from Avast products. It separately imposes consent conditions on other defined uses. A consent screen is therefore not a cure for every activity the order prohibits. These are case-specific restrictions, not a universal permission model.
Test the decision in your own operation
For your own product, document the proposed revenue activity before accepting an advertiser’s or analytics buyer’s description. Use ELN’s promise-and-use record with the product, commercial and qualified privacy leads.
| Record to establish | Evidence to bring | Owner decision |
|---|---|---|
| Consumer promise | Actual product words, interface and version | What will an ordinary user understand about tracking or sharing? |
| Proposed data flow | Information detail, source product, recipient and specific purpose | What must be evaluated beyond the label “anonymous analytics”? |
| Applicable boundary | Actual prohibitions, required permission and remaining uncertainty | Is the use prohibited, conditional or unresolved for this operation? |
| Operational control | Who can enable the flow, change recipients and check the permitted use | Can a commercial deal activate a use before the relevant decision? |
Resolve the next commitment
Fictional example: the sales team proposes licensing a detailed usage feed while the product page promises that activity stays private. Renaming the feed “research” does not reconcile those facts. The team must examine the actual data and proposed recipient use, then obtain the supported decision before supply.
Use Relationship factsheet to identify the collecting business, recipient, permitted work and unresolved data-use terms. Keep sensitive records and any legal assessment in the authorised product file. Completing the map does not establish consent or lawful monetisation.
Scope
- The historical final order and complaint do not determine every current Avast product or another company’s privacy obligations. No allegation is presented as an admission.
- A privacy promise, consent flow and lawful data use each need review for the actual people, information, products and requirements.
Next step
A promise-to-data-use matrix recording purpose, actual recipient/use and missing evidence before launch. Connect the collecting product, receiving party, actual purpose and person authorised to decide the use.
Terms used here
- Browsing information
- Information about a person’s web navigation; a general label such as analytics does not explain its detail, recipient or use.
- Affirmative express consent
- In the cited order, specific informed agreement following a separate clear disclosure; accepting broad terms is expressly insufficient.
Sources & review notes
Federal Trade Commission
Passage, dates and research notes
agency-final-consent-order · Final package complaint allegations on tracking/data sale; Decision and Order pp 1–6, definitions A and Part I–III, issued 26 June 2024 and effective-date provision
Complaint allegations remain separate from the final order. The order distinguishes prohibited disclosures from consent-conditioned uses; consent is not assumed to cure every prohibition.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.