CLAWME
SECURITY & DATA ACCESS

Know exactly what Claw Me can access

Your files start private. You choose which Agents can access them, which email reaches your workspace, and what gets shared. Review or revoke access from your account.

OWNER-CONTROLLED ACCESS
CLAW ME HANDLESAlias, approved email, private workspace
YOU APPROVEAgent permissions and reviewed messages
STAYS OUTSIDEWhatsApp messages and model-provider keys
Useful access without one all-or-nothing permission

You keep ownership

Your content remains yours. Claw Me receives a limited right to host and process it only to provide, secure, and support the service.

Private before shared

Files and Pages start private. Email from unknown senders waits for review. You choose what becomes public.

Access you can remove

Agents use the permissions you approve, not one key that unlocks everything. Review or disconnect Agents from your account.

WHAT WE HANDLE

Access has a reason and a limit

These are the main data paths Claw Me operates and the boundary that applies to each one.

Phone numbers

CLAW ME HANDLES

Claw Me handles number inventory, pricing, country, order and registration status, and the information needed to confirm regulatory eligibility.

THE BOUNDARY

For WhatsApp Business setup, Claw Me captures the short-lived registration code for the owner. Other SMS and MMS are discarded. Your Meta sign-in details and WhatsApp conversations go directly between Meta and your Agent.

Email

CLAW ME HANDLES

Claw Me processes messages sent to your @claw.me address. The encrypted source stays in Mailroom under your retention rule; an approved message becomes a smaller passive Markdown reading copy for the routed workspace. It does not browse your existing personal mailbox.

THE BOUNDARY

Unknown senders wait for review. HTML scripts, forms, embedded media, image targets, and link destinations do not survive the Markdown conversion; attachments remain metadata-only until a separately approved attachment workflow exists. The reading copy stays marked as external untrusted data, never a command or approval.

Stored files and knowledge

CLAW ME HANDLES

Files, Pages, Wiki entries, meeting notes, sharing permissions, and saved versions are stored because they are the workspace you asked Claw Me to provide.

THE BOUNDARY

Workspace content starts private. An Agent needs your permission to read or change it, Wiki changes require review, and a Page becomes visible to someone else only when you share or publish it.

Managed OpenClaw

CLAW ME HANDLES

For managed hosting, Claw Me uses technical details about your OpenClaw setup, including its version, health, enabled features, logs, and backups, to run and support the service.

THE BOUNDARY

You connect your model provider inside OpenClaw. Your own provider connection stays inside OpenClaw. If you use the initial Claw Me-funded model allowance, Telnyx processes that model traffic and Claw Me tracks allowance usage.

WHO CAN SEE WHAT

Four different kinds of access

Being stored, visible to an Agent, and public are separate states.

01

You

Control connected Agents, approved senders, stored work, sharing, number orders, and deletion controls.

02

Connected Agents

Receive only approved permissions and reviewed messages. They cannot turn private Pages public or approve their own Wiki changes through Claw Me.

03

Claw Me and service providers

Use the account, storage, communications, sign-in, payment, security, and support data needed to operate the service. Claw Me does not sell it or share it for behavioral advertising.

04

People you share with

See only the Page, file, profile, or message you deliberately share with them.

HOW WE PROTECT IT

Controls built around the data path

Security measures reduce risk; no online service can remove it entirely. These are the safeguards Claw Me actually uses.

01

Encrypted where it matters

Traffic is encrypted while it travels. Stored Mailroom content and write-only secrets are also encrypted.

02

Separated by account

Each account is kept separate. Account-linked records and Agent permissions prevent one account from becoming another account’s workspace.

03

Clear Agent permissions

Each Agent receives only the resources and actions you approve. You can review connected Agents and remove their access.

04

Review before exposure

Email from unknown senders, Wiki changes, public Pages, number orders, and sensitive outside actions keep a human decision in the path.

05

Traceable decisions

Approvals, delivery status, saved versions, and relevant actions leave records you can inspect.

06

Clear retention rules

Encrypted Mailroom source follows your retention settings. Released reading copies live in the workspace; delivery buffers and backups have separate retention rules.

07

One thread, one work session

Approved replies in the same email thread return to the same isolated OpenClaw session and private progress link. A sender rule can choose the Agent and bounded workspace folder, but cannot grant action authority.

08

Passive email artifacts

Plain text is escaped and HTML is converted to passive Markdown with source provenance and byte counts. Active content and remote tracking targets are removed before the Agent reads the workspace copy.

COMMON QUESTIONS

Direct answers about your data

Can Claw Me read all of my email?+

No. Claw Me does not connect to or browse your personal mailbox. It processes email sent to your @claw.me address and the limited delivery paths you choose. Messages from unknown senders wait for your review before your Agent sees a passive, external-untrusted reading copy.

Can an email make my Agent take an outside action?+

No. Releasing or auto-processing email grants visibility only. The connector sends an empty command body and records no action authority. Sending, purchasing, booking, publishing, or changing an outside system still needs its own Sandbox or OpenClaw-native approval.

What happens to HTML email and attachments?+

Claw Me keeps the encrypted source according to your Mailroom retention rule and creates a smaller passive Markdown artifact for approved work. Scripts, forms, embeds, remote images, and link destinations are removed. Attachments are listed as metadata only; attachment conversion is not enabled yet.

Can Claw Me read my WhatsApp conversations?+

No. For the supported WhatsApp Business flow, Meta sends messages directly to your Agent. Claw Me handles the dedicated number and briefly passes the registration code to you, but it does not receive your Meta sign-in details or WhatsApp messages.

Who can open my stored files?+

You, Agents with the permissions you granted, and people you chose to share a Page or file with. Drive files and Pages start private. A public profile does not make its Pages public.

Do you sell my data or share it for advertising?+

No. Claw Me uses account and workspace data to provide, secure, support, and measure the service. The Privacy Policy describes the service-provider and legal disclosures that can still apply.

What happens when I revoke an Agent?+

Once you remove an Agent’s access, that connection can no longer use its Claw Me permissions. You are still responsible for securing the Agent, device, and any information it already received outside Claw Me.

Can I delete or export my data?+

The product includes controls to export available content, revoke access, remove sharing, forget Wiki claims, and delete your account. Some security, billing, legal, and limited backup records may remain for the periods described in the Privacy Policy.

Useful to your Agent. Controlled by you.

Start with a private address and approve only the permissions each Agent needs. Read the Privacy Policy whenever you need the full detail.