[ PRIVACY ]

Privacy Policy

How Overclock handles platform data and how Overclock connects to your paired desktop through the relay, with end-to-end protected content.

Version privacy_v2026_11_15_mobile · Updated November 15, 2026

PrivacyApp support

Overclock — Português (Brasil)

O Overclock conecta o celular (iPhone ou Android) ao desktop Overclock que você pareou. A conexão passa pelo relay da Overclock e funciona em qualquer rede, inclusive fora do Wi-Fi do desktop. O desktop precisa estar ligado e conectado; os comandos rodam no desktop, não no celular. O app não inclui analytics, publicidade nem rastreadores. Ele envia relatórios de falhas e diagnóstico pelo Sentry, como descrito abaixo.

Conteúdo protegido de ponta a ponta: mensagens, comandos, saídas de terminal, imagens e resultados são cifrados no celular e só são abertos no desktop pareado, e vice-versa. O relay só encaminha os dados cifrados, em memória, e não guarda histórico. A Overclock não consegue ler esse conteúdo. As chaves privadas ficam só nos seus aparelhos (no iPhone, no Keychain do iOS; no Android, no armazenamento seguro do aparelho).

Dados que guardamos para o serviço funcionar: o identificador do aparelho pareado; o identificador da sua conta Overclock, ligado a esse aparelho; o nome do aparelho exibido no app; as chaves públicas usadas para autenticar o aparelho; as permissões e o estado da autorização; convites e tickets temporários, guardados como resumo criptográfico; e, se você permitir notificações, o token de push da Apple (só no iPhone). Usamos esses dados só para parear, autenticar, encaminhar a conexão, revogar acesso e enviar notificações.

Conta no app (iPhone): você pode entrar com a sua conta Overclock, comprar a assinatura pelo iPhone e usar o mesmo acesso no desktop. O login é feito dentro do app, com 3 opções: Entrar com a Apple, Google e código enviado por e-mail. Não usamos senha. Usamos o e-mail e o identificador da conta para autenticar, manter a sessão e ligar o app à sua conta, e o app guarda a sessão no Keychain do iOS. Ao entrar, o app avisa o nosso servidor, que registra o aceite dos Termos e da Política. Com Entrar com a Apple, recebemos o identificador da Apple e o e-mail (o seu ou um endereço de retransmissão da Apple, se você escolher “Ocultar meu e-mail”); o app não pede o seu nome à Apple. Com o Google, o login passa pelo Google e pelo Supabase, nosso provedor de autenticação, e recebemos o identificador da conta Google, o e-mail, o nome e a foto do seu perfil Google. Usamos esses dados para identificar a sua conta. Esses dados ficam na sua conta enquanto ela existir (veja “Excluir a conta”, abaixo). No código no e-mail, você informa o e-mail da conta e recebe nele um código de uso único; o app usa o Cloudflare Turnstile para barrar robôs. No Android, o app segue sem conta. Base legal: execução do contrato e procedimentos preliminares a pedido do titular; legítimo interesse para segurança e prevenção de abuso.

Compras pela Apple (iPhone): a assinatura pelo iPhone é uma compra dentro do app, feita e gerenciada pela Apple, que cobra na forma de pagamento do seu ID Apple. Não recebemos dados de cartão. A Apple nos envia, assinados por ela, os dados da transação: identificadores da transação e da assinatura, produto, datas de compra e de vencimento, ambiente (produção ou teste), estado da renovação, preço, moeda e país da loja, e o identificador da sua conta Overclock que o app informa na compra. Usamos esses dados para liberar o acesso na sua conta, também no desktop, manter o estado da assinatura em dia e evitar cobrança em dobro com uma assinatura feita pelo site. Cancelar, trocar ou pedir reembolso de uma compra pela Apple é com a Apple: no iPhone, em Ajustes → seu nome → Assinaturas, ou em reportaproblem.apple.com. Guardamos esses registros por 5 anos, pelas obrigações fiscais e para defesa de direitos. Base legal: execução do contrato e cumprimento de obrigação legal.

