diff --git a/docs/install/hetzner.md b/docs/install/hetzner.md
index 7ca46ff7cd9..9baf90278b8 100644
--- a/docs/install/hetzner.md
+++ b/docs/install/hetzner.md
@@ -17,6 +17,14 @@ Run a persistent OpenClaw Gateway on a Hetzner VPS using Docker, with durable st
 If you want “OpenClaw 24/7 for ~$5”, this is the simplest reliable setup.
 Hetzner pricing changes; pick the smallest Debian/Ubuntu VPS and scale up if you hit OOMs.
 
+Security model reminder:
+
+- Company-shared agents are fine when everyone is in the same trust boundary and the runtime is business-only.
+- Keep strict separation: dedicated VPS/runtime + dedicated accounts; no personal Apple/Google/browser/password-manager profiles on that host.
+- If users are adversarial to each other, split by gateway/host/OS user.
+
+See [Security](/gateway/security) and [VPS hosting](/vps).
+
 ## What are we doing (simple terms)?
 
 - Rent a small Linux server (Hetzner VPS)
diff --git a/docs/vps.md b/docs/vps.md
index f0b1f7d7777..adb88403890 100644
--- a/docs/vps.md
+++ b/docs/vps.md
@@ -34,6 +34,16 @@ deployments work at a high level.
 Remote access: [Gateway remote](/gateway/remote)  
 Platforms hub: [Platforms](/platforms)
 
+## Shared company agent on a VPS
+
+This is a valid setup when the users are in one trust boundary (for example one company team), and the agent is business-only.
+
+- Keep it on a dedicated runtime (VPS/VM/container + dedicated OS user/accounts).
+- Do not sign that runtime into personal Apple/Google accounts or personal browser/password-manager profiles.
+- If users are adversarial to each other, split by gateway/host/OS user.
+
+Security model details: [Security](/gateway/security)
+
 ## Using nodes with a VPS
 
 You can keep the Gateway in the cloud and pair **nodes** on your local devices