Trust Center

your agent acts.
you set the limits.

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 agents
Subprocessors
17
Receipts
Ed25519
Spend limits
Before execution
Provider secrets
Managed storage

Infrastructure security

Access to production systems, network boundaries, encryption keys and operational monitoring.

Implemented

Access control procedures established

Employee access follows business need through onboarding, role changes and offboarding, with approval and revocation when no longer needed.

Implemented

Production database access restricted

Production database access is restricted to authorized personnel and service identities with a documented business need.

Implemented

Unique production database authentication enforced

Production database access uses attributable authentication for authorized administrators and service identities.

Implemented

Encryption key access restricted

Only authorized identities can manage encryption keys. Sensitive fields use envelope encryption backed by Google Cloud KMS.

Implemented

Firewall access restricted

Only authorized personnel can administer network security rules that control access to production infrastructure.

Implemented

Network segmentation implemented

Network boundaries and service authorization separate production workloads and restrict communication to approved access paths.

Implemented

Intrusion detection system utilized

Intrusion detection monitors suspicious activity and supports investigation and response when security alerts are raised.

Implemented

Log management utilized

Google Cloud Logging records service logs; organization audit history covers selected changes. Coverage varies by service and event.

Implemented

Network firewalls reviewed

Network firewall rules are reviewed and updated to maintain appropriate access restrictions for production systems.

Implemented

Network firewalls utilized

Network filtering restricts unauthorized access to production systems and services through network access controls.

Implemented

Remote access MFA enforced

Employees must use multi-factor authentication when accessing production systems remotely, in addition to their sign-in credentials.

Implemented

Remote access encrypted enforced

Remote administration of production systems uses encrypted connections, including HTTPS and SSH, to protect access in transit.

Implemented

Network and system hardening standards maintained

Network and system hardening standards guide secure configuration and ongoing maintenance of production infrastructure.

Implemented

Infrastructure performance monitored

Infrastructure performance and service health are monitored, with alerts supporting investigation of operational issues.

Organizational security

People, devices and inventories, including the boundary between OneShot and its cloud providers.

Implemented

Visitor procedures enforced

Visitor access follows authorization and supervision procedures. Hosting providers operate cloud data-center visitor controls.

Implemented

Asset disposal procedures utilized

Asset disposal procedures cover secure information removal. Hosting providers manage disposal of physical cloud infrastructure.

Implemented

Portable media encrypted

Portable media containing sensitive information is encrypted according to the requirements for handling that data.

Implemented

Password policy enforced

Password requirements apply to relevant accounts and authentication systems, in line with the established password policy.

Implemented

Production inventory maintained

An inventory of production systems and resources is maintained to support ownership, access management and operational oversight.

Product security

Protection of customer data and review of the controls supporting the product.

Implemented

Control self-assessments conducted

Internal assessments review security controls, identify gaps and track corrective actions to address those findings.

Implemented

Data encryption utilized

Managed cloud storage encrypts customer data at rest. Supported sensitive application fields also use envelope encryption.

Implemented

Data transmission encrypted

Public endpoints use HTTPS. Production access and supported service integrations also use encrypted connections.

Implemented

Vulnerability and system monitoring procedures established

Vulnerability management and system monitoring procedures support identification, assessment and remediation of security issues.

Internal security procedures

Access reviews, change management, incident response, risk ownership and vendor oversight.

Implemented

Physical access processes established

Physical access is restricted by business need. Hosting providers manage physical access to their cloud facilities.

Implemented

Data center access reviewed

Cloud hosting providers manage and review physical access to their data centers under their infrastructure security programs.

Implemented

Access reviews conducted

Access rights are reviewed for ongoing business need, with inappropriate or obsolete permissions identified for removal.

Implemented

Access requests required

Access to restricted systems requires an approved request before permissions are granted to the requesting person.

Implemented

Configuration management system established

Production configuration is maintained in version control and applied to production through managed deployment workflows.

Implemented

Development lifecycle established

The development lifecycle includes code review, automated checks and controlled deployment for changes to the product.

Implemented

Incident response plan tested

Exercises test the incident response plan to assess readiness, identify gaps and inform improvements to response procedures.

