Skip to content

Data Processing Addendum

Version . This is the version in force. The acceptance recorded when a Dija account is created names this document and the version in force on that day.

1. What this document is

This Data Processing Addendum ("Addendum") forms part of the Terms of Service between you (the business or organisation on whose behalf the Service is used) and Dija Limited ("Dija", "we", "us"), a company incorporated in Cyprus, registration number HE 483340, with its registered office at Inomenon Ethnon, 2 Anastasia Court, Floor 4, 6042 Larnaca, Cyprus. Accepting the Terms accepts this Addendum on behalf of your business. There is no separate signature.

"The Service" and "the agent" mean what they mean in the Terms: the hosted Dija sales agent, and Dija ID, the sign-in service.

It applies whenever your company uses the Service to hold or process personal data about other people: the prospects and contacts it researches, the people it contacts, and anyone who replies. We call that Prospect Data. It is the contract that Article 28 of the GDPR requires between a controller and a processor, and it is written to satisfy the equivalent rules in the UK GDPR and comparable laws.

Personal data about you, our user, is covered by our Privacy Policy, where we are the controller.

Contact for anything in this Addendum: legal@dija.ai.

2. Who is who

You are the controller. You decide who is researched, what is recorded about them, what is sent to them, and when. Those are your decisions and nobody else makes them.

We are the processor. We hold and handle Prospect Data to run the Service for you, and for nothing else.

3. Your instructions

Your documented instructions are: the Terms, this Addendum, and your use of the Service. In practice that means the tools and AI providers your company connects, what you and your team ask the agent to do, the schedules you set, the requests you approve, the rules that let the agent act without asking, and the notes you keep in its memory.

We will not process Prospect Data for any other purpose. If we believe an instruction breaks data protection law, we will tell you.

We do not offer a separate instruction channel on the hosted Service. If you need us to process your data in a way the Service does not support, we will decline.

4. What we promise

We will:

  1. process Prospect Data only on your documented instructions, including as regards transfers out of the EEA, unless the law requires otherwise, in which case we will tell you first unless the law forbids us to;
  2. keep it confidential, and make sure everyone we authorise to process it is under a duty of confidentiality;
  3. apply the security measures in Annex B, and not materially weaken them while you are a customer;
  4. use sub-processors only as set out in section 7;
  5. help you answer requests from the people whose data it is, as set out in section 9;
  6. help you with your own obligations on security, breach notification, data protection impact assessments and prior consultation, taking account of the nature of processing and the information available to us;
  7. delete or return Prospect Data when you stop using the Service, as set out in section 11;
  8. give you the information you need to show that we meet Article 28, and allow audits as set out in section 12.

5. What you promise

You confirm and warrant that:

  • you have a lawful basis for every piece of Prospect Data you put into the Service or instruct it to collect;
  • you have given the people concerned the information the law requires, including under Article 13 and Article 14 of the GDPR where the agent discovers or records data about people not collected directly from them;
  • you will not use the Service to process special-category data (such as health, religious belief, political opinion or trade union membership) or data about children. The Service is not designed to filter free text for special-category or children's data, so preventing its ingestion and removing it if it appears is solely your responsibility;
  • you will honour objections, opt-outs and erasure requests from the people whose data your company's agent holds or reaches in your tools;
  • your instructions to us will be lawful.

6. Your own AI provider

Dija supplies no AI capacity. The agent runs against your company's own account with an AI provider, using the credentials you entered. When it runs, we build a prompt that can contain names, business email addresses, job titles, notes, content read from your tools and the full text of replies, and send it to your provider.

Because that account is yours:

  • your provider is not our sub-processor. They are your vendor, under your contract, and we are not a party to it;
  • what they do with the content is governed solely by your contract and your account settings, including how long they retain it and whether they use it to train models. We make no representation about your provider's retention or training practices, and you are responsible for configuring your provider account settings appropriately;
  • we transmit content to them only to carry out an instruction you gave the Service.

If you need a different arrangement, do not connect that provider.

7. Sub-processors

You give us general authorisation to use the sub-processors listed in Annex C, and to appoint others in accordance with this section.

Before a new sub-processor begins processing Prospect Data, we will notify the owner of your company's agent by email or through an in-product notice. You may object in writing within 14 days on reasonable data protection grounds. If we cannot resolve your objection, you may stop using the Service and request deletion of your data, and this Addendum ends with it.

We will place obligations on each sub-processor we appoint that are no less protective than those in this Addendum, and we remain responsible to you for their performance of those sub-processor obligations. Where your company or team elects to communicate with the agent through optional third-party messaging platforms (such as Telegram, WhatsApp, or Slack, described in Annex C), those platforms operate as independent third-party services under their own platform terms rather than as our sub-processors under this section.

8. Where data is processed

Our production servers are in the European Union.

Where a sub-processor processes Prospect Data outside the European Economic Area and we are the exporter, we rely on the standard contractual protections recognised under EU data protection law.

