Privacy

Data We Handle

• Editorial profiles of living public figures: name, public role, country or region, public sources, editorial score, confidence, uncertainty, model and corrections.
• Anonymous cohorts: base city, age and declared gender to estimate an aggregate position. The general population is not published by name by default.
• Opt-in claimed profiles: Google UID, email, display name, photo if provided by Google, login timestamp, estimated rank, consent and evidence the person voluntarily adds.
• Model feedback: votes on weights, optional rationale, language, optional website and timestamp.
• Editorial requests: name, email, source, detail and request type when someone asks for correction, claim, source addition or appeal.

How We Use Data

• Display editorial rankings with sources, uncertainty and model version.
• Enable claims, corrections, appeals and profile improvement.
• Store revocable consent and claim traceability in Firestore.
• Audit the model, investigate abuse, deduplicate claims and improve source quality.
• Publish aggregates or statistics that do not identify private people.

Sharing and Selling Data

We do not sell personal data. We may use infrastructure providers such as Google Cloud, Firebase, Firestore, BigQuery and Cloud Run to operate the service. If advertising, advanced analytics or data partnerships are added later, this policy must be updated before they are enabled.

Your Choices and Rights

• Anyone can request a correction, additional source, appeal or claim through the editorial form.
• A claimed user can request access, rectification, export, unpublishing or deletion of opt-in data.
• Voluntary evidence can be revoked. If evidence affects score, the change may enter an editorial queue and remain versioned.
• Public figures can dispute factuality, source, context, uncertainty and editorial category.
• For privacy requests, email apps@brainystack.co from the email tied to the claim or include sufficient identity evidence.

Retention and Security

We keep data while a profile, request, audit or operational obligation requires it. We use Google Cloud controls, service-level permissions and progressive minimization. No system is perfect, so we avoid collecting sensitive data unless there is explicit opt-in and a clear need.

Public Data and Public People

A source being public does not make every use fair or correct. HumanRank limits named profiles to living public figures with verifiable evidence, shows sources and accepts corrections. Private people remain anonymous cohorts unless they opt in to claim.

Regulatory References Used as Guidance