Framework reference
ePrivacy for EU B2B software companies.
The ePrivacy Directive matters when a website or app uses cookies, tracking, analytics, electronic marketing, or communication services for EU users. For software companies, it sits beside GDPR and often appears in consent, analytics, and marketing compliance work.
- Kaamos support
- Information only
- Category
- Binding EU regulations
- Obligation
- Binding
- Last updated
The obligation, in the act's words
Member States shall ensure that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user is only allowed on condition that the subscriber or user concerned has given his or her consent…
This is the consent rule behind cookie banners, and it covers any storage or access on the device, not only cookies.
Who it applies to
- Websites and apps serving EU users.
- Companies using cookies, analytics, advertising pixels, or electronic marketing.
- Software products that process communication metadata or user tracking signals.
What you need to do
- Cookie consent, marketing consent, tracking controls, and communication confidentiality.
- Records showing which tracking technologies are used and why.
- Alignment between consent tooling, privacy notices, and vendor management.
How to use this entry
- Use this page to understand the buyer or regulatory pressure before it becomes a deadline.
- Run the regulation checker to see whether this area is likely to matter for your company now.
- If it becomes relevant, Kaamos can help you scope the gap and turn it into prioritized security work.
Sources
Information bank
ePrivacy is included as an information-bank entry. Use it to understand the pressure, then run the checker to see whether it should enter your roadmap.