Investigate the record. Do not weaponize uncertainty.

The beta is intended for journalism, security research, incident response, victim support, compliance research, public-interest analysis, and other lawful investigation where the user has a legitimate purpose and applies appropriate safeguards.

• No harassment, stalking, doxxing, extortion, threats, discrimination, unlawful surveillance, or publication of sensitive personal data.
• No theft, phishing, credential abuse, wallet compromise, sanctions evasion, laundering, concealment of proceeds, or assistance that meaningfully facilitates cybercrime.
• No attempt to identify shielded or private-chain users as fact when public evidence does not support that conclusion.
• No bulk scraping, automated harvesting, reselling source responses, denial of service, limit bypass, account or network rotation, or evasion of an upstream provider's restrictions.
• No probing of private systems, access-control bypass, malware delivery, transaction signing, or submission of private keys, seed phrases, credentials, or viewing secrets.

• Label observations, attribution, leads, hypotheses, and limitations separately.
• Do not describe a proximity score, cluster, common-input heuristic, contract interaction, mixer deposit, or sanctions list match as proof of ownership, intent, or criminality.
• Give affected people or organizations an appropriate correction path, minimize unrelated personal data, and obtain editorial or legal review before publishing sensitive attribution.

Automated verification, per-visitor limits, daily source budgets, concurrency caps, source cooldowns, and operator kill switches protect the free beta and its upstream providers. Attempts to bypass these controls may be blocked. Serious suspected abuse may be preserved or reported where permitted or required by law.