One flow for sign-up and sign-in. A code verifies email control. Ordinary publishing and inquiries do not require identity review; identity badges are separate.
Checking this browser's completed sign-in state; no code is sent automatically.
Email verification grants L1 for private needs, confirmed publication of your own ordinary cards and optional inquiries. Claiming existing resources separately requires control proof. Email control is not an identity badge. Instances without email delivery report it; fixture codes do not represent real delivery.
Claim an existing resource (optional; not needed for a new ordinary card)
For resources with a supported original-source record, place a marker at the fixed location supplied by the server. The server independently reads it. An email suffix, screenshot or self-report is insufficient and no identity badge is granted.
You can prepare a draft first. Unavailable account, save or publication routes will be reported as unavailable.
Sign-out revokes this device’s email session and clears its sign-in state and displayed private content. You can sign in again with an email code. Server accounts, cards and revisions are retained; explicitly saved historical advanced keys are retained.
Request handling of specific personal data
This submits a deletion or correction request. It does not immediately erase, correct or close an account and is not the direct Delete card action. Current request states are pending, needs information or rejected. History, necessary audit and existing backup limitations are handled separately.
Your objects are read only when you click. Describe the requested scope without passwords, keys, identity documents, private file contents or other people's information. Requests and receipts stay in the private owner interface.
Confirm only this object's handling request. This does not delete the whole account, shared facts, other people's proposals or existing backups. Receipt is not completion.