How Hanasand protects monitoring data today.

Customer data handled

Hanasand stores the information needed to monitor companies and send alerts: account details, organization memberships, watchlist terms, webhook destinations, alert records, delivery status, and audit logs.

• Watch terms can include company names, domains, suppliers, brands, executives, aliases, and portfolio companies.
• Alert records can include the matched term, company, source, time, confidence, status, delivery result, and notes.
• Service logs can include request IDs, health checks, errors, rate-limit events, and audit events.

Safety boundary

The default buyer workflow is intentionally metadata-first. Customers should not need to upload raw leak dumps, malware, production credentials, or unnecessary personal data to receive company exposure alerts.

Access controls

Protected dashboard routes require authentication. Organization pages use member/role context for shared watchlists, alert scope, webhook destinations, and admin workflows. Enterprise identity requirements should be raised before purchase so SSO and provisioning scope are explicit.

Service controls

The product shows service status, delivery history, admin tools, and support tools where those services are enabled. Check the target deployment before relying on a control.