Short answer: GDPR Article 6(1)(f) lists "legitimate interests" as a lawful basis, and Recital 47 says direct marketing "may be regarded as carried out for a legitimate interest" [[1]](#sources) [[2]](#sources). That is not a ruling that a cold email to Germany is lawful. Whether UWG requires prior consent is a separate question: get it answered by a German lawyer before you send.
Who this is for
This guide is for a founder, sales lead or operations owner who plans Kaltakquise by email, the German term for cold outreach, to businesses in Germany. It helps you decide what to settle before the first message goes out. It is also for someone who has been told "B2B cold email is fine in Europe" and wants to see what that claim rests on.
It is not for you if you want a yes or no. Anyone who answers that flatly, from outside a law firm, is simplifying. What follows is a method: what you can verify yourself, what you must hand to a lawyer, and what you can set up in your own tooling so the answer, whichever way it falls, is easy to follow.
Outlevo asks which countries a customer sells into and never proposes markets [[3]](#sources). Nothing here suggests that Germany or any other country is where you should sell. The question is only how to send there lawfully, if you already do.
What the law texts say, and what they do not
Two GDPR passages matter for any B2B cold email to a person in the EU, and both are short.
Article 6(1)(f) lists a lawful basis for processing personal data. Its words: "processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party" (checked 2026-10-22) [[1]](#sources).
Recital 47 speaks to marketing directly: "The processing of personal data for direct marketing purposes may be regarded as carried out for a legitimate interest." (checked 2026-10-22) [[2]](#sources).
Read both closely. Article 6(1)(f) says legitimate interests can be a lawful basis. It is one entry on a list [[1]](#sources). Recital 47 says direct marketing "may be regarded" as a legitimate interest. It does not say it always is, and it does not say every email is allowed [[2]](#sources).
These passages cover how you handle personal data [[1]](#sources) [[2]](#sources). They do not tell you whether the act of sending an unsolicited commercial email needs the recipient's prior agreement under UWG. Whether a B2B cold email to someone in Germany needs consent first, or can go out on an opt-out basis, is the question to put to a German lawyer. Treat any claim about the text of UWG section 7, German regulator guidance, a German opt-out deadline, mandatory contents for a German cold email or fines on record as unconfirmed until you see the statute or a regulator citation.
Why other countries' rules are not German law
Two quotes from other countries show why you cannot import their rules.
The UK regulator, the ICO, says: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." (checked 2026-10-22) [[4]](#sources). That is UK guidance under UK rules. It says nothing about Germany. A reader who sees "corporate bodies are fine" and applies it to a German GmbH has borrowed a rule from the wrong country.
The US FTC's CAN-SPAM guide says: "Your message must include your valid physical postal address." (checked 2026-10-22) [[5]](#sources). That is a US rule for commercial email. It is a sensible habit to copy. It is not evidence of what German law requires.
Keep these as contrasts only [[4]](#sources) [[5]](#sources). The German rules for sender identity, address and unsubscribe need their own source, and that source is the German statute or a German lawyer's reading of it.
Mailbox-provider rules are a separate layer
Even if the law allows a message, the mailbox provider has its own conditions. These are not statutes. They are the providers' own rules.
Google's sender guidelines say: "Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body." (checked 2026-10-22) [[6]](#sources).
Yahoo's sender best practices say: "Honor unsubscribes within 2 days" (checked 2026-10-22) [[7]](#sources).
Treat these as a floor for how you build the email and the opt-out process. They are not a substitute for the German answer. A German deadline for honoring an opt-out could be shorter or longer than Yahoo's, or framed differently. Do not assume that meeting Yahoo's 2 days means you meet German law, and do not assume the reverse [[7]](#sources).
Steps
These steps assume you will send, and want the legal question handled in the right order.
1. Split your list by recipient type. Decide who you plan to email: named people at companies, role addresses such as a sales or info mailbox, or both. Ask your lawyer whether German law and GDPR treat these differently, and whether each type counts as personal data. A list that mixes them without labels makes the answer harder to apply.
2. Ask a German lawyer the UWG question in writing. Keep it narrow. Does a first B2B cold email to a named person at a German company require prior consent, or is an opt-out basis enough under UWG? Ask them to cite the statute section and any case law they rely on. Ask what the B2B and B2C difference is, if any. Keep the written reply. It becomes part of your record.
3. Ask what the email must contain. Sender identity, postal address, unsubscribe mechanism: ask for the German requirements for each, as a list you can paste into a template. Do not rely on the US address rule [[5]](#sources) or the Google link rule [[6]](#sources) as a stand-in.
4. Ask how fast an opt-out must be honored. Get a number of days, or confirmation that the rule is "without delay" with no number. Compare it with Yahoo's 2 days [[7]](#sources). Build your process to meet whichever is stricter.
5. Write down your GDPR basis. If you rely on legitimate interests under Article 6(1)(f) [[1]](#sources), write down why, in plain words, for this specific campaign. Note who the recipients are, what you are offering and why it is relevant to them. Ask your lawyer to review the note. A basis you can explain on paper is easier to defend than one you assumed.
6. Ask who enforces and what the exposure is. Ask which German bodies or other parties can act on a complaint about cold email, and what penalties or costs have followed in comparable cases. Get these from the lawyer with references. We cannot give you amounts or cases here.
7. Put the answers into your sending setup. Turn the lawyer's list into rules in your tools: who can be contacted, how often, which template, what the footer says. The next section shows how Outlevo's controls map onto this.
How Outlevo's controls can carry your answers
None of this makes a campaign lawful. In Outlevo, nothing is sent outside a policy that a person approved. Policies set who can be contacted, on which channels and how often [[8]](#sources). If your lawyer says a certain recipient type needs consent first, the policy is where that rule goes.
Every external action is checked against the approved policy before it runs, and recorded in a ledger [[8]](#sources). That gives you a record of what ran under which policy, which is useful if you are ever asked what you did.
Kill switches pause a campaign, a channel or the whole workspace at once [[8]](#sources). If advice changes, or a complaint arrives, you can stop sending without hunting through settings.
When you send through Smartlead, Outlevo reads sent, reply, bounce and unsubscribe events back by webhook [[9]](#sources).
The public API has "suppressions" and "compliance" among its resources [[10]](#sources). If you keep a do-not-contact list elsewhere, the API reference is where to check how to connect it. We do not describe here how those resources behave. Read the reference at developers.outlevo.com.
If you import contacts from HubSpot, the import is optional. It happens only after an admin turns it on with a stated purpose, and it includes the email opt-out field alongside email, name and job title [[11]](#sources). That stated purpose is a natural place to record the lawful basis from step 5.
The Gmail extension has a recipient guard that warns before you email a contact Outlevo should not reach [[12]](#sources). Personal data such as email addresses is encrypted at the field level [[13]](#sources).
One neighboring feature is easy to confuse with email. Outlevo's website-visitor tool never identifies a person or sets a cookie, and browsers that send Do Not Track or Global Privacy Control send nothing at all [[14]](#sources). It shows companies, not people. It is not an email list and does not change the cold email questions above.
What to check
Run through this list before the first send, and again whenever you change the template or the audience.
- A written answer on UWG. Not a blog post, including this one. A statement from a German lawyer that cites the statute, covering a first B2B email to a named person.
- The B2B and B2C line. If your list could include sole traders or private individuals, ask where the line falls and how you will tell the difference in your data.
- Required contents. Your template matches the German list from your lawyer: sender identity, postal address, unsubscribe. Not the US list and not the Google list, though you also meet those.
- An unsubscribe that works. The link is visible in the body, in line with Google's wording [[6]](#sources), and one-click where the mailbox provider expects it.
- A deadline you can meet. You know the German number, or the German wording, and your process is at least as quick as Yahoo's 2 days [[7]](#sources).
- A suppression list that sticks. Anyone who opts out stays out across campaigns, mailboxes and channels. Test it by unsubscribing from one of your own test addresses and confirming the next send skips it.
- A recorded GDPR basis. A short note per campaign, kept with the policy [[1]](#sources).
- An enforcement picture. You know who could complain and who could act. You have the lawyer's view of the exposure.
- Sending hygiene that limits harm. Separate your cold sending from your main domain where you can. Our comparison of secondary vs primary domain for cold email covers that choice. Our post on how many follow-ups a cold email sequence needs is a starting point for cadence.
Common ways this goes wrong
Quoting the wrong country. A UK "corporate body" rule or a US postal-address rule gets pasted into a German plan [[4]](#sources) [[5]](#sources). Label every rule you rely on with its jurisdiction.
Treating Recital 47 as permission. It says direct marketing "may be regarded" as a legitimate interest [[2]](#sources). That is about the GDPR basis for processing. It does not remove the need to check UWG.
Treating a mailbox-provider rule as the legal deadline. Yahoo's 2 days is Yahoo's guidance, not a German statute [[7]](#sources).
Having no record. If you cannot show what policy a message ran under, you cannot show what you decided. The approval policy and ledger exist for this [[8]](#sources).
Next step
Send your lawyer the three questions from steps 2 to 4: does a first B2B email to a named person in Germany need prior consent under UWG, what must the email contain, and how fast must an opt-out be honored. Ask for the statute sections in the reply.
While you wait, you can see how your own market and offer look on paper. The free ICP assessment reads up to 5 public pages of your website and returns facts labeled as verified observations or AI inferences, with up to 5 experimental segment hypotheses [[15]](#sources). It asks which countries you sell into [[16]](#sources). It does not give legal advice.
When your lawyer's answers are in, set them as policy limits and approve the policy before anything runs [[8]](#sources). See how Outlevo works for the approval flow.
This is not legal advice. It quotes GDPR [[1]](#sources) [[2]](#sources) and mailbox-provider guidance [[6]](#sources) [[7]](#sources) as published on the dates shown, and it leaves the German statute, regulator and penalty questions to a qualified German lawyer.
Sources
- GDPR Article 6(1)(f): lawfulness of processing
- GDPR Recital 47: legitimate interests of the controller
- ICP from evidence
- ICO: Electronic mail marketing (PECR)
- FTC: CAN-SPAM Act compliance guide for business
- Google: Email sender guidelines
- Yahoo: Sender best practices
- How Outlevo works
- Smartlead integration
- Outlevo API reference
- HubSpot integration
- Gmail extension integration
- Security
- Website visitors integration
- Free ICP assessment
- Release 2026-10-19