- Supports treating ePrivacy as a continuing EU privacy framework for electronic communications rather than a one-time marketing-policy note.
"online privacy"
Use this workflow before sending electronic-mail direct marketing without fresh consent under the Article 13 soft opt-in.
The review focuses on proof of an existing customer relationship, own similar products or services, collection-time and message-level opt-out, sender identity, suppression records, approval gates, and national transposition caveats.
Structured answer sets in this page tree.
Cited legal and guidance references.
Article 13 of the ePrivacy Directive starts from prior consent for electronic-mail direct marketing, then allows a narrow existing-customer exception for a sender's own similar products or services when the customer received a clear, free, easy opportunity to object at collection and with each later message. This workflow turns that exception into an approval record for marketing, product, privacy, CRM, and regional operations teams.
Start with the contact-detail event, not the campaign brief. The soft opt-in is tied to electronic contact details obtained from customers in the context of a product or service sale, with the later 2009 amendment text referring to the same customer relationship logic for Article 13.
Approve this gate only when the CRM record can show what was sold or negotiated, when the address was collected, which legal entity collected it, the privacy notice or checkout screen shown at collection, and whether the person objected at that moment.
The campaign must market the same sender's own similar products or services. Treat this as a product-scope review, not a copywriting preference: the product owner must explain why the offer is adjacent to what the customer bought or negotiated for, and why the sending entity is the same natural or legal person that obtained the address.
Use a short similarity matrix before audience upload. Compare the original purchase category, intended customer use, pricing model, delivery channel, brand or legal entity, and whether a reasonable customer would recognize the new message as related to the earlier relationship.
The opt-out must exist twice: at collection and on each marketing message if the customer did not initially refuse. The send must also avoid disguised or concealed sender identity and provide a valid address or mechanism for requests to stop further communications.
Marketing operations should test the unsubscribe path before approval, then prove suppression after the test. The record should show that an objection entered through the campaign link, reply route, preference center, or support channel reaches the same suppression store used by the sending platform.
Do not convert this EU-level workflow into a country-rule database. Article 13 is implemented through national provisions, and the ePrivacy/GDPR relationship can affect enforcement and documentation. Before launch, the regional owner should confirm whether the target country implementation changes the practical result for the channel, audience type, timing, or objection mechanism.
If a national-law answer is missing, record the issue as blocked for that country instead of guessing. The campaign can proceed only for countries whose legal, product-similarity, opt-out, sender-identity, and suppression gates are approved.
Sorena can help convert the Article 13 checks on this page into campaign approval gates, segment evidence, suppression tests, and reusable regional review records.
Ask cited questions about customer relationship evidence, similar products, opt-out controls, sender identity, and soft opt-in campaign approval.
Review a proposed electronic-mail marketing send, source gaps, and national-law caveats before launch.
"online privacy"
"on the occasion of each message"
"Member States shall lay down the rules on penalties"
"valid address to which the recipient may send a request"
"freely given, specific, informed and unambiguous"