Ditado por voz (iPhone): o botão de microfone da conversa usa o reconhecimento de fala da Apple. Quando o aparelho tem o idioma baixado, o reconhecimento é feito nele; quando não tem, o áudio é processado nos servidores da Apple, conforme a política da Apple. A Overclock não recebe nem guarda o áudio. O texto reconhecido aparece no campo da mensagem e só segue para o desktop pareado quando você toca em enviar, como mensagem cifrada de ponta a ponta. O app pede a permissão de microfone e a de reconhecimento de fala no primeiro uso do ditado; você pode negar ou retirar a permissão nos Ajustes do iOS.

No iPhone, as notificações usam o serviço de push da Apple (APNs), com um aviso genérico, sem conteúdo de projeto ou conversa. No Android, os avisos são locais: o próprio app os gera enquanto está aberto e conectado ao desktop, com mensagem genérica; o app não registra token de push, não usa Firebase Cloud Messaging e não recebe notificações com o app fechado. Você pode desligá-las nos Ajustes do iOS, nas configurações do Android ou no app.

Registros técnicos: o relay registra eventos de conexão (tipo de aparelho, código de encerramento, duração) sem endereço IP e sem identificar você ou o aparelho. O proxy do nosso servidor registra cada requisição com data, caminho, status e tempo de resposta; o endereço de origem que ele registra é o da Cloudflare, não o seu. Esses registros do proxy são apagados após 14 dias. A Cloudflare, que fica na frente do servidor como rede de entrega e proteção, recebe o seu endereço IP para entregar o tráfego e o trata conforme a política dela.

Relatórios de falhas e diagnóstico: o app envia automaticamente relatórios de falha ao Sentry e, quando você toca em Ajustes → “Enviar diagnóstico” e confirma, um diagnóstico com versão e build do app, sistema e versão do sistema, modelo do aparelho, estado da conexão e um registro curto e recente do app. Antes de sair do aparelho, o conteúdo é limpo: removemos endereços de servidor, URLs, IPs, portas, tokens, chaves, códigos de pareamento, e-mails e qualquer conteúdo de terminal ou conversa. Não enviamos capturas de tela, gravação de tela nem identificadores da sua conta ou do aparelho. Esses dados não são vinculados à sua identidade, não são usados para publicidade nem para rastrear você, e servem só para corrigir falhas e atender pedidos de suporte. O projeto no Sentry está configurado para não guardar endereço IP.

Fornecedores e localização: o relay roda em servidor próprio no Brasil, gerenciado com Coolify; o banco de dados e a autenticação ficam no Supabase, em data center nos Estados Unidos; a Apple entrega as notificações e processa as compras dentro do app; a Cloudflare faz a entrega e a proteção do tráfego; o Sentry recebe os relatórios de falha e os diagnósticos do app.

Retenção: convites e tickets são apagados automaticamente 24 horas depois de vencerem. Ao revogar um aparelho, ele perde o acesso na hora e o token de push é apagado; o registro da autorização revogada continua guardado, sem o token, até a exclusão da conta. Ao excluir a conta, os registros dos aparelhos são apagados. Cópias de segurança do banco mantidas pelo Supabase podem conter esses dados por um período limitado, conforme a política do fornecedor. No app, remover um host apaga a credencial guardada no celular.

Excluir a conta: pelo próprio app, que abre a página de exclusão, ou em overclock.sh/app/conta/excluir, depois de entrar de novo (pedimos um login de menos de 10 minutos). Na hora, a conta é desativada e as sessões são encerradas em todos os aparelhos. Uma assinatura feita pelo site deixa de renovar, sem cobrança nova e sem estorno do período já pago; com pagamento pendente, ela é cancelada na hora. Uma assinatura feita pela Apple não é cancelada pela exclusão: cancele no iPhone, em Ajustes → seu nome → Assinaturas. Há 14 dias de carência, em que o suporte ainda pode reativar a conta; depois deles, os dados da conta são apagados, sempre em até 30 dias do pedido. Ficam guardados, por 5 anos, os registros de cobrança, a prova de que você aceitou os Termos e a Política e os registros de conflito entre uma assinatura do site e uma da Apple, por obrigação legal e para defesa de direitos. O pedido de exclusão fica registrado só com o identificador da conta e as datas, como prova do atendimento. Se você pediu para não receber mensagens de WhatsApp, guardamos só um resumo criptográfico do número, sem prazo, porque o pedido de não receber precisa valer sempre. Também dá para pedir por [email protected].

