LynkMind

Data Processing Addendum

This Data Processing Addendum describes the data-protection terms that apply when LynkMind processes Customer Data on behalf of a customer.

It is designed for B2B review and must be aligned with the customer agreement, legal entity, infrastructure, subprocessors, and actual data flows before execution.

Last updated: September 12, 2026

Parties and roles

The customer is generally the controller or equivalent business determining the purposes and means of processing Customer Data. LynkMind is generally the processor or service provider. The contracting parties and any jurisdiction-specific role must be stated in the signed agreement.

Processing details

Subject matter: provision and support of LynkMind CRM services for the term of the customer agreement.

Nature and purpose: store, organise, display, secure, support, and process CRM data on documented customer instructions.

Data subjects and categories: contacts, prospects, customers, employees, users, and other individuals represented in Customer Data, including contact, company, deal, activity, communication, task, note, attachment, and account data.

Instructions, confidentiality, and security

LynkMind processes Customer Data only on documented instructions, including the customer agreement and use of configured service features. Personnel and approved subprocessors with access to Customer Data must be subject to confidentiality obligations. Security measures are described in the signed agreement and verified technical and organisational measures.

Subprocessors and transfers

LynkMind may use approved subprocessors to provide the service. The current verified list, notice process, processing locations, and transfer mechanism must be attached or linked before execution. See Subprocessors.

Assistance and incidents

Taking account of the nature of processing and information available to LynkMind, the parties should define assistance with data-subject requests, impact assessments, regulator engagement, audits, and security incidents. Notification timing must follow the signed agreement and applicable law; no unsupported deadline is promised on this page.

Return, deletion, and audit

The customer agreement should define data export, return, deletion, backup handling, and reasonable audit evidence. LynkMind should retain only what is required by the agreement, law, security, or dispute resolution after termination.

Technical and organisational measures

The final DPA should include or reference a current schedule of technical and organisational measures covering access control, confidentiality, resilience, recovery, testing, vulnerability management, and incident response. This schedule must reflect the live architecture rather than a competitor’s controls.