# Kin OAuth

> **In short** A sign in button that tells any app a user is real and unique to that app, and nothing else. Built on OpenID Connect; in development.

Kin OAuth lets any app, game or community check that each user is a real, unique person, with one tap and without collecting who they are. It is in development.

## How it works

1. **The app asks.** It adds a Kin OAuth button where it needs to know someone is real: sign up, rewards, voting or posting.
2. **The person confirms in Kin ID.** They see exactly what the app will learn and approve with one tap.
3. **The app gets a proof.** A signed answer that the person is human and unique to this app, with an identifier that is the same every time they return, and different in every other app.

![Kin OAuth: one tap, one answer.](fig:shield)

## What an app receives

| Field | Meaning |
| --- | --- |
| `human` | The person passed Kin's proof of human checks |
| `unique` | This is the only account this person has in this app |
| `sub` | An identifier for this person in this app only |
| Name, email, photo | Never shared |

Kin OAuth follows open standards, OpenID Connect and OAuth 2.0, so it works like the sign in buttons developers already know. We are designing it for the web, iOS and Android, with SDKs for the most common platforms.

## Where it helps

- **Social apps and communities** keep feeds, comments and groups free of bots and fake followers.
- **Games** get fair leaderboards and matchmaking, with one player per person.
- **Rewards and giveaways** reach real people, once each.
- **Polls and voting** count one person, one vote, without asking who anyone is.
- **Marketplaces** reduce fake reviews and repeat fraud.

## Timeline

A private beta with partners is planned for early 2027, and general availability for developers later that year. See the [Roadmap](./roadmap).