Managed EU region
Choose an EU managed deployment when the collection and platform workload must remain in-region.
For privacy and infrastructure teams
Run Hardal in a managed EU region or your own environment, then apply consent and field rules before any configured destination receives an event.
EU collection endpoint
Receive events in the selected deployment region or environment.
Consent, PII, and retention rules
Apply the policy before storage or downstream delivery.
Separately reviewed recipients
Document the region and transfer path of each configured service.
Collection, policy, and delivery rules sit in one event path, so privacy and infrastructure teams can see what happens before data leaves.
Choose an EU managed deployment when the collection and platform workload must remain in-region.
Run Hardal in your own environment when infrastructure policy requires your team to control the account and network boundary.
Mask, hash, redact, or block named fields before events reach a downstream system.
Carry the consent state from collection into the processing and destination rules attached to the event.
Set retention requirements during implementation rather than inheriting one generic period for every event class.
Treat every advertising, analytics, and warehouse destination as its own data path with separate terms and regions.
Name the region where Hardal collection and storage run.
Show which fields are changed or blocked before export.
List the separate transfer path for every destination.
Hardal uses encrypted transport and managed access controls. Its security programme includes ISO 27001, ISO 27701, and ISO 9001:2015 certifications. Check the Trust Center for scope and certificate details.
Bring the sources, destinations, retention policy, and infrastructure constraints. We will map where each event goes.