Recipients that you connect, such as your AI provider, your CRM, your sending tool, your mailbox and your enrichment tools, receive data under your own arrangements with them, including where they are outside the EEA.

9. Requests from the people whose data it is

Taking account of the nature of the processing, we will help you meet requests from data subjects. Most of what the agent works with stays in your own tools, where you answer a request yourself. For Prospect Data held within the Service:

  • Objection to being contacted. Anyone on your team can add an email address, a domain or a phone number to your company's do-not-contact list. The agent is then refused actions that visibly target that contact identifier, whatever rule would otherwise allow the action. This filter only checks contact details explicitly visible in the action payload; you remain responsible for maintaining suppression lists in your connected tools.
  • Rectification. Your team can edit any note in the agent's memory.
  • Erasure, access, portability, and restriction. Where a data subject request cannot be fulfilled directly by your team within the Service or your connected tools, your company's owner may write to legal@dija.ai identifying the relevant data subject and records, and we will provide commercially reasonable assistance within a reasonable time. We may require identity and authority verification, and we reserve the right to charge our reasonable administrative costs for repetitive, excessive, or complex manual extraction or deletion requests where permitted by law.

If a data subject contacts us directly about data your company's agent holds, we will not answer for you. We will tell them that you are the controller and pass the request to you.

10. Personal data breaches

We will tell you without undue delay after becoming aware of a personal data breach affecting Prospect Data we process for you, and give you the information you reasonably need for your own obligations, so far as it is available to us.

The notification will describe, so far as we can, what happened, the kinds and rough number of people and records affected, the likely consequences, and what we have done or propose to do.

11. Deletion and return

When your company stops using the Service, or on your earlier request, your company's owner may write to legal@dija.ai to request the deletion or return of your company's Prospect Data, which we will complete within a reasonable period unless applicable law requires retention. We may also delete data belonging to inactive or terminated workspaces on the free Service after giving reasonable notice.

Things you can do yourself, and things to know:

  • Removing a connection empties its stored credentials at once. The record that the connection existed stays, because the log of past actions refers to it.
  • Deleting a person's Dija account does not remove that person, or the work done for them, from your company's records.
  • Backups. Copies in system backups are retained for up to 90 days before automatic rotation. We do not use backups to bring deleted data back into live service, and if we ever restore from a backup, prior deletions are re-applied.

12. Audits

We will give you the information reasonably necessary to demonstrate that we meet Article 28.

  • Questionnaire. You may send us a reasonable written data protection questionnaire once in any 12 months, and we will answer it in a reasonable time.
  • This Addendum and its annexes, which we keep current, form part of that answer.
  • Inspection. Where a supervisory authority requires it, or following a confirmed breach affecting your data, you or an independent auditor you appoint (not a competitor) may inspect the relevant parts of our processing, on at least 30 days' written notice, during business hours, at your cost (including reimbursing our reasonable time and expenses), under a written duty of confidentiality, and no more than once in any 12 months.

Nothing in this section limits your mandatory rights under Article 28(3)(h) where the law does not allow them to be limited.

13. Liability

The liability provisions of the Terms apply to this Addendum. There is one aggregate cap of EUR 100 across both documents taken together, not one for each.

Nothing in either document excludes or limits liability for fraud, wilful misconduct, death or personal injury caused by negligence, or any liability the law does not allow to be excluded. In particular, an individual's right to compensation under Article 82 of the GDPR is not affected by anything agreed between us.

14. Precedence and versions

Where this Addendum and the Terms conflict about the processing of Prospect Data, this Addendum wins.

This Addendum carries its own version, shown at the top of this page. The Terms incorporate it, so a change here also moves the Terms version, and section 19 of the Terms says how we tell you.


Annex A: what we process

Subject matter. Providing the Service to you.

Duration. As long as your company uses the Service, plus the periods in Annex D.

Nature and purpose. Reading from and writing to the tools you connect, researching companies and people, keeping notes, drafting messages and record changes for a person to approve, receiving events such as replies from your tools, and keeping a record of the work, all about the people your company is selling to.

Frequency. Continuous, including work on a schedule and work started by an event.

Categories of data subject. Prospects and contacts at the companies you target, whether you named them or the agent found them; anyone whose reply or other event reaches the agent from a tool you connected; people your team mentions to the agent or in its notes; and people on your do-not-contact list.

Categories of personal data

  • Identity and business contact details, as they appear in what your tools return and in notes and drafts: name, job title, employer, email address, phone number, profile links.
  • Notes about accounts and people, written by the agent or by your team, including earlier versions.
  • Drafted messages and proposed changes: the recipients, the text, the exact content of each proposed action, who decided it, and its result.
  • Events received from your tools, including the full text of a reply.
  • Working data of each job: prompts, tool calls, tool results, and the model's messages, saved so that a job can pause and resume.
  • Conversations between your team and the agent, which can mention any of the above.
  • The do-not-contact list: email addresses, domains, phone numbers, and the reason given.
  • Whatever else your tools return or your team types.

