Development status

Development and publication work have resumed. Service APIs remain unavailable unless explicitly documented as live.

Renkan ID

Renkan ID and project access

Renkan ID provides shared identity and sign-in. Each project sets its own permissions and keeps its private data.

Access labels

No account: a public action that does not require persistent identity. Temporary verification: short-lived proof for a specific action. Renkan ID account: a persistent account where a service requires sign-in.

A Renkan ID does not combine project profiles, roles, permissions, balances, saved data or billing records. Each project controls those separately.

The UID identifies an account. It does not grant a project role, entitlement or access by itself.