隐私说明

适用站点:agx.cool · 更新日期:2026 年 10 月 31 日

AGX 是供参赛者报名比赛、提交代码和查看评测结果的平台。本文说明本站处理的数据、登录方式、Cookie、保存期限和数据请求。

账号与第三方登录

使用 Google 登录时,AGX 请求 openid、profile 和 email 权限,读取 Google 账号标识、显示名称及已由 Google 验证的邮箱。使用 GitHub 登录时,AGX 请求只读邮箱权限(user:email),读取公开账号标识、登录名、显示名称及已由 GitHub 验证的主邮箱。平台将这些资料与平台账号绑定,用于创建账号、识别再次登录、你主动选择的账号绑定,以及依据已验证身份校验权限。账号还没有账号邮箱时,平台会把第三方已验证的邮箱记为账号邮箱。只有当 Google 能担保邮箱归属(gmail.com 邮箱或 Google Workspace 账号),且该邮箱已是某个平台账号的账号邮箱时,Google 登录才会直接进入该账号;其他情况不会仅凭同名或邮箱合并账号,你需要先登录原账号,再在设置中绑定。平台不请求 Google 邮件正文、通讯录、云盘或 GitHub 仓库权限。授权码和第三方访问令牌仅用于本次登录验证,不作为持久凭据保存在平台数据库。

登录资料的保存、共享与保护

平台数据库保存第三方提供方、账号标识、显示名称、已验证的 Google 或 GitHub 邮箱、GitHub 登录名及绑定时间;绑定存在期间保留这些资料,并在再次登录时更新。获授权的平台管理员可在账号管理及教学管理工具中查看这些身份资料,用于核对参赛者和处理账号请求;这些资料不向其他普通用户公开。你可以在账号设置中解绑第三方账号,但须保留至少一种可用登录方式。解绑会从当前数据库移除对应的身份绑定资料,不会删除平台账号和比赛记录。Google 登录资料用于上述账号与权限功能,不用于出售、广告投放或通用 AI 模型训练。站点及数据库运行在腾讯云香港基础设施上,云服务承载服务运行与运维备份;第三方登录提供商按其自身隐私政策处理登录请求。平台通过 HTTPS 传输资料,使用登录鉴权、权限检查和受限制的数据库网络访问保护数据。

账号邮箱与验证码

注册密码账号时,平台会验证并保存你的邮箱和验证时间,作为账号邮箱。账号邮箱可以代替用户名登录,可以接收登录验证码,忘记密码时也可以用验证码登录后重设密码。已有账号可在设置中自愿绑定或更换账号邮箱,不绑定不影响原有登录和参赛;通过 Google 或 GitHub 登录的账号会自动以第三方已验证的邮箱作为账号邮箱。邮箱验证码仅用于你发起的注册、绑定、更换邮箱或登录,不用于营销。腾讯云邮件推送服务会处理收件邮箱、验证码及邮件内容以完成投递。平台只保存验证码的加密校验值、用途、到期时间和尝试次数,不保存验证码明文;验证码 10 分钟后失效,过期记录在后续发送请求中分批清理。账号邮箱不向其他普通用户公开。

Cookie 与运行记录

平台使用必要的会话 Cookie 保持登录,并使用最长 10 分钟的授权流程 Cookie 校验登录回调。登录成功后,平台还会设置一个最长 30 天的静默设备 Cookie,只记录这个浏览器曾成功登录哪个账号,用于在有人反复猜测密码时让你的常用设备免于登录限速;退出登录或修改密码会使其失效。数据库保存会话校验信息、授权流程临时记录及用于限制滥用的请求计数。服务运行日志可能包含请求路径、网络地址、状态和错误信息,用于排障及安全维护;应用访问日志去除 OAuth 回调的查询参数。

参赛数据与公开内容

你提交的代码与版本、报名、对局结果、回放、决策记录和训练轨迹会保存在平台,用于运行比赛、评测和呈现结果。公开赛事、榜单和正式对局回放可被其他用户访问;代码、决策记录和训练导出只对所属账号及获授权的教师或管理员开放。公开回放不包含私有决策轨迹。比赛数据由平台及上述云基础设施承载。请勿在公开名称、代码或其他公开内容中提交个人秘密。

保存、导出与账号管理

代码、比赛记录和训练轨迹会保存至 2031 年,并包含于平台运维备份中。登录账号或使用账号 API 密钥,只能从自己有权访问且成功结束、轨迹完整的游戏对局导出本人席位;公开回放不含私有决策轨迹。解绑第三方账号不会删除平台账号或比赛记录;备份按运维保留策略轮转,解绑或数据请求不会立即移除已有备份副本。当前站点没有自动删除账号入口。

