[{"data":1,"prerenderedAt":1350},["ShallowReactive",2],{"help-category-\u002Fsecurity-privacy\u002Fshared-responsibility-model":3,"help-article-\u002Fsecurity-privacy\u002Fshared-responsibility-model":4,"related-articles-\u002Fsecurity-privacy\u002Fshared-responsibility-model":360},[],{"id":5,"title":6,"body":7,"category":342,"description":343,"draft":344,"extension":345,"meta":346,"navigation":347,"order":348,"path":349,"relatedArticles":350,"seo":354,"slug":355,"stem":356,"updatedAt":357,"__hash__":358,"excerpt":343,"searchText":359},"help\u002Fhelp\u002Fsecurity-privacy\u002F14.shared-responsibility-model.md","Shared responsibility model",{"type":8,"value":9,"toc":322},"minimark",[10,14,169,174,177,180,183,187,192,200,204,212,216,219,223,226,241,245,264,268,271,275,278,282,286,289,293,296,300,303],[11,12,13],"p",{},"Security in MultiClaw follows a shared responsibility model. MultiClaw secures the cloud infrastructure and the desktop app; you secure your local environment, credentials, and workspace configuration. Understanding each party's role helps you protect your workspace effectively.",[15,16,17,30],"table",{},[18,19,20],"thead",{},[21,22,23,27],"tr",{},[24,25,26],"th",{},"Responsibility",[24,28,29],{},"Party",[31,32,33,42,49,56,63,70,77,84,92,99,106,113,120,127,134,141,148,155,162],"tbody",{},[21,34,35,39],{},[36,37,38],"td",{},"Infrastructure security (servers, databases, networking)",[36,40,41],{},"MultiClaw",[21,43,44,47],{},[36,45,46],{},"AES-256-GCM application-layer encryption for sensitive values in MultiClaw Cloud",[36,48,41],{},[21,50,51,54],{},[36,52,53],{},"TLS encryption between the gateway and MultiClaw Cloud",[36,55,41],{},[21,57,58,61],{},[36,59,60],{},"Desktop app update signing and verification (minisign)",[36,62,41],{},[21,64,65,68],{},[36,66,67],{},"Patching the desktop app and MultiClaw Cloud",[36,69,41],{},[21,71,72,75],{},[36,73,74],{},"Access controls and audit trail in MultiClaw Cloud",[36,76,41],{},[21,78,79,82],{},[36,80,81],{},"Security incident notification (GDPR Art. 33 and Art. 34)",[36,83,41],{},[21,85,86,89],{},[36,87,88],{},"Keeping the desktop app updated",[36,90,91],{},"You",[21,93,94,97],{},[36,95,96],{},"Keeping OpenClaw updated",[36,98,91],{},[21,100,101,104],{},[36,102,103],{},"Protecting your LLM API keys",[36,105,91],{},[21,107,108,111],{},[36,109,110],{},"Securing the local OpenClaw data directory",[36,112,91],{},[21,114,115,118],{},[36,116,117],{},"Managing workspace member access",[36,119,91],{},[21,121,122,125],{},[36,123,124],{},"Configuring agent guardrails",[36,126,91],{},[21,128,129,132],{},[36,130,131],{},"Securing the machine running the desktop app",[36,133,91],{},[21,135,136,139],{},[36,137,138],{},"Reviewing third-party MCP servers before adding them",[36,140,91],{},[21,142,143,146],{},[36,144,145],{},"Infrastructure monitoring",[36,147,41],{},[21,149,150,153],{},[36,151,152],{},"Agent activity monitoring and suspicious behaviour reporting",[36,154,91],{},[21,156,157,160],{},[36,158,159],{},"Secure default configuration",[36,161,41],{},[21,163,164,167],{},[36,165,166],{},"Configuration changes (for example, disabling auto-updates)",[36,168,91],{},[170,171,173],"h2",{"id":172},"multiclaws-responsibilities","MultiClaw's responsibilities",[11,175,176],{},"MultiClaw secures the cloud infrastructure that powers MultiClaw Cloud. This includes the physical security of data centres via AWS, server and database hardening, and network-level protections. MultiClaw Cloud stores data on AWS infrastructure, which encrypts underlying storage volumes at rest. Sensitive values including agent configuration and credentials are additionally encrypted at the application layer using AES-256-GCM before being written to the database.",[11,178,179],{},"All connections between the gateway and MultiClaw Cloud are encrypted with TLS. Desktop app updates are signed with minisign and verified before installation. MultiClaw patches and maintains the desktop app and MultiClaw Cloud on an ongoing basis.",[11,181,182],{},"MultiClaw Cloud enforces access controls and maintains an audit trail of key platform events. If a security incident is confirmed to have affected your data, MultiClaw will notify the relevant supervisory authority within 72 hours as required by GDPR Art. 33. MultiClaw will also notify you directly without undue delay if the breach poses a high risk to your rights (Art. 34).",[170,184,186],{"id":185},"your-responsibilities","Your responsibilities",[188,189,191],"h3",{"id":190},"keep-the-desktop-app-updated","Keep the desktop app updated",[11,193,194,195,199],{},"Auto-updates are enabled by default. Do not disable them, as updates include security patches. If you need to verify which version you are running, check the desktop app's ",[196,197,198],"strong",{},"About"," screen.",[188,201,203],{"id":202},"keep-openclaw-updated","Keep OpenClaw updated",[11,205,206,207,211],{},"OpenClaw is installed and updated separately from MultiClaw. Keep your OpenClaw installation current by following the update instructions for your platform (for example, ",[208,209,210],"code",{},"brew upgrade openclaw"," on macOS). MultiClaw does not distribute or update the OpenClaw binary on your behalf.",[188,213,215],{"id":214},"protect-your-llm-api-keys","Protect your LLM API keys",[11,217,218],{},"Your LLM API keys are stored in MultiClaw Cloud and encrypted at rest using AES-256-GCM. You control which services receive those keys. If you suspect a key has been compromised, rotate it immediately in your LLM provider's dashboard and update it in MultiClaw Cloud. Only connect services you trust.",[188,220,222],{"id":221},"secure-the-local-openclaw-data-directory","Secure the local OpenClaw data directory",[11,224,225],{},"The local OpenClaw data directory is protected by your operating system's file-system permissions. Enable full-disk encryption on any machine running the desktop app. Keep the machine's operating system updated and apply security patches promptly.",[11,227,228,229,232,233,236,237,240],{},"On macOS, confirm FileVault is on in ",[196,230,231],{},"System Settings → Privacy & Security",". On Windows, check ",[196,234,235],{},"Settings → Privacy & security → Device encryption"," or search for ",[196,238,239],{},"BitLocker",". On Linux, verify LUKS encryption is active.",[188,242,244],{"id":243},"manage-workspace-member-access","Manage workspace member access",[11,246,247,248,251,252,255,256,259,260,263],{},"Invite only trusted users and revoke access when members leave. Two roles exist: ",[196,249,250],{},"Owner"," and ",[196,253,254],{},"Member",". Periodically review the member list by navigating to your workspace's ",[196,257,258],{},"Users"," page (",[208,261,262],{},"\u002F{your-workspace}\u002Fusers",") in MultiClaw Cloud.",[188,265,267],{"id":266},"configure-agent-guardrails","Configure agent guardrails",[11,269,270],{},"MultiClaw provides secure defaults, but you are responsible for adjusting approval flows, scope limits, and execution permissions to match your organisation's risk tolerance. Review guardrail settings whenever your security requirements change.",[188,272,274],{"id":273},"vet-third-party-mcp-servers","Vet third-party MCP servers",[11,276,277],{},"Before adding a third-party MCP server, verify its source and review its permissions. MultiClaw cannot audit or vouch for third-party servers. You are responsible for any access those servers receive.",[170,279,281],{"id":280},"shared-responsibilities","Shared responsibilities",[188,283,285],{"id":284},"incident-detection","Incident detection",[11,287,288],{},"MultiClaw monitors infrastructure for anomalies. You are responsible for monitoring your own agent activity. If you notice unexpected behaviour — agents running tasks you did not approve, unusual output, or activity at unexpected times — review the audit trail and revoke agent access if necessary.",[188,290,292],{"id":291},"configuration","Configuration",[11,294,295],{},"MultiClaw ships secure defaults for all settings. When you change a default (for example, disabling auto-updates or granting an agent broad file access), you accept responsibility for the security implications of that change. Review any configuration change against your organisation's security policies before applying it.",[170,297,299],{"id":298},"what-this-model-does-not-cover","What this model does not cover",[11,301,302],{},"This model describes the division of security responsibilities between MultiClaw and you. It does not guarantee that either party's measures will prevent every possible incident. No security programme can eliminate all risk.",[11,304,305,306,311,312,316,317,321],{},"If you are unsure where a specific responsibility falls, contact MultiClaw support. For the technical detail behind the protections described here, see ",[307,308,310],"a",{"href":309},"\u002Fhelp\u002Fsecurity-privacy\u002Fsecurity-overview","Security overview",", ",[307,313,315],{"href":314},"\u002Fhelp\u002Fsecurity-privacy\u002Fdata-encryption","Data encryption",", and ",[307,318,320],{"href":319},"\u002Fhelp\u002Fsecurity-privacy\u002Fhow-credentials-and-secrets-are-stored","How credentials and secrets are stored",".",{"title":323,"searchDepth":324,"depth":324,"links":325},"",2,[326,327,337,341],{"id":172,"depth":324,"text":173},{"id":185,"depth":324,"text":186,"children":328},[329,331,332,333,334,335,336],{"id":190,"depth":330,"text":191},3,{"id":202,"depth":330,"text":203},{"id":214,"depth":330,"text":215},{"id":221,"depth":330,"text":222},{"id":243,"depth":330,"text":244},{"id":266,"depth":330,"text":267},{"id":273,"depth":330,"text":274},{"id":280,"depth":324,"text":281,"children":338},[339,340],{"id":284,"depth":330,"text":285},{"id":291,"depth":330,"text":292},{"id":298,"depth":324,"text":299},"security-privacy","What MultiClaw secures versus what you are responsible for as a customer.",false,"md",{},true,14,"\u002Fsecurity-privacy\u002Fshared-responsibility-model",[351,352,353],"security-privacy\u002Fsecurity-overview","security-privacy\u002Fdata-encryption","security-privacy\u002Fhow-credentials-and-secrets-are-stored",{"title":6,"description":343},"shared-responsibility-model","help\u002Fsecurity-privacy\u002F14.shared-responsibility-model","2026-03-30","hIH39R_Cs9_Maa_AMfiy_aXwvGhQrYoqXAyei0o7818","Shared responsibility model What MultiClaw secures versus what you are responsible for as a customer.",[361,636,1047],{"id":362,"title":310,"body":363,"category":342,"description":623,"draft":344,"extension":345,"meta":624,"navigation":347,"order":625,"path":626,"relatedArticles":627,"seo":631,"slug":632,"stem":633,"updatedAt":357,"__hash__":634,"excerpt":623,"searchText":635},"help\u002Fhelp\u002Fsecurity-privacy\u002F01.security-overview.md",{"type":8,"value":364,"toc":608},[365,375,378,382,385,401,404,411,419,423,426,432,436,439,445,449,471,476,480,483,490,494,500,505,509,516,523,527,530,537,541,544,550,554,561,568,572,575,581,585,588,595,599,602],[11,366,367,368,371,372,321],{},"MultiClaw protects your data through multiple independent security layers: local credential storage, TLS connections, app sandboxing, and zero telemetry. Each layer works on its own, reducing the risk that a single vulnerability leads to broader exposure. The architecture follows ",[196,369,370],{},"defense-in-depth"," principles aligned with ",[196,373,374],{},"ISO\u002FIEC 27001:2022",[11,376,377],{},"This article gives you a high-level view of how MultiClaw handles security and privacy. Each section links to a dedicated article with full details.",[170,379,381],{"id":380},"separate-trust-zones","Separate trust zones",[11,383,384],{},"The desktop app, the local OpenClaw gateway, and MultiClaw Cloud operate as three distinct trust zones, each with its own authentication:",[386,387,388,395],"ul",{},[389,390,391,394],"li",{},[196,392,393],{},"Desktop app",": connects to MultiClaw Cloud over HTTPS and WSS for API calls, real-time updates, agent configuration, and session data.",[389,396,397,400],{},[196,398,399],{},"Local OpenClaw gateway",": connects to MultiClaw Cloud separately over an authenticated WebSocket secured with short-lived signed tokens. These tokens rotate automatically, so a captured token expires before it can be reused.",[11,402,403],{},"Each connection enforces its own credentials. No zone shares authentication tokens with another.",[11,405,406],{},[407,408],"img",{"alt":409,"src":410},"MultiClaw security architecture — the four components and how they connect across trust boundaries","\u002Fimages\u002Fmulticlaw-security-architecture.png",[11,412,413,414,418],{},"See ",[307,415,417],{"href":416},"\u002Fhelp\u002Fsecurity-privacy\u002Fnetwork-security","Network security"," for details on how each connection is secured.",[170,420,422],{"id":421},"authentication-and-login-security","Authentication and login security",[11,424,425],{},"All authentication is handled by MultiClaw Cloud. You can sign in with email and password or through Multiplai single sign-on (SSO). Sessions use short-lived tokens that rotate automatically, and repeated failed login attempts trigger temporary account lockouts.",[11,427,413,428,431],{},[307,429,422],{"href":430},"\u002Fhelp\u002Fsecurity-privacy\u002Fauthentication-and-login-security"," for details on session handling, token rotation, and lockout policies.",[170,433,435],{"id":434},"roles-and-access-control","Roles and access control",[11,437,438],{},"MultiClaw uses role-based access control (RBAC) in workspaces. Each person is assigned exactly one role — Owner or Member — which determines what they can view, create, and manage. Permissions follow a least-privilege model: users only have access to what their role requires.",[11,440,413,441,444],{},[307,442,435],{"href":443},"\u002Fhelp\u002Fsecurity-privacy\u002Froles-and-access-control"," for the full permission matrix.",[170,446,448],{"id":447},"encryption-at-rest-and-in-transit","Encryption at rest and in transit",[11,450,451,454,455,458,459,462,463,466,467,470],{},[196,452,453],{},"Config values"," are stored in your local config file (",[208,456,457],{},"~\u002F.openclaw\u002Fopenclaw.json",") as plain JSON. The file is not encrypted at rest; it is protected by your operating system's file permissions. Credentials and API keys stored in ",[196,460,461],{},"MultiClaw Cloud"," receive an additional application-layer encryption with ",[196,464,465],{},"AES-256"," on top of AWS disk encryption. All connections to external MultiClaw services use ",[196,468,469],{},"TLS 1.2 or higher",", covering both HTTPS and WebSocket (WSS) traffic. Communication between the desktop app and the local OpenClaw gateway uses an unencrypted connection on localhost only — this traffic never leaves your machine.",[11,472,413,473,475],{},[307,474,315],{"href":314}," for the full encryption model.",[170,477,479],{"id":478},"local-first-data-storage","Local-first data storage",[11,481,482],{},"Your agents, conversations, and credentials are stored on your machine by default. When you're not connected to a workspace, everything stays local. When you connect to a workspace, conversation transcripts sync to MultiClaw Cloud automatically.",[11,484,413,485,489],{},[307,486,488],{"href":487},"\u002Fhelp\u002Fsecurity-privacy\u002Fdata-residency-and-storage","Data residency and storage"," for details on where your data lives.",[170,491,493],{"id":492},"credential-and-secret-storage","Credential and secret storage",[11,495,496,497,499],{},"Credentials and other sensitive values are stored in your local config file (",[208,498,457],{},") as plain JSON, protected by operating system file permissions. The desktop app does not send stored credentials to MultiClaw Cloud. Each credential is scoped to the context that needs it.",[11,501,413,502,504],{},[307,503,320],{"href":319}," for details on how credentials are stored, scoped, and managed.",[170,506,508],{"id":507},"sandboxed-desktop-app","Sandboxed desktop app",[11,510,511,512,515],{},"The desktop app is built on ",[196,513,514],{},"Tauri v2",", which enforces a capability-based permission model. The interface layer cannot access your filesystem or start processes on its own. Every sensitive operation goes through an explicitly declared Tauri command, limiting the potential damage from any interface-level vulnerability.",[11,517,413,518,522],{},[307,519,521],{"href":520},"\u002Fhelp\u002Fsecurity-privacy\u002Fdesktop-app-security","Desktop app security"," for details on the sandboxing model and capability declarations.",[170,524,526],{"id":525},"browser-extension-isolation","Browser extension isolation",[11,528,529],{},"The MultiClaw Chrome Extension content script is loaded on all pages, but it only captures and transmits interaction data when a recording session is active. Event listeners are registered when the extension loads; they check whether recording is active before capturing anything, and no data is collected or sent between sessions.",[11,531,413,532,536],{},[307,533,535],{"href":534},"\u002Fhelp\u002Fsecurity-privacy\u002Fbrowser-extension-security","Browser extension security"," for full details on what the extension accesses and when.",[170,538,540],{"id":539},"privacy-and-data-handling","Privacy and data handling",[11,542,543],{},"MultiClaw Desktop does not collect usage analytics or telemetry. If the app crashes, the crash log stays on your machine. Conversation content stays on your machine unless you choose to sync it to a workspace. MultiClaw Cloud stores only the account, workspace, and session data needed to operate the service.",[11,545,413,546,549],{},[307,547,540],{"href":548},"\u002Fhelp\u002Fsecurity-privacy\u002Fprivacy-and-data-handling"," for what data MultiClaw collects, how long it's retained, and your rights.",[170,551,553],{"id":552},"signed-updates-and-supply-chain-security","Signed updates and supply chain security",[11,555,556,557,560],{},"App updates are signed with ",[196,558,559],{},"minisign",". Before installing an update, the updater verifies the signature against the published public key and rejects any update with an invalid or missing signature. Third-party dependencies are pinned to exact versions, scanned for vulnerabilities, and reviewed before they ship.",[11,562,413,563,567],{},[307,564,566],{"href":565},"\u002Fhelp\u002Fsecurity-privacy\u002Fdependency-and-supply-chain-security","Dependency and supply chain security"," for the full scanning and review process.",[170,569,571],{"id":570},"allowed-external-connections","Allowed external connections",[11,573,574],{},"MultiClaw makes a fixed, documented set of outbound connections from your machine. Each connection has a specific purpose — API calls, real-time updates, AI execution, or update checks. No undocumented connections are made.",[11,576,413,577,580],{},[307,578,571],{"href":579},"\u002Fhelp\u002Fsecurity-privacy\u002Fallowed-external-connections"," for the full list of endpoints, protocols, and when each connection occurs.",[170,582,584],{"id":583},"incident-reporting","Incident reporting",[11,586,587],{},"If you discover a security vulnerability, you can report it directly to the MultiClaw security team. Reports are acknowledged within 24 hours and follow a structured triage and resolution process.",[11,589,413,590,594],{},[307,591,593],{"href":592},"\u002Fhelp\u002Fsecurity-privacy\u002Fincident-reporting-and-response","Incident reporting and response"," for how to submit a report and what to expect.",[170,596,598],{"id":597},"shared-responsibility","Shared responsibility",[11,600,601],{},"Security in MultiClaw is a shared effort. MultiClaw secures the infrastructure, encrypts data in transit, and hardens the app. You're responsible for protecting your credentials, managing workspace access, and configuring agents appropriately.",[11,603,413,604,607],{},[307,605,6],{"href":606},"\u002Fhelp\u002Fsecurity-privacy\u002Fshared-responsibility-model"," for a clear breakdown of what each party owns.",{"title":323,"searchDepth":324,"depth":324,"links":609},[610,611,612,613,614,615,616,617,618,619,620,621,622],{"id":380,"depth":324,"text":381},{"id":421,"depth":324,"text":422},{"id":434,"depth":324,"text":435},{"id":447,"depth":324,"text":448},{"id":478,"depth":324,"text":479},{"id":492,"depth":324,"text":493},{"id":507,"depth":324,"text":508},{"id":525,"depth":324,"text":526},{"id":539,"depth":324,"text":540},{"id":552,"depth":324,"text":553},{"id":570,"depth":324,"text":571},{"id":583,"depth":324,"text":584},{"id":597,"depth":324,"text":598},"MultiClaw protects your data through layered security, TLS encryption in transit, app sandboxing, and a no-telemetry policy.",{},1,"\u002Fsecurity-privacy\u002Fsecurity-overview",[352,628,629,353,630],"security-privacy\u002Fnetwork-security","security-privacy\u002Fbrowser-extension-security","security-privacy\u002Fprivacy-and-data-handling",{"title":310,"description":623},"security-overview","help\u002Fsecurity-privacy\u002F01.security-overview","3x0_VX5XDDMQT5kwODVWQnpjsjlxJfe0Lbg5V4Kim9I","Security overview MultiClaw protects your data through layered security, TLS encryption in transit, app sandboxing, and a no-telemetry policy.",{"id":637,"title":315,"body":638,"category":342,"description":1035,"draft":344,"extension":345,"meta":1036,"navigation":347,"order":1037,"path":1038,"relatedArticles":1039,"seo":1041,"slug":1042,"stem":1043,"updatedAt":1044,"__hash__":1045,"excerpt":1035,"searchText":1046},"help\u002Fhelp\u002Fsecurity-privacy\u002F04.data-encryption.md",{"type":8,"value":639,"toc":1021},[640,643,647,652,701,706,748,752,756,766,769,775,778,788,791,795,798,866,870,873,876,879,883,886,915,917,920,986,990,1002,1008,1014],[11,641,642],{},"MultiClaw encrypts credentials and API keys stored in MultiClaw Cloud and secures all external traffic in transit with TLS. Your local OpenClaw config file, conversation history, and agent definitions are stored as plain text on your device, protected only by OS file permissions.",[170,644,646],{"id":645},"protection-overview","Protection overview",[11,648,649],{},[196,650,651],{},"On your device:",[15,653,654,664],{},[18,655,656],{},[21,657,658,661],{},[24,659,660],{},"Data",[24,662,663],{},"Protection at rest",[31,665,666,676,684,694],{},[21,667,668,673],{},[36,669,670,671],{},"API keys and credentials in ",[208,672,457],{},[36,674,675],{},"Not encrypted (plain JSON, OS file permissions)",[21,677,678,681],{},[36,679,680],{},"Desktop app authentication bearer token",[36,682,683],{},"Not encrypted (WebView local storage)",[21,685,686,692],{},[36,687,688,689],{},"Conversations in ",[208,690,691],{},"~\u002F.openclaw\u002Fconversations\u002F",[36,693,675],{},[21,695,696,699],{},[36,697,698],{},"Agent definitions, skill files, workflow recordings",[36,700,675],{},[11,702,703],{},[196,704,705],{},"In MultiClaw Cloud (when connected to a workspace):",[15,707,708,716],{},[18,709,710],{},[21,711,712,714],{},[24,713,660],{},[24,715,663],{},[31,717,718,726,734,741],{},[21,719,720,723],{},[36,721,722],{},"LLM API keys and instance credentials",[36,724,725],{},"AWS disk encryption + application-layer AES-256",[21,727,728,731],{},[36,729,730],{},"Synced conversations",[36,732,733],{},"AWS disk encryption",[21,735,736,739],{},[36,737,738],{},"Synced agent definitions and skill files",[36,740,733],{},[21,742,743,746],{},[36,744,745],{},"Workspace and account metadata",[36,747,733],{},[170,749,751],{"id":750},"encryption-at-rest","Encryption at rest",[188,753,755],{"id":754},"local-device","Local device",[11,757,758,759,761,762,765],{},"Your local OpenClaw config file (",[208,760,457],{},") is stored as ",[196,763,764],{},"plain JSON"," on disk. It is not encrypted. Access is limited by OS file permissions. Only your user account can read the file.",[11,767,768],{},"The OpenClaw runtime stores all configuration as plain JSON files. MultiClaw reads and writes these files but does not apply its own encryption layer.",[11,770,771,772,774],{},"The desktop app's authentication bearer token is stored in the WebView's local storage. The bearer token is separate from the gateway workspace auth token, which is stored in ",[208,773,457],{}," alongside the API keys. Neither token is encrypted at rest on the local device.",[188,776,461],{"id":777},"multiclaw-cloud",[11,779,780,781,784,785,787],{},"Workspace data stored in MultiClaw Cloud is hosted on ",[196,782,783],{},"AWS",", which encrypts storage volumes at rest using AWS-managed encryption keys. Sensitive values — such as LLM API keys and instance credentials — receive an additional layer of protection: they are encrypted at the application layer using ",[196,786,465],{}," before being stored. When MultiClaw Cloud syncs your configuration to a cloud desktop instance, it also encrypts API keys and credentials with AES-256-GCM in the sync payload, using a key derived from your instance token.",[11,789,790],{},"Application-layer encryption keys for credentials are managed by MultiClaw's infrastructure. Workspace members do not hold or control these keys.",[170,792,794],{"id":793},"encryption-in-transit","Encryption in transit",[11,796,797],{},"All traffic between MultiClaw components and external services travels over encrypted connections. The only exception is the link between the desktop app and the local OpenClaw gateway, which uses an unencrypted connection on localhost. This traffic never leaves your machine.",[15,799,800,810],{},[18,801,802],{},[21,803,804,807],{},[24,805,806],{},"Connection",[24,808,809],{},"Protocol",[31,811,812,823,834,845,855],{},[21,813,814,817],{},[36,815,816],{},"Desktop app ↔ MultiClaw Cloud (HTTP)",[36,818,819,822],{},[196,820,821],{},"HTTPS",": TLS 1.2 minimum, TLS 1.3 preferred",[21,824,825,828],{},[36,826,827],{},"Gateway ↔ MultiClaw Cloud (WebSocket)",[36,829,830,833],{},[196,831,832],{},"WSS"," (WebSocket Secure): TLS-encrypted",[21,835,836,839],{},[36,837,838],{},"Desktop app ↔ local OpenClaw gateway",[36,840,841,844],{},[196,842,843],{},"WS\u002FHTTP on localhost",": unencrypted, never leaves your machine",[21,846,847,850],{},[36,848,849],{},"Local gateway → LLM provider API",[36,851,852,854],{},[196,853,821],{},": TLS-encrypted",[21,856,857,860],{},[36,858,859],{},"Cloud desktop viewer (WebRTC)",[36,861,862,865],{},[196,863,864],{},"DTLS-SRTP",": standard encryption for peer-to-peer media",[170,867,869],{"id":868},"what-is-not-encrypted-locally","What is not encrypted locally",[11,871,872],{},"The local files listed in the protection overview use OS file permissions as their only protection. That's sufficient against remote access, but it doesn't protect against physical access to your device.",[11,874,875],{},"If your device is lost, stolen, or accessed by someone with your OS credentials, these files are readable. Full-disk encryption closes this gap.",[11,877,878],{},"When you connect to a workspace, conversations, agent definitions, and skill files sync to MultiClaw Cloud, where they receive AWS disk encryption.",[188,880,882],{"id":881},"enable-full-disk-encryption","Enable full-disk encryption",[11,884,885],{},"Full-disk encryption protects all files on your device, including the plain-text data listed above, from unauthorized physical access.",[386,887,888,898,909],{},[389,889,890,893,894,897],{},[196,891,892],{},"macOS",": Open ",[196,895,896],{},"System Settings → Privacy & Security → FileVault"," and turn FileVault on.",[389,899,900,893,903,905,906,908],{},[196,901,902],{},"Windows",[196,904,235],{},", or search for ",[196,907,239],{}," on Pro and Enterprise editions.",[389,910,911,914],{},[196,912,913],{},"Linux",": Most distributions offer LUKS encryption during installation. If your disk is not already encrypted, back up your data and reinstall with the encryption option enabled.",[170,916,598],{"id":597},[11,918,919],{},"MultiClaw encrypts your credentials and API keys in the cloud. Protecting your local device is your responsibility.",[15,921,922,935],{},[18,923,924],{},[21,925,926,929,932],{},[24,927,928],{},"Area",[24,930,931],{},"Who handles it",[24,933,934],{},"Protection",[31,936,937,947,957,967,977],{},[21,938,939,942,944],{},[36,940,941],{},"API keys and credentials in MultiClaw Cloud",[36,943,41],{},[36,945,946],{},"AES-256 application encryption + AWS disk encryption",[21,948,949,952,954],{},[36,950,951],{},"Cloud storage volumes",[36,953,783],{},[36,955,956],{},"AWS-managed disk encryption",[21,958,959,962,964],{},[36,960,961],{},"Traffic between MultiClaw and external services",[36,963,41],{},[36,965,966],{},"TLS 1.2+ for HTTP, WSS for WebSocket",[21,968,969,972,974],{},[36,970,971],{},"Local config, agent files, and conversations",[36,973,91],{},[36,975,976],{},"OS file permissions + full-disk encryption",[21,978,979,982,984],{},[36,980,981],{},"Authentication tokens on your device",[36,983,91],{},[36,985,976],{},[188,987,989],{"id":988},"what-you-can-verify","What you can verify",[11,991,992,995,996,998,999,321],{},[196,993,994],{},"Full-disk encryption",": Check your OS settings using the instructions above. On macOS, look for \"FileVault: On\" in ",[196,997,231],{},". On Windows, look for \"Device encryption is on\" in ",[196,1000,1001],{},"Settings → Privacy & security",[11,1003,1004,1007],{},[196,1005,1006],{},"Transit encryption",": All connections from the desktop app and Gateway to MultiClaw Cloud use HTTPS and WSS. You can confirm this with browser developer tools or a network monitoring tool — all external traffic will show TLS certificates issued to MultiClaw domains.",[11,1009,1010,1013],{},[196,1011,1012],{},"Cloud encryption at rest",": Application-layer encryption of cloud-stored credentials is handled transparently by MultiClaw's infrastructure. You cannot inspect it directly — this is a trust boundary inherent to any cloud-hosted service.",[1015,1016,1018],"callout",{"type":1017},"tip",[11,1019,1020],{},"MultiClaw Cloud encrypts credentials and API keys stored in its database. Local files on your device — including config, conversations, and agent data — are not encrypted by MultiClaw. Full-disk encryption is the most effective way to protect them.",{"title":323,"searchDepth":324,"depth":324,"links":1022},[1023,1024,1028,1029,1032],{"id":645,"depth":324,"text":646},{"id":750,"depth":324,"text":751,"children":1025},[1026,1027],{"id":754,"depth":330,"text":755},{"id":777,"depth":330,"text":461},{"id":793,"depth":324,"text":794},{"id":868,"depth":324,"text":869,"children":1030},[1031],{"id":881,"depth":330,"text":882},{"id":597,"depth":324,"text":598,"children":1033},[1034],{"id":988,"depth":330,"text":989},"MultiClaw Cloud encrypts credentials and API keys with AES-256 and secures all traffic with TLS; local files are plain JSON protected only by OS file permissions.",{},4,"\u002Fsecurity-privacy\u002Fdata-encryption",[351,628,353,1040],"security-privacy\u002Fdata-residency-and-storage",{"title":315,"description":1035},"data-encryption","help\u002Fsecurity-privacy\u002F04.data-encryption","2026-03-31","PS01Cx_PLkHKehAf_-QLVhM6_dJhqwlHYiJ4B5fUh18","Data encryption MultiClaw Cloud encrypts credentials and API keys with AES-256 and secures all traffic with TLS; local files are plain JSON protected only by OS file permissions.",{"id":1048,"title":320,"body":1049,"category":342,"description":1339,"draft":344,"extension":345,"meta":1340,"navigation":347,"order":1341,"path":1342,"relatedArticles":1343,"seo":1345,"slug":1346,"stem":1347,"updatedAt":1044,"__hash__":1348,"excerpt":1339,"searchText":1349},"help\u002Fhelp\u002Fsecurity-privacy\u002F09.how-credentials-and-secrets-are-stored.md",{"type":8,"value":1050,"toc":1330},[1051,1054,1148,1151,1154,1160,1163,1166,1170,1180,1189,1192,1198,1218,1221,1227,1234,1237,1240,1251,1255,1258,1273,1276,1282,1286,1289,1303,1305,1308,1322],[11,1052,1053],{},"MultiClaw stores your LLM API keys encrypted in MultiClaw Cloud, auth tokens in local config files protected by OS file permissions, and session tokens in memory only. The table below shows where each secret lives, how it's protected, and how to clear it.",[15,1055,1056,1072],{},[18,1057,1058],{},[21,1059,1060,1063,1066,1069],{},[24,1061,1062],{},"Secret",[24,1064,1065],{},"Where it lives",[24,1067,1068],{},"Encrypted at rest",[24,1070,1071],{},"Cleared by",[31,1073,1074,1088,1106,1121,1134],{},[21,1075,1076,1079,1082,1085],{},[36,1077,1078],{},"LLM API keys",[36,1080,1081],{},"MultiClaw Cloud database",[36,1083,1084],{},"Yes — AES-256 application-level encryption",[36,1086,1087],{},"Removing the key from your agent's settings",[21,1089,1090,1093,1100,1103],{},[36,1091,1092],{},"LLM API keys (cloud desktop sync)",[36,1094,1095,1096,1099],{},"Cloud desktop instance config (prefixed ",[208,1097,1098],{},"enc:",")",[36,1101,1102],{},"Yes — AES-256-GCM per-instance key",[36,1104,1105],{},"Instance reset or re-sync from MultiClaw Cloud",[21,1107,1108,1111,1115,1118],{},[36,1109,1110],{},"Gateway workspace auth token",[36,1112,1113],{},[208,1114,457],{},[36,1116,1117],{},"No — OS file permissions only",[36,1119,1120],{},"Removing the user from the workspace",[21,1122,1123,1126,1129,1131],{},[36,1124,1125],{},"Desktop app bearer token",[36,1127,1128],{},"Desktop app WebView local storage",[36,1130,1117],{},[36,1132,1133],{},"Signing out of the desktop app",[21,1135,1136,1139,1142,1145],{},[36,1137,1138],{},"WebSocket session tokens",[36,1140,1141],{},"Memory only — not written to disk",[36,1143,1144],{},"N\u002FA",[36,1146,1147],{},"Connection close or token expiry",[170,1149,1078],{"id":1150},"llm-api-keys",[11,1152,1153],{},"MultiClaw Cloud stores your LLM provider API keys in its database, encrypted at rest with application-level encryption.",[11,1155,1156,1157,1159],{},"When MultiClaw syncs your configuration to a cloud desktop, it re-encrypts each API key with AES-256-GCM using a per-instance key derived through HKDF-SHA256. MultiClaw writes the encrypted value (prefixed ",[208,1158,1098],{},") to the instance's local config. At runtime, the gateway decrypts the key in memory to call your LLM provider.",[11,1161,1162],{},"The desktop app and gateway are designed not to log configuration values. Under normal operation, keys do not appear in diagnostic logs.",[11,1164,1165],{},"To add, update, or remove an API key, open your agent's settings in MultiClaw Cloud. Changes sync to connected cloud desktops on the next configuration push. Removing a key from MultiClaw Cloud deletes the encrypted copy from every synced instance.",[170,1167,1169],{"id":1168},"workspace-auth-token","Workspace auth token",[11,1171,1172,1173,1175,1176,1179],{},"When you sign in, MultiClaw Cloud issues a long-lived auth token stored in ",[208,1174,457],{}," as a plain JSON string. The gateway uses this token to authenticate WebSocket connections to MultiClaw Cloud. The token is not encrypted at rest. OS file permissions on ",[208,1177,1178],{},"~\u002F.openclaw\u002F"," control read access.",[1015,1181,1183],{"type":1182},"note",[11,1184,1185,1186,1188],{},"OS file permissions mean that only your operating system user account is intended to read the contents of ",[208,1187,1178],{},". If you share an OS-level user account with other people, they may be able to read the token. Treat your OS user account as the trust boundary for this file.",[11,1190,1191],{},"The token is scoped to your user account and is not designed to permit access to another user's data.",[11,1193,1194,1195,1197],{},"To revoke access after a device is lost, a workspace owner can remove the user on the ",[196,1196,258],{}," page in MultiClaw Cloud. MultiClaw does not currently offer per-device session revocation.",[1015,1199,1200],{"type":1017},[11,1201,1202,1203,1205,1206,1209,1210,1213,1214,1217],{},"On macOS and Linux, verify your ",[208,1204,1178],{}," directory permissions by running ",[208,1207,1208],{},"ls -ld ~\u002F.openclaw\u002F",". The output should show ",[208,1211,1212],{},"drwx------"," (owner-only access). On Windows, right-click the folder, open ",[196,1215,1216],{},"Properties → Security",", and confirm only your user account has read access.",[170,1219,1125],{"id":1220},"desktop-app-bearer-token",[11,1222,1223,1224,1226],{},"The desktop app uses a separate bearer token for its HTTP and real-time API calls to MultiClaw Cloud. It stores this token in its WebView local storage, not in ",[208,1225,457],{},", and does not encrypt it at rest.",[11,1228,1229,1230,1233],{},"This bearer token is distinct from the gateway workspace auth token. The gateway reads ",[208,1231,1232],{},"openclaw.json"," for its WebSocket connection, while the desktop app holds its own bearer token. Signing out of the desktop app clears the bearer token from local storage.",[170,1235,1138],{"id":1236},"websocket-session-tokens",[11,1238,1239],{},"Each WebSocket connection uses a short-lived HMAC-SHA256-signed token generated fresh for every session. These tokens exist in memory only while the connection is active and are not written to disk.",[11,1241,1242,1243,1246,1247,1250],{},"Token lifetime depends on the connection type: user session tokens expire after ",[196,1244,1245],{},"4 hours",", and daemon (cloud desktop) connection tokens expire after ",[196,1248,1249],{},"24 hours",". When a token expires, the system generates a new one automatically on reconnect.",[170,1252,1254],{"id":1253},"if-a-device-is-lost-or-compromised","If a device is lost or compromised",[11,1256,1257],{},"If you lose a device or suspect unauthorized access, take these steps in order:",[1259,1260,1261,1267,1270],"ol",{},[389,1262,1263,1264,1266],{},"Ask a workspace owner to remove your user account on the ",[196,1265,258],{}," page in MultiClaw Cloud. This revokes the gateway workspace auth token stored on the device.",[389,1268,1269],{},"Sign in to MultiClaw Cloud from a trusted device and rotate any LLM API keys your agents use. Open your agent's settings, remove the current key, and add a new one.",[389,1271,1272],{},"If you use the same password elsewhere, change it. MultiClaw Cloud stores only a bcrypt hash of your password, but credential reuse remains a risk outside MultiClaw.",[11,1274,1275],{},"The desktop app bearer token is cleared when you sign out, but you cannot remotely sign out a lost device. Removing the user from the workspace is the primary revocation mechanism.",[1015,1277,1279],{"type":1278},"warning",[11,1280,1281],{},"MultiClaw does not currently offer per-device session revocation. Removing a user from the workspace revokes all of that user's tokens across every device.",[170,1283,1285],{"id":1284},"what-multiclaw-does-not-store","What MultiClaw does not store",[11,1287,1288],{},"MultiClaw does not retain the following values in their original form:",[386,1290,1291,1297],{},[389,1292,1293,1296],{},[196,1294,1295],{},"Plaintext passwords",": MultiClaw Cloud stores only a bcrypt hash of your password. Neither MultiClaw Cloud nor the desktop app is designed to retain the original password.",[389,1298,1299,1302],{},[196,1300,1301],{},"Browser cookies and session tokens",": MultiClaw is not designed to store cookies or session tokens from pages recorded during a workflow.",[170,1304,186],{"id":185},[11,1306,1307],{},"MultiClaw encrypts API keys at rest, scopes tokens to your user account, and keeps session tokens short-lived. The protections above assume:",[386,1309,1310,1313,1316,1319],{},[389,1311,1312],{},"Your OS user account is not shared with other people.",[389,1314,1315],{},"Your device has full-disk encryption enabled (FileVault on macOS, BitLocker on Windows, LUKS on Linux).",[389,1317,1318],{},"You sign out of the desktop app before lending or decommissioning a device.",[389,1320,1321],{},"You keep your device locked when unattended.",[11,1323,1324,1325,1327,1328,321],{},"Without these measures, unencrypted tokens in ",[208,1326,1232],{}," and local storage are accessible to anyone with physical access to the device. For a full breakdown of where platform protections end and yours begin, see ",[307,1329,6],{"href":606},{"title":323,"searchDepth":324,"depth":324,"links":1331},[1332,1333,1334,1335,1336,1337,1338],{"id":1150,"depth":324,"text":1078},{"id":1168,"depth":324,"text":1169},{"id":1220,"depth":324,"text":1125},{"id":1236,"depth":324,"text":1138},{"id":1253,"depth":324,"text":1254},{"id":1284,"depth":324,"text":1285},{"id":185,"depth":324,"text":186},"API keys are encrypted in MultiClaw Cloud, auth tokens rely on OS file permissions, and session tokens live in memory only.",{},9,"\u002Fsecurity-privacy\u002Fhow-credentials-and-secrets-are-stored",[352,351,1344,1040],"security-privacy\u002Fauthentication-and-login-security",{"title":320,"description":1339},"how-credentials-and-secrets-are-stored","help\u002Fsecurity-privacy\u002F09.how-credentials-and-secrets-are-stored","zk_b1Ew5T-ezUvHLnuGENrO82-pDLoeQaYbEfcU6ESI","How credentials and secrets are stored API keys are encrypted in MultiClaw Cloud, auth tokens rely on OS file permissions, and session tokens live in memory only.",1778463888382]