Safety
Safety Guidelines
Practical guidance for using PawOS's Companion Runtime, Browser Automation, and Desktop Automation responsibly.
Last updated: 31 August 2026
1. Review before confirming
PawOS shows a plan and asks for your confirmation before a destructive or production-impacting action runs. Read what's actually being proposed before confirming — the Confirmation Gate only protects you if you use it.
2. Scope your Organization's approval policies
In a Team or Enterprise Organization Workspace, configure approval policies for genuinely high-risk action types (production deploys, credential access, member/role changes) rather than everything, so approvals stay meaningful rather than routine rubber-stamping.
3. Point automation only at what you're authorized to touch
Browser Automation and Desktop Automation can act on real accounts, files, and systems. Only direct them at accounts, devices, and systems you own or are explicitly authorized to use — the same standard that applies to any automated tooling.
4. The Companion Runtime is not a substitute for adult supervision
The Companion Runtime (the 3D companion, including its voice and conversational features) is a software feature, not a substitute for parental or adult supervision. It is not designed or intended for unsupervised use by children.
5. Get consent before recording
Communication capture (meeting/call recording) requires your explicit consent inside PawOS and, where applicable, the consent of other participants under your jurisdiction's recording-consent laws. You are responsible for obtaining consent from other participants where required.
6. Contact
General questions about this document: legal@revantaai.com. Privacy and data-protection requests: privacy@revantaai.com. Security reports: security@revantaai.com, following our Vulnerability Disclosure Policy. See also our Grievance Officer contact above where this document includes one.
7. Changes to this document
We may revise this document as PawOS's features or applicable law change. The date at the top of this page reflects the version currently in effect. Where a change is material, we will note it in our Changelog and, where required by law, notify affected users directly (for example, by email or an in-app notice) before the change takes effect. Continuing to use PawOS after a revised document takes effect constitutes acceptance of it.