Account access
By choosing Enter or opening your Identity Seal, you allow Bankeiz to identify your account and read your Reserve and Settlement balances and available account history. Enter creates a new identity; Use existing account inspects and opens the original you provide. A seal that requires an unlock phrase waits for that phrase. This account-read permission does not authorize transfers, purchases or sales. You can read these notices without creating an account or submitting an Identity Seal.
The account transport
Private account requests pass through the Bankeiz account gateway to Receiz. The gateway handles the protected request and the account response needed to serve the bank; device-held signing does not mean the gateway cannot receive account data. This transport omits browser cookies, forwards the scoped authorization when required and marks private responses no-store. That cache instruction does not define an infrastructure provider’s log-retention policy. Connecting to a website also exposes ordinary request metadata to the infrastructure handling the connection.
What is stored on your device
The browser retains encrypted identity custody and its protected transport copy for returning access. It can also retain balance observations, chart points, available private-history records, original deposited proofs and unfinished operation references. Private custody uses browser-held AES-GCM encryption. Public market data and the last public conformance result are separate display records. Keeping a display record does not grant account access, prove ownership or replace an original source.
Returning access and session expiry
Returning users can reopen the identity already held by this browser. When the scoped access grant expires, the bank can renew account-read access using the held identity and the approved account-read statement. Leaving the page or closing a tab does not remove saved device custody. Requests are bound to the open identity and application; the bank checks the returned account and granted scopes before using them. A failed refresh does not grant broader permissions or turn a saved balance observation into a new financial proof.
Balances and private history
The bank reads the account associated with the verified identity. A balance carried by a seal or retained on this device can provide an initial display while a current read is requested. History may come from carried evidence, a private account read or retained observations; those sources are distinguished from public activity. An identity-only seal does not necessarily carry every past transaction. An unavailable source is not treated as permission to invent transactions, ownership or funds.
Public and private information
Opening your account does not by itself publish your private balances or Identity Seal to the public Market or Ledger. Proof objects already published on a public showcase remain publicly discoverable. A public username or showcase attribution is discovery information, not authority to spend as that person. Actions that publish a proof or record have their own visibility and authorization requirements. Keep a private Identity Seal separate from an object you intend to publish or send as a payment.
Separate approval for financial actions
A card deposit, native account connection or other available financial action may request additional permissions. Its review identifies the operation you are approving. Account-read access alone cannot authorize sending your balance, purchasing an asset, selling ownership, redeeming a note or committing backing. A payment request, QR code or NFC link identifies a requested payment; opening it is not authorization to pay. Payment-specific information is handled by the payment flow and the processors identified there.
Backups and removal
In your account profile, Back up my Identity Seal saves the original needed to open your identity again. Remove ID from this device removes the current saved identity and stops its open account requests; it does not close the underlying account, erase public proofs or revoke copies of your Identity Seal held elsewhere. The app checks for held Offline Notes and pending receiving requests before permitting removal. Save originals and resolve those operations before clearing site data, because an identity backup alone does not restore device-specific note custody.
Scope of this notice
This notice describes account access in the Bankeiz reference implementation. Local removal is not an account-erasure or remote key-revocation service, and it does not promise deletion from independently operated infrastructure. A separately hosted or modified implementation can have different operators and data handling; consult its own notice. These explanations describe the implemented product flow and do not make a broader guarantee about every service, payment destination or external institution.
Exact read permissions
Account opening requests these scoped permissions: receiz:wallet.read, receiz:settlement.read, receiz:reserve.read. They cover account reads, including available wallet history and the Reserve and Settlement views. Additional card or native-action permissions are separate from this initial read grant.
Full account-read statement
Allow Bankeiz to open my account using my proof objects and read my Reserve and Settlement balances. Receiz receives my encrypted Identity Seal and signed consent to open this account. My signing key stays on this device. This permission does not authorize transfers, purchases or sales.