1. Introduction
At Brigades AI, we respect your privacy and are committed to protecting your personal data, workspace files, and intellectual inputs.
This Privacy Policy details how we collect, process, and secure your specifications, prompt histories, canvas markups, and reference files when using our agentic 3D modeling platform.
2. Information We Collect
To deliver a responsive, secure 3D modeling workspace, we collect and process the following metrics:
- Account Details: Registration parameters including your name and email address.
- Design & Workspace Inputs: Conversational instructions, 3D coordinate markups, and reference attachments (such as user-uploaded STL files, images, or dimensional details) that you provide to guide the modeling agent.
- Execution & Telemetry Logs: Compilation records from sandbox runs, including runtimes, model dimension metrics, trimesh calculation metrics, and compiler warnings. This is used solely for usage estimates and bug diagnostic routines.
- Payment Details: Stripe handles billing information and transactional profiles. We do not store credit card details directly.
3. How We Use Data
Your workspace and telemetry records are processed for direct system performance and billing operations:
- To allocate and manage ephemeral sandboxes, run Python geometry tasks, and serve generated models.
- To track credit consumption rates based on LLM tokens and sandbox runtimes.
- To analyze compiler exceptions and runtime errors to improve the reliability of the agent modeling loop.
- To secure our API systems and block infrastructure abuse or container escalation vulnerabilities.
4. AI & LLM Data Policy
Zero Foundation Training Policy:
We respect your intellectual design models. We **do not** use your uploaded STL models, prompt histories, canvas markups, or compiled code to train our custom AI models.
Furthermore, we do not permit our upstream API providers (such as Anthropic, OpenAI, or Google Gemini) to use the data transmitted during your modeling runs to train their general public foundation models. Your data is processed solely to perform live code generation for your active session.
5. Sandboxing & Security
We employ enterprise-grade isolation standards to safeguard active sessions:
- Isolated Sandboxes: Every modeling run is allocated inside an ephemeral, network-restricted Kubernetes container. Your workspace cannot be accessed by other active users or outside web resources.
- Data Encryption: All communications between the Next.js client, the Postgres DB, and Supabase storage are fully encrypted in transit using TLS 1.3, and at rest using AES-256 standard encryption.
6. Data Retention & Deletion
You maintain complete control over the lifespan of your design archives:
- Session Deletion: Deleting a modeling session in the dashboard instantly requests our database to purge associated message logs, and deletes the workspace archive (`workspace.tar.gz`) from Supabase storage.
- Account Purges: If you request full account deletion, all personal profiles, payment links, uploaded reference STLs, and CAD generations are permanently removed from our storage systems within 30 days.
7. Contact Us
If you have questions regarding this Privacy Policy, your personal details, or to submit data deletion requests, contact our privacy officer: