Privacy Policy
Last updated: August 13, 2026
zip→repo ("we", "the app") lets you sign in with GitHub, upload a ZIP archive, and commit its contents to a repository you control. This page explains what data we handle to provide that service.
What we collect
- GitHub account info: your GitHub username, avatar, and user ID, provided by GitHub during OAuth sign-in.
- GitHub access token: stored only in your encrypted server-side session, used solely to make the GitHub API calls you request (listing repos, creating branches, committing files). We never persist this token to disk outside the active session store.
- Uploaded ZIP contents: held in memory/temporary storage only for the duration of the extraction-and-commit workflow, then discarded.
- Deployment history: a local record of past deployments (repository, branch, commit SHA, file count, timestamp) so you can review what you've shipped.
- Marketplace account state: if you install zip→repo from GitHub Marketplace, we receive your marketplace account ID, plan name, and purchase/cancellation events directly from GitHub so we can keep your plan status accurate.
What we don't do
- We don't sell or share your data with third parties.
- We don't read, scan, or retain the contents of your repositories beyond what you explicitly upload and deploy.
- We don't use your code or account data to train any models.
Data retention
Session data expires automatically. Deployment history is kept so you can review past activity and can be cleared on request. You can revoke zip→repo's access at any time from your GitHub application settings, which immediately invalidates our access token.
Contact
Questions about this policy or your data can be sent to ziptorep@gmail.com.
This is a starting-point policy, not legal advice. Confirm the description above matches your actual deployment (e.g. where sessions/history are hosted) before publishing, and consider a quick legal review if you'll be handling paid-plan billing data later.
zip