Blockchain Core 0.17.2 / Privacy
Redacted transaction journal
Offer bounded cross-session transaction status without storing sensitive transaction inputs.
The optional journal is disabled by default. Open Blockchain → Wallet & Privacy, review the disclosed fields, and enable site availability only when cross-session receipt resumption is required.
Site availability is not user consent. Each signed-in user must accept the current journal policy before new records are written. Disabling the setting stops ordinary reads and writes, while users can still revoke consent or erase their existing records.
Entries are capped at 25 per user and expire after seven days. They may include intent or action, ecosystem, CAIP-2 chain, transaction hash or signature, lifecycle status, and server timestamps. They exclude wallet and recipient addresses, amounts, calldata, proofs, provider credentials, RPC URLs, and raw receipt payloads.
Administrators can clear records immediately. Test consent, revocation, erasure, expiry, and a resumed pending transaction with a normal signed-in account before relying on the journal in production.