Plain-language policy
Privacy Policy
This policy explains the data practices for git-universe. It is written to match the app's aggregate-only repository model.
What we collect
When you sign in with GitHub, git-universe receives your GitHub identity details needed to create your account, such as your GitHub ID, username, and profile image. To let you choose repositories, the app also uses the GitHub access token supplied during your signed-in session.
Repository information
git-universe is designed around aggregate repository signals only: total lines of code, lines of code by language, total commit count, and public/private status. It does not collect or send file names, file paths, file contents, commit messages, author information, clone URLs, or repository configuration.
How information is used
Account information is used to provide sign-in and ownership checks. Aggregate repository information is used to generate your procedural system. We store the systems, galaxies, chosen nicknames, resource inventory, and purchases needed to operate the features you use.
Public sharing
A galaxy appears publicly only when its owner marks it public. Private repositories remain scrubbed in public galaxy views: they appear only as anonymous black holes, without their label, seed, or repository-derived details.
Service providers and security
GitHub provides sign-in and repository access. A managed database stores application data. Stripe processes Stardust purchases and acts as our payment subprocessor. We use reasonable safeguards appropriate to the project, but no online service can guarantee absolute security.
Payments
When you buy Stardust, your card details are entered directly on Stripe's own hosted checkout page and are never received or stored by git-universe. We keep a record of the purchase (amount, Stardust granted, and Stripe's transaction reference) to credit your account and handle support requests.
Your choices
You can choose what to register and what to make public. For questions about your account data or this policy, contact the project maintainer through the public repository.
See also the Terms & Conditions and Credits.