Privacy Policy

Privacy Policy for modcore Extension Manager (modcore EM)

Last updated: June 30, 2025

modcore Extension Manager (modcore EM) is an open-source Chrome extension developed by a team of personal individuals operating from Germany, within the European Union. Your privacy is paramount to us, and we are committed to transparency regarding data handling.

1. Our Commitment to Data Minimization and Local Processing

modcore EM is designed with a fundamental focus on data minimization. This means we only process the data that is strictly necessary for the extension's functionality. We do not collect or transmit any personally identifiable data, nor any anonymous data, to our servers or any third-party servers for purposes such as "improving user experience" or analytics. Our core principle is that your data remains on your device, under your complete control.

2. Local Data Storage and Purpose

modcore EM stores certain data locally on your device to ensure its smooth functioning and to provide you with a customized experience. This locally stored data includes:

• Settings: Your preferences for how modcore EM operates (e.g., display options, default behaviors).

• Profiles: Configurations you create for different extension setups (e.g., sets of enabled/disabled extensions, custom names).

• Groups: Organization of your extensions into custom groups for easier management.

• Cached API Data: As detailed in Section 3, certain data received from the GitHub API is cached locally to minimize API requests and improve performance. This data is non-personally identifiable and solely relates to extension metadata.

• Other functional data: Any other data essential for the direct, local operation of the extension.

This data is stored exclusively on your local machine (your PC) and is not transmitted to our servers or any third-party servers, unless explicitly stated and with your informed consent (as detailed below for Cloud Sync and voluntary bug reports). This local data is generally not considered personally identifiable by itself, as it's designed to be functionally generic and stored consistently for all users.

2.1. Accessing Your Local Data

You have full control and access to your locally stored data. You can access it through:

• Developer Tools: By opening your browser's developer tools (typically F12) and navigating to the "Application" or "Storage" tab, you can inspect the data stored by modcore EM in your browser's local storage.

• In-Built Backup Feature: (Available from version 2.3.81) modcore EM provides an in-built backup feature that allows you to export your local settings, profiles, and groups as a JSON file directly to your device. This enables you to easily manage and control your data.

3. Server Requests to GitHub API

modcore EM makes server requests to the GitHub API for specific, user-initiated functionalities:

• "Support the Developer" Program Data: To display information related to the "Support the Developer" program for extensions, modcore EM makes requests to the GitHub API to retrieve relevant data.

• "Extension Scan" Data: For the "Extension Scan" feature, which helps identify potential conflicts or deprecated extensions, modcore EM makes requests to the GitHub API to gather necessary metadata.

Important considerations regarding GitHub API requests:

• No Personal Data Transmission: modcore EM does not transmit any of your personal data or local data to GitHub or any other server during these API requests. The requests are made to retrieve publicly available or non-personally identifiable metadata from GitHub.

• Caching for Efficiency: To minimize the number of API requests and improve performance, data received from the GitHub API may be cached locally on your device. This cached data is solely for the functionality of modcore EM and does not contain any personal information about you.

• GitHub's Data Practices: Please be aware that when modcore EM makes a request to the GitHub API, standard web request information (such as your IP address and user agent string) will be communicated to GitHub. We do not have control over how GitHub processes this information. We recommend reviewing GitHub's privacy policy for details on their data handling practices.

• Strict Communication Rules: modcore EM has strict internal rules for communicating with servers, especially when third-party add-ons are involved. Our architecture is designed to prevent unauthorized data transmission.

4. Personally Identifiable Data (Optional)

While modcore EM is designed to operate without requiring personally identifiable data, it is possible for you to:

• Create a profile/group/rule (...) and provide your name: If you choose to enter your name or other identifying information within a locally stored profile, this will obviously constitute personally identifiable data on your device. We highly recommend anonymizing such data if privacy is a concern.

5. Data Collection for Bug Reports (Voluntary)

To help us improve modcore EM and fix issues, we may, at your voluntary request, ask you to provide local data when submitting a bug report.

• What kind of data? This would typically involve specific local settings, profiles, or other operational data from your modcore EM installation that is relevant to the bug you are reporting.

