Legal · Privacy
Privacy Policy
This Policy explains how MetaBlox Code processes information for account review, software engineering tasks, billing, and security operations.
1. Information we collect
We may process legal names, work email addresses, organizations, job titles, countries or regions, intended-use descriptions, terms-acceptance records, authentication and session records, payment and Credit records, prompts, code, files, tool results, model inputs and outputs, IP addresses, devices, and security logs.
2. How we use information
We use information to review identity and intended use, provide the workspace and Model Interface, execute tasks, settle Credits, provide support, prevent fraud and resale, detect abuse and model extraction, protect systems, and comply with law.
3. Service providers
To fulfill user requests, relevant prompts, code, and workspace context may be sent to controlled upstream model, hosting, payment, monitoring, and infrastructure providers. We require them to process information under applicable contractual and data-protection terms. Provider API Keys are not disclosed to customers.
4. Model training
Unless a customer separately provides explicit consent or enters a written agreement, MetaBlox Code does not use customer content to train general-purpose generative models. Processing required for security analysis, abuse detection, debugging, and service delivery is not general-purpose model training.
5. Retention and security
Account, billing, security, and dispute records are retained for periods required by operational, contractual, and legal needs. Retention for workspaces, model traffic, and logs depends on product configuration. We use access controls, server-side keys, session protection, logging, and account enforcement, but no system can guarantee absolute security.
6. Rights and choices
Subject to applicable law, users may request access, correction, export, restriction, or deletion of personal information. We may require identity verification to prevent fraud, and records required for legal, billing, security, or dispute purposes may be retained.
7. Cookies and sessions
We use necessary secure session Cookies after login. Provider API Keys are not stored in the browser. Necessary sessions support authentication, security, and prevention of unauthorized access.
8. Contact and updates
Privacy requests may be submitted through in-account support. We may update this Policy for legal, provider, or product changes and will publish the revised version and effective date on the website or within the account.