Effective Date: June 30, 2026
This Cookie Policy explains how DC++ Hubs Directory – Public Hublist & Real-Time Hub Search uses cookies and similar technologies. Cookies are small files stored on your device that help websites remember sessions, keep accounts signed in, protect forms, measure performance, and save preferences.
1. Types Of Cookies We May Use
Required cookies: These cookies are needed for the site to work. They may support login sessions, account authentication, CSRF protection, security checks, Google CAPTCHA, route state, and abuse prevention.
Remember-me cookies: If you choose a remember-me option, we may store a cookie that keeps you signed in for a longer period. You can clear this cookie by logging out or clearing browser cookies.
Preference cookies: These cookies remember choices such as locale, interface settings, chart ranges, admin filters, or similar site options.
Analytics cookies: If analytics are enabled, cookies or similar technologies may help measure page usage, hublist downloads, route performance, errors, and general traffic patterns. Where required, analytics cookies are used only after consent.
Social login cookies: If Google, Facebook, or another login provider is enabled, that provider may use cookies or similar technologies during authentication. Those cookies are controlled by the provider and are subject to the provider's own policies.
2. Why We Use Cookies
We use cookies to keep the site secure, maintain login sessions, remember preferences, prevent abuse, support account features, improve performance, troubleshoot technical problems, and understand how users interact with hub search, hub pages, hublist downloads, support forms, and admin tools.
3. Third-Party Cookies
Some cookies may be set by third-party providers that help operate the service, such as authentication providers, Google CAPTCHA, analytics providers, hosting tools, or security services. We will update this policy when major third-party cookie providers are added or removed.
4. Google CAPTCHA
If Google CAPTCHA is enabled, DC++ Hubs Directory – Public Hublist & Real-Time Hub Search uses it only on forms where the CAPTCHA field is rendered, such as login, registration, password reset, support tickets, hub submission, or diagnostics when configured to require it. The site can be configured to use Google reCAPTCHA v2 checkbox, Google reCAPTCHA v2 invisible, or Google reCAPTCHA v3 score validation.
Google reCAPTCHA v2 checkbox: v2 checkbox shows a visible widget. Google checks browser, device, interaction, network, and security signals to decide whether to accept the interaction or show an image or audio challenge. The form is submitted only after Google returns a successful CAPTCHA token.
Google reCAPTCHA v2 invisible: v2 invisible does not show a checkbox before submission. When the user submits the form, Google runs the check in the background. If Google trusts the request, the form continues. If Google is unsure, it may interrupt the flow with a visible challenge before returning a token. The badge may appear at the bottom right, bottom left, or inline with the protected form.
Google reCAPTCHA v3 score: v3 usually runs in the background and returns a score for a named action, such as login or form submission. DC++ Hubs Directory – Public Hublist & Real-Time Hub Search sends the token to the server, verifies the expected action, and compares the score with the site threshold. A higher threshold is stricter.
Google reCAPTCHA may set a cookie named _GRECAPTCHA, commonly from www.google.com, google.com, or www.recaptcha.net, to provide risk analysis and abuse prevention. DC++ Hubs Directory – Public Hublist & Real-Time Hub Search does not set or read the _GRECAPTCHA cookie directly. Google controls it as part of the CAPTCHA service.
5. Cookie Consent
Required cookies may be used because they are necessary to provide the service. For optional cookies, such as analytics or advertising cookies if enabled, we will request consent where required by law. You can accept, reject, or change optional cookie choices through a cookie banner, cookie settings page, browser setting, or device setting.
6. Managing Cookies
You can control cookies through browser settings. Most browsers let you delete cookies, block cookies, or receive alerts before cookies are stored. Blocking required cookies may cause account login, hub editing, support tickets, CAPTCHA checks, or admin tools to stop working correctly.
7. Current Cookie Categories
This table lists the main cookie categories expected for DC++ Hubs Directory – Public Hublist & Real-Time Hub Search. Provider-controlled cookie names or retention periods may vary based on browser settings, provider configuration, region, and whether the user is already signed in to that provider.
| Name | Provider | Purpose | Type | Retention |
|---|---|---|---|---|
| PHPSESSID or the current Symfony/PHP session cookie name | DC++ Hubs Directory – Public Hublist & Real-Time Hub Search | Maintains login sessions, CSRF protection, flash messages, and site security | Required | Usually the active browser session, subject to browser behavior and server session settings |
| REMEMBERME or the current remember-me cookie name | DC++ Hubs Directory – Public Hublist & Real-Time Hub Search | Keeps users signed in when remember-me is selected | Required or preference | Up to the configured remember-me lifetime, unless cleared sooner by the browser or logout |
| Locale, interface, chart, or admin preference storage | DC++ Hubs Directory – Public Hublist & Real-Time Hub Search | Stores display preferences such as locale, chart ranges, filters, or interface options | Preference | Varies by preference and browser storage lifecycle |
| Provider-defined analytics cookie names when analytics is enabled | Configured analytics provider, if analytics is enabled | Measures traffic, hublist downloads, usage patterns, feature performance, and errors if analytics are enabled | Optional analytics | Controlled by the analytics provider and current consent/configuration state |
_GRECAPTCHA |
Google reCAPTCHA | Supports abuse prevention, bot detection, risk scoring, and account security if Google CAPTCHA is enabled | Security | Controlled by Google policy |
| Provider-defined authentication cookie names during social login | Google, Facebook, or other enabled login provider | Supports authentication when users choose social login | Authentication | Controlled by provider policy |
8. Optional Cookies And Consent Choices
Where required by law, optional analytics, advertising, or similar cookies will not be used unless you consent. If a cookie banner or settings page is available, you may use it to accept, reject, or change optional cookie choices. Required cookies cannot be disabled through the site because they are needed for login, security, and core functionality.
9. Changes To This Cookie Policy
We may update this Cookie Policy when cookie use changes, when providers are added or removed, or when legal requirements change. The effective date above shows when this policy was last updated.
10. Contact
Questions about cookies should be sent through the contact or support information published on DC++ Hubs Directory – Public Hublist & Real-Time Hub Search.