Local-first by design, not just by marketing copy.
This policy matches the real extension behavior. Packpour is scoped to metadata filling on App Store Connect and keeps the final review step manual.
What the extension stores
Imported TXT or Markdown metadata packs and the selected interface language are stored in Chrome local storage on your machine.
What it does not collect
- No account system
- No analytics
- No remote sync backend
- No advertising or tracking SDK
How page access works
The extension is limited to https://appstoreconnect.apple.com/*. It fills
the active tab only after a direct user action from the side panel.
Sensitive fields
Password, payment, token, and secret-looking fields are intentionally skipped. Packpour is built for metadata operations, not credential handling.
Submission boundary
Packpour does not click Save, Publish, or Submit for Review. Final submission remains manual.
Third-party network requests
Packpour makes exactly one outbound network request, and only when you ask for it:
when you click Settings → About → Check for updates, the extension fetches the
latest release metadata from the public GitHub Releases API at
https://api.github.com/repos/hooosberg/Packpour/releases/latest.
The request sends no identifying information about you — it is a plain version-check call. GitHub may log the request IP as part of its normal service operation; see GitHub's own privacy policy for details. No other network calls leave your browser.
How to delete your data
Because all Packpour data is held in Chrome local storage on your own device, you can remove it at any time:
- Uninstall the extension from
chrome://extensions— Chrome deletes its storage automatically. - Or, in
chrome://extensions, open Packpour's details and click Clear storage to wipe imported packs and preferences while keeping the extension installed.
Contact
Questions, concerns, or privacy-related requests: email zikedece@proton.me or open an issue at github.com/hooosberg/Packpour/issues.
Changes to this policy
If Packpour's behavior ever changes in a way that affects this policy, the updated policy will be published at this URL with a new "last updated" date. Continued use of the extension after an update constitutes acceptance of the revised policy.