Overclock Terms of Use

The controller responsible for operating Overclock is GL Estrategias Digitais Ltda. (Overclock), CNPJ 29.231.457/0001-99.

By creating an account, subscribing, accessing the dashboard, downloading the app, or using Overclock, you declare that you have read, understood, and accepted these Terms and the Privacy Policy.

If you use Overclock on behalf of a company, client, organization, or third-party project, you declare that you have authority to accept these Terms on behalf of that entity.

Overclock's Data Protection Officer (DPO) is Guilherme Laschuk. The official channel for privacy, LGPD, personal data, exercising data subject rights, and communications with the ANPD (Brazil's data protection authority) is [email protected].

Overclock is an AI agent orchestration, automation, development, and webcoding tool. The product can assist in creating, reviewing, modifying, and executing code, commands, files, integrations, and workflows.

Overclock is not a legal, accounting, medical, financial, compliance, audit, managed security, or penetration testing service, a guarantee of results, managed hosting, or a substitute for human review.

Experimental features, betas, overLabs, early builds, and integrations under development may fail, change, break workflows, alter files, lose state, produce incorrect results, or become unavailable.

You are responsible for keeping your account, device, session, credentials, configured providers, and permissions granted to tools, agents, and integrations secure.

• Do not share passwords, keys, tokens, cookies, .env files, secrets, or credentials.
• Review permissions before connecting providers, APIs, repositories, databases, deployments, or external tools.
• Overclock may suspend or limit access in case of abuse, fraud, security risk, violation of these Terms, improper chargeback, or risk to third parties.

You are responsible for everything you decide to build, run, publish, integrate, sell, or deliver using Overclock, including code, commands, files, prompts, integrations, deployments, databases, end clients, and environments under your control.

You must technically review every output before using it in production. AI agents can make mistakes, omit risks, generate insecure code, suggest destructive commands, misinterpret requirements, or produce incorrect content.

In the standard product-use relationship, Overclock acts as the controller of the data necessary to operate its own platform, account, subscription, payment, support, community, authentication, security, and communication.

You act as the controller of the personal data you enter, process, copy, upload, expose, test, use in prompts, store, or send to third parties within your own projects, repositories, databases, applications, automations, prompts, integrations, and environments.

Overclock will only act as a processor of a client's personal data when there is a specific contract or data processing addendum signed between the parties.

• Do not send sensitive personal data, data belonging to children/teenagers, financial data, documents, credentials, secrets, keys, tokens, cookies, signed URLs, database dumps, or client data without proper authorization.
• You are responsible for the legal basis, consents where applicable, contracts, privacy policy, governance, and security of your own clients', users', and third parties' data.

Overclock may depend on or integrate with third parties, such as authentication, payment, database, anti-fraud, Discord, AI, hosting, analytics, email, support, and automation providers.

When you configure or use external providers, you are responsible for reviewing and accepting the terms, policies, costs, limits, risks, and data handling practices of those third parties.

Paid plans may unlock access to downloads, features, models, Founders, Boost, Boost Pro, overLabs, support, community, or additional benefits, as described on the applicable page at the time of purchase.

Benefits may depend on an active subscription, eligibility, technical availability, third-party integration, or specific rules. Cancellation, payment failure, chargeback, fraud, or violation of these Terms may result in loss of access.

Cancellation, withdrawal, and refunds follow the Overclock Refund Policy, available at overclock.sh/refund, including the 7-day full-refund guarantee.

Discord and other community channels have their own rules of conduct and moderation. Community participation is optional and subject to the Overclock Community Terms on Discord.

Responses received in the community, livestreams, chats, comments, Discord, WhatsApp, forums, or informal messages do not constitute professional advice, a guarantee of correctness, SLA-backed support, or final validation for production.

• Illegal, fraudulent, abusive, or malicious activity.
• Intrusion, exploitation, spam, malware, phishing, abusive scraping, credential theft, or security bypass.
• Violation of privacy, LGPD, intellectual property, third-party contracts, or other people's rights.
• Processing third-party data without a legal basis or authorization.
• Exposure of secrets, tokens, credentials, client data, or confidential information.

Overclock may change, suspend, limit, or discontinue features, plans, builds, integrations, and resources, especially when they are experimental, unsafe, unfeasible, abused, or dependent on third parties.

To the maximum extent permitted by law, Overclock is not liable for indirect damages, lost profits, loss of revenue, loss of opportunity, data loss, deployment failure, business interruption, vendor failure, AI error, the user's own technical decisions, misuse, lack of backup, leaks caused by the user's own credentials, or impacts on end clients under the user's control.

Nothing in these Terms limits liability that cannot be limited by law, including willful misconduct, fraud, bad faith, or mandatory legal obligations.

For acceptance and security records, Overclock may store technical hashes, such as ip_hash and user_agent_hash, instead of raw IP or full user-agent strings.

If Overclock identifies a security incident involving personal data under its responsibility as controller, it will assess the risk, adopt reasonable measures, and make the communications required by applicable law.

If an incident involves an environment, project, client, database, credential, provider, or deployment under your control, you are responsible for assessing, mitigating, and reporting the incident to data subjects, authorities, and third parties, as applicable.

These Terms are governed by the laws of Brazil. Venue or dispute resolution mechanism may be defined in a specific contractual version.

These Terms were originally written in Portuguese and translated into English for convenience. In case of any conflict, ambiguity, or divergence between the Portuguese and English versions, the Portuguese version prevails.