Privacy and data

Clear limits on what Sissel collects and sends.

Current data practices, implemented retention controls, processing boundaries, and environment-specific facts. Last reviewed 31 July 2026.

Production data is not approved for this environment

Export, correction, and deletion requests are handled through a privacy contact that has not yet been supplied. Self-service tooling is not yet available. Agree the request owner, identity verification, response window, and deletion scope before production use.

Collection follows your consent decision

In strict consent mode, Sissel does not write its browser identifier or send an event until your consent system grants permission. Events seen before permission are dropped rather than held for later.

Identity links require evidence

Sissel links a visit to a person using an explicit tracking token, email address, phone number, or external system ID. It does not use browser fingerprinting or anonymous contact enrichment.

Customers remain separate

Each customer organisation has its own data boundary. Sissel does not share identity links or build recognition profiles across customers.

Sending is a separate decision

Connecting an ad account does not start sending conversion events. Destinations begin in test or off mode and must be enabled deliberately.

Data categories and roles

The customer is intended to act as controller for its website, CRM, advertising, identity, and outcome data; the hosted Sissel operator acts as processor under signed terms. Data categories include visit/campaign context, consent state, pseudonymous visitor/session identifiers, encrypted person identifiers, CRM outcome fields, campaign/spend facts, and delivery/audit records.

Implemented retention controls

Pending raw collector batches are encrypted and scrubbed after 24 hours if processing does not complete.
Processed/failed raw receipt envelopes are deleted after 30 days.
Audit records are retained for 25 months.
Canonical journey, outcome, identity, and delivery retention is not globally fixed in the beta and must be agreed before production use.

Hosting and subprocessors

Last reviewed 31 July 2026

Hosting region: Not supplied for this environment
Subprocessors: Not supplied for this environment

What we do not claim

Sissel does not claim that attribution proves an ad caused a sale.
Sissel does not claim a production hosting region when this page marks it unsupplied.
Sissel does not replace your consent platform or legal assessment.