Privacy Policy

Information we process

Dep-Man processes the contents of supported dependency files, such as package.json, requirements.txt, and pubspec.yaml, to identify packages and compare their versions with public package registries.

The Chrome extension may also process the GitHub repository name and branch required to locate those files. The VS Code extension reads supported files from the workspace selected by the user.

How information is used

Dependency file contents are sent over HTTPS to the Dep-Man API, or to a custom API endpoint configured by the user, solely to provide dependency analysis and version information. Analysis results may be cached briefly to improve performance and reduce repeated requests.

GitHub tokens

Providing a GitHub Personal Access Token is optional. In Chrome, the token is stored locally through chrome.storage. In VS Code, it is stored through VS Code SecretStorage. Tokens are used only to authenticate requests to the GitHub API, including requests for private repositories, and are not sent to the Dep-Man API.

Data we do not collect

The extensions do not collect analytics, telemetry, browsing history, advertising identifiers, or personal information for marketing. We do not sell personal data or use extension data for purposes unrelated to providing Dep-Man's dependency analysis features.

Third-party services

Dep-Man communicates with GitHub and public package registries such as npm, PyPI, and pub.dev as needed to provide its core functionality. Those services process requests under their own privacy policies. If a user chooses a custom API endpoint, that endpoint's operator is responsible for its data practices.

Your choices and data deletion

You may remove a saved GitHub token at any time from the extension's settings. Chrome users can clear locally cached analysis results from the extension side panel or remove the extension. VS Code users can remove the extension and its saved token through VS Code. You may stop all further processing by uninstalling the extension.

Security and retention

Dep-Man uses HTTPS for production network requests and limits retained information to what is needed to operate the service, including short-lived caches. No method of transmission or storage is completely secure, but we take reasonable measures to protect processed data.

Children's privacy

Dep-Man is a developer tool and is not directed to children under 13. We do not knowingly collect personal information from children.

Changes to this policy

We may update this policy when Dep-Man's data practices change. The effective date at the top of this page will identify the latest revision.

Contact

For privacy questions or requests, open an issue in the Dep-Man GitHub repository.