Privacy policy

Information we collect

Proxbyte Auth stores the name and email address you provide, your email verification status, a password hash, account timestamps, and information needed for verification and password recovery. Login records can include an IP address, browser information, and session timestamps.

When you register an application, we store its name, client identifier and connection credentials, callback URLs, allowed domains, icon, policy links, sharing permissions, and completed sign-in count. We also store authorization grants and tokens needed to operate sign-in.

Proxbyte Git stores the profile and authentication information you provide, account settings, SSH keys or other access credentials you configure, and repositories, commits, issues, pull requests, and other content you submit. Git commits can contain author names and email addresses.

Requests to our websites pass through Cloudflare. Request metadata, including IP addresses, browser details, visited URLs, and security events, may be processed by Cloudflare and the servers operating these services. If you contact us, we receive your message and contact details.

Why we use it

We use this information to create and protect accounts, verify email ownership, recover access, authenticate sign-ins, manage applications and repositories, deliver service emails, prevent abuse, investigate problems, and respond to requests.

Where a legal basis is required, operating the features you request supports providing the service; security, abuse prevention, and diagnostics support legitimate operational interests; legal requirements may require specific records; and optional sharing or other optional features may rely on your choices or consent. You do not have to create an account to read the public website. Account features require the information necessary to operate them.

What connected apps receive

When you approve a Proxbyte Auth sign-in, the app receives the account identifier and the profile or email claims permitted by the requested scopes, such as your display name, generated username, email address, and email verification status. The app receives authorization tokens, not your Proxbyte password.

Each sign-in requires approval. Connected apps have their own policies and may keep a local account or session after Proxbyte access is revoked. Contact the app operator about data it has already received.

App names, uploaded logos, and sign-in images are public so connected services can display them. App settings, client secrets, and account details are not included in those public images.

Repositories and public information

Content you publish in public repositories, profiles, issues, or other public areas can be read, indexed, downloaded, and copied by others. Private repositories are subject to their configured access permissions. Administrators can access information where needed to operate, secure, or support the services.

Removing a repository or account cannot remove clones, forks, cached pages, or copies already held by other people. Git history can retain author details and contributions unless that history is changed separately.

Semi-private Git service

Proxbyte Git serves approved projects and collaborators on a semi-private basis. Administrators approve access and create Git accounts. If you request access, we receive the account and contact details you provide to process that request.

Individual repositories, profiles, and contributions have their own visibility settings; the semi-private nature of the service does not make content marked public confidential.

Cookies and analytics

Auth and Git use cookies and similar browser storage for login sessions, security checks, and preferences such as theme or language. Blocking necessary cookies can prevent sign-in from working.

Cloudflare provides network delivery and security, and Cloudflare Web Analytics is enabled on Proxbyte Auth to understand site traffic and performance. The basic Proxbyte homepage does not add its own advertising or analytics scripts. Cloudflare’s own processing is described in its privacy policy.

Service providers and disclosure

Cloudflare handles traffic delivery, tunnels, and security for the public services. Resend delivers Proxbyte Auth’s verification and password-reset emails and processes recipient addresses, message content, and delivery information for that purpose. Other email services configured for Git may process Git notification emails.

Infrastructure and email providers may process information in countries other than yours. Their policies describe their processing. We may also disclose information when required by law, to address abuse or security incidents, to protect rights, or at your request.

Storage and retention

Account data, application settings, and Git content do not have scheduled automatic deletion in the current service. They remain until removed through available controls or an administrator handles a deletion request, subject to legal and security needs.

Auth sessions normally expire after seven days, with expiry refreshed during continued use. Auth access tokens normally last one hour, authorization codes one minute, and grants and refresh tokens up to seven days. Expiry makes a credential unusable; it does not promise that every related database record disappears immediately. Git manages its own sessions and credentials separately.

Operational logs and provider records follow the retention settings of the systems that hold them. Existing backups may retain earlier information until they are replaced or manually removed. Ask us about the records relevant to your request.

Your choices and requests

You can sign out, revoke other Auth sessions, manage your registered applications, and use Git’s available account and repository controls. For access, correction, export, restriction, objection, account closure, or deletion requests, email liam@proxbyte.online. We may verify account ownership before making changes or disclosing information.

Some data is needed to provide an account or preserve repository history, security records, or legal obligations. We will explain relevant limits when responding. Depending on where you live, you may also have rights to withdraw consent or complain to your local data protection authority. These rights remain subject to applicable law.

Security and updates

We use access controls, password hashing, and HTTPS on the public services. No service can guarantee that information will never be lost or accessed without permission. Report suspected security problems privately to liam@proxbyte.online.

We will update this page when the services or their data practices change and show the latest update date. Contact liam@proxbyte.online if anything in this policy is unclear.