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 or Google, git-universe receives the identity details needed to create your account, such as your GitHub ID or Google account ID, your name, and your profile image. If you create an account with a username and password, we store that username, a one-way hash of the password (never the password itself), and the email address you give us, which we use only to confirm your account and to send password-reset links; it is sent through our email provider, Resend. A guest account stores no identity details at all. 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.
Cookies, local storage, and analytics
One cookie keeps you signed in; a few values the game remembers live in your own browser and are never sent anywhere. We use Vercel Web Analytics and Speed Insights to see which pages are used and how fast they load, both are cookieless and build no cross-site profile. There are no advertising pixels or third-party trackers. The Cookie Policy lists every item by name.
Retention and deletion
Account data is kept while the account exists, because it IS the account: your systems, galaxies, inventory and progress. You can delete the account yourself at any time from Edit profile on your Captain's record. It takes effect immediately: the account and everything attached to it is erased, there is no copy to restore from, and we cannot undo it for you afterwards. Stripe keeps its own record of any payment, which we cannot delete on your behalf and which tax and accounting rules require anyway.
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, Cookie Policy, Refund Policy, and Credits.