Sign in with Pupul · Person-owned login

What is a sign-in you own?

Every "Sign in with" button you have ever pressed grew someone else's record of you. Sign in with Pupul is the same familiar OAuth handshake, pointed the other way: the login grows a profile you own, carries only what you agreed to share, and shuts off the moment you say so.

Nothing here is a promise. Every revocation is published to the public revocation list, and tokens verify against published keys.

What "own" means

Familiar plumbing, reversed ownership.

Sign in with Pupul is OAuth with ES256 tokens, scoped at the door by the person, revocable by the person, and verifiable by the app receiving it.

Nothing exotic is happening in the pipes. If an app has ever integrated Sign in with Google or Sign in with Apple, this is the same shape: a redirect, a consent screen, a signed token. What changes is who each part answers to.

Scoped at the door means you decide what the app gets at the moment you sign in, not buried in a settings page you find later. Revocable by the person means the decision stays yours afterward: revoking any app's access is free forever, and every revocation is published to a list anyone can read, so the app is never guessing and neither are you. Verifiable by the app means the receiving app checks the ES256 token against published keys rather than taking anyone's word for it.

Owning a sign-in is not a metaphor here. The grant is an object you issued, on your terms, that you can watch, narrow, and kill.

A login that grows your record

Every sign-in leaves a dated check-in
in the profile you own.

With every other login on the internet, the record of the event lives with the app or the identity provider. Here, every completed sign-in adds a dated check-in to your profile. The most routine act on the internet quietly builds the one record that is yours.

01 / You press the button

Scope is set at the door

The consent screen shows exactly what the app is asking for. You grant that and nothing else. What you keep private is simply absent from the grant.

02 / The app verifies

An ES256 token, checked against public keys

The app receives a signed OAuth token and verifies it itself. Standard plumbing that any developer already knows how to hold.

03 / Your profile grows

A dated check-in lands in your record

Every completed sign-in writes a dated check-in to the profile you own. Day by day, the logins you were doing anyway become continuity you can point to.

What a grant carries

Only what you agreed to.
Never what you wrote.

A grant is deliberately small. Three properties bound it, and none of them have exceptions.

Scoped to your consent

A grant carries only what you agreed to share at the door. There is no bundle of extras, and no scope creep after the fact.

Expires on its own

A grant is built to go stale. You do not have to remember to clean up after it; it shuts off by itself, and continuing requires your standing consent.

Never carries your writing

What you wrote in your profile stays in your profile. Apps receive claims about the record, never the words inside it.

Revocation is free forever

Cutting off any app never costs anything, on any plan, ever. A right you have to pay to exercise is not a right.

Revocations are public

Every revocation is published to a list anyone can read. The app knows, you know, and anyone checking knows. Nobody is guessing about standing consent.

Verifiable by the receiver

The app receiving your sign-in verifies the ES256 token against published keys. Trust in the system does not require trusting us.

One sign-in, five rooms

One login covers everything on one dashboard.

One sign-in covers every room, personal, practitioner, family, instructor, and firm, on one dashboard. You do not maintain five accounts or five passwords for five contexts of your life. You hold one profile, and each room sees exactly the slice of it you granted, no more.

That is the practical payoff of a sign-in you own: the boundary between contexts is drawn by your consent, not by which company happens to run which app. Start in the personal room and the rest are already yours.

FAQ

The questions people actually ask.

Is this a new protocol I have to learn?
No. Sign in with Pupul is standard OAuth with ES256 tokens. For a person it is a familiar consent screen. For a developer it is the same integration shape as any other OAuth provider.
How is this different from Sign in with Google or Apple?
The direction of ownership. Every completed sign-in adds a dated check-in to a profile you own, the grant carries only what you agreed to share and never what you wrote, and every revocation is published to a list anyone can read. The login grows your record, not only the app's.
Can an app read what I wrote in my profile?
No. A grant carries only what you agreed to share, expires on its own, and never carries what you wrote. Apps receive claims about your record, never the words inside it.
What does revoking cost, and how do I know it worked?
Revoking any app's access is free forever. Every revocation is published to a public list anyone can read, so you can confirm it yourself rather than trusting a settings toggle.
Do I need separate accounts for the different rooms?
No. One sign-in covers every room, personal, practitioner, family, instructor, and firm, on one dashboard.
Try it yourself

Press the button. Keep the record.

Open the personal room, sign in once, and watch the dated check-in land in a profile that belongs to you. Revoking anything, anytime, is free forever.