Privacy and data use

This page explains the current public report flow and how to ask BMM about your data. Use only public blockchain targets and public notes. Never submit private keys, seed phrases, passwords or signed payment secrets.

What you submit and why

BMM uses the public wallet, contract or transaction, selected network and report type to generate a research report. Notes help describe your question. Name, email, project name and implementation-help interest are optional and can be stored with the report for follow-up. Separate manual-review, watchlist and feedback forms store the details you submit for those requests.

Public blockchain lookups use external data providers. When AI report generation is configured, report context is processed by the configured AI provider. Keep notes public even when you leave contact fields blank.

Saved reports and shared links

A successful report-generation request saves the report; you do not need to press Save report first. An unlisted link is not the same as a private account: anyone who receives a working link may be able to read the report. Avoid private information in notes that may be reflected in the report, and share links only with intended reviewers.

Retention and removal requests

There is currently no published fixed automatic deletion period for public reports or contact requests. Do not assume a saved report expires when you close the browser. There is no self-service deletion control in this report flow.

Contact support@blockchainmoneymap.com to ask about retention, correction or removal. Include the report link or request date and only the details needed to identify your request. Support must confirm what action is possible; this page does not promise instant deletion or deletion of third-party copies.

Operational records

BMM records service and page events, report identifiers, request outcomes and referral or campaign information to operate and improve the product. Payment services also use request and settlement records. Do not include raw signed payment headers or other secrets in feedback or support messages.

Read the agent API trust boundaries and storage and security facts.