Effective Date: June 30, 2026
This Privacy Policy explains how DC++ Hubs Directory – Public Hublist & Real-Time Hub Search collects, uses, stores, shares, and protects information when you use the website, hub search, generated hublist downloads, account features, hub submission forms, diagnostic tools, support requests, optional social login, and related services.
1. Who Is Responsible For Your Information
DC++ Hubs Directory – Public Hublist & Real-Time Hub Search is operated as a public Direct Connect hublist service. Privacy questions, data requests, or complaints should be sent through the contact or support information published on the site.
2. Information We Collect
We may collect information you provide directly, information created when the pinger checks a public hub, information collected automatically from your device, and information received from third-party login providers if social login is enabled.
| Category | Examples | Purpose | Retention | Shared With |
|---|---|---|---|---|
| Account data | Email address, username or account name, login method, locale, time zone, account preferences | Account access, authentication, hub ownership, support, security, and account management | Kept while needed for account operation, security, moderation, backups, audit records, or legal compliance. | Infrastructure and authentication providers used to operate DC++ Hubs Directory – Public Hublist & Real-Time Hub Search. |
| Hub submission data | Hub name, host, port, protocol, description, topic, country, software, owner notes, icons, logos, and pinger credentials if provided | Publish hub listings, verify hub availability, display hub pages, generate files, and contact hub owners when needed | Kept while the hub is listed or while needed for auditing, abuse prevention, backups, or legal compliance. | Public visitors, search engines, generated hublist files, and infrastructure providers used by the site. |
| Pinger and hub history data | Online status, user counts, share size, reliability, ping timestamps, hub software, requirements, errors, and historical chart values | Show current hub status, build history graphs, detect broken listings, and generate hublist files | Kept while useful for hub history, statistics, debugging, abuse prevention, backups, or legal compliance. | Public pages when the data is part of a hub listing, plus infrastructure and logging providers. |
| Technical and request data | IP address, browser type, device type, operating system, session identifiers, route, referrer, user agent, security logs, error logs, and request records | Security, abuse prevention, troubleshooting, performance monitoring, analytics if enabled, and operational records | Kept while needed for troubleshooting, abuse prevention, analytics, security, audit records, or legal compliance. | Infrastructure, security, logging, and analytics providers used by DC++ Hubs Directory – Public Hublist & Real-Time Hub Search. |
| Email and support data | Verification emails, password reset emails, service notices, delivery logs, support tickets, replies, and status updates | Account messages, support, security notices, ticket handling, and service communications | Kept while needed to confirm delivery, troubleshoot mail issues, prevent abuse, handle tickets, or comply with legal obligations. | Email delivery providers and infrastructure providers used for transactional and support messages. |
| Social login data | Provider account ID, email address, name, profile image if enabled, and verification status | Login, account linking, duplicate account prevention, account security, and support | Kept while needed for authentication, account security, support, or legal compliance. | Google, Facebook, or other enabled login providers. |
3. How We Use Information
We use information to operate hub search, generate hublist files, maintain accounts, authenticate users, verify hub availability, display hub history, send service email, handle support tickets, prevent abuse, moderate listings, debug errors, improve performance, process privacy requests, and comply with legal obligations.
4. Public Hub Data
Hub data submitted for listing is intended to be public. Hub pages, search results, hublist downloads, JSON files, XML files, sitemaps, Open Graph previews, and search engines may display or cache public hub information.
5. Pinger History
The pinger may store snapshots such as online status, users, share size, reliability, hub requirements, software names, ping counters, error messages, and timestamps. These snapshots help users understand long-term hub activity without recalculating large audit tables.
6. Cookies And Similar Technologies
We use cookies and similar technologies for required site functions such as login sessions, remember-me authentication, security, CAPTCHA, locale preferences, admin settings, and analytics if enabled. More details are available in the Cookie Policy.
7. Email And Communications
We may use your email address to send account verification messages, password reset messages, security notices, support replies, ticket status updates, moderation notices, and service updates. We may keep delivery logs and related technical records to confirm that messages were sent and to troubleshoot email issues.
8. Third-Party Service Providers
We may use third-party providers for hosting, storage, email delivery, analytics, CAPTCHA, authentication, social login, logging, security, DNS, and infrastructure. Those providers may process information on our behalf only to provide their services, secure the site, troubleshoot problems, or meet legal requirements.
9. Social Login Providers
If Google, Facebook, or another social login provider is enabled, you may choose to sign in through that provider. We request only information needed to authenticate the account, such as provider account ID, name, email address, email verification status, and profile image if enabled. We do not receive your social login password.
10. Legal Basis Where Required
If privacy law requires a legal basis for processing, we process information because it is needed to provide the service, because you consented, because we have a legitimate interest in operating, securing, debugging, moderating, and improving the service, or because we must comply with legal obligations.
11. How We Share Information
We do not sell personal information. We may share information with service providers that help operate the site, when required by law, to protect rights and safety, to investigate abuse or security issues, in connection with a business transfer, or with your consent. Public hub data is also shared by design through hub pages, hublist downloads, and search results.
12. Analytics, Advertising, And Tracking
If analytics are enabled, we may use analytics tools to understand traffic, route usage, hublist downloads, errors, and performance. If advertising or cross-site tracking is ever enabled, this Privacy Policy and the Cookie Policy should be updated before those features run. Unless stated otherwise, DC++ Hubs Directory – Public Hublist & Real-Time Hub Search does not sell personal information or use submitted hub data for targeted advertising.
13. Data Retention
We keep information only as long as reasonably needed for the purposes described in this Privacy Policy, unless a longer period is required or allowed by law. Account data is generally kept while the account remains active. Hub submissions, pinger history, generated file records, logs, tickets, and backups may be kept for periods needed for operation, auditing, security, recovery, statistics, and legal compliance.
14. Security
We use reasonable technical and organizational measures designed to protect information from unauthorized access, loss, misuse, alteration, or disclosure. No online service can guarantee complete security, so you should use a strong password, keep login details private, and contact the site administrator if you believe your account has been compromised.
15. Your Choices And Rights
Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal information. You may also be able to withdraw consent where processing is based on consent. We may need to verify your identity before completing a request.
16. Account And Data Deletion
You may request deletion of your account and personal information through available account tools or by contacting the site administrator. Some information may remain in backups, security logs, audit records, pinger history, moderation records, or legal records for a limited period where needed to protect the service, prevent abuse, resolve disputes, or comply with law.
17. Children
The service is not intended for children under 13. We do not knowingly collect personal information from children under 13. If we learn that we collected personal information from a child under 13 without required consent, we will take reasonable steps to delete it.
18. International Users
If you access DC++ Hubs Directory – Public Hublist & Real-Time Hub Search from outside the country where our servers or service providers are located, your information may be processed in countries with privacy laws different from those in your location.
19. Changes To This Policy
We may update this Privacy Policy when site features, providers, legal requirements, or operational practices change. When we make material changes, we will update the effective date and may provide additional notice where appropriate.
20. Contact
Privacy questions and requests should be sent through the contact or support information published on DC++ Hubs Directory – Public Hublist & Real-Time Hub Search.