Access control procedures established
Employee access follows business need through onboarding, role changes and offboarding, with approval and revocation when no longer needed.
Trust Center
Review how OneShot protects customer data, controls access and constrains agent actions. Explore our security controls, see who processes data on our behalf, and request documents for your security review.
How OneShot handles attacks on agentsAccess to production systems, network boundaries, encryption keys and operational monitoring.
Employee access follows business need through onboarding, role changes and offboarding, with approval and revocation when no longer needed.
Production database access is restricted to authorized personnel and service identities with a documented business need.
Production database access uses attributable authentication for authorized administrators and service identities.
Only authorized identities can manage encryption keys. Sensitive fields use envelope encryption backed by Google Cloud KMS.
Only authorized personnel can administer network security rules that control access to production infrastructure.
Network boundaries and service authorization separate production workloads and restrict communication to approved access paths.
Intrusion detection monitors suspicious activity and supports investigation and response when security alerts are raised.
Google Cloud Logging records service logs; organization audit history covers selected changes. Coverage varies by service and event.
Network firewall rules are reviewed and updated to maintain appropriate access restrictions for production systems.
Network filtering restricts unauthorized access to production systems and services through network access controls.
Employees must use multi-factor authentication when accessing production systems remotely, in addition to their sign-in credentials.
Remote administration of production systems uses encrypted connections, including HTTPS and SSH, to protect access in transit.
Network and system hardening standards guide secure configuration and ongoing maintenance of production infrastructure.
Infrastructure performance and service health are monitored, with alerts supporting investigation of operational issues.
People, devices and inventories, including the boundary between OneShot and its cloud providers.
Visitor access follows authorization and supervision procedures. Hosting providers operate cloud data-center visitor controls.
Asset disposal procedures cover secure information removal. Hosting providers manage disposal of physical cloud infrastructure.
Portable media containing sensitive information is encrypted according to the requirements for handling that data.
Password requirements apply to relevant accounts and authentication systems, in line with the established password policy.
An inventory of production systems and resources is maintained to support ownership, access management and operational oversight.
Protection of customer data and review of the controls supporting the product.
Internal assessments review security controls, identify gaps and track corrective actions to address those findings.
Managed cloud storage encrypts customer data at rest. Supported sensitive application fields also use envelope encryption.
Public endpoints use HTTPS. Production access and supported service integrations also use encrypted connections.
Vulnerability management and system monitoring procedures support identification, assessment and remediation of security issues.
Access reviews, change management, incident response, risk ownership and vendor oversight.
Physical access is restricted by business need. Hosting providers manage physical access to their cloud facilities.
Cloud hosting providers manage and review physical access to their data centers under their infrastructure security programs.
Access rights are reviewed for ongoing business need, with inappropriate or obsolete permissions identified for removal.
Access to restricted systems requires an approved request before permissions are granted to the requesting person.
Production configuration is maintained in version control and applied to production through managed deployment workflows.
The development lifecycle includes code review, automated checks and controlled deployment for changes to the product.
Exercises test the incident response plan to assess readiness, identify gaps and inform improvements to response procedures.
Incident response policies define how security incidents are identified, escalated, investigated and brought to resolution.
Management responsibilities define ownership of information security, oversight of controls and escalation of issues.
Incident management procedures guide response, tracking, resolution and follow-up review throughout the incident lifecycle.
Risk assessment objectives define the scope and evaluation criteria used to assess risks to systems and information.
Risk assessments identify and evaluate security risks, helping determine which mitigation actions should take priority.
The risk management program tracks identified risks, assigns responsibility and supports decisions about their treatment.
Security roles and responsibilities are assigned to relevant personnel and communicated so each person understands their role.
Product documentation and customer-facing materials describe OneShot services, security capabilities and applicable responsibilities.
Relevant system changes are communicated to affected personnel and customers through channels appropriate to the change.
The system description covers service scope, components and controls for SOC 2 review. Request it from [email protected].
Agreements with applicable third parties set out their obligations for information security, privacy and confidentiality.
Vendor procedures assess relevant providers and maintain oversight of their security and data-processing responsibilities.

Classification, handling, retention and disposal of company and customer information.
The data classification policy defines categories of information and the handling requirements for each level of sensitivity.
Admins set retention for eligible content. Financial, receipt and audit records, backups and provider copies follow separate rules.

Additional controls for agent actions, execution isolation and verifiable records.
Configured limits are checked before payment authorization; compute goals reserve budget first. Limits constrain spending, not action quality.
Configured policies allow, deny or require approval for supported actions. Approvals are request-specific, expire and can be used once.
Ed25519 signatures and public keys enable offline receipt verification. Signatures verify recorded actions and outcomes, not decision quality.
Compute runs in isolated sandboxes with short-lived task tokens. Model and vendor credentials stay in services handling authorized requests.
Additional controls for backup integrity, freshness and controlled restoration.
Weekly PostgreSQL and Redis backups go to a separate cloud project. The newest four successful sets are kept; they are not atomic platform snapshots.
Scheduled checks monitor backup freshness; restore tooling checks integrity and isolated restores. Neither proves complete service recovery.
Restores use separate targets, reconcile queues and reapply deletion and retention rules. Configuration, credentials and keys are also required.
Verify it yourself
Execution receipts are signed with Ed25519. Verify a receipt offline with our public key, using the SDK's verifyReceipt() or the oneshot-verify-receipt CLI. A signature verifies the record; it does not judge the action.
Use the compliance portal to request restricted documents. Access is subject to review and any applicable confidentiality terms. Contact our security team to discuss the scope of your review.
Contact us for SOC 2 report access and scope.
A Data Processing Agreement is available on request. Email us and we will send it.
Read about organization sign-in settings and support-assisted configuration.
Explore how OneShot handles attacks on agents and where each safeguard applies.
Subprocessors
Our published subprocessor list describes providers and their purposes. The providers involved in your workflow depend on the tools and integrations you use. Contact us to discuss specific data-processing requirements.
Product analytics for the API and dashboard.
Tracing of model calls for debugging and quality.
Cloud hosting and AI model inference for agent workflows.
Hosting, databases, queues and storage for the OneShot API and workers.
Cloud hosting and AI model inference for agent workflows.
Hosting and domains for sites built by agents.
Agent mailboxes on branded domains (send and receive email).
Models for agent reasoning and content safety.
Alternate executor for long-running research tasks.
AI models and social platform integrations for agent workflows.
Models for content safety checks and voice.
Model routing for agent reasoning, research and drafting.
Grok models for agent reasoning, research and drafting.
SMS sending and phone numbers.
DNS, CDN and DDoS protection; DNS for customer sending domains.
Found a security issue? Email us what you found and the steps to reproduce it. We acknowledge every report, and we ask for time to fix the issue before you share it publicly. Please do not access other customers' data or disrupt the service while testing.
Report a vulnerability