Data processing agreement
Your clients’ data, on your instructions
This is the agreement between your agency and us under Article 28 of the GDPR. Your agency is the controller of its buyers’ and sellers’ data; we process it only to run Jedro for you. It is in place before Jedro imports a single message, contact or listing — until then, nothing comes in.
Importing past chats is being built. Where a row describes it, it describes how it will work, and this agreement binds us to it.
Who signs
The controller: the agency that accepts this agreement, under the legal name, company ID and registered address it gives when it does — its OIB if it is registered in Croatia, its VAT number elsewhere in the EU, and its registration number anywhere else.
The processor, which runs Jedro:
Vila Markotić d.o.o. · OIB 75035836266 · MBS 060469540
Prapatnice 27, 21276 Prapatnice (Grad Vrgorac), Croatia · hello@jedro.ai
This agreement is part of the contract under which your agency uses Jedro. Where the two differ on personal data, this agreement wins.
What it covers
Purpose
Answering and qualifying the enquiries that reach your agency, drafting replies in the language each client writes in, offering and holding viewing times, preparing the brokerage agreement from your own template, recording outcomes in your pipeline, estimating property prices for your agency’s valuations from your own records and the area figures, and showing your owners how the work is going. Nothing else.
What we do with the data
Receive it from the channels you connect, import the history you choose, store it, sort out conversations that are not about property, translate messages, when a member of your staff opens them, between the sender’s language and the language that staff member uses Jedro in, keeping each translation with its message, draft replies with an AI model, send the replies a person at your agency approves — or the kinds you have switched on to send alone — and delete it.
How long
For as long as your agency uses Jedro, and then for the 30 days it takes us to hand everything back and delete it. Within that time, a conversation is deleted 12 months after the person last wrote to you, with everything in it; if they write again before that, the 12 months start again. Jedro shows the date on the conversation in its last 30 days.
Whose data, and which
Whose
People who write to your agency — buyers, sellers, tenants and landlords; people they name in their messages; and your own staff who use Jedro.
Which
Names, phone numbers and email addresses; messages and their attachments, and their translations; language; the properties someone asked about, their budget and dates; viewing times and outcomes. For your staff: name, email address and their activity in Jedro — what they approved, changed or sent, and when.
OIB and home address
Only when your brokerage agreement template asks for them, and only for the person signing it. They are used to fill that agreement and nothing else.
Sensitive data
Jedro never asks for health, religion, ethnicity or any other special category under Article 9. If a client volunteers it in a message, it stays inside that message: it is not extracted, not tagged and not used to sort or score anyone.
Before anything is imported
Nothing is imported and no channel is connected until this agreement is in place. Once it is, data comes in like this:
- Past WhatsApp chats: Meta shares up to six months. Jedro sorts them and lists the ones that look like enquiries. Only the chats you tick come in.
- Email: Jedro reads the last 30 days of the inbox you connect, and keeps only threads about property.
- New WhatsApp and Messenger messages: Jedro sorts the first messages from each new person before it keeps anything. A conversation about property is kept, for 12 months after the person last wrote. One it cannot place yet is kept for up to 7 days for you to decide, then deleted with everything in it; anything you reply to from Jedro is kept. Any other chat, and any chat you remove from Jedro, is not stored. From Messenger, Jedro receives the message and the identifier Meta gives the sender for your Facebook Page, not their name or number. Photos, voice notes and files stay with Meta: from WhatsApp, Jedro fetches one only when someone at your agency opens it; from Messenger, it keeps only what kind of thing was sent. When you disconnect a number or a Facebook Page, or remove Jedro from it at Meta, everything that came through it is deleted within 30 days.
- Personal chats are not stored. Jedro keeps only a one-way hash of the number, made with a secret key, so it knows not to read that chat again — never the name, the number or a word of the conversation.
- If you choose nothing, the list of chats on offer is deleted after 24 hours.
Your instructions — Art. 28(3)(a)
We process your data only on your documented instructions. Those are this agreement, the settings your agency chooses in Jedro — including what Jedro may send alone and the rules you teach it — and anything you ask of us in writing.
If we think an instruction breaks the GDPR or Croatian data protection law, we tell you at once and do not carry it out until you confirm or change it.
If EU or Croatian law requires us to process your data in any other way, we tell you before we do, unless that law forbids telling you.
Who can see it — Art. 28(3)(b)
Only the people who run Jedro, each bound to confidentiality in writing, and only when running the service needs it or you ask us to. Your staff see what Jedro shows them; no other agency ever does.
How it is kept safe — Art. 28(3)(c)
We apply the measures Article 32 requires, and keep them at least at this level:
- Your data is stored in Frankfurt, Germany, and processed there.
- Encrypted in transit and at rest. From WhatsApp and Messenger, the sender’s name, number or identifier and the text of each message are encrypted once more, with a key of our own, before they are stored.
- Each agency’s data is separated at the database level, so no one signed in to one agency can reach another’s.
- No passwords to leak: staff sign in with a one-time code or with Google.
- Access to production data is limited to the people who run the service, each with their own account.
- We review these measures at least once a year and whenever the service changes in a way that affects them.
Other companies — Art. 28(3)(d)
You authorise us to use these sub-processors. Each is bound by a written agreement with the same data protection obligations as this one, and each handles only what its job needs.
- Supabase — the database. Frankfurt, Germany (AWS eu-central-1).
- Vercel — runs the application. Frankfurt, Germany (fra1).
- Anthropic — sorts conversations, translates messages and drafts replies with its Claude models. United States. It does not use your data to train its models.
Meta for WhatsApp and Messenger, and Google or Microsoft for your inbox, are not our sub-processors: they are the providers your agency already uses, under your own terms with them — for WhatsApp and Messenger, the terms your agency accepts with Meta for its number and its Facebook Page. Jedro connects to them on your behalf.
Before we add or replace a sub-processor, we email your owner at least 30 days ahead with who, what and where. You can object in that time. If we cannot meet your objection, you can end the contract at no cost before the change takes effect.
We remain fully liable to you for what our sub-processors do with your data.
Data that leaves the EU
One transfer: sorting, translating or drafting sends the message to Anthropic in the United States. It is covered by the Standard Contractual Clauses in Anthropic’s data processing agreement (Commission Implementing Decision (EU) 2021/914).
If your agency is registered outside the EU and EEA, in a country without an adequacy decision, your own access to your data from there is a transfer too. For that case the Standard Contractual Clauses, module four (processor to controller), are part of this agreement, governed by Croatian law and decided by Croatian courts.
We make no other transfer outside the EU without telling you first under the sub-processor rule above.
Requests from clients — Art. 28(3)(e)
If a buyer, seller or anyone else asks us to see, correct, delete or move their data, we forward the request to you within five working days and do not answer it ourselves unless you ask us to.
Jedro lets you find everything held about a person, export it, correct it and delete it — so you can answer within the month Article 12 gives you.
If something goes wrong — Art. 28(3)(f)
If we become aware of a personal data breach affecting your data, we tell you without undue delay and within 48 hours at the latest — so you can notify AZOP within the 72 hours Article 33 gives you.
We tell you what happened, whose data and how much of it, the likely consequences, and what we have done and will do about it. What we do not know yet, we send as soon as we do.
If the people affected must be told under Article 34, we help you tell them.
Assessments — Art. 28(3)(f)
We give you what you need for a data protection impact assessment, including where AZOP’s list of processing that requires one applies to you, and for any consultation with AZOP that follows.
When you leave — Art. 28(3)(g)
When your agency closes its account, you can first export every thread, contact and listing in a format your next system can read.
Then we delete your data, and have our sub-processors delete it, within 30 days, and confirm it to you in writing.
Copies inside backups are deleted as those backups expire, and are never restored into the service.
We keep nothing on your behalf after that. If a law obliges your agency to keep records — the Croatian Anti-Money Laundering and Terrorist Financing Act, for one — export them before you close, and before a conversation reaches its 12 months: Jedro is not your archive.
Checking on us — Art. 28(3)(h)
We give you everything you need to show that this agreement is kept, and answer your written questions within 30 days.
You, or an auditor you appoint who is bound to confidentiality, can audit us once a year with 30 days’ notice — and at any time after a breach or when AZOP asks. Each side bears its own costs.
What stays yours
As controller, your agency remains responsible for:
- having a legal basis to handle each enquiry and the data in it;
- telling buyers and sellers how their data is handled, as Articles 13 and 14 require — including that a processor handles it and that replies are drafted with AI;
- telling your staff what Jedro records about their work, and consulting employee representatives where the Croatian Labour Act requires it, before using performance figures;
- your own record of processing, and how long your agency must keep its records.
AI, and what it never does
Your data never trains a language model — ours, Anthropic’s or anyone’s. We do not use it for our own purposes except under the Pool Addendum: market statistics, which count only totals and never messages or anything that came through WhatsApp or Messenger, come with this agreement unless your agency leaves them out. We never sell your data. The area figures, property values and reports Jedro may publish or sell are built only from those totals and never identify an agency, a sale or a person. The shared price model learns only from those combined figures; your own sales calibrate only your own valuations.
What Jedro learns from your agency are rules you can read, each with who taught it, and the calibration of your own valuations on your own closed sales. Both are your data, used for you only, and are deleted with it.
Every message Jedro writes says so, in the recipient’s language, as Article 50 of the EU AI Act requires.
Jedro makes no decision about a person that has legal or similarly significant effects. Who gets a viewing, an address or an agreement is decided by your agency.
Liability
Each of us is liable for its own part, as Article 82 of the GDPR sets out. Nothing in the contract limits what either of us owes a person whose data was harmed.
Law, courts and the authority
This agreement is governed by Croatian law — the GDPR and the Act on the Implementation of the General Data Protection Regulation (NN 42/2018).
Disputes go to the competent court in Split.
The supervisory authority is AZOP — Agencija za zaštitu osobnih podataka, Ulica Metela Ožegovića 16, 10000 Zagreb.
It is published in English, Croatian, Italian and Spanish. If they differ, the English text prevails.
How it is signed
Your agency’s owner accepts it in Jedro before the first channel is connected. Article 28(9) allows the agreement to be in electronic form, and that acceptance is it. If you would rather sign on paper, write to us.
Either way, you receive a copy with the version, the date and who accepted it.
Changes
We change this agreement only with your agreement — except the sub-processor list, which follows the notice rule above. Each version has its own number and date, and the one you accepted stays available to you.