Não usamos esses dados para publicidade e não rastreamos você entre apps e sites. Para exercer seus direitos (LGPD), escreva para [email protected].

Suporte do Overclock

Overclock — English (United States)

Overclock connects your phone (iPhone or Android) to the Overclock desktop you paired. The connection goes through Overclock’s relay and works on any network, including away from the desktop’s Wi-Fi. The desktop must be on and online; commands run on the desktop, not on the phone. The app includes no analytics, advertising, or trackers. It sends crash reports and diagnostics through Sentry, as described below.

End-to-end protected content: messages, commands, terminal output, images, and results are encrypted on the phone and only opened on the paired desktop, and vice versa. The relay only forwards the encrypted data in memory and keeps no history. Overclock cannot read this content. Private keys stay on your devices only (on iPhone, in the iOS Keychain; on Android, in the device’s secure storage).

Data we keep to run the service: the paired device identifier; your Overclock account identifier linked to that device; the device name shown in the app; the public keys used to authenticate the device; the grant’s permissions and status; temporary invites and tickets, stored as cryptographic hashes; and, if you allow notifications, the Apple push token (iPhone only). We use this data only to pair, authenticate, route the connection, revoke access, and send notifications.

Account in the app (iPhone): you can sign in with your Overclock account, buy the subscription on the iPhone, and use the same access on the desktop. Sign-in happens inside the app, with 3 options: Sign in with Apple, Google, and a code sent by e-mail. We do not use passwords. We use the e-mail and the account identifier to authenticate you, keep the session, and link the app to your account, and the app stores the session in the iOS Keychain. When you sign in, the app notifies our server, which records your acceptance of the Terms and the Policy. With Sign in with Apple, we receive the Apple identifier and the e-mail (yours, or an Apple relay address if you choose “Hide My Email”); the app does not ask Apple for your name. With Google, sign-in goes through Google and Supabase, our authentication provider, and we receive the Google account identifier, the e-mail, and the name and photo of your Google profile. We use this data to identify your account. This data stays on your account for as long as it exists (see “Deleting your account”, below). With the e-mail code, you enter your account e-mail and receive a one-time code there; the app uses Cloudflare Turnstile to stop bots. On Android, the app still has no account. Legal basis: performance of the contract and pre-contractual steps at your request; legitimate interest for security and abuse prevention.

Purchases through Apple (iPhone): the iPhone subscription is an in-app purchase made and managed by Apple, which charges the payment method of your Apple Account. We do not receive card data. Apple sends us, signed by Apple, the transaction data: transaction and subscription identifiers, product, purchase and expiration dates, environment (production or test), renewal status, price, currency and storefront country, and the Overclock account identifier the app provides at purchase. We use this data to grant access on your account, including on the desktop, keep the subscription status up to date, and avoid double billing with a subscription bought on the website. Cancelling, changing, or asking for a refund of an Apple purchase is done with Apple: on the iPhone, in Settings → your name → Subscriptions, or at reportaproblem.apple.com. We keep these records for 5 years, for tax obligations and the defense of rights. Legal basis: performance of the contract and compliance with legal obligations.

Voice dictation (iPhone): the microphone button in the conversation uses Apple’s speech recognition. When the device has the language downloaded, recognition runs on the device; when it does not, the audio is processed on Apple’s servers, under Apple’s policy. Overclock does not receive or store the audio. The recognized text appears in the message field and only goes to the paired desktop when you tap send, as an end-to-end encrypted message. The app asks for microphone and speech recognition permission the first time you use dictation; you can deny or withdraw the permission in iOS Settings.

On iPhone, notifications are sent through Apple Push Notification service (APNs) with a generic alert and no project or conversation content. On Android, alerts are local: the app creates them itself while it is open and connected to the desktop, with a generic message; the app does not register a push token, does not use Firebase Cloud Messaging, and does not receive notifications while closed. You can turn them off in iOS Settings, in Android settings, or in the app.

Technical records: the relay logs connection events (device type, close code, duration) without IP addresses and without identifying you or the device. Our server’s proxy logs each request with date, path, status, and response time; the source address it records is Cloudflare’s, not yours. These proxy logs are deleted after 14 days. Cloudflare, which sits in front of the server as a delivery and protection network, receives your IP address to deliver the traffic and handles it under its own policy.

