Handling data safely
What to enter, download and share with others.
Keys and credentials
Never place a seed phrase, private key, password, API secret or recovery code in a wallet name, tag, description or support message. A public address is different from a private key.
Registration email codes and independent MFA proofs are credentials too. Type them only into the intended CRM form. They never belong in a bookmark or support attachment. The registration form clears passwords and proofs when you leave; keep the original email privately while resolving an uncertain creation.
Operation files
Original request and signing files can contain sensitive transaction terms. Store them in an organization-approved location. Recovery uses the exact original file, preserving its key and amount.
Support and shared computers
For diagnostics, provide error code, request_id, time and action name. Exclude cookies, tokens, passwords and private keys. Hide unrelated business data before taking a screenshot.
On a shared computer, sign out of the current organization. Other organizations have separate sessions; sign out of those as needed. Downloaded files remain on the device.
This guide
This static guide does not accept payment or account data, connect to the console API or store organization records. Search runs locally over article content. Interface screenshots contain only fictional training data.
Private resources inside an organization
Wallet, Address and AddressGroup default to organization visibility. Private access requires the active human owner, an explicit active member, or membership in an explicitly shared active group. There is no administrator or API-client bypass. Ownership is immutable in this release.
The owner needs wallets.share or addresses.share and fresh confirmation to replace sharing through the API. An inaccessible resource returns not found. Lists, history, tags and dependent documents follow the same filter; a group or payout is never shortened to only visible recipients.
Active public publications and machine jobs must be explicitly revoked/stopped before privatization. Sharing changes do not reverse accounting, cancel signed transfers or remove history. Ledger/Audit authorities and the database operator retain their independent access; public-chain observations remain public. Previously received data cannot be recalled.
New bookmarks created by CSV import into a private group or saved from private address history start private. Existing bookmarks retain their visibility; sharing grants are not copied. Another participant may need an explicit grant on the new address.