

Security is a foundational aspect of TaskForge's architecture. This guide covers the security controls, data privacy policies, and compliance features available to all workspace administrators and developers. Whether you are building internal tooling or processing customer data, TaskForge provides the infrastructure to meet your security requirements.
All data processed and stored by TaskForge is encrypted at rest using AES-256 and in transit using TLS 1.3. This applies to pipeline configurations, task payloads, model weights, logs, and all other workspace data.
Encryption keys are managed per-workspace using a BYOK (Bring Your Own Key) model for enterprise plans. Standard plans use TaskForge-managed keys rotated automatically every 90 days.
TaskForge uses a role-based access control (RBAC) system to govern what each workspace member can see and do. The default roles are:
Custom roles can be created on Enterprise plans, allowing granular permission assignment at the resource level.
For production workloads handling sensitive data, TaskForge supports:
To configure IP allowlisting, go to Settings → Security → Network Restrictions.
Every action performed in your TaskForge workspace is recorded in the audit log, including:
Audit logs are retained for 90 days on standard plans and up to 2 years on Enterprise plans. They can be exported in JSON or CSV format and streamed to an external SIEM using the webhook integration.
TaskForge is designed to support compliance with major data privacy frameworks including GDPR, CCPA, and SOC 2 Type II. Key privacy features include:
TaskForge operates a responsible disclosure program for security researchers. If you discover a vulnerability, please report it to security@taskforge.io with a detailed description of the issue, steps to reproduce, and potential impact. We aim to acknowledge all reports within 48 hours and provide a resolution timeline within 7 days for critical issues.