PREEBLOCK / PRIVACY

Your data, explained.

What PreeBlock processes when you use its tools.

Public account data.

PreeBlock reads public wallet addresses, positions, trades and receipts to display account tools, reconcile transactions and attribute copies. Onchain records are public and cannot be erased from a blockchain by deleting a PreeBlock ticket.

Sign-in and permissions.

Wallet sign-in creates a temporary authenticated software session. Trading requires separate permissions. The execution service stores authorized trading configuration and encrypted session-key material needed for enabled copying; signing access and revocation remain separate from software membership.

Browser storage.

Your browser may retain preferences, pending payment references and private support-ticket access keys to recover workflows. Clearing browser data can remove those local references. Do not use a shared device for private account sessions.

Support and alert records.

Support tickets store your selected topic, message, timestamps, staff reply and an access-key hash. A rotating client-address digest limits submissions. No email address is required. Tickets are removed on an authorized deletion request or during subsequent service cleanup after 90 days. Saved price-alert events are retained for up to 30 days.

Agent evidence.

Agent access stores signed policies, hashed API tokens, encrypted owner-signature evidence, market snapshots, model identifiers, explanations, paper outcomes and an append-only audit chain. Private API tokens are shown once and are not saved in this browser. Decision evidence remains after key expiry or revocation to preserve evaluation continuity; contact support about access or privacy requests. Do not include secrets or unnecessary personal information in agent explanations. Paper evaluation does not automatically grant live trading authority.

External services.

Wallet software, blockchain RPC providers, prediction-market data and execution providers, font and script hosts, and hosting services receive requests needed to serve the site. Their services have their own policies. Avoid including secrets or unnecessary personal information in support messages.

Requests about your data.

Use the private support inbox for access, correction or privacy questions. A request does not authorize disclosure of another person’s account. Public blockchain records and financial reconciliation evidence may remain necessary independently of a support-ticket deletion.