• Purpose: This data is strictly used for the purpose of diagnosing and resolving the reported bug.

• Anonymization: We encourage you to anonymize any personally identifiable information within this data before submitting it. We will treat any submitted data with the utmost care and will not use it for any other purpose.

• Consent: Your decision to provide this data is entirely voluntary and constitutes your explicit consent for us to use it for bug fixing.

6. Cloud Sync Feature (chrome.sync storage)

Introduced in version 2.3.81, the Cloud Sync feature utilizes chrome.sync storage. This means:

• Disabled by Default: The Cloud Sync feature is disabled by default upon installation or startup of modcore EM. It will only become active if you, the user, explicitly enable it.

• User Control: You have full control over the Cloud Sync feature. You can activate, customize, and deactivate it at any time within modcore EM's settings.

• Google's Service: Data stored via chrome.sync is synced across your Chromium browsers if you are logged into your Google account and have sync enabled. This synchronization is handled directly by the Chromium browser and Google's infrastructure, not by our team or our servers.

• Google's Privacy Policy Applies: The privacy policy of the Chromium browser sync feature and Google's overall privacy policy apply to data stored via chrome.sync. We do not have direct access to the data stored in your Google Cloud account.

• Your Control: You can inspect the data synced via chrome.sync by opening your browser's Developer Tools > Application > Storage > "Sync storage" (the exact path may vary slightly depending on your browser version).

7. Content Security Policy (CSP)

modcore EM implements a Content Security Policy (CSP) to enhance security and protect your data. Our CSP for extension pages is:

"content_security_policy": {

    "extension_pages": "script-src 'self'; object-src 'self'"

}

This CSP ensures that:

• Script Execution: Only scripts included within the extension package itself ('self') are permitted to execute. This prevents the execution of malicious code injected from external sources.

• Object Loading: Similarly, only objects (e.g., plugins) from within the extension package are allowed to load.

This policy helps to mitigate risks such as Cross-Site Scripting (XSS) attacks and unauthorized data access by restricting the resources the extension can load and execute.

8. Third-Party Addons and Forks

modcore EM is an open-source project, which means forks and third-party addons may exist. Please be aware that:

• Separate Privacy Policies: If you use any third-party addons or forks of modcore EM, their privacy policies will apply. We strongly recommend reviewing their (extra) privacy policies, if available.

• No Policy, This Policy Applies (with limitations): If no specific privacy policy is provided by an addon or fork, this modcore EM privacy policy will still apply to the core modcore EM functionality. However, we cannot be held responsible for the data practices of independent addons or forks that operate outside of modcore EM's direct control.

9. Data Security

All data processed by modcore EM is handled locally on your device. For any data voluntarily provided for bug reports, we ensure it is handled securely and used only for its stated purpose. Our use of a strict Content Security Policy further enhances the security of the extension.

10. Your Rights (under GDPR)

As a user within the EU, you have certain rights under the General Data Protection Regulation (GDPR) regarding your data. While modcore EM primarily processes data locally on your device, these rights apply to any personal data you may voluntarily provide to us (e.g., for bug reports):

• Right to Information: You have the right to be informed about the collection and use of your personal data. This privacy policy aims to provide that information.

• Right of Access: You have the right to request a copy of any personal data we hold about you (e.g., from bug reports).

• Right to Rectification: You have the right to request that we correct any inaccurate personal data we hold about you.

• Right to Erasure (Right to be Forgotten): You have the right to request that we delete any personal data we hold about you.

• Right to Restriction of Processing: You have the right to request that we restrict the processing of your personal data in certain circumstances.

• Right to Data Portability: While most of your data is local, for any personal data you have provided to us, you have the right to receive it in a structured, commonly used, and machine-readable format.

• Right to Object: You have the right to object to the processing of your personal data in certain circumstances.

• Right to Lodge a Complaint: You have the right to lodge a complaint with a supervisory authority (e.g., in Germany, a state data protection authority) if you believe your GDPR rights have been violated.

11. Contact Us

If you have any questions or concerns regarding this privacy policy or modcore EM's data practices, please do not hesitate to contact us at:

NGDE@WEB.DE

Thank you for using modcore EM!