Product · Compliance & guardrails

Compliance is the product, not a footnote

Every competitor in this category sells volume. DM Handled is built around the one question every serious buyer actually asks first: will this get my account restricted? Here is the honest, complete answer.

Account safety

The three things that actually get accounts restricted — and why this does none of them

What gets accounts restricted

Messaging people who never contacted you first. Sending identical text at machine speed. Automating the app through a logged-in browser session instead of an official API.

What DM Handled does instead

Replies only to people who messaged first. Writes freshly-worded replies at a throttled rate, well inside Meta's own limits. Connects only through the official Meta Graph API — never a logged-in session, never your password.

Enforced in the code, not left to a setting

Inbound only

It cannot open a conversation on Instagram or Facebook at all — there is no code path that does it. On WhatsApp it never sends an unprompted message either.

No Human Agent tag

That tag extends Meta's messaging window to seven days and is reserved for real people. Using it to stretch an automation's reach would be a breach, so DM Handled never touches it.

Official APIs only

Every message is sent and received through Meta's own Graph API, through an app you authorise. No logged-in browser session, ever — the thing that actually gets cheap "DM bots" restricted.

The EU AI Act

Article 50 has been enforceable since 2 August 2026

Anything that talks to a person must tell them they're talking to AI — clearly, at the start. Penalties reach €15 million or 3% of worldwide turnover. DM Handled sends that disclosure once, at the start of every conversation, in wording you write — and the product does not let you remove it, empty it, or work around it.

Read how the disclosure works and what Article 50 actually requires.

Data

EU company. EU servers. EU law.

Every conversation, every piece of your knowledge and your account record is stored on servers inside the European Union, across three data centres in two countries. You stay the controller of your customers' data; DM Handled acts as processor under a Data Processing Agreement already in force the moment you sign up.

One sub-processor sits outside the EU: writing a reply sends the message to Anthropic PBC in the United States, under Standard Contractual Clauses, and nothing is used to train a model. Every party that touches your data is named, with where they are, on the sub-processors page.

See it before you switch it on

Sign up free and read exactly what it would say before it answers anyone.

Free to set up.