RunningHub Duck Decoder Privacy Policy
This Privacy Policy applies to the browser extension RunningHub Duck Decoder (the "Extension"). It explains what data the Extension may access, where that data comes from, how it is used, whether it is shared, how long it is kept, and how you can contact us about privacy-related requests.
1. Scope
This Policy applies only to data processing activities that occur when you install
and use the Extension in Chrome or other compatible browsers. It does not apply to
data processing independently carried out by the RunningHub website, Bilibili
(bilibili.com), or any other third-party websites or services.
2. Data We Collect and Process
The Extension processes data only to the extent necessary to provide its features, verify authorization, protect service security, and troubleshoot issues.
2.1 Data You Provide or That Is Directly Related to Your Account
- RunningHub account identifiers, binding status, and membership expiration status.
- Tokens or other security credentials used for login verification and activation checks.
- Bilibili account information used in the activation flow, such as UID, login status, and whether the required activation condition is met.
This data is used to complete account binding, verify membership, synchronize activation results, and protect account and service security. We do not collect your plaintext passwords.
2.2 Browser, Device, and Extension Runtime Information
- A device identifier generated by the Extension.
- Basic runtime details such as browser type, extension version, language, and time zone.
- Necessary technical information used to recognize the device or runtime environment, such as browser environment identifiers, page runtime state, and technical status information related to feature execution.
This information is used for device recognition, authorization checks, service security, and compatibility diagnostics. We do not use it for advertising profiles or cross-site behavioral tracking.
2.3 Usage Statistics and Service Interaction Records
- Service usage information and necessary interaction records, such as whether a feature request has been made and whether further authorization checks are needed.
- Basic status information related to account or authorization state, such as whether an account is bound and whether membership is active.
- Minimal runtime and error information related to service requests, such as request time, response status, and error prompts.
These records are used to keep the service stable, support normal operation, and troubleshoot failures.
2.4 Cookies, Local Storage, and Web Login State
- The Extension uses browser storage to save device IDs, authorization tokens, guest configuration, language preferences, and other necessary settings.
- The Extension reads login-related cookies or login state from the current RunningHub site only when you actively trigger account activation, binding verification, or status synchronization, so it can confirm which account is currently signed in in that browser.
- That login-identification information may be sent together with a device identifier to our server only for activation checks, account binding, abuse prevention, and authorization status synchronization. It is not used for advertising, profiling, or sale to third parties.
- The Extension does not read cookies from unrelated websites for advertising or data-broker purposes, and it does not continuously monitor your general browsing activity.
Cookies, login state information, and local storage are used only for the Extension's own features, not for third-party advertising, and are not sold to third parties.
2.5 Download and Page Access Scope
- The Extension may access currently open RunningHub, Bilibili, and pages required for Extension features in order to identify page state and execute those features.
- When you actively trigger download or decoding features, the Extension may access image resource URLs, file download URLs, and related resource links on the page, and may use browser download capabilities to save selected resources to your local device.
The Extension does not continuously monitor all of your browsing activity for advertising or data-broker purposes. Host permissions and page access are used only to provide the declared Extension functionality.
3. How the Data Is Processed
Depending on the feature scenario, data may be processed in the following ways:
- Read and compared locally in the browser, such as local storage, cookies, page state, or login state, to determine whether a feature can continue.
- Sent to our server for verification, such as device identifiers, authorization tokens, account identifiers, binding status, membership status, login verification results, and the minimal login-identification data needed only when you actively trigger RunningHub activation or binding verification.
- Cached locally in the browser, such as tokens, configuration, and language preferences, to reduce repeated requests and improve user experience.
- Used for troubleshooting and service protection, such as minimal runtime logs, interface status, and error information needed to identify compatibility or service issues.
We do not use this data for advertising unrelated to the Extension, and we do not sell it, broker it, or use it for cross-site profiling.
4. Data We Do Not Collect or Sell
During your use of the Extension, we do not collect, retain as business data, or sell:
- Plaintext passwords, payment passwords, or bank card numbers.
- Original text, images, or file contents related to decoded materials as separate business content uploaded to our server.
- Highly sensitive identity information such as national ID numbers.
We do not sell personal information, and we do not provide your data to third-party advertisers for targeted advertising or cross-site tracking.
5. How We Use the Data
We use the data only for the following necessary purposes:
- Provide core Extension features, including RunningHub- and Bilibili-related login detection, binding checks, membership recognition, and activation flows.
- Record necessary usage information and perform security checks to support stable service operation.
- Synchronize authorization state, cache necessary local configuration, and re-check status when tokens expire.
- Fix failures, analyze compatibility issues, and improve Extension stability and user experience.
- Respond to support requests, complaints, deletion requests, and compliance inquiries.
6. Where Data Is Stored, How Long It Is Kept, and Security Measures
Depending on purpose, data may be stored in the following locations:
- In the browser locally, such as device IDs, authorization tokens, feature configuration, language preferences, and local state needed for the Extension to run.
- On our servers, such as data related to authorization, activation, account binding, membership status, login verification results, service usage, and necessary troubleshooting.
- In logs or cache systems, such as minimized runtime data used for short-term state synchronization, performance support, error diagnosis, and service stability.
We retain data only for the shortest reasonable period necessary for the relevant purpose and apply reasonable safeguards.
- Sensitive fields such as device identifiers, tokens, and similar data are handled and stored using appropriate security measures where possible.
- Data related to security, authorization, and service operation is kept only for as long as needed to fulfill the relevant purpose.
- Locally stored tokens and settings usually expire or are removed when tokens expire, when you clear browser data, or when you uninstall the Extension.
- When data is no longer necessary for the purposes described above, we delete, de-identify, or anonymize it within a reasonable period.
7. Who We Share Data With
We do not sell or rent your personal data. We share data only when necessary:
- With our own backend services or infrastructure providers as needed to provide, maintain, and protect the Extension service.
- With service providers that support cloud hosting, storage, network security, messaging, or operations, but only to the extent necessary for them to perform those services for us.
- When required by applicable law, court order, or lawful request from authorities.
- When reasonably necessary to address security incidents, fraud risks, or service abuse, within a lawful and limited scope.
We do not use your data for third-party advertising, data brokerage, sale of personal information, or cross-site behavioral tracking.
8. Your Rights
Subject to applicable laws and technical feasibility, you have the right to:
- Access basic status information associated with your account or device.
- Request correction of inaccurate account or binding information.
- Uninstall the Extension and contact us to request deletion of server-side data associated with your account, device identifier, or activation records, where permitted by law.
- Clear local browser storage, delete relevant cookies, stop using the Extension, or ask us to stop processing certain data.
- Contact us or, where applicable, contact a competent regulator if you believe our processing does not comply with applicable law.
To help us process a deletion request, please include your account identifier, device identifier, or other relevant details in your email where possible.
9. Browser Permission Disclosure
The Extension may request the following browser permissions to operate:
- storage: to save configuration and language preferences.
- cookies: only to read login-related cookies from the current RunningHub site when you explicitly trigger activation, binding verification, or status synchronization, so the Extension can confirm the signed-in account and complete authorization checks.
- downloads: to download files to your local device when you explicitly trigger a download.
- host permissions: only to access the four service-related domains
xiaoyaoyou.com,runninghub.com,runninghub.ai, andrunninghub.cnfor session initialization, authorization checks, activation requests, and status synchronization.
If you deny these permissions, some or all Extension features may not work properly.
10. Children's Privacy
The Extension is intended for users with full civil capacity and is not directed to children. If you are a minor, please use the Extension under the guidance of a guardian. If we become aware that a child has provided data without guardian consent, we will take steps to delete such data.
11. Changes to This Policy
We may update this Policy from time to time due to feature changes, legal requirements, or other reasonable reasons. For material changes, we will use appropriate means, such as a prominent notice on this page, to inform you. The updated Policy takes effect upon publication unless otherwise stated.
12. Contact Us
If you have any questions, comments, or complaints regarding this Policy or data processing related to the Extension, please contact:
- Email: copydreams@gmail.com
- Website: https://duckp.airush.top/
We will handle your request within a reasonable time and within the time limits required by applicable laws.