Law / Communications
Communications law, instrument by instrument
Law on contacting people and listening in on them: consent and opt-out for marketing email and texts, rules on autodialed and prerecorded calls, consent to record or intercept a conversation, and consent before storing or reading data on a person's device. In practice, it applies when your product sends marketing messages, places calls, records audio, or sets cookies and trackers.
Every communications law instrument LexLint holds, grouped by the jurisdiction that made it. Choose which stages of law to show: the map, the counts and the tables all answer to that choice. To see every area of law, follow Law in the breadcrumb above.
- 1
- 5
- 10
- 20+
- instruments shown
- law on file, none at these stages
- tracked, no law on file
- not tracked
Unions14 in 1 jurisdiction
Law made above the state, binding its members.
| Instrument | When |
|---|---|
 European Union
eu
14 instruments
| |
| Temporary Derogation for Detecting Online Child Sexual Abuse in Messaging ServicesRegulation (EU) 2026/1881 | since |
| Consumer Rights DirectiveDirective 2011/83/EU, Art. 16a(3), second sentence, as inserted by Directive (EU) 2023/2673 | since |
| Consumer Rights DirectiveDirective 2011/83/EU, Art. 16a(3), first sentence, as inserted by Directive (EU) 2023/2673 | since |
| Crypto-Asset Service Providers, Records of Communication with ClientsCommission Delegated Regulation (EU) 2025/1140, Art. 2(2) and Annex, Section 1; Regulation (EU) 2023/1114, Art. 68(9) | since |
| Whistleblower DirectiveDirective (EU) 2019/1937, Art. 18(2) and (4) | since |
| European Electronic Communications CodeDirective (EU) 2018/1972, Art. 115 and Annex VI, Part B, point (a) | since |
| MiFID IIDirective 2014/65/EU, Art. 16(7); Commission Delegated Regulation (EU) 2017/565, Art. 76 | since |
| Consumer Rights DirectiveDirective 2011/83/EU, Art. 8(5) and (6) | since |
| Cookie DirectiveDirective 2002/58/EC, Art. 5(3) | since |
| ePrivacy DirectiveDirective 2002/58/EC, Art. 13 | since |
| Unfair Commercial Practices DirectiveDirective 2005/29/EC, Annex I, point 26 and Art. 5(5) | since |
| ePrivacy DirectiveDirective 2002/58/EC, Art. 5(1) and (2) | since |
| ePrivacy DirectiveDirective 2002/58/EC, Art. 15(1) | since |
| e-Commerce DirectiveDirective 2000/31/EC, Arts. 6 and 7 | since |
Countries187 in 33 jurisdictions
Grouped by region, the European Union heading its member states as a block; alphabetical within each group.
United States: states105 in 17 jurisdictions
Law made below the national level, binding inside it. The slug beside each name says which tier it is.
What this page claims, and what it does not
The stages are the in-force tag's. Each filter is one of the
states the tag names across lexlint.io, in its words (in force, not yet in
force, blocked by a court, proposed, no longer in force, and never in force),
and each filter's label wears that tag's mark. In the tables a law in force
is unmarked, its date in plain text, and every other law wears the same tag
the rest of lexlint.io draws: highlighted, boxed, dotted, or struck with its
reason underlined. A withdrawn bill has a filter of its own, never in force:
the /law/<jurisdiction> docket leaves it out, and "no
longer in force" would be false of a law that never was.
Blocked by a court has its own filter. A law a court has blocked is neither in force nor gone: an injunction can be lifted on appeal, and the duty with it. Pooled with a repeal it would hide a count that reads as a signal, how contested a jurisdictional hook is. It is off by default, with the proposals and the laws that have ended.
One date column, and it says what kind of date it is. The date is the day the law started or starts to bind: the earlier of a published start date and the instrument's own date. Neither source is reliably the start, and the earlier one cannot make a law look newer than it is. The column draws the in-force tag, so a bare date never stands beside a law that has stopped: a law in force reads "since" its date, a law not yet in force is highlighted with its date and how far off it is, a law a court has blocked is boxed in red, and an ended law has its dates struck and its reason underlined. Nothing is inferred from our own review date.
The map is the table. Its fill is the count of instruments at the
stages you chose, binned on the same RAMP_BINS edges
/law/map uses, and it redraws on
every change. Point at, click, or tab to a jurisdiction for what applies there,
every stage it holds shown even when your filter is excluding it.
Three ways of showing nothing, and they are different claims. A jurisdiction washed pale holds communications law your filter is excluding, so widening the filter brings it back. A hatched jurisdiction is one we track and hold no communications law for at all: that is a statement about our research, not about the law. A white shape has no jurisdiction record for this topic at all. Only the first of the three moves when you change the filter; the other two are facts about us and hold still.
Nothing here needs the script. The default resultset is in the
HTML: counts, tally, map fills and the hidden rows are all rendered at
build. The script recomputes them when a box changes and does nothing else,
which is what lets this page ship under script-src 'self' and
be read whole by a crawler.
Every instrument here links its own note page, which carries the primary source and the date it was read. This is a research index, not legal advice.