Help centre
Straight answers about keys, verification, claims, and recovery.
Where exactly is my private key stored?
In your browser’s IndexedDB, encrypted with AES-GCM. The encryption key is derived from your PIN with PBKDF2 at 600,000 iterations. It is never transmitted, never copied to the server, and never written to any log.
What if I forget my PIN?
The PIN cannot be recovered, reset, or bypassed — by anyone. Your options are: sign in on another device that holds a copy of the key, or complete the recovery process with a proof you provisioned earlier (backup code, device token, or guardian approvals). Recovery installs a brand-new key on a new PIN; your address is unchanged.
Can I have the same identity on two devices?
Not by copying — there is deliberately no export function for the private key. The supported path is recovery: provision a device token while signed in on device A, then recover onto device B. Each device then holds its own key, and the latest rotation wins.
What happens if I clear my browser data?
Clearing this site’s storage deletes the encrypted key. If you have a recovery method set up, you can recover; if not, the identity is unreachable — permanently. This is why setting up recovery is the first thing the dashboard asks you to do.
How do I receive my verification code?
In the current development deployment, codes are written to the platform’s server log and relayed by the operator — the API never returns a code to any client. When out-of-band delivery (email/SMS gateway) is enabled, the code will go to the address or number you entered.
What can services see about me?
Your address, the methods you have verified (and when), and any claim you explicitly store in your vault and grant access to. Nothing else. The on-chain record redacts identity payloads on public reads by design.
What is a claim?
A single structured fact — e.g. {"country":"SG"} under the key residency — stored in your vault with a SHA-256 integrity seal. You disclose exactly the claim a service needs; the vault never exposes your other claims through the same grant.
Someone started a recovery on my address — what do I do?
Act now: sign in from a device that still holds your key, open Notifications to confirm, then cancel the request from the Recovery page. The 24-hour waiting period exists precisely so you always have this window. If you cannot cancel in time, contact the operator at business@spacexity.org — completion still requires a valid proof the attacker will not have.
Why does recovery take 24 hours?
The delay is the security model. Initiation is free and proofless, so it must also be harmless; the waiting period plus owner notification makes it harmless. Only the proof, checked after the wait, can complete a takeover.
My backup code does not work.
Check you did not provision a newer code since writing it down — provisioning always invalidates the previous code. Codes are single-use and case-sensitive hex. If it is exhausted, and you still have access, provision a new one now.
How do guardians sign my recovery?
Each guardian signs the canonical JSON {"new_public_key":"<your new PEM>","request_id":"<your id>"} with their wallet key and gives you the hex signature. You submit the list of {guardian, signature} pairs when completing. A majority of enrolled guardians must sign — two of three, three of five.
Can I delete my identity?
On-chain records are immutable by design — the chain is an audit log, not a database row. What you can do: sign out everywhere, clear this device’s key, and contact business@spacexity.org to have the identity status set to DELETED through the operator process.
Does it cost anything?
No. XityConnect identity services are provided by the Republic of Xity without user fees during this phase.
Still stuck?
Write to business@spacexity.org. Include your address (never your PIN or private key — we will never ask for them) and, for recovery matters, the request ID.