Skip to content

Privacy Policy

Version . This is the version in force.

1. Who we are

Dija Limited ("Dija", "we", "us") is a company incorporated in Cyprus, registration number HE 483340, with its registered office at Inomenon Ethnon, 2 Anastasia Court, Floor 4, 6042 Larnaca, Cyprus. We are the controller of the personal data described in this notice.

This is a notice, not a contract. It tells you what we do with personal data. It is not something you agree to, and nothing in it takes away a right you have under data protection law.

We have not appointed a Data Protection Officer. Privacy questions, requests and complaints all go to one address: legal@dija.ai.

In this notice, "the Service" means the hosted Dija sales agent ("the agent") together with Dija ID, the sign-in service at id.dija.ai.

2. What this notice covers

Different kinds of personal data run through Dija, and they are governed separately.

Whose dataOur roleWhere it is covered
Yours, as a user: your name, email, IP address, sign-in sessions, and what you do in your company's agentControllerThis notice
Partners in our partner programme, and the business contacts a partner names when registering an introductionControllerThis notice, section 7
Visitors to dija.ai, including people who fill in a form, book a call, or apply for a jobControllerThis notice, section 12
The people your company researches and contacts through the agent: their names, business emails, job titles, messages drafted to them, their repliesProcessor, acting on your instructionsThe Data Processing Addendum

If you are one of those third parties and you want to know why a Dija user holds data about you, the user is the controller and is the right person to ask. Write to us at legal@dija.ai and we will help you reach them.

3. What we collect about you

Your account. Your email address, your first and last name, the address of an avatar image if you set one, a hash of your password (never the password), your two-factor secret and backup codes if you enable them, verification and password-reset tokens, failed sign-in counts, the time you last signed in, and, if it applies, that your account is suspended or waiting to be deleted.

Sign-in sessions. For each session at Dija ID: your IP address, your browser's user agent, a device name, and when it was last used. We store a hash of the session token, never the token itself. The agent's own web page keeps a session for you as well, holding only a hash of its token and when it ends.

Assistants you connect. When you connect an outside assistant, such as Claude or ChatGPT, to your company's agent, we record which application it is, which company you chose, what you allowed, when you connected it and when it was last used.

Your place in your company's agent. Your name, your email address, your role, who your manager is, your time zone, your limits and your notification preferences. If you link a channel, we hold the identifier that channel gives you, such as your Telegram or Slack user ID or your WhatsApp number.

What you do there. The messages you exchange with the agent, including the text of voice notes; the jobs you ask for and their logs; the requests you approve, change or reject and the rules you set; the notes you write; and a record of sign-ins and changes, such as who added a connection or changed a role. Everyone in your company can read these, because the agent is shared by the whole team.

Connections you make. When you connect a tool or an AI provider, we store its credentials, encrypted before they are stored, and the settings of the connection.

Acceptance records. When you accept our Terms of Service and Data Processing Addendum, we record which document, which version, when, your IP address, your user agent, and which screen captured it. That record is the evidence that an agreement exists.

4. Why we use it

What forOn what basis
Creating and running your account and your company's agentPerformance of our contract with you
Signing you in, keeping sessions, and protecting your accountContract, and our legitimate interest in security
Verifying your email address and resetting passwordsContract
Preventing abuse, spam and fraud, including the bot check at sign-up and limits on sign-in attemptsOur legitimate interest, and the interest of the people your company contacts
Keeping a record of sign-ins and changesOur legitimate interest in security and accountability
Sending you service and security messagesContract
Measuring how our website is used, as section 12 describesOur legitimate interest
Running the partner programme and the partner accounts in itPerformance of our contract with you, and our legitimate interest in running the portal
Checking and deciding the introductions partners register, including the contact a partner namesOur legitimate interest in verifying referrals and preventing duplicate registrations
Recording your acceptance of the Terms and the Addendum, and a partner's confirmation of the programme ruleOur legitimate interest in evidencing agreements
Meeting a legal obligation, or establishing or defending a legal claimLegal obligation, or our legitimate interest

Where we rely on a legitimate interest, you can object. See section 11.

We do not sell your personal data, and we do not use it for advertising. Section 12 explains separately what happens on our marketing website, which does use advertising technology with your consent.

5. Automated checks and eligibility rules

We do not make decisions based solely on automated processing that produce legal or similarly significant effects on individuals under Article 22 of the GDPR.

Account security. Automated security controls lock an account temporarily after repeated wrong passwords or two-factor codes, and refuse sign-ups where the email address is not a valid work address or the anti-bot check fails.

