Privacy information
This page describes the behavior implemented in the current controlled-QA build. A production privacy notice must be reviewed for the final hosting, providers and jurisdictions before launch.
Data handled by the service
Depending on selected features, HawkOpen can handle account and mailbox connection data, message and recipient metadata, classified open and click observations, replies, campaign outcomes, documents submitted to enabled workflows, and security or audit records. The signature generator on this public page runs in the browser and does not submit entered signature details to HawkOpen.
Purposes and legal basis
The application code supports providing requested product functions, account administration, security, fraud prevention, diagnostics and privacy requests. The applicable legal basis depends on the deployment, customer relationship, feature and jurisdiction and must be confirmed in the production notice; this page does not invent one universal basis.
Access, export and deletion
Authenticated account tools support owner export and deletion requests. A separate recipient privacy portal supports verified requests to view tracking data or request erasure. Fulfilment can be limited where restricted legal or audit retention applies; the portal reports the available status.
Retention, processors and transfers
There is no single published retention promise in this controlled build. Retention depends on data category, plan, tenant configuration and any applicable legal or audit restriction. The final processor list, hosting region and transfer safeguards depend on services selected for production and must be published before those services are enabled.