Privacy Policy

1. Scope

This policy applies to OpenClaw mobile apps for iOS and Android and to the OpenClaw Chrome extension. It also covers supported features tied to those apps, such as share-sheet forwarding or live mobile status surfaces where available. It does not cover the privacy practices of the gateway, server, AI provider, or other services you choose to connect to through OpenClaw.

2. Information the app can access

The apps can access the following categories of data, depending on which features you turn on:

• Connection and setup data, such as gateway host/port, tokens, passwords, TLS fingerprints, pairing state, local display name, wake-word settings, feature toggles, local discovery state, and push or notification tokens on supported platforms.
• A local device identity and device-specific auth tokens used to pair and authenticate with your gateway.
• Camera photos and videos if you use snapshot or clip features.
• Microphone audio if you use voice transcription, talk mode, voice wake, or audio capture.
• Location data if you enable location sharing. Background location is only used if you explicitly enable "Always" or the platform equivalent.
• Photos you choose to make available through the Photos permission.
• Contacts if you enable contact search or contact creation.
• Calendar data and, on supported platforms, reminders if you enable those features.
• Notification-related data. On Android, if you enable the notification listener, the app can access notification content and metadata and perform supported actions. On supported platforms, the app may also use notification permissions or push tokens to deliver its own notifications.
• Motion sensor data if you enable activity or pedometer features.
• On Android, SMS sending metadata if you use SMS send features. The app does not request SMS read permissions.
• Screen content only when you explicitly start a supported screen capture or recording flow.
• Content you intentionally share with OpenClaw through a system share sheet or share extension on supported platforms.

3. Where data goes

• OpenClaw sends commands, content, and device capability data to the gateway you configure. That gateway may be local, on your tailnet, self-hosted, or operated by someone else.
• If you use voice transcription or wake words, the relevant platform speech recognition service may process microphone audio and transcripts.
• If you enable talk mode with ElevenLabs, text and voice configuration needed for speech output may be sent to ElevenLabs.
• On supported platforms, push notification tokens may be sent to your gateway so it can deliver app notifications or wake events.
• If your configured gateway forwards data to AI models or other third-party services, those services will handle data according to their own policies.
• Mobile operating systems may copy app data through backup, restore, or device-transfer features depending on platform and device settings.

4. Chrome extension

The OpenClaw Chrome extension connects your own OpenClaw gateway to your Chrome browser. It has a single purpose: let the agent you run see and operate the specific tabs you explicitly share with it, and send page text to that agent when you ask.

• The extension requests no host permissions. It cannot read arbitrary pages you visit.
• Tabs you place in the OpenClaw tab group are the consent boundary: the extension attaches Chrome's debugging interface only to those tabs so your gateway can read and drive them. Removing a tab from the group, clicking the toolbar toggle, or dismissing Chrome's debugging banner revokes access immediately.
• "Send page to OpenClaw" is a one-shot, explicit action: the readable text or current selection of the active tab, its URL and title, and your optional note are sent to your own gateway. For Google Docs, the extension exports the document as plain text inside that tab using your existing signed-in browser session; the export goes only to your gateway.
• All extension traffic goes to the relay or gateway you paired yourself, over an authenticated loopback or TLS WebSocket connection. There is no OpenClaw cloud in the path and no third-party data collection.
• The extension stores its pairing configuration (relay URL, pairing token, tab-group color) and per-tab share state locally in extension storage on your machine.

5. What we do not do

• We do not sell your personal data.
• We do not include ad SDKs in the current mobile or extension builds.
• We do not include analytics or crash-reporting SDKs in the current mobile or extension builds.
• Current Android builds do not request SMS read permissions.

6. Local storage and security

The mobile apps store connection secrets such as gateway tokens and passwords locally using platform security features, such as Android encrypted shared preferences and the iOS Keychain. They also store local device identity, app settings, and pairing state in app-private storage.

Temporary files may be written to app cache while features run, for example media output, update packages, or debugging artifacts.

7. Retention

Data stored on your device generally remains there until you remove it, clear app data, or uninstall the app. Data handled by your gateway or any connected third-party service is retained according to that service's own configuration and policies.

8. Your choices

• You can deny or revoke iOS or Android permissions at any time in system settings.
• You can disable features such as location, notifications, voice, or talk mode inside the app.
• You can disconnect from a gateway, clear app storage, or uninstall the app or extension.
• You can control retention and third-party routing on the gateway you choose to use.

9. Changes and contact

We may update this policy as the app changes. If we do, we will post the updated version here and update the effective date above.

For privacy or security questions, email security@openclaw.ai.