What we collect, and why
AIpkgs uses Google & Github for authentication. We only use the email and name scopes. This page explains what we do with that — and what we do not.
- edition§03
- classnotice / privacy
- revised2026-05-19
- codexv0.1 · binding
Scope of this policy
This Privacy Policy describes how Org443 ("we," "us") handles personal information for users of the AIpkgs registry and website (the "Service").
It applies to information we receive when you sign in through a third-party identity provider, when you use the Service, and when you contact us. By using the Service, you agree to this policy.
Identity provider account data
When you sign in through a supported identity provider (currently Google and GitHub), we request and receive the following user data through the standard OAuth basic-profile scopes:
- your email address (the primary email associated with your provider account);
- your name (the display name on your provider account);
- a unique account identifier issued by the provider so we can recognize you on return visits.
We do not access, request, store, or process any other data from the provider. We do not read your mail, calendar, files, contacts, photos, location, repositories, or any other product or resource the provider may offer. We do not request a profile photo. We do not request any restricted or sensitive scopes from any provider.
How we use this data
We use the provider data above for exactly two purposes:
- Account verification. The provider's unique identifier and your email let us identify you as the same person on each sign-in and tie your registry activity to your account.
- Display. Your name and email are shown in the Service interface — on your settings page, in package ownership metadata, and to organization members who share an account with you.
That is the full extent of our use of provider data. We do not use it for advertising, profiling, analytics, model training, or any other purpose.
Data you generate by using the Service
Beyond the provider data above, we also process the following:
- Registry content you publish — packages, manifests, lockfiles, version metadata, and any text you submit through the Service.
- Session data — a short-lived session cookie issued after sign-in so you stay signed in across requests.
This data is generated by your use of the Service and is not received from any identity provider.
Changes to this policy
We may update this Privacy Policy at any time.
Continued use of the Service after changes take effect constitutes acceptance of the updated policy.
Contact
Questions about this policy or about the data we hold about you? Email support@org443.com.