Coming back and leaving
How Anna signs out of Example Tickets, disconnects it from her wallet, sees what the site keeps about her, and keeps her ticket when she leaves.
There are two ways to stop using Example Tickets, and they live in different places. Signing out happens on the site and ends the site's session on one device. Disconnecting happens in the wallet and takes back what the wallet granted the site. Signing out and switching identity explains the difference, and why the words must not blur it.
Neither one touches the ticket. It is in Anna's wallet, and it stays there.
The account menu
Your account opens a short menu: Your tickets, What we keep, Sign out. Under Sign out, in small text: "To disconnect this site completely, remove it in your wallet." There is no "Disconnect wallet" item, because the site cannot do what those words promise.
Do
Label the site's own control Sign out, and put the one-line pointer to the wallet directly beneath it, so the two actions are read together.
Don't
Put a "Disconnect" button on the site that only clears the session. Anna would believe the site lost its access when the wallet still lists it.
Signed out
After signing out, the site goes back to the gig page with the Connect wallet button and one line: "Signed out on this device. Example Tickets is still listed in your wallet, and your ticket is still there."
On a shared computer, this is what Anna wants. On her own laptop it barely matters, because the wallet can sign her straight back in without asking. One line covers both cases, so she does not have to read a paragraph.
Do
Say on sign-out that it applies to this device only, and that the ticket is unaffected, in one line on the page she lands on.
Don't
Sign Anna straight back in on the next page load after she pressed Sign out. Wait until she presses Connect wallet again on this device.
Disconnecting in the wallet
In Bitcoin SV Wallet, Connected apps lists Example Tickets with its verified domain and what it holds:
- "Recognises you" (the sign-in key), last used 14 November
- "Reads your Tickets list" (the basket)
- "Was sent: Over 18, yes" on 25 October
- "Spending: asks every time"
At the bottom, Remove Example Tickets. After Anna removes it, the wallet says what stopped and what did not: "Example Tickets can no longer recognise you or read your tickets. Your ticket is still in your wallet." The full list of what a wallet's dashboard shows is in The permissions dashboard.
The "over 18" line is in the past tense on purpose. Removing the site stops future requests; it cannot take back an answer the site already received. Deleting that is the site's job, on the next screen.
When Anna next visits, the site has no session and no permission. It shows Connect wallet, as on a first visit. If she connects with the same wallet, she gets the same account and her orders back.
Do
Treat a sign-in that suddenly prompts again as a returning user whose wallet was cleared or who removed the site, and show the ordinary connect flow without asking why.
What the site keeps
What we keep is a short page in plain words, written for Anna rather than a regulator:
- A key your wallet made for this site. It can't be used to find you anywhere else.
- Your orders: the gig, the price, the date.
- That your age was checked, for which gig and when. Not the Pass, not your date of birth.
- Your email, only if you added one for receipts.
And under What we can't see: your balance, your other apps, your name, your other tickets.
At the bottom, Delete what we keep. It explains the consequence in one line before asking her to confirm: "Your orders will be gone from this site. Your ticket stays in your wallet and still gets you in."
The ticket is the part Anna takes with her. It is a token in her wallet, so it survives her removing the site or deleting her data. What happens if the site closes is an open question below. Restoring her wallet brings the ticket back if her backup includes the wallet's records and not only its recovery words (see Backups). She can give the ticket to a friend from her wallet without the site's involvement.
Do
Store the result of an age check, the gig and the date, and never the Pass or any field beyond the one asked for, and say so on the site's data page.
Do
Make a ticket valid at the door from the token alone, so it still works after Anna deletes her data or removes the site from her wallet.
Don't
Keep anything about Anna that this page does not list. If the site starts storing something new, the page changes the same day.
Open questions
- Do people understand that signing out on the site leaves the site in their wallet, even with the pointer beneath the button?
- Should the site be able to ask the wallet to remove it, so "Disconnect" on the site could be honest? The pattern pages do not describe such a request.
- When Anna deletes her data and later connects the same wallet, the site recognises the same key with no history. Should it say "We've seen this wallet before" or treat her as new?
- If the site closes, what should a wallet show for a ticket whose issuer no longer answers? See the open questions on Holding tokens.
Related
- Signing in: signing out against revoking
- Permissions and allowances: the dashboard and revoking
- Disclose what you use: the exposure statement behind "What we keep"
- Holding tokens
- Signing in to Example Tickets
- Buying a ticket: where the ticket came from
Written from: /guide/patterns/signing-in/, /guide/patterns/permissions-and-allowances/, /guide/patterns/connecting-a-wallet/, /guide/patterns/holding-tokens/, /guide/how-it-works/identity/.
Checklist
The rules on this page, in a form you can work through.
8 rules