Device-held signing
Your private signing key creates cryptographic signatures for your identity. Its corresponding public key lets a verifier check those signatures without receiving the usable private key. Bankeiz unlocks and uses the private key on this device. A signature is evaluated with its exact request and proof context; possessing a username, seeing a balance or displaying a verification badge does not provide the same authority.
Your key and your Identity Seal
Your Identity Seal is an original file carrying identity and signing custody. It is not just a profile image or a link to an account. When you deliberately save, copy or import that original, you are handling a file that carries the ability to open the identity. Device-held signing describes where the app unlocks and uses the key; it does not prevent you from moving your own backup. Keep the original private. A payment note and an Identity Seal serve different purposes: do not send your identity backup as payment.
Protected network transport
Account opening shares a protected, encrypted Identity Seal and signed consent with Receiz. If the opened original has an unprotected private key, the bank creates and verifies an encrypted transport copy of the same identity before sending it. The usable private key and transport unlock phrase remain local. The encrypted copy still contains protected signing material, so encrypted transport should not be described as sending no identity data at all.
How local custody is protected
Saved identity bytes and their unlock material are encrypted with AES-GCM using a non-extractable browser-held wrapping key. Private proof files and operation records are encrypted and bound to their account context too. This protects stored records from being ordinary plaintext files. It does not make an unlocked browser immune to malicious scripts, extensions or a compromised device. Use a trusted browser and device, keep them updated and protect the device’s own access.
New seals and existing unlock phrases
New Identity Seal downloads are self-contained and do not require you to save a generated recovery phrase. When you upload an existing seal, the bank inspects whether it requires a phrase. A no-phrase seal opens after inspection; a protected legacy seal waits for its original phrase. Adding a filename, changing a picture or guessing a phrase cannot replace verification of the original identity and its signing custody.
Device registration and note custody
Creating an ID also enrolls a device signer for sealing proofs. Device registration records a signing capability; it does not transfer your identity’s usable private key or give a service permission to spend. Offline Note custody can also depend on a separately qualified device and its receiving state. Restoring an Identity Seal is not the same operation as restoring that device-specific note custody. Keep the required originals and the qualified device until note transfers or deposits are complete.
Backing up and moving devices
Use Back up my Identity Seal from the account profile and keep the downloaded original intact. If that original requires a phrase, retain its existing phrase separately. Do not rely on a screenshot, edited image or converted file: the original carries structured proof and custody material. Keep original deposited proofs and notes as well. An identity backup can open the identity on another device, but it does not promise that every private local record, pending operation or device-qualified note state is inside the seal.
Removing an ID or clearing storage
Remove ID from this device removes the current saved identity and ends its open account requests. It does not close the underlying account, rotate the identity key or invalidate copies of the original held elsewhere. Held notes and pending receiving requests can prevent removal. Clearing browser site data bypasses the app’s custody checks and can remove local keys and recovery records; keep your originals and resolve device-bound operations first. Closing a tab alone leaves saved custody available for your return.
If a device or original is exposed
Someone who can open your original Identity Seal may be able to sign as that identity. Creating another backup does not change the key, and removing the identity from one browser does not revoke another copy. Protect remaining originals and stop using a device you no longer trust. Do not place a private seal, usable key or unlock phrase in a public showcase, issue report or support message. The backup and removal controls described here are not a remote identity-key rotation or revocation service.
Verification and continuity
A verifier checks signatures and original proofs under the applicable protocol rules. It does not rely on the appearance of a note, a public profile name or the reputation of the page displaying it. Keep the original source and its ownership history connected to the action. Key custody, account-read permission, ownership, funding and receiving conformance are distinct checks; passing one does not silently authorize the others.