> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/docs/docs_se/referens/references/email/emarketeer-sender-policy.md).

# eMarketeers avsändarpolicy

Reglerna du måste följa när du skickar e-post eller SMS till mottagare via eMarketeer-komponenter.

Reglerna skyddar både dina mottagare och ryktet för eMarketeers avsändarinfrastruktur.

## Regler för avsändare

* Du måste ha mottagarens samtycke (opt-in) innan du skickar e-post eller SMS via eMarketeer. Opt-in gäller per kanal — e-post och SMS måste godkännas separat — om du inte har en affärsrelation med mottagaren.
* Avsändare inom EU måste följa [Directive on Privacy and Electronic Communications](https://en.wikipedia.org/wiki/Directive_on_Privacy_and_Electronic_Communications).
* Avsändare i USA accepterar att följa [CAN-SPAM Act](https://en.wikipedia.org/wiki/CAN-SPAM_Act_of_2003).
* Varje icke-transaktionell e-post måste innehålla en möjlighet att avregistrera sig.
* Mottagare måste aktivt ha gett sitt samtycke till att ta emot marknadsföringsmejl, med full vetskap om vad de godkände. Förifyllda eller förkryssade fält är inte giltigt samtycke.
* Varje skickat e-postmeddelande måste identifiera avsändaren och förklara hur man kommer i kontakt.
* Du får inte skicka oönskad e-post eller meddelanden (spam).
* Du får inte skicka eller publicera olagligt eller omoraliskt innehåll, eller delta i bedräglig verksamhet.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/docs/docs_se/referens/references/email/emarketeer-sender-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.