Privacy Policy
This page explains what ArmGit stores about you and why.
What we store
- Account data: user name, e-mail address, a password hash (never the password itself), the profile details you choose to add, and your preferences such as the colour theme.
- Your content: repositories, issues, comments, pull requests and files you upload. Public content is visible to everyone; private repositories only to you and the people you invite.
- Security records: when you sign in we record the time, the result, an approximate browser description and your IP address, so that we can warn you about unfamiliar sign-ins and investigate abuse. IP addresses are anonymised after 90 days and the records are deleted after 365 days.
- Sessions: a list of the browsers signed in to your account, which you can review and sign out in Settings → Security.
Automated safety checks
Files pushed or imported into ArmGit are scanned automatically on our own servers for known malware, malicious scripts and leaked secrets such as keys and tokens. A repository that contains malware is placed in quarantine, which hides it from everybody except the ArmGit team, and its owner is told. Pushes that contain a recognised secret are flagged to the repository's owners. These checks run on ArmGit's own servers; your files are not sent to an outside scanning service.
Dependency alerts
When the ArmGit team switches on dependency alerts, the package names and version numbers found in lockfiles (for example package-lock.json or requirements.txt) are sent to the public vulnerability database osv.dev to find known problems. No source code, file contents, repository names or account details are sent. This is off unless the team enables it.
Pages and packages
If you publish a Pages site, its files are served to anybody on the internet from a separate address. Packages you publish to the built-in registry are visible to everybody when you publish them as public; restricted packages are visible only to you or the members of your organization.
AI features
ArmGit currently has no AI features and sends no repository, issue or account data to any AI service. If one is ever added it must be switched on by the ArmGit team, will list exactly what data it uses, and can be turned off for your own account in Settings → Interface.
Webhooks
If you add a webhook to a repository you choose which outside address receives event data (such as push and issue events). That data goes to the receiver you named. Remove the webhook to stop it.
What we do not do
- We do not sell your data and we do not show advertising.
- We do not use third-party trackers or analytics on ArmGit.
We send e-mail only for things you ask for or that protect your account: verification, password reset, security alerts such as a sign-in from a new device, and notifications you have enabled. Security messages cannot be switched off; the rest can be changed in Settings → Notifications.
Cookies
See the Cookie Notice.
Your choices
You can edit your profile, export your repositories with Git at any time, and ask the ArmGit team to delete your account. Deleting an account removes its repositories.
Contact
Questions about privacy: use the Contact page.
Last updated November 15, 2026