Legal

What Markin processes

Markin decides which action a customer should receive next. To do that it processes behavioural, transactional and lifecycle signals a customer already generates inside the enterprise's own systems. Customers remain the controller of that data; Markin acts as processor under the DPA, for the purposes the enterprise sets and no other.

What we never do with it

Customer data is not pooled across accounts, not sold, and not used to train models that serve another customer. Models are trained per account. Subprocessors are listed publicly and change with notice, so a security team can review a new one before it is used.

How commitments are evidenced

Access is least-privilege and logged, every automated decision keeps an audit trail of the signals and constraints behind it, and controls are described in the security overview rather than asserted in a sales deck.