GCA Privacy Notice

This notice explains how the public GCA website handles live email registration, contact suppression, local member pre-registration packets, wallet balance verification data, and controlled HTTPS intake for the GCA AI Quant Access account layer.

Email Registration Email Unsubscribe Participation Terms Support & Intake Member Pre-Registration Member Ledger Technical Evidence

Status Public privacy notice

Current Site Mode Email API live / member packet local

Contact support@gcagochina.com

Last Updated 2026-05-20

What The Public Site Collects

Email registration submits email, optional display name, source, language, interest tags, contact-consent acknowledgement, and no-secrets acknowledgement to the GCA Cloudflare Workers + D1 email API.

Email unsubscribe submits email, reason, source, contact-suppression acknowledgement, and no-secrets acknowledgement to the GCA Cloudflare Workers + D1 contact-suppression API.

The member pre-registration page still creates a local pre-registration packet in the browser. That packet can include email, Telegram handle, Base wallet address, declared GCA balance, program intent, consent flags, generated registration ID, and timestamp.

When Data Leaves The Browser

Email registration and email unsubscribe requests leave the browser when the user submits those forms on gcagochina.com; the production API base is https://gca-registration-api.gcagochina.workers.dev.

Member pre-registration data leaves the browser only when a user copies it, downloads it, emails it to support@gcagochina.com, or later submits it through a controlled HTTPS account UI after that flow is published.

Wallet Verification

Wallet verification is planned as a read-only ERC-20 balanceOf check against the GCA contract on Base Mainnet. GCA does not need private keys, seed phrases, exchange API secrets, withdrawal permission, or custody to verify a public wallet balance.

Future Controlled Intake

After controlled HTTPS account UI is live, GCA may store pre-registration fields, wallet verification results, holding-period evidence, credit ledger records, GCA Member status, member benefit status, review statuses, operational logs, and support notes needed to run the account path.

How Data May Be Used

Support review and user follow-upAllowed

Wallet balance eligibility checksAllowed

100 credits, GCA Member, and member benefit ledger recordsAllowed

Fraud, abuse, and duplicate-registration preventionAllowed

Private keys, seed phrases, or custody requestsNever

User Requests

Users can request correction or deletion by emailing support@gcagochina.com. Users can also use unsubscribe.html to request that an email be excluded from future GCA contact exports. Some records may be retained when needed for abuse prevention, security review, operational integrity, or legal compliance. GCA does not sell registration or contact data.

Privacy References

Use these readable privacy, terms, member, ledger, registration, unsubscribe, and support pages for public privacy and participation context.

Email registrationregister.html

Email unsubscribeunsubscribe.html

Participation Termsterms.html

Member programmembers.html

Member ledgermember-ledger.html

Support intakesupport.html

Public Safety Boundary

No private key, seed phrase, exchange API secret, withdrawal permission, or custody request is part of the GCA member flow. Pre-registration data does not create a live GCA AI Quant Access account, does not make credits claimable from this static page, and does not override wallet balance checks or risk controls.