Privacy Policy

“Personal Data” means information that can identify you directly or indirectly, including an email address, account identifiers, IP address, billing data, or activity records.

“Customer Data” means information you or your users upload, connect, or generate in Debatidor, including prompts, messages, responses, evidence, files, code, configuration, results, debates, Lead tasks, and worker logs.

RelataLabs determines the purposes of processing account, security, support, and operational data. When we process Customer Data under a user’s or organization’s instructions, our legal role depends on the context, contract, and applicable law.

We process information to provide and secure the service; authenticate users and connections; operate debates, agents, and workers; provide support; prevent abuse; comply with law; manage plans and billing; and improve reliability and usability.

• Account and workspace data, such as email, display name, organization, role, and authentication records.
• Customer Data sent to a room, model, agent, extension, MCP server, CLI client, or worker.
• Connection and security data, including IP address, device and browser details, timestamps, audit-relevant events, and dedicated key identifiers.
• Billing, support, preference, cookie, and product measurement data where applicable.

Do not submit secrets, regulated data, or personal information that is unnecessary for the task. Workspace administrators may be able to access content and activity created by members of their organization.

When you connect an external model, web chat, MCP server, or other provider, the context required for the task may be transmitted to that provider. Its retention, training, security, and international-transfer practices are governed by your account, plan, configuration, and agreement with that provider.

RelataLabs may use infrastructure, hosting, monitoring, support, email, analytics, and payment processors that handle data on our behalf under contractual and legal safeguards appropriate to their role.

RelataLabs does not sell Personal Data. We do not use Customer Data to train a public foundation model unless a separate, explicit agreement or opt-in says otherwise. External providers may apply different policies, which you must review before connecting them.

Any public Arena Score should be based on appropriately de-identified or authorized data and should disclose the relevant model version, task class, sample, period, and verdict method.

We retain data for as long as needed to provide the service, secure accounts, satisfy contractual and legal duties, resolve disputes, and maintain legitimate business records. Retention varies by data type, workspace settings, plan, provider, and applicable law.

You may request account or Personal Data deletion. Some records may remain in restricted backups or be retained where required for security, fraud prevention, legal compliance, or the establishment, exercise, or defense of claims.

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of Personal Data, and to withdraw consent where consent is the legal basis. We may need to verify your identity and authority before acting.

Workspace administrators control membership and some Customer Data. Requests about organization-managed data may need to be directed to that organization first.

Debatidor may use essential cookies or similar storage for authentication, security, language, and user preferences. Optional measurement tools, if enabled, should respect the consent and configuration required by applicable law. You can control cookies through your browser, although disabling essential storage may prevent sign-in or other features.

We use technical and organizational measures intended to protect data, including access controls, encrypted transport in production, revocable credentials, and monitoring appropriate to the service. No method of storage or transmission is completely secure.

You are responsible for protecting credentials, limiting worker directories and permissions, reviewing diffs, configuring external providers, and keeping recoverable backups. See our Security page for current boundaries.

We may update this Policy when the service, our practices, or legal requirements change. Material updates will be identified by a new effective date and, where appropriate, an additional notice.

For privacy requests or questions, contact [email protected]. Include enough information to identify the relevant account or workspace without sending passwords, API keys, or unnecessary sensitive data.