The Service adds no open or click tracking of its own.

Special categories. Not knowingly processed, and prohibited by section 5.

Annex B: security measures

We maintain the following technical and organisational security measures for the hosted Service:

Encryption. The credentials your company gives the Service for its tools and AI providers (including access tokens, API keys, sign-in registrations, and webhook secrets), as well as two-factor authentication secrets in Dija ID, are encrypted at the application layer before storage using authenticated encryption (such as AES-256-GCM) with contextual binding so a ciphertext cannot be replayed across tenants or records. Credentials are never placed in a model prompt. All network traffic to and from the Service is encrypted in transit via TLS.

Separation between companies. Every table that holds a company's data carries that company's identifier, and the database enforces tenant isolation with row-level security for both reading and writing. The running service connects with a database role that cannot bypass row-level security.

Access control and authentication. Three roles in a company: owner, manager and member. Within a company, every member can read its shared conversations, jobs, notes and log entries. Adding a connection or an AI provider of the company's own is reserved to the owner. Sign-in is through Dija ID. Passwords and session tokens are stored only as cryptographic hashes. Access tokens are short-lived, and repeated failed sign-in attempts temporarily lock the account. TOTP two-factor authentication is available to every user. A user can review and disconnect any outside assistant they connected at any time.

Record of changes. Sign-ins and changes to connections, rules, roles and settings are recorded with the user who made them in the same database transaction as the change. Every proposed action is logged with its content, who decided it, and its result.

Application hardening. Input is validated at the service boundary. Outbound requests to customer-supplied URLs block private network ranges at connection time and do not follow cross-host redirects. Inbound webhooks and channel events are verified against cryptographic signatures or shared secrets before acceptance. Untrusted text from tools and external sources is demarcated for the model as data rather than instruction, and outward actions are enforced in application code regardless of model output.

Error monitoring. Reports sent to our error-monitoring provider are scrubbed before transmission so that request bodies, headers, model prompts, model responses, and database values are excluded. Error monitoring runs only when enabled.

Controls that protect data subjects. Outward actions require human approval unless an authorised user has configured an auto-approval rule, and the company do-not-contact list blocks matching actions as described in section 9.

Scope of commitments. The measures set out in this Annex B are our sole technical and organisational security commitments for the hosted Beta Service. As set out in the Terms, the Service is provided "as is" and "as available" without redundancy, failover, or third-party security certifications. You are responsible for reviewing these measures and determining whether they meet your compliance requirements before using the Service.

Annex C: sub-processors

Sub-processorWhat they doWhat they receive
Hetzner Online GmbHCloud infrastructure and hosting (EU)All Prospect Data, at rest and in transit
PostmarkTransactional and agent email routing, including incoming/outgoing mail & invitesEmail addresses and message content routed through the agent's email channel or invitations
SentryError monitoring of the agentScrubbed error reports, as Annex B describes. Used only when error monitoring is switched on
ResendDija ID's own email: account verification, password resetYour email address and the content of those messages. No Prospect Data
CloudflareAnti-bot challenge on the Dija ID sign-up pageThe signing-up person's IP address and a challenge token. No Prospect Data

Optional third-party messaging channels your company uses. Your team can choose to talk to the agent in third-party messaging platforms outside its own web page. When your company or its people link one of these optional channels, messages exchanged between your team and the agent on that channel (which may contain Prospect Data) pass through that platform under its own platform terms:

Channel platformHow it is used
TelegramThrough Dija's Telegram bot, when linked by a user
Meta (WhatsApp)Through Dija's WhatsApp Business number, when linked by a user
SlackThrough Dija's Slack app, when installed by your company

Recipients you connect are not our sub-processors. They receive data because you connected them, under your own credentials and your own contract: your AI provider, your CRM, your sending tool, your mailbox and calendar, your enrichment and meeting-note tools, your phone-call provider, your speech-to-text provider, and any connection your company adds itself.

We use no third-party connector service between the Service and your tools, no payment processor, no product analytics, and no session recording inside the product.

Annex D: how long we keep it

WhatHow long
What your company's agent holds: notes and their earlier versions, jobs and their logs, proposed actions and their results, events from your tools, messagesUntil deleted at your request under section 11, or after reasonable notice if a workspace is terminated or becomes inactive
The do-not-contact listUntil a manager or the owner removes an entry, or the company's data is deleted
Credentials of a connectionUntil the connection is removed, when they are emptied at once. The connection's record is kept
The record of sign-ins and changesKept with the company's data until the company's data is deleted
Short-lived working state, such as a sign-in in progress or a channel link codeFrom minutes to a day, then deleted automatically
System backupsUp to 90 days, rotated automatically; deletions are re-applied if a backup is ever restored