Privacy & Cookie Notice
Last updated: 2026
This notice covers dija.aiand explains what Dija Limited (“Dija”, “we”) collects when you use it, why we collect it, how long we keep it, and who else sees it. We collect what we need to run the site, deliver what you ask for, reply to you, and measure our advertising.
What we keep, and for how long
Most of this site asks nothing of you. These are the records we hold when you do give us something.
| Record | What it holds | Why | How long |
|---|---|---|---|
| Job applications | Your name, email address, phone number if you give one, the links and free-text answers on the form, your résumé file, and the campaign parameters your visit carried. | To consider you for the role and to reply to you. | The résumé file is deleted after 12 months. The rest of the application is kept until you ask us to delete it. |
| Resource requests and sign-ups | Your email address, your name if you give one, which resource you asked for, and anything you entered about your company, role, LinkedIn profile, or deal size. | To send you what you asked for and to follow up about it. | Until you ask us to delete it, or unsubscribe. |
| Booked calls | Your name, email address, the meeting time and its status, and the booking record Cal.com sends us, which can include anything you entered when booking. | To hold the meeting and keep a record that it happened. | Until you ask us to delete it. |
| Outreach links | If we emailed you a personal link, we hold your name, email address, LinkedIn profile, our own note about why we contacted you, and which resources you opened from that link. | To make the approach relevant and to know whether it was welcome. | The link stops working after 90 days. The record is kept until you ask us to delete it. |
| Partner deal registrations | The partner’s name, email address, company and country, plus the company, contact name and role they are registering, and how they know that contact. | To adjudicate the registration and pay the referral fee it earns. | For as long as the programme obliges us to either party, then until either asks us to delete it. |
| Site analytics | The page, where you came from, campaign parameters, country, device type, browser, operating system, how long the page was open, how far you scrolled, what you clicked, and a rotating pseudonymous code described below. | To see which pages work. | 180 days for page views and time-on-page. Conversions, and which version of a page you saw when we were testing two, are kept longer. |
First-party analytics
Our own analytics set nothing on your device and never store your IP address. Instead, each page view carries a code made by hashing your IP address and browser together with a secret that rotates on a schedule. It lets us tell one visit from another and count returning visitors within a window, and it stops being linkable to you once the secret rotates. It is a pseudonym, so we treat it as personal data and list it here, but nothing in it names you and we hold no way to reverse it.
The rest is the page you were on, where you arrived from, your country, your device, browser and operating system, how long the page was open, how far down it you scrolled, and which links you clicked. This needs no consent because it stores nothing on your device, which is also why it is not in the table below.
LinkedIn Insight Tag
On our campaign pages (such as /start and resource pages) we use the LinkedIn Insight Tag, a small JavaScript pixel from LinkedIn. When enabled, it sets cookies in your browser to measure the performance of our LinkedIn ads and to show you relevant ads on LinkedIn (retargeting). It records page visits and, on a successful form submission, a conversion. We never load this tag until you have consented where consent is required.
Conversions API (server-side sharing)
When you submit a form and have consented to LinkedIn tracking, we also send LinkedIn a server-side conversion through its Conversions API. To do this we share a one-way hashed (SHA-256) version of your email address, never your email in the clear. LinkedIn uses it to match the conversion to an ad interaction. This server-side event is deduplicated with the pixel event so a single submission is counted once. It exists so that conversions are still measured if the in-browser pixel is blocked.
Cookies and browser storage
dija.ai itself sets no non-essential cookie at all. One is set on the Dija Marketplace, at market.dija.ai, and only if you arrive there on an author’s link. That link carries a ?ref= handle, we keep it in a first-party dija_refcookie for 30 days, and we read it once, server-side, when you open the “Get it” page for a listing: if you install that author’s agent or playbook, the install is credited to them. It holds the handle and nothing about you, it is marked httpOnly so no script on the page can read it, and it is never used for advertising and never shared outside Dija. A later link with a different handle replaces the first, because the click before an install is the one that caused it. If you would rather not carry it, reach the marketplace by typing market.dija.ai instead of following the link, or clear cookies for that site.
| Name | Provider | Purpose | Retention |
|---|---|---|---|
| li_* / lidc / bcookie / UserMatchHistory | Advertising measurement and retargeting via the LinkedIn Insight Tag. | Up to 6 months (per LinkedIn). | |
| dija_ref | Dija (first-party cookie, set on market.dija.ai) | Remembers which author’s link brought you to the Dija Marketplace, so they are credited if you install it later. Contains an author handle, nothing about you. | 30 days. |
| dija-consent | Dija (first-party, browser storage) | Remembers your cookie choice so we do not ask again. | Until you clear it or change your choice. |
| dija-theme, dija_utms | Dija (first-party, browser storage) | Your light or dark preference, and the campaign parameters the page you arrived on carried, so a form you submit later is still attributed to it. | Theme until you clear it; campaign parameters until you close the tab. |
Who else sees it
We do not sell your personal information. We share it only with the services that make this site work: Resend delivers our email, Cal.com runs our booking calendar, Cloudflare checks that a sign-up is not a bot, and our hosting provider runs the servers this site and its database sit on. Sharing with LinkedIn is described above and happens only where you have consented.
Your choices and rights
EU / EEA / UK / Switzerland (GDPR)
If you are in the EU, EEA, UK, or Switzerland, we do not set advertising cookies or fire the Conversions API until you opt in via our cookie banner. You can decline, and declining is as easy as accepting. You may withdraw consent at any time using the “Cookie settings” button below. You also have the right to access, correct, delete, or port your personal data, and to object to processing — contact us using the details below.
California / US (CCPA / CPRA)
Use of advertising cookies and the Conversions API may be considered a “sale” or “sharing” of personal information under California law. You have the right to opt out of the sale or sharing of your personal information, and the right to know, delete, and correct it. To opt out, use the “Cookie settings” button below to decline tracking, or send a Global Privacy Control signal (see below).
Global Privacy Control
We honor the Global Privacy Control (GPC) signal everywhere. If your browser or extension sends GPC, we treat it as an opt-out and do not load the LinkedIn Insight Tag or fire the Conversions API, regardless of your location.
Asking us to delete something
Email us at the address below and say what you want removed. We will delete the record and any file attached to it, and confirm when it is done. We do not need you to have an account, and we will not ask you why.
Withdrawing consent
Use the “Cookie settings” button below to change or withdraw your choice at any time. Your updated choice applies the next time you visit one of our pages that use these cookies. You can also clear cookies in your browser settings.
Contact
Questions or requests about your data? Email hello@dija.ai.