联系与数据请求

如需查询、更正或申请删除账号相关数据,或对本说明有疑问,请联系 haozhe_wu@connect.hku.hk,说明平台用户名及请求事项。处理请求前需要核实账号归属;请勿发送密码、恢复码、访问令牌或客户端密钥。

Privacy Notice

Applies to: agx.cool · Updated: 31 October 2026

AGX lets participants enter competitions, submit code, and view evaluation results. This notice explains the data, sign-in methods, cookies, retention, and data requests for this site.

Accounts and social sign-in

For Google sign-in, AGX requests openid, profile, and email and reads your Google account identifier, display name, and email address verified by Google. For GitHub sign-in, AGX requests read-only email access (user:email) and reads your public account identifier, login name, display name, and the primary email address verified by GitHub. These details are linked to your platform account to create the account, recognize later sign-ins, support linking you choose, and check permissions based on verified identity. If your account has no account email yet, AGX records the provider-verified email as your account email. A Google sign-in goes straight into an existing account only when Google vouches for the address (a gmail.com address or a Google Workspace account) and that address is already the account email of that platform account; otherwise accounts are not merged by email or name, and you sign in to your existing account first and link the provider in settings. AGX does not request Google mail contents, contacts, Drive files, or GitHub repository access. Authorization codes and provider access tokens are used for the current sign-in verification and are not stored as persistent database credentials.

Storage, sharing, and protection of sign-in data

The platform database stores the provider, account identifier, display name, verified Google or GitHub email, GitHub login name, and linking time. It retains these details while the identity remains linked and updates them on later sign-ins. Authorized platform administrators can view these identity details in account and teaching administration tools to identify participants and handle account requests; these details are not disclosed to other ordinary users. You can unlink an identity in account settings while retaining at least one usable sign-in method. Unlinking removes that identity record from the current database; it does not delete your platform account or competition records. Google sign-in data is used for the account and permission features described above, not sold or used for advertising or general-purpose AI model training. The site and database run on Tencent Cloud infrastructure in Hong Kong, which hosts service operation and operational backups. Sign-in providers process sign-in requests under their own privacy policies. AGX uses HTTPS, authentication, permission checks, and restricted database network access to protect data.

Account email and sign-in codes

When you register a password account, AGX verifies and stores your email and verification time as your account email. You can sign in with your account email instead of your username, receive sign-in codes at it, and use a code to sign in and set a new password if you forget it. Existing users may optionally add or change an account email in settings; choosing not to does not affect existing sign-in or competition access. Accounts that sign in with Google or GitHub use the provider-verified email as their account email automatically. Codes are used only for registration, adding or changing an email, or signing in that you request, not for marketing. Tencent Cloud Simple Email Service processes the recipient address, code, and message to deliver the email. AGX stores only a keyed hash of the code, its purpose, expiry, and attempt count, not the plaintext code. Codes expire after 10 minutes, and expired records are cleaned up in batches during later send requests. Account emails are not public to other ordinary users.

Cookies and operational records

The platform uses a necessary session cookie to keep you signed in and an authorization-flow cookie for up to 10 minutes to validate the sign-in callback. After a successful sign-in it also sets a silent device cookie for up to 30 days that only records which account this browser signed in to, so your usual device is not slowed down when someone repeatedly guesses your password; signing out or changing your password invalidates it. The database stores session verification data, temporary authorization records, and request counters used to limit abuse. Operational logs may contain request paths, network addresses, status, and errors for debugging and security; application access logs remove OAuth callback query parameters.

Competition data and public content

Your submitted code and versions, entries, match results, replays, decision records, and training traces are stored to run competitions, evaluate submissions, and present results. Public competitions, leaderboards, and official replays can be viewed by other users; code, decision records, and training exports are available only to the owning account and authorized teachers or administrators. Public replays do not include private decision traces. Competition data is hosted by the platform and the cloud infrastructure described above. Do not put personal secrets in public names, code, or other public content.

Retention, exports, and account management

Code, competition records, and training traces are retained through 2031 and included in operational backups. A signed-in account or account API key can export only its own seat from an accessible game match that completed successfully with a complete trace; public replays do not contain private decision traces. Unlinking a social account does not delete the platform account or competition records. Backups rotate under the operational retention policy, and unlinking or a data request does not immediately remove existing backup copies. This site has no automatic account-deletion endpoint.

Contact and data requests

For access, correction, or deletion requests about account data, or questions about this notice, contact haozhe_wu@connect.hku.hk with your platform username and request. We verify account ownership before processing a request. Do not send passwords, recovery codes, access tokens, or client secrets.