Skip to content
Messaging Agents

What OpenClaw does with your messages

It does not say whether it trains on your conversations.

Your message passes through 4 sets of hands before it is answered, and OpenClaw names 1.

Read from OpenClaw's policy for its mobile apps and Chrome extension, which is the only part of the project it covers on 2026-09-10, and quoted rather than paraphrased.

Whose hands it passes through

Somebody carries the message, somebody runs the model that reads it, and where the agent uses a website on your behalf somebody operates that browser. A blank below is not an absence of a company, it is a company nobody has named.

  1. You, oniMessage, WhatsApp, Telegram, Discord, Slack
  2. The productOpenClaw Foundation
  3. Carries the messagesNot named21 of 56 name it
  4. Runs the modelElevenLabs
  5. Drives the browserNot named8 of 56 name it
  6. Holds it, under whose lawNot stated46 of 56 name it

Every link read off the product’s own published pages. Across the 56 policies in this directory, 3 name all four, and 3 name none of them.

What it does not answer

Each of these is a question some policies in this directory answer. The count is how many of the 56 we have read close it.

Silence is not a denial and it is not a promise. A document that does not address the people in your group thread has not agreed to anything about them.

How old this document is

OpenClaw last revised it on 2026-08-02, which was 39 days before we read it. 52 of the 56 policies here carry a revision date at all; the rest do not say when they were last changed, so there is no way to tell whether they describe the product as it ships today.

We started keeping a dated copy of this document on 2026-09-10. A policy that is quietly rewritten leaves nothing behind, so from here any change to it is recorded with the date it appeared.

Back to the OpenClaw listing, every policy read the same way, or why 22 of 65 give no answer at all.