01Private custody on the device.
Bankeiz uses device-held signing material and retains supported protected identity, pending-operation and Note records locally. A service’s account display cannot replace that authority. Protect the original, the device and any required phrase.
02Connected account and payment services.
The current consent identifies the proofs and signed scopes sent to Receiz to open the account and execute supported operations. Account reads, messaging, recovery and financial execution have distinct permissions. Card entry uses the selected secure payment flow and its provider terms.
03Agent conversations and shared context.
Messages and selected context are sent to the configured connected service when you choose. The public BJ Twin uses guest conversation continuity; it does not establish a verified Receiz ID for an anonymous visitor. Volunteered contact details and confirmed appointments can be stored under the native conversation rules.
04Public proof and operational records.
A deliberately public proof discloses its carried information. Recipients may retain it. Hosting and connected services may process operational metadata for reliability and security. Ask about access, retention or deletion through the support route; already shared originals and legally retained records have their own persistence.