Implemented

Incident response policies established

Incident response policies define how security incidents are identified, escalated, investigated and brought to resolution.

Implemented

Management roles and responsibilities defined

Management responsibilities define ownership of information security, oversight of controls and escalation of issues.

Implemented

Incident management procedures followed

Incident management procedures guide response, tracking, resolution and follow-up review throughout the incident lifecycle.

Implemented

Risk assessment objectives specified

Risk assessment objectives define the scope and evaluation criteria used to assess risks to systems and information.

Implemented

Risks assessments performed

Risk assessments identify and evaluate security risks, helping determine which mitigation actions should take priority.

Implemented

Risk management program established

The risk management program tracks identified risks, assigns responsibility and supports decisions about their treatment.

Implemented

Roles and responsibilities specified

Security roles and responsibilities are assigned to relevant personnel and communicated so each person understands their role.

Implemented

Service description communicated

Product documentation and customer-facing materials describe OneShot services, security capabilities and applicable responsibilities.

Implemented

System changes communicated

Relevant system changes are communicated to affected personnel and customers through channels appropriate to the change.

Implemented

SOC 2 - System Description

The system description covers service scope, components and controls for SOC 2 review. Request it from [email protected].

Implemented

Third-party agreements established

Agreements with applicable third parties set out their obligations for information security, privacy and confidentiality.

Implemented

Vendor management program established

Vendor procedures assess relevant providers and maintain oversight of their security and data-processing responsibilities.

Data and privacy

Classification, handling, retention and disposal of company and customer information.

Implemented

Data classification policy established

The data classification policy defines categories of information and the handling requirements for each level of sensitivity.

Implemented

Data retention procedures established

Admins set retention for eligible content. Financial, receipt and audit records, backups and provider copies follow separate rules.

Agent safeguards

Additional controls for agent actions, execution isolation and verifiable records.

Implemented

Spending limits

Configured limits are checked before payment authorization; compute goals reserve budget first. Limits constrain spending, not action quality.

Implemented

Action policies and approvals

Configured policies allow, deny or require approval for supported actions. Approvals are request-specific, expire and can be used once.

Implemented

Signed receipts

Ed25519 signatures and public keys enable offline receipt verification. Signatures verify recorded actions and outcomes, not decision quality.

Implemented

Agent compute sandboxes

Compute runs in isolated sandboxes with short-lived task tokens. Model and vendor credentials stay in services handling authorized requests.

Backup and recovery

Additional controls for backup integrity, freshness and controlled restoration.

Implemented

Scheduled database backups

Weekly PostgreSQL and Redis backups go to a separate cloud project. The newest four successful sets are kept; they are not atomic platform snapshots.

Implemented

Backup validation

Scheduled checks monitor backup freshness; restore tooling checks integrity and isolated restores. Neither proves complete service recovery.

Implemented

Controlled restoration

Restores use separate targets, reconcile queues and reapply deletion and retention rules. Configuration, credentials and keys are also required.

Verify it yourself

don't trust the log. check the signature.

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.

How receipts work Why we sign every receipt

Security documents and review resources

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 our security team

Subprocessors

Who processes data on our behalf.

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.

Analytics

  • PostHog

    Product analytics for the API and dashboard.

Cloud monitoring

  • LangSmith

    Tracing of model calls for debugging and quality.

Cloud provider

Collaboration

Engineering

  • Anthropic

    Models for agent reasoning and content safety.

  • Manus

    Alternate executor for long-running research tasks.

  • Meta

    AI models and social platform integrations for agent workflows.

  • OpenAI

    Models for content safety checks and voice.

  • OpenRouter

    Model routing for agent reasoning, research and drafting.

  • SpaceXAI

    Grok models for agent reasoning, research and drafting.

  • Twilio

    SMS sending and phone numbers.

Finance

  • Coinbase

    x402 payment verification and USDC settlement (CDP).

  • Stripe

    Card payments, subscriptions and Agentic Commerce Protocol checkouts.

Security

  • Cloudflare

    DNS, CDN and DDoS protection; DNS for customer sending domains.

Reporting a vulnerability

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

Your security team
has questions. Good.