Partner registrations. When a partner submits a company introduction, programme eligibility rules check whether the company is already a customer, already registered by another partner, recently in contact with us, or affiliated with the partner. The partner is told the outcome and can ask for a person to review a decision by replying to the confirmation email or writing to legal@dija.ai.

6. Connected Google accounts, and Google's Limited Use rules

If you connect Gmail to the agent, Dija asks Google for permission to read your mailbox and to prepare drafts in it. The agent prepares a draft and you open it in Gmail and send it yourself. If you connect Google Calendar, Dija asks for permission to see your calendars and free time and to manage events. These are personal connections: each person connects their own Google account, and the agent uses it only for that person's work. You can disconnect at any time, in the agent and in your Google account.

Dija's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We do not use mailbox content for advertising, we do not sell it, and we do not use it to train AI models. Mailbox content is sent to your company's own AI provider only where work you asked the agent to do requires it, such as reading a reply or drafting an answer.

7. Partners

Partners introduce companies to Dija through the partner portal at account.dija.ai. If you are a partner, we are the controller of the data below, and this notice covers it.

Your sign-in. The portal signs you in with your Dija account. From it we take the identifier Dija ID gives us for you, your name, and your email address once it is verified.

Your partner profile. Your name, whether you act as an individual or a company, your company name, and your country.

Your confirmation of the programme rule. We record when you confirmed the eligibility rule shown in the portal. That record is evidence, for the same reason as the acceptance records in section 3.

The introductions you register. The company's name and domain, the name and role of your contact there, your note on how you know them, the outcome and its reason, and the dates of each milestone. A registration is also emailed to our team. Partners must ensure they are authorised to share a business contact's details before registering an introduction.

Payment. We arrange payment with you by email, including any tax form we need. The portal stores only the dates of the milestones.

If a partner named you. If a partner names you as their point of contact when registering an introduction for your company, we hold your name, business role, and the partner's note on the relationship solely to verify the referral and attribute the introduction. When a company opens a referral link shared by a partner, the page shows that partner's name and company. You can ask us to remove your details at any time by writing to legal@dija.ai.

8. Who else sees your data

WhoWhat they getWhen
Hetzner Online GmbH (hosting)Everything, because our servers and databases run on their infrastructureAlways
Resend (our own email)Your email address and the content of our own messages to you: account verification and password reset, and the confirmations and partner programme messages the website sendsWhen we send you one of those messages
Cloudflare (Turnstile)Your IP address and a challenge token, so that we can tell a person from a botOnly on the Dija ID sign-up page
Sentry (error monitoring)Error reports from the agent, Dija ID and this website, with technical details. They are cut down before they leave us: no web address beyond its host, no headers, no request or response content, no account details, and no model prompt or answerOnly when error monitoring is switched on
Telegram, Slack, Meta (WhatsApp), Postmark (email)The messages you exchange with the agent on that channel, and your identifier there. Invitations to join a company's agent are sent by email through PostmarkOnly for a channel you or your company use
An outside assistant you connectAn identifier for your account and for the company you chose and, if the assistant asks and you allow it, your name and email address. After that, whatever the agent answers when the assistant asks on your behalfOnly while the assistant stays connected

Everyone in your company's agent can read its conversations, jobs, notes and record, including yours.

We do not use any analytics, tracking or advertising service inside the product. The marketing website is different, and is described in section 12.

We may also disclose personal data where the law requires it, or to establish, exercise or defend a legal claim.

Our own staff. Access to production infrastructure, databases, and internal administration tools is restricted to authorised personnel who need it to operate, secure, and support the Service and our website.

Sub-processor changes. If we add or replace a core service provider above, we will notify the owner of each company's agent by email or through an in-product notice before the new provider starts processing.

9. Where your data is, and transfers out of the EEA

Our production servers are in the European Union.

Some of the providers in section 8 process data outside the European Economic Area, either because they are established elsewhere or because they operate a global network. Where we are the exporter and a transfer outside the EEA takes place, we rely on the standard contractual protections recognised under EU data protection law.

If your company connects an AI provider or a tool, that connection is yours. Data reaches that provider under your company's own contract with them, including where they are outside the EEA.

10. How long we keep it

