Updated 15 October 2026
Privacy notice
How AntiCode uses account information, repository data, and review content, and how to contact us about your data.
Who is responsible
AntiCode is operated by Rashad Elkersawy, Friedrich-Naumann-Str. 66, 26125 Oldenburg, Germany. For privacy questions and requests, contact privacy@anticode.app. This notice covers the website, authenticated workspace, and the distinction between hosted review and local Mac checks. It also explains where further provider information remains to be confirmed.
What happens during a review
Eligible website built-in checks retrieve the selected CodHub pull-request diff on our server and inspect it without sending a model request. This is limited to SHA-1 repositories with complete matching diff and source counts. Missing metadata, unsupported formats and incomplete input stop the review. Personal path and severity preferences filter displayed findings; they do not remove code from the retrieved diff. Separately saved review source exclusions affect inspection after AntiCode retrieves and verifies the full provider diff; they do not prevent retrieval of excluded files. The effective exclusions are recorded with that run.
We save findings, source locations, review-run records and personal triage decisions. CodHub AI reviews, repository scans, automated comment delivery and coding proposals are not enabled in this release. Historical GitHub, AI and automation records may remain under existing retention arrangements. Native local checks inspect code on the device; configured native reporting or telemetry is a separate data path.
The personal Review Notebook stores your investigation notes, risk decision, intended manual change, checklist marks and customer-reported validation against an immutable saved review run and finding. These records belong to your AntiCode account and require current repository access. They are not team assignments, provider comments or verified repair evidence. Only the latest saved notebook content is retained in this feature; Undo keeps the prior content for the current visit and saves it as a new version number. Notebook records follow the owning account and captured-run retention; disconnecting access is not a deletion request. Do not enter credentials or unnecessary personal information. Your explicit exports include the selected evidence and your saved personal content.
Optional Human Review
When you submit a Human Review request, you explicitly authorize sharing a bounded package from a saved review you can access. It contains the repository and pull-request reference, head and base commits, target branch, review coverage, file references and credential-redacted finding explanations, together with your focus, question and subsequent messages. The package excludes source files, provider access tokens and suggested patches. Automated masking cannot guarantee detection of every sensitive value; do not include credentials or unnecessary personal data.
Authorized Human Review operators can see only requests submitted to that service; their role does not grant general access to customer repositories. We store the agreed scope and quote, assignments, messages, activity, and published assessments with the human reviewer identity, time and exact reviewed revision. Internal operator notes are separate from customer-visible conversations. An automated result is not a human assessment: an assigned person must write and publish the assessment after scope acceptance. Submission requests a separate quote, makes no charge and does not change your software plan.
Why we process information
We process information necessary to provide the account, requested reviews, saved results, and exports on the basis of providing the service you request under Article 6(1)(b) GDPR. Security and misuse prevention rely on our legitimate interest in protecting the service and its users under Article 6(1)(f), subject to individuals' rights. We process information under Article 6(1)(c) where an applicable legal obligation requires it.
Signing into CodHub or requesting a review is not blanket consent to unrelated processing. Repository information about other people requires a separate assessment of our role and the customer's authority; an account contract does not automatically establish a legal basis for every contributor's data. Contact us before relying on a particular data-processing arrangement for your organisation.
Who can receive information
Available sign-in methods are shown on the sign-in page. The Cloudflare-owned sign-in path does not merge AntiCode accounts by email or profile. Where an additional method is enabled, you can explicitly connect an unbound CodHub or Cloudburg identity to your current account. An identity already connected to another AntiCode account cannot be moved or merged here. Cloudburg sign-in grants identity access only. Repository access requires separate read-only CodHub authorization, including private repositories you may access. Repository authorization must match your linked CodHub identity. Repository tokens are encrypted on the server and are never returned by dashboard APIs. Supabase provides authentication and database services. Cloudflare infrastructure handles application traffic. Historical provider processing remains distinct from the current CodHub workflow.
Customers with verified access to the same repository can see its canonical saved findings. Personal preferences and triage are account-scoped. Disconnecting access does not erase all historical records.
When notification sending is enabled, Resend handles customer Human Review notices, and review-team notices can use the configured Cloudflare mail gateway. Customer notices use the verified AntiCode authentication email; review-team notices go to admin@rtwochain.com. Notifications include a request ID, generic update message and authenticated portal link, not source code, OAuth tokens, findings or request conversations. Sending attempts and provider acceptance do not establish inbox delivery. Cloudflare Email Routing forwards inbound human-review@anticode.app messages to admin@rtwochain.com; information you choose to email reaches that inbox.
Retention, deletion, and processing locations
Stored workspace records remain available unless removed. There is currently no verified fixed deletion schedule covering every account record, review, operational log, telemetry record, or provider backup. You can request deletion or retention information at privacy@anticode.app. Disconnecting a repository removes your workspace access; it does not delete every stored record or revoke your CodHub authorisation.
Withdrawing Human Review consent deletes the copied evidence package, removes operator access to the request and blocks pending notifications. It does not recall messages already submitted to the email provider. The request, messages, activity and prior assessments remain in account records until the account is deleted; deleting the account removes these linked application records. Account deletion currently requires a request to privacy@anticode.app. This describes application records, not a promise that delivered email, provider logs or backups are immediately erased.
The Resend sending domain notify.anticode.app is verified and configured in the EU (Ireland) region. This identifies the sending-domain configuration, not the location of all AntiCode processing. Other provider regions, contracting entities and applicable international-transfer safeguards remain to be confirmed for this notice. We do not promise EU-only processing or zero retention. OpenAI's API data controls distinguish response storage from other retention, including abuse monitoring; a storage-disabled request alone does not establish zero retention.
Your choices and rights
You can change workspace preferences, disconnect repositories, and stop requesting hosted reviews. Providing account and repository information is necessary for the corresponding features. Browser storage supports sign-in and interface preferences as described in our cookies notice. The regular website browser offers separate language remembering and a limited display reset. These controls do not revoke CodHub access or delete server-side records; the installed Mac app manages its language separately.
Subject to the GDPR's conditions, you may request access, correction, deletion, restriction, or portability and object to processing based on legitimate interests. Where consent applies, you may withdraw it. Contact privacy@anticode.app; we may request proportionate information to verify your identity. Dashboard exports are not a complete legal access response, and account deletion is not currently self-service. You may complain to a competent supervisory authority; the EDPB directory lists the authorities.
Contact fallback
If you cannot reach privacy@anticode.app, email admin@rtwochain.com and identify AntiCode in the subject.