Crash reports and diagnostics: the app automatically sends crash reports to Sentry and, when you tap Settings → “Send diagnostics” and confirm, a diagnostic with the app version and build, operating system and version, device model, connection state, and a short recent app log. Before leaving the device, the content is sanitized: we remove server addresses, URLs, IPs, ports, tokens, keys, pairing codes, e-mails, and any terminal or conversation content. We do not send screenshots, screen recordings, or identifiers of your account or device. This data is not linked to your identity, is not used for advertising or to track you, and is used only to fix crashes and answer support requests. The Sentry project is configured not to store IP addresses.

Providers and location: the relay runs on our own server in Brazil, managed with Coolify; the database and authentication run on Supabase, in a data center in the United States; Apple delivers notifications and processes in-app purchases; Cloudflare delivers and protects the traffic; Sentry receives the app’s crash reports and diagnostics.

Retention: invites and tickets are deleted automatically 24 hours after they expire. When you revoke a device, it loses access immediately and its push token is deleted; the revoked grant record is kept, without the token, until the account is deleted. Deleting the account erases the device records. Database backups kept by Supabase may contain this data for a limited period under the provider’s policy. In the app, removing a host deletes the credential stored on the phone.

Deleting your account: from the app itself, which opens the deletion page, or at overclock.sh/app/conta/excluir, after signing in again (we require a sign-in from less than 10 minutes ago). Right away, the account is disabled and sessions are ended on every device. A subscription bought on the website stops renewing, with no new charge and no refund of the period already paid; if a payment is pending, it is canceled right away. A subscription bought through Apple is not canceled by the deletion: cancel it on the iPhone, in Settings → your name → Subscriptions. There is a 14-day grace period in which support can still reactivate the account; after it, account data is deleted, always within 30 days of the request. We keep, for 5 years, billing records, the proof that you accepted the Terms and the Policy, and the records of conflicts between a website subscription and an Apple one, as required by law and for the defense of rights. The deletion request is recorded with only the account identifier and the dates, as proof that we handled it. If you asked not to receive WhatsApp messages, we keep only a cryptographic hash of the number, with no time limit, because the request not to be contacted must hold permanently. You can also ask at [email protected].

We do not use this data for advertising and do not track you across apps or websites. To exercise your privacy rights, contact [email protected].

Overclock support

1. Controller and channels

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

Overclock is the controller of the data necessary to operate its own platform, account, subscription, payments, support, security, community, Discord/Founders, and communications.

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]. The community and moderation channel is [email protected].

8. Data you should not send

To protect you, your clients, and the community, do not send data that isn't necessary for support or participation.

  • API keys, bearer tokens, refresh tokens, passwords, cookies, .env files, secrets, private keys, and signed URLs.
  • Database dumps, full logs, OAuth callbacks, unmasked screenshots, or confidential client data.
  • Sensitive personal data, financial data, documents, health data, or data belonging to children/teenagers.
  • Material protected by NDA, contract, trade secret, copyright, or professional confidentiality without authorization.

11. Local-first and AI providers

Overclock is designed to be local-first. Code, files, prompts, workspace, and terminal should not leave your machine to reach Overclock, except when a feature, support request, integration, or your own action requires sending it.

When you use an AI provider you configured, the request may be sent to the provider you chose, according to your settings, terms, policies, and keys.

Sending mobile content to third-party AI: before the 1st send, the app shows a notice and asks for your agreement. The text you write, the text recognized by dictation, and files you choose to attach travel over the end-to-end encrypted connection to the paired computer; the app does not call the AI provider’s API directly. The Overclock relay forwards only encrypted data and does not keep it as history. On the computer, when you send this content to an agent that uses an external service you chose — for example Claude, Codex, or Gemini — that service provider receives the content and context the tool sends to answer, under its own terms and policies. Overclock does not receive this content in readable form. If you decline, nothing is sent; you can allow it later in Settings → Privacy. The permission stays on the device until you revoke it. The computer’s local history and the AI service’s retention follow the tool’s settings and the provider’s rules; Overclock does not set one retention period for those providers.

12. Retention

We keep data for as long as necessary to operate the account, perform the contract, deliver benefits, comply with legal obligations, prevent fraud, protect the platform, respond to requests, preserve acceptance evidence, and exercise rights.

