Describe your question and we’ll point you in the right direction.
Loading
Data processing review
A buyer-readable review of data categories, retention boundaries, transfer questions, and breach-notification routing. This is not an executed data processing agreement.
Contract status
No public standard DPA is offered today; signed processing terms require a written agreement.
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
Organization-scoped JSON export and bounded purge requests are available; retention enforcement and protected-evidence handling remain explicitly bounded.
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.
The organization workspace exposes the configured retention period, a JSON privacy export, and a confirmation-gated bounded purge request. Automated lifecycle enforcement for every customer record is not claimed as generally available; a production order must identify records in scope, purge timing, protected-evidence handling, legal holds, and the evidence used to verify enforcement.
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
