Updated 13 October 2026
Service providers and processing
The providers involved in AntiCode's current hosted workflow and the scope of this information.
How to read this list
AntiCode is operated by Rashad Elkersawy. This page identifies known technical providers and the information involved in their roles. It is not a final contractual subprocessor schedule: a provider's legal role depends on the service and agreement. Contact privacy@anticode.app about your organisation's processing requirements.
CodHub, Cloudburg and historical repository providers
CodHub supplies identity and the repository API for explicitly authorized read-only access. Where Cloudburg is enabled on the sign-in page, it supplies identity only; it does not grant CodHub repository access. The Cloudflare-owned sign-in path does not merge provider identities or accounts because an email, identifier or name matches. Repository metadata, pull-request information and selected diffs come from separately authorized CodHub access matching the linked CodHub identity. Historical GitHub records remain separate from current providers.
Supabase
Supabase provides authentication and database services for the hosted workspace. Information includes account-linked preferences, repository access records, repository and pull-request information, encrypted provider connections, review jobs, findings, and personal triage decisions.
Optional Human Review also stores submitted evidence packages, customer questions and messages, scope and quote acceptance, reviewer assignments, attributed human assessments, activity records and notification state. Operator authority is provisioned separately from customer or Enterprise roles and is limited to explicitly submitted requests.
Historical AI processing
CodHub AI reviews, coding, scans and automated replies are not enabled in this release. Eligible built-in checks do not send a model request. Earlier hosted AI workflows sent selected source context to OpenAI; historical results and applicable provider retention remain separate from current feature availability. A storage-disabled request did not establish zero retention or exclusion from abuse-monitoring records.
Hosting infrastructure
The current website uses Cloudflare infrastructure to deliver pages and process application requests. Application content and connection information can pass through that infrastructure. Historical Sites deployments and their retained records are distinct from the current host. Contractual roles and production-data access need assessment against the actual accounts used.
Cloudflare Email Routing separately forwards inbound human-review@anticode.app messages to admin@rtwochain.com. The message and sender information you choose to email pass through that forwarding service and the destination mailbox. Email does not create a Human Review request or establish repository authorization; use the authenticated portal to submit evidence.
Human Review notification providers
When notification sending is enabled, Resend handles customer notices using the configured notify.anticode.app sending domain. Review-team notices can use the configured Cloudflare mail gateway with its verified destination admin@rtwochain.com. The selected mode is an operational configuration, not an assurance of delivery. Providers receive the recipient address, sender and reply-to addresses, a generic subject and update, a request ID and an authenticated portal link. Customer recipients come from verified AntiCode authentication email records.
Notifications do not include source code, OAuth tokens, finding explanations or request conversations. AntiCode records sending attempts and provider acceptance separately from the saved request. Acceptance by the provider does not establish delivery to an inbox. The selected sending region does not establish that all account information, support operations or other providers process data only in that region.
Locations and agreements
The Resend sending-domain region is identified above. Other selected provider regions, exact contracting entities, applicable international-transfer safeguards, and the coverage of provider and customer data-processing agreements remain to be confirmed for this service. No EU-only processing or particular contractual protection is promised by this inventory.
Provider documentation below explains their published arrangements; linking it does not demonstrate that a specific AntiCode account has selected every available control. Ask privacy@anticode.app for clarification before relying on a required region, retention period, or processing agreement.
Contact fallback
If you cannot reach privacy@anticode.app, email admin@rtwochain.com and identify AntiCode in the subject.