PRIVACY

Privacy policy

This policy explains what ByteZoneX processes when you browse publicly, submit or claim projects, sign in with GitHub, or contact us.

Effective date: 2026-08-19

In short: ByteZoneX does not sell account or contact information to advertisers. The public site currently does not include dedicated advertising or behavioral-tracking scripts. If future tracking requires additional notice or consent, this policy and the relevant controls will be updated at the same time.
01

Information we collect

Public browsing does not require an account. For anonymous project submissions, the system primarily stores the submitted GitHub repository URL. After GitHub sign-in, we store basic identity data such as GitHub user ID, login, and avatar, and can associate submissions and claims with that account. If you contact us by email, we also receive the address, message, and attachments you choose to send.

02

GitHub OAuth and permissions

GitHub sign-in currently requests the read:user scope to identify the signed-in user and support ownership or permission checks needed for submission and claim workflows. The GitHub access token returned by OAuth is kept in the server-side session and is not published as profile data.

03

Browser storage and sessions

After GitHub sign-in, the public site stores an opaque ByteZoneX session token in browser localStorage for later submission and claim requests. The corresponding server-side session is valid for at most 14 days and expires afterward. You can also remove the local token by clearing site data in your browser. The admin console uses a separate HttpOnly session cookie for administrator access only.

04

How we use the information

We use this information to provide sign-in, project submission and claiming, repository permission checks, duplicate prevention, ownership management, correction and business communication, service security, and troubleshooting. A commercial partner does not gain access to account, submission, or contact information simply because it pays ByteZoneX.

05

Third-party services and sharing

GitHub OAuth and repository verification require communication with GitHub. Operation of the site also depends on necessary hosting, database, cache, object-storage, and network infrastructure, through which data may pass only as needed to provide those services. ByteZoneX does not sell personal information to advertisers. Sponsorship or advertising does not automatically provide access to user accounts, submissions, or contact emails.

06

Analytics, advertising, and tracking

As of the effective date, the public ByteZoneX code does not include Google Analytics, Clarity, AdSense, or similar dedicated behavioral-tracking or advertising scripts. Servers and infrastructure may still generate ordinary access logs for security, performance, and troubleshooting. If we later introduce advertising or analytics that uses cookies, device identifiers, or cross-site tracking, we will update this policy when it launches and provide additional notice or choices where applicable.

07

Data retention

Server-side login sessions remain valid for no more than 14 days. Project submissions, claims, and account associations are operational records and may be retained while the relevant project remains on the platform to support ownership management, auditability, and duplicate prevention. Contact email is retained by the mailbox as reasonably needed for business communication. When information is no longer needed, deletion or de-identification is considered alongside security, audit, dispute-resolution, and applicable requirements.

08

Security

We use reasonable access controls and technical measures intended to reduce unauthorized access, disclosure, or misuse. Login tokens and administrative credentials are not published as project data. No internet system can guarantee absolute security, so please do not send unnecessary sensitive information through submissions or email.

09

Access, correction, and deletion requests

You may contact us to ask about, correct, or request deletion of account, submission, claim, or contact information associated with you. Please include enough information to verify your identity and locate the relevant records. Public project facts or necessary audit records may require a different treatment depending on the nature of the record, platform integrity, and applicable requirements.

10

Changes to this policy

We will update this policy when ByteZoneX materially changes sign-in methods, advertising or analytics, data uses, or third-party services. Material changes will be described through the site or another reasonable channel, and the effective date will be updated.

Privacy contact

For questions about this policy, personal-information handling, or deletion requests, contact ByteZoneX by email.

mybolide@163.com