Billing data may be retained for the period required by legal, tax, accounting, and rights-defense obligations. Community/moderation data may be kept when necessary for security, investigation, abuse, incidents, or defense. Cookie preferences stay in your browser until you clear local data or we change the consent version.

The phone number linked to the members WhatsApp group is kept while your account exists or until you unlink it on the /whatsapp/membros page; deleting your account also deletes the link.

Order log of Guru notices: Guru sends subscription notices out of order. To avoid giving access back to a canceled or refunded subscription, we keep, per subscription, only its Guru code, the last status, the date of the last notice and, when applicable, the code of the site subscription we ended because of it. This log is deleted 13 months after the last Guru notice, and never while the subscription is in force.

Deleted account: if you delete your account, we note the deletion date in that log, without keeping your email. While Guru keeps sending notices for that subscription, the note stays, and for 13 months after the last notice. This way, a later Guru charge does not create a new account: our team is alerted to cancel the subscription at Guru.

The name, email, and WhatsApp number entered in the ticket form of an in-person immersion are kept until 30 days after the event ends.

The answers and contact data of the Escale seu SaaS application are kept until 90 days after the event ends (November 1, 2026); data of those who buy the ticket follows the purchase relationship.

Escale seu SaaS waitlist data is kept for up to 12 months after sign-up, or until you ask to leave the list ([email protected]).

Escale seu SaaS 2nd edition waitlist data, including the application answers, is kept for up to 12 months after sign-up, or until you ask to leave the list ([email protected]).

Shared harness items are kept with no time limit, because the link does not expire. To take an item down, ask support ([email protected]) and include the link; deleting your account also deletes its items.

Clockinho ranking data is kept while you participate. To leave, turn off Participate in the app: the record is deleted right away, always, with no conditions. Deleting your account also deletes the record.

The answers, contact data, and booking of the Overclock demo (/demo) are kept for 12 months after the application is submitted.

A job application (/vaga-cortes and /vaga-vibe-coder-poa), with the contact data, links, answers, and proof of acceptance, is kept for up to 12 months after it is sent, or until you ask for deletion ([email protected]).

Account deletion: the account stays in a 14-day grace period in which support can still reactivate it, and account data is deleted within 30 days of the request. We keep for 5 years the billing records (including Apple purchases), the proof that you accepted the Terms and the Policy, and the records of conflicts between a website subscription and an Apple one, as required by law and for the defense of rights; the deletion request is recorded with only the account identifier and the dates; and, if you asked not to receive WhatsApp messages, we keep only a cryptographic hash of the number, with no time limit, because the request not to be contacted must hold permanently.

13. Data subject rights

You may request confirmation of processing, access, correction, portability where applicable, deletion, information about sharing, objection, and other rights under the LGPD, through the [email protected] channel.

To delete your account, sign in again and use the /app/conta/excluir page (the iPhone app opens this same page). Right away, the account is disabled and sessions are ended on every device; a subscription bought on the website stops renewing, with no new charge and no refund of the period already paid (if a payment is pending, it is canceled right away); a subscription bought through Apple must be canceled on the iPhone, in Settings → your name → Subscriptions. What we keep and for how long is in section 12.

Some requests may depend on identity verification and may be limited by legal obligations, fraud prevention, security, defense of rights, or proportional technical impossibility.

14. Security and incidents

We adopt reasonable security and minimization measures, including a preference for technical hashes for acceptance evidence instead of raw IP and full user-agent.

If we identify a security incident involving personal data under Overclock's responsibility, we will assess the risk, adopt appropriate measures, and make the communications required by applicable law.

15. Changes

This Policy may change to reflect changes in the product, vendors, legal obligations, or security practices. Material changes may require new acceptance or a highlighted notice.

16. Language

The U.S. course section is an independently versioned English supplement and governs the description of that processing if it conflicts with a general description or Portuguese translation. It does not change Brazilian contracts or limit mandatory privacy rights. For other products, this Policy is a translation of the Portuguese policy and the Portuguese version prevails in case of conflict.

Controller: GL Estrategias Digitais Ltda. (Overclock) · CNPJ 29.231.457/0001-99

Data Protection Officer (DPO): Guilherme Laschuk · [email protected]

Community and moderation: [email protected]

PrivacyApp support