Legal
Platform Privacy Policy
How Optimus Labs processes data for customers of the Optimus platform: what the sensor collects, what it redacts, where data lives, who processes it, and how it is secured and deleted.
Effective November 21, 2026. See also the Website Privacy Policy.
1. Who we are and how to reach us
Optimus AI, Inc. (Optimus Labs), Oakville, Ontario, Canada, is responsible for this policy. The person accountable for privacy is Nipun Gupta, CEO.
Privacy and security requests: security@optimuslabs.io.
2. Our role
Our customers decide which devices and people the Optimus sensor covers. For that data the customer is the controller (or business) and Optimus Labs is its processor (or service provider), acting only on the customer's documented instructions under our customer agreement and data processing agreement (DPA).
If you are an employee of one of our customers, your employer's privacy notice explains why it monitors AI agent use. You can send requests to your employer or to us, and we will pass them on and help your employer answer.
3. What the sensor collects
To build the agent asset inventory, check posture and detect risky agent behaviour, the sensor sends:
- Usernames of the people running AI agents
- Hostnames of the devices the sensor runs on
- IP addresses of those devices
- File paths that agents, SKILLs, MCP servers and plugins read, write or run
- Prompts sent to and through AI agents
- Names and versions of installed software, agents, SKILLs, MCP servers and plugins
4. What is redacted by default
Before data leaves the device, the sensor redacts these kinds of sensitive data by default. Prompts and file contents can still contain other personal information, so customers should set their own monitoring scope.
Secret types
- ANTHROPIC_KEY
- AWS_ACCESS_KEY
- BASIC_AUTH
- BEARER_TOKEN
- BRAVE_KEY
- GITHUB_TOKEN
- GOOGLE_API_KEY
- HUGGINGFACE_TOKEN
- JWT
- NPM_TOKEN
- OPENAI_KEY
- PERPLEXITY_KEY
- PRIVATE_KEY
- PYPI_TOKEN
- SENDGRID_KEY
- SLACK_TOKEN
- STRIPE_KEY
- URL_CREDENTIALS
Field names
- api_key
- apikey
- secret
- token
- password
- passwd
- credential
- private_key
- secret_key
- signing_key
- encryption_key
- access_key
- authorization
- token_cache
- *_key
Field name endings
- *tokens
- *secrets
- *credentials
- *api_keys
Whole containers
- env
- environment
- headers
- http_headers
5. How we use it
- To discover and govern agent assets and organise them by owner.
- To analyse agent configuration and posture against the OWASP Top 10 for Agentic Applications.
- To detect, alert on and, where the customer chooses, block risky agent activity.
- To support, secure and fix the service.
Some analysis is done by AI models from Anthropic. Customer data is never used to train AI models, by us or by Anthropic.
We do not sell customer data or use it for advertising.
6. Subprocessors
We use the subprocessors below. Each is bound by written data protection terms. We give customers notice before adding or replacing a subprocessor, so they can object.
| Vendor | Purpose |
|---|---|
| AWS | Hosting and storage of platform data (United States (US West, US East)) |
| Anthropic | AI analysis of agent activity. Never used to train models |
| Supabase | Application database and authentication |
| Lovable | Hosting of web interfaces |
| Attio | Customer account and contact records |
7. Security controls
Our controls are designed to align with the AICPA SOC 2 Trust Services Criteria and ISO/IEC 27001:2022. No SOC 2 report or ISO 27001 certificate has been issued yet.
| Control | SOC 2 | ISO 27001 |
|---|---|---|
| Encryption: TLS 1.2 or higher in transit, AES-256 at rest, keys managed in AWS Key Management Service (KMS). | Security (CC6) | A.8.24 |
| Each customer's data is logically separated and scoped to that customer's tenant. | Confidentiality (C1) | A.8.3, A.5.15 |
| Role-based access for staff, least privilege, server-side checks of admin roles and periodic re-verification of admin sessions. | Security (CC6.1 to CC6.3) | A.5.15, A.5.18, A.8.2 |
| Administrative and security events are logged and monitored. | Security (CC7.2) | A.8.15, A.8.16 |
| Vendors are reviewed before use and bound by data protection terms. | Security (CC9.2) | A.5.19 to A.5.22 |
| Changes are reviewed and tested before release. | Processing integrity (CC8.1) | A.8.32 |
| The service runs in two AWS US regions, US West and US East. | Availability (A1.2) | A.8.13, A.5.30 |
| Incidents follow a documented response process, and affected customers are notified within 72 hours of a confirmed breach. | Security (CC7.3 to CC7.5) | A.5.24 to A.5.28 |
| Data is kept for 180 days and then deleted. | Privacy (P4) | A.5.33, A.8.10 |
8. Retention and deletion
Platform data is kept for 180 days and then deleted. When a customer leaves, their data is deleted within 180 days, or sooner on written request, except where the law requires us to keep it.
9. Your privacy rights
Depending on where you live, you can ask us to confirm whether we hold your personal information, give you a copy, correct it, delete it, restrict or object to its use, or move it to another provider. You can withdraw consent at any time where we rely on consent. For data we process on a customer's behalf, we help the customer answer your request.
Email security@optimuslabs.io. We verify your identity before acting. We answer within 30 days for residents of the EU, the UK and Quebec, and within 45 days for everyone else. If we need more time where the law allows it, we tell you why before the deadline.
We do not sell personal information or share it for cross-context behavioural advertising, and we do not treat you differently for using your rights. California and other US state residents may use an authorised agent and may appeal a decision by replying to our answer.
Complaints
Please contact us first so we can fix the problem. You can also complain to the Office of the Privacy Commissioner of Canada, the Commission d'accès à l'information du Québec, your EU data protection authority, or the UK Information Commissioner's Office.
10. International transfers
Optimus AI, Inc. (Optimus Labs) is based in Canada. Platform data is stored in the United States (AWS, US West and US East regions) and may be processed by the vendors listed in this policy in the United States.
For personal information from the EU and the UK we rely on the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum, or another valid transfer mechanism. Quebec residents' information is transferred only after a privacy impact assessment of the destination.
EU and UK representative (GDPR Article 27): not yet appointed. Until one is named here, contact us directly at security@optimuslabs.io.
11. Changes to this policy
We review this policy at least once a year and whenever our processing changes. We post the new version here with a new effective date. Customers are told about material changes by email before they take effect.

