The repository now lives in the poli0981org organization, and this makes it at home there. - main was red since 2026-11-18: RUSTSEC-2026-0543 (chrono), in Cargo.lock only through serde_with's weak features and compiled into nothing; ignored with its reason and exit condition. - Supersedes #113–#118 (Rust 1.100.0, rusqlite 0.42.0, Tauri 2.12.6, code-health pins, actions, npm) plus jsdom 31.0.1; minimatch 11 closes GHSA-g3hv-75wg-m249. rfd 0.18 (#112) is held again until tauri-plugin-dialog moves. - Dependabot's tauri groups never worked (it picks the most specific group); exclude-patterns on the catch-alls fix it. - CI is self-contained: no workflow calls poli0981/.github; every action is pinned by commit; notify.yml vendors the Discord notifier. - npm licences: scripts/check-licenses.mjs, deny.toml's allowlist for the npm half. Required, with cargo deny and tauri lockstep — eight required checks. - Qodana in two parts (Rust, TS/JS), full scans, a triaged Rust baseline, fail on anything new. The Rust container needed its toolchain and CARGO_HOME pointed somewhere writable before it analysed anything. - SonarQube Cloud analyses into poli0981org_pipdock; every npm ci runs with --ignore-scripts (S6505). - Every repository URL points at the organization. README's attestation command for 1.4.0/1.5.0 had stopped working; it now says --owner poli0981 --signer-repo poli0981/pipdock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4.7 KiB
PipDock — Privacy Policy
Version 1.2 · Effective 2026-10-17 · Governing language: English.
1. The short version
PipDock collects nothing. No telemetry, no analytics, no crash reporting, no accounts, no identifiers. The developer receives no data from your use of the application unless you personally choose to open a bug report.
2. Data stored locally on your device
All application data lives under %LOCALAPPDATA%\PipDock\data\ and never leaves your machine:
| Data | Purpose |
|---|---|
| Settings (engine, locale, thresholds, consent record) | app configuration |
| Environment list, package index cache, and the Python versions each release supports | discovery, instant search, and refusing a version your Python cannot run |
| Snapshots (package lists of your environments) | rollback |
| Pins | update exclusions |
PipDock's own tool environments (tools\, audit\) |
running deptry, vulture and ruff for Code Health, and pip-audit for the Security tab; reinstalled on demand, clearable in Settings |
Log files in logs\ (14-day rotation) |
troubleshooting; they record the commands PipDock ran, so they contain package names and file paths |
Deleting the data\ folder is a complete reset. Delete data\, not its parent: PipDock's own program files are installed in %LOCALAPPDATA%\PipDock\, so removing that folder uninstalls the application as well — use the uninstaller for that. No data is synced or backed up anywhere by PipDock.
3. Network connections
PipDock connects to exactly one destination: pypi.org / files.pythonhosted.org, for the package name index, per-package and per-release metadata, the advisory data the Security tab's pip-audit reads, and the Code Health and Security tools PipDock installs into its own environments — standard web requests carrying no personal data beyond your IP address, as with any website.
PipDock does not update itself, so it never contacts GitHub or anywhere else to look for a new version. New versions are downloaded by you from the Releases page.
Some buttons hand a URL to your browser rather than fetching anything: the legal documents and the bug-report form on github.com, ruff's rule pages on docs.astral.sh, an advisory's page on osv.dev from the Security tab, and the author's contact page on poli0981.dev. Those are visits your browser makes, under its own settings, only after you click.
The pip/uv engines make their own connections to the package indexes configured on your system (including any private indexes you have set up); PipDock does not alter or observe those configurations beyond invoking the engines.
4. Bug reports (opt-in, manual)
The in-app Report bug button prepares a GitHub issue in your browser, prefilled with app version, Windows version, engine and Python versions, the error code, and a short log excerpt; the full log is copied to your clipboard. Nothing is transmitted until you personally review and submit the issue on GitHub, under GitHub's own terms and privacy policy. Check the excerpt for paths or names you consider private before submitting — the template reminds you to.
5. Children
PipDock is a developer tool and is not directed at children; it processes no personal data regardless of the user's age.
6. Changes
Material changes to this policy bump the legal documents' version hash, and the application will present the legal gate again before continuing. History is visible in the repository's git log.
7. Contact
Privacy questions: email contact@poli0981.dev, or open a discussion or issue at https://github.com/poli0981org/pipdock. The same contact details are listed in the application under About.
Tóm tắt Tiếng Việt (tham khảo)
PipDock không thu thập bất kỳ dữ liệu nào: không telemetry, không analytics, không tài khoản. Mọi dữ liệu (cài đặt, cache chỉ mục, snapshot, môi trường công cụ riêng của PipDock, log ghi lại các lệnh đã chạy) nằm trong %LOCALAPPDATA%\PipDock\data\ trên máy bạn; xóa thư mục data\ là xóa sạch — đừng xóa thư mục cha, vì chính chương trình được cài ở đó và xóa nó là gỡ luôn ứng dụng. Ứng dụng chỉ kết nối tới pypi.org (dữ liệu gói); PipDock không tự cập nhật nên không bao giờ gọi về GitHub. Một vài nút giao URL cho trình duyệt của bạn mở (github.com, docs.astral.sh, osv.dev, poli0981.dev) — đó là trình duyệt truy cập, sau khi bạn bấm. Nút báo lỗi chỉ mở form GitHub đã điền sẵn — không gì được gửi đi cho tới khi bạn tự xem lại và bấm gửi. Liên hệ: contact@poli0981.dev.