Loading
DPA readiness
A buyer-readable preview of data categories, retention posture, transfer questions, and breach-notification routing. A signed DPA is still handled by request.
Signed DPA
Available by request for paid pilots and enterprise review.
Customer data
Watchlists, alert records, user/account data, webhook settings, and support context.
Raw leak material
Not required for the default alerting workflow.
Deletion/export
Handled through account, support, or contract path today.
For customer-configured monitoring, Hanasand generally acts as a service provider/processor for customer watchlists, account data, alert routing, and delivery settings. Some public threat-intelligence source records may be processed as Hanasand operational data.
The service can process business contact details, organization membership, watchlist terms, source records, alert records, webhook endpoints, API keys, support messages, audit events, and operational logs.
Retention depends on plan, deployment, and contract. Default product data is kept while needed to provide monitoring, support, security, dispute resolution, auditability, and legal compliance. Enterprise customers should set alert retention, audit retention, and deletion expectations in the order/DPA.
Security concerns are routed through support/procurement channels with customer, system, and timeline details. Contracted notification windows should be agreed in the DPA or order form before production use.
Review table
Next steps