# Data Processing Agreement | Ekos Labs

> The data processing agreement (Art. 28 GDPR) for lead data that Ekos Labs processes for its customers.

Updated 2026-11-17 · https://www.ekoslabs.com/dpa

This is a data processing agreement under Art. 28 GDPR. It covers all lead data that Ekos processes for a customer.

## 1. Parties

- Controller: the customer who holds the Ekos account.
- Processor: Magic Labs, trading as Ekos Labs, Eshaan Kansal, Schönbergstr. 15, 85057 Ingolstadt, Germany. Contact: [eshaan@ekoslabs.com](mailto:eshaan@ekoslabs.com).

## 2. Subject and duration

Ekos processes lead data for the customer while it provides the Ekos service. This agreement runs as long as the customer's account exists, and after that until all lead data is deleted.

## 3. Nature and purpose

Ekos processes lead data only to:

- find and screen leads that fit the customer's brief,
- find business contact details when the customer asks for them,
- send LinkedIn invitations and messages from the customer's own LinkedIn account,
- show the replies in the customer's account.

Ekos does not use the customer's lead data for itself or for other customers.

Ekos honours objections across all customers. When a person objects, Ekos keeps a minimal block record (their LinkedIn id, or a one-way hash of their email or phone) as its own duty as controller, so that nobody contacts them through Ekos again.

## 4. Types of data and data subjects

Types of data:

- name, role and company
- LinkedIn profile
- public posts or comments
- business email address and phone number, where found
- fit score
- messages and replies

Data subjects:

- business contacts at the customer's target companies
- people who reply to the customer's messages

## 5. Instructions

The customer's brief, chosen signals, campaigns and settings in the app are its documented instructions. The customer can give other instructions in writing or by email. Ekos processes lead data only on these instructions, unless EU or German law requires otherwise. Ekos tells the customer at once if it thinks an instruction breaks data protection law.

If EU or German law requires Ekos to process lead data in another way, Ekos tells the customer before it does so, unless that law forbids telling. Ekos transfers lead data to a country outside the EU only on the customer's instructions or as this agreement allows (section 9). Annex 2 lists what counts as an instruction.

## 6. Confidentiality

Everyone at Ekos who can access lead data is bound to confidentiality. Today that is only the founder.

## 7. Technical and organisational measures

- The database is hosted in the EU.
- Each customer's data is separated by account in our application code. Database access is limited to our servers; no customer or browser reaches the database directly.
- Sign-in codes are stored hashed, never in plain text.
- Admin actions are logged.
- Access to lead data is limited to the founder.
- All data is encrypted in transport.
- Lead data is deleted on the schedule in section 12.

The full list is in Annex 1.

## 8. Sub-processors

The customer gives Ekos a general authorisation to use sub-processors. The current list is in your account under Settings. You can also ask for it by email. Ekos tells the customer at least 30 days before it adds or replaces a sub-processor. The customer can object within that time. If Ekos cannot meet the objection, the customer can close the account. Ekos binds every sub-processor to the same data protection duties as this agreement. Ekos remains liable to the customer for its sub-processors (Art. 28(4) GDPR).

Categories of sub-processors:

- hosting and database (EU and US)
- AI model provider (US)
- LinkedIn connection service (EU)
- business contact data providers (EU and US)
- email delivery
- payment provider

## 9. Transfers outside the EU

Where a sub-processor processes data in the US or another country outside the EU, the transfer is based on the EU-US Data Privacy Framework or on the EU Standard Contractual Clauses (Commission Decision (EU) 2021/914).

## 10. Help for the customer

Ekos helps the customer answer requests from data subjects, for example for access or deletion. If a data subject contacts Ekos directly, Ekos passes the request on to the customer. Ekos also helps with data protection impact assessments and with consulting the supervisory authority, as far as it has the information.

## 11. Data breaches

Ekos tells the customer about a personal data breach without undue delay, and at the latest within 48 hours after Ekos becomes aware of it. The notice says what is known and what Ekos is doing about it.

## 12. Deletion and return

- A rejected lead is deleted at once.
- A lead that is not used within 30 days is deleted.
- All lead data of an account is deleted within 30 days after the account is closed. Before that, the customer can ask for a copy.
- Message text is cleared 12 months after the last activity.

## 13. Audits

Ekos gives the customer the information it needs to check that Ekos keeps to this agreement. Once a year, on request, the customer or an auditor it names may carry out an audit, with reasonable notice and under confidentiality.

## 14. Acceptance

If the terms and this agreement differ on lead data, this agreement applies.

Accepted together with the terms. No signature needed.

## Annex 1: Technical and organisational measures

- Database in the EU (Ireland); the app runs on servers in Frankfurt.
- Each customer's data is separated by account in our application code; database access is limited to our servers, with row level security switched on for every table.
- Admin access only for the founder, with a password and an emailed code; every admin read and change of customer data is logged.
- Ekos staff cannot sign in as a customer.
- Sign-in codes, API keys and block records are stored hashed.
- All traffic is encrypted (TLS); secrets live only in the hosting settings.
- Logs hold error codes, never the content of requests; AI calls are traced without prompts or replies.
- Session recording in the app only on a few screens, with all text masked, and only after consent.
- A daily deletion run carries out the schedule in section 12; people who objected are checked before every search, contact lookup, delivery and message.
- A written plan for data breaches, with the 48-hour notice in section 11.

## Annex 2: The customer's instructions

These settings in the app are the customer's documented instructions:

- the brief: what the customer sells, to whom, roles, region and company size
- the buying signals (plays) the customer chooses
- campaign settings: sequence, sending automatically or by approval, the privacy line
- whether contact details (email, phone) are looked up

The customer can turn signals and contact lookups off in the app at any time, and can pause or stop any campaign.

## Links

- Human page: https://www.ekoslabs.com/dpa
- Site guide for agents: https://www.ekoslabs.com/llms.txt