WhatHow long
Your Dija accountUntil you delete it, or until closed for inactivity after reasonable notice. Deletion takes effect after a 7-day grace period, described in section 13 of our Terms
What you did in your company's agent: conversations, jobs and their logs, approvals, rules, notes, the recordKept in your company's records, including after your own account is deleted, until the company's data is deleted or the workspace is closed
Sign-in sessions at Dija IDA session lasts 7 days. Its record, with the IP address and user agent, is deleted 90 days after it ends
Sign-in sessions on the agent's web pageA session lasts 30 days, or ends sooner when you sign out, reset your password, or your account is suspended or deleted
Connected assistantsA connection ends when you disconnect it, or after 90 days without use. Its record is deleted 30 days after the date it would have lapsed
Acceptance records for the Terms and the Addendum, including the IP address and user agent that evidence themFor the life of the account and as needed to evidence our agreements
Server logsShort-lived security and operational logs containing account identifiers and IP addresses are held briefly in runtime storage and cleared automatically as services rotate or redeploy
Partner profiles and registrationsFor as long as the programme obliges us to either party, then until either asks us to delete them
Website forms, bookings and personal outreach linksUntil you ask us to delete them
Website analytics180 days for page views and time on page. Aggregated or conversion records (clicks, form conversions, and page variant exposures) are kept until no longer needed
Job applicationsThe uploaded CV file is deleted after 365 days. The application record itself is kept until we delete it
BackupsUp to 90 days for Dija ID and the Service. Up to 14 days for the website's database and uploaded files

11. Your rights

Subject to the conditions in the law, you have the right to access your personal data, to have it corrected, to have it erased, to restrict or object to processing, to portability, and to withdraw consent where we rely on it. You can also complain to a data protection supervisory authority in the country you live or work in.

Two of these you can exercise yourself, without asking us:

  • Deleting your account. On the security page of your Dija account at id.dija.ai, where you confirm with your password. Your account is switched off in every company's agent, the assistants you connected are disconnected, you can cancel for 7 days on the same page, and then the account is permanently deleted.
  • Disconnecting an assistant. On the same page, under connected applications. It is cut off within about a minute.

To exercise any other right, including requesting a copy of your data, write to legal@dija.ai. We will respond within one month (or within the period allowed by law where a request is complex).

Two limits on erasure.

Backups. Deleting data removes it from the live systems. Copies stay in our backups for the periods in section 10. We do not use backups to bring deleted data back into service, and if we ever have to restore from one, the deletion is applied again.

Your company's records. Deleting your Dija account does not remove your name, your email address or the history of what you asked for and approved from your company's agent. Those records belong to your company. Ask your company's owner, or write to us, if you want them removed.

12. Our website

The marketing pages on dija.ai are separate from the product and use a small number of technologies.

  • First-party analytics. We measure page views, time on page, scrolling and clicks without storing anything on your device and without storing your IP address. Each record carries a code made by hashing your IP address and browser together with a secret and the current time window, so that repeat visits within a window can be counted. Section 10 says how long records are kept.
  • LinkedIn Insight Tag and Conversions API. On campaign pages, and only with your consent, we load LinkedIn's advertising tag and, on a form submission, send LinkedIn a hashed version of your email address rather than the address itself.
  • Cal.com. If you book a call, the booking form is provided by Cal.com and loads only when you click. Cal.com then sends us the booking, which we keep.
  • Consent. We ask for consent before loading advertising technology for visitors in the EEA, the United Kingdom, Switzerland, and anywhere we cannot determine the country. We work out the country from your IP address on our own server and do not store it. Accept and Reject are given equal prominence, and we honour the Global Privacy Control signal everywhere.
  • Forms. If you ask for a resource or sign up for updates, we hold what you enter and email you what you asked for.
  • Job applications. If you apply for a role, we hold what you send us, including your CV, in order to consider your application. The application, with the CV attached, is also emailed to our team. Section 10 gives the retention periods.
  • Cookies. Our own code sets no cookies on the public pages of dija.ai. With your consent, LinkedIn's tag sets its own on campaign pages. Signing in to the partner portal, to Dija ID or to the agent sets only the cookies needed to sign you in and keep you signed in. The cookie notice lists each one.

13. Security

We protect personal data with technical and organisational measures, including: encryption of stored credentials at the application layer; encrypted transport; role-based access control; separation between companies enforced by the database itself; optional two-factor authentication; passwords and session tokens stored only as hashes; limits on sign-in attempts; and a record of sign-ins and changes. The security annex of our Data Processing Addendum describes these in more detail.

No system is perfectly secure. If a personal data breach affects your data, we will tell you where the law requires it, and we will notify the supervisory authority within the time the law allows.

14. Children

The Service is for business use by adults. It is not intended for anyone under 18, and we do not knowingly collect data from children.

15. Changes to this notice

We may update this notice. Every version carries its date, and the version in force is shown at the top of this page. If we make a material change, we will tell you by email or in the product.

16. Contact

legal@dija.ai

Dija Limited (HE 483340), Inomenon Ethnon, 2 Anastasia Court, Floor 4, 6042 Larnaca, Cyprus.