Privacy policy

What we collect

Account data: the email address, display name and profile details (company, location, bio, website) you provide, plus the account identifier issued by our authentication provider.

Usage data: repositories you screen, discussions you post, models you like, API keys you issue (we store only a hash of each key, never the secret) and files you upload.

Technical data: request logs containing timestamps, paths, response status and a request identifier, kept for operational diagnosis.

What we do not want

Do not upload protected health information, personal data about third parties, or any regulated record into the registry. The service is not operated as a HIPAA-covered system and no business associate agreement is in place by default. Enterprise deployments that require one are contracted separately.

Processors we use

Google Firebase Authentication for sign-in. MongoDB Atlas for the registry database. Amazon Web Services for hosting, compute and object storage. Each processes data on our instructions under its own terms.

We pull public metadata from model hubs such as Hugging Face. Those requests carry no user data; they identify our service only.

Why we process it

To operate your account and authenticate requests, to attribute the screenings, discussions and uploads you create, to keep an audit record where governance features are used, and to secure the service against abuse.

Retention

Account and profile data are kept while the account exists. Audit entries and mirror snapshots are append-only by design and are retained for [retention period] to preserve a defensible record. Request logs are kept for [log retention].

Your rights

Depending on where you live, you may ask for a copy of your data, correct it, delete it, or object to processing. Write to [admin@deepneurons.ai] and we will respond within [response window].

Deleting an account removes profile data and revokes API keys. Entries already written to the append-only audit trail are retained, because their integrity is what makes them evidence; they are tied to an account identifier rather than a name.

Transfers and security

Data is hosted in [region]. Access is limited to named administrators, API keys are stored hashed, and traffic is encrypted in transit.

Changes

We will update the effective date above when this policy changes, and note material changes on the site.