Privacy Policy

1. Introduction & Scope

Welcome to GitHub Acceleration Doctor ("we", "us", or "our service"). We place the highest priority on user privacy and data rights. This Privacy Policy is designed to explain transparently how we handle information when you visit this website and utilize our open-source proxy relay services.

This policy applies to all network acceleration features, URL conversion tools, and web pages provided under the domain. By accessing or using our services, you acknowledge and agree to the practices described in this policy.

2. Zero Personally Identifiable Information (Zero PII) Policy

As a pure developer productivity tool, we operate under strict principles of data minimization and zero personal data collection:

• No Registration or Sign-in: Using any acceleration feature requires no account creation, no email address, no real names, no phone numbers, and no payment details.
• No Credential Harvesting: We strictly never collect, log, or request your Git Personal Access Tokens (PAT), SSH private keys, or passwords. Our proxy operates exclusively on public open-source assets.

3. Zero Persistence & Stream Relay (No-Logs Policy)

As an in-flight proxy for open-source files, we adhere strictly to the following data handling standards:

• Real-time Stream Relay: Data chunks received from upstream servers are immediately streamed into the client socket. No file payload is ever persisted or written to disk on our servers.
• No Decryption or Tampering: All transfers use encrypted HTTPS. We do not unpack, inspect, inject, tamper with, or cache the source code, binaries, or archives passing through.
• Ephemeral Sessions: Once the transfer terminates, the connection state is closed and discarded. No project copies remain on our systems.

4. Infrastructure Security & Standard Operational Logs

To maintain infrastructure uptime, defend against Distributed Denial of Service (DDoS) attacks, mitigate scraping abuse, and monitor capacity, edge web servers may automatically record standard technical HTTP access logs:

• Typical technical fields include: timestamp, client IP address, requested path, HTTP status code, and browser User-Agent.
• These operational logs are used strictly for traffic health, firewall rule tuning, and load balancing analysis. They are automatically rotated and deleted on rolling schedules and never used for behavioral profiling.

5. Website Analytics Notice

This site employs a lightweight, privacy-focused open-source analytics engine (Umami):

• Cookieless: The analytics program does not use any HTTP cookies and never tracks users across different websites.
• Anonymized Metrics: It reports aggregate aggregate daily page views (PV), unique visits (UV), and coarse regional distribution to help us forecast edge server bandwidth needs.

6. Local Storage Usage

We use HTML5 localStorage strictly for a single UI preference: theme (holding dark, light, or system). This ensures your visual mode preference persists across reloads. This value resides entirely on your device and is never uploaded or transmitted to our servers.

7. External Links & Upstream Platform Terms

Our proxy service routes requests to third-party open-source platforms based on user-supplied URLs. The legality, licensing, and upstream platform data practices of those repositories are governed entirely by their respective hosts and licenses.

We are not responsible for the privacy policies or practices of third-party websites linked from our pages. Users are encouraged to review the privacy notices of external platforms directly.

8. Policy Updates & Contact

We may update this Privacy Policy from time to time to reflect technological updates or regulatory changes. Any revisions will be published here with an updated effective date.

If you have questions, feedback, or compliance inquiries regarding this Privacy Policy, please reach out via our community channels.