Security
This page describes Task Machine's current security boundaries and operating practices for the website, application, local daemon, and managed execution.
Last updated: 7 August 2026
Infrastructure security
Task Machine runs on managed infrastructure for application hosting, PostgreSQL, object storage, transactional email, observability, networking, and backups. Production access is limited to the operator and systems that need it, and infrastructure changes are managed as reviewed code.
Public traffic is served over HTTPS. Managed PostgreSQL encryption at rest is enabled, object-storage buckets holding private product data are private, and application access uses scoped infrastructure identities. Provider backup schedules and retention remain part of the underlying managed-service configuration.
Data in transit
Traffic to taskmachine.io and the application uses HTTPS. Managed daemons and model-gateway requests use TLS with credentials scoped to the workspace, machine, run, and route where applicable. Plaintext public requests are redirected to HTTPS in production.
Data at rest
Application data is stored in Scaleway Managed Database for PostgreSQL. Uploads, generated artifacts, skill bundles, static assets, and backup material use Scaleway Object Storage according to their purpose. Vault secrets are encrypted before storage with key material separated from the database. Managed worktree files are stored on provider volumes and local worktree files remain on the machine chosen by the customer.
Authentication and access control
People authenticate through verified magic links or Google. Browser sessions use signed, Secure production cookies with SameSite protection, and forms use cross-site request forgery protection. Workspace roles and permission checks hide unavailable actions in the interface while server-side domain authorization remains the security boundary.
Agents and managed daemons do not receive a human user's general-purpose session. They use purpose-bound, short-lived, revocable credentials scoped to the workspace and active run. Vault grants and connector access are limited to the credentials and actions assigned to the work.
Application security
The application sets security headers including a content security policy, validates provider webhooks before processing them, records payment events idempotently, bounds growing reads and rendered payloads, separates secrets from analytics and logs, and applies framework and dependency security updates through the normal release process.
Local daemon boundary
Task Machine gives each local run a task-specific work directory and isolated coding-tool configuration. This prevents automatic reuse of unrelated tool settings, plugins, skills, connectors, and sessions, but it is not an operating-system or filesystem sandbox.
A coding tool allowed to use shell or filesystem capabilities runs with the access of the operating-system user that runs tama. It may reach other files, processes, credentials, and network services available to that user. Customers should use a dedicated operating-system user, virtual machine, or container when stronger isolation is needed and should expose only required repositories and credentials.
Managed execution boundary
Managed coding runs execute in provider sandboxes with task or chat worktree volumes. Runtime credentials are supplied through ephemeral storage or process memory rather than the persistent worktree, and a run receives a short-lived Task Machine credential instead of a human session or the workspace's upstream model key.
Prompts, files, tool calls, outputs, and network requests may still be processed by Blaxel, OpenRouter, the selected model developer, Exa, and customer-selected connectors. Provider isolation and security practices remain part of the complete boundary.
Logs, analytics, and retention
Operational logs and analytics are designed to exclude credentials, prompts, file contents, and raw provider bodies. Product analytics uses identifier-only and bounded operational properties. Application logs are configured for 30 days and infrastructure metrics for 15 days. Product transcripts and run history are separate customer records and follow the Privacy Policy rather than log retention.
Compliance and independent assurance
Task Machine is operated from Spain and handles personal data under applicable EU data-protection law. The Privacy Policy, Data Processing Addendum, and Subprocessor Schedule describe the applicable roles and providers.
Task Machine does not currently claim SOC 2, ISO 27001, penetration-test, or other third-party certification status. Provider certifications do not automatically certify Task Machine. Security and compliance evidence can be discussed for a qualified customer request.
Incident response
We investigate suspected security incidents, contain affected access, preserve relevant evidence, remediate the cause, and notify affected customers, people, Link, or authorities when applicable law or a contract requires notice. The Data Processing Addendum states the processor notification commitment for customer personal data.
Responsible disclosure
Report a suspected vulnerability privately to security@taskmachine.io . Include enough detail to reproduce the issue, avoid accessing data that is not yours, do not disrupt the service, and allow a reasonable period for investigation and remediation before public disclosure.
Contact and related terms
For security questions, email security@taskmachine.io . Read the Privacy Policy, Data Processing Addendum, and Subprocessor Schedule.