Data Processing Addendum

Last Updated: November 14, 2026

This Data Processing Addendum ("DPA") is part of the Datajar Terms of Service. It applies when Datajar processes personal data on your behalf while you use our Services, including Datajar MCP (https://mcp.datajar.co). If this DPA and the Terms of Service differ on personal data we process for you, this DPA wins.

1. Roles

You, the customer who holds the Datajar account, are the controller of the personal data you ask us to process: for example the leads you save in a lead jar, the contact lists you send to an advertising audience, and the customer data we read from a store you connect.
Datajar, Inc. ("Datajar"), a Delaware corporation, is your processor. We process that data only to provide the Services to you, and only on your instructions.
Your instructions are the actions you, or the AI client you connect to Datajar, take in the Services, these Terms and this DPA.

2. What we process


Kinds of people	Your leads, customers and contacts.
Kinds of data	Contact details: name, email address, phone number and, where given, city, state, postcode, country, date of birth and gender, with the date and source (form, ad or campaign name) you or Meta give with them. Other details you choose to add to a lead yourself (for example company, budget or interest). Customer and order details read from a store you connect.
Special categories	None. Do not save health, religion, political or other special category data in Datajar.
Purpose	To store your data for you and use it as you ask, for example to build custom and lookalike audiences in your own advertising accounts.
How long	As set out in section 6.

3. Our commitments

Your instructions only. We process your personal data only on your documented instructions. We tell you if we believe an instruction breaks data protection law.
Never for our own use. We do not use your personal data for our own purposes. We do not train AI models on it, do not use it to build our own audiences or profiles, do not sell it, and do not combine it with other customers' data.
Only your account. Data you save, such as a lead jar, belongs to your account only. No other Datajar user can see or use it, and we never pool it across accounts.
Confidentiality. Only people at Datajar who need access to run and support the Services can reach your data, and they are bound by confidentiality.
Security. We apply the measures in section 8.
Help with your duties. We help you answer requests from people exercising their rights (access, erasure and others), and with security, breach notices and impact assessments, as far as we reasonably can given what we process.

4. Subprocessors

You give us general permission to use the subprocessors below. Each one is bound by written terms that protect your data at least as well as this DPA.

Subprocessor	What it does	Where
Google Cloud (Google Cloud EMEA Limited)	Hosting: servers, database, encrypted backups	Frankfurt, Germany (europe-west3); disk snapshots in the EU

We list any new subprocessor on this page before it starts processing your personal data. If you object on reasonable data protection grounds, tell us at the contact below; if we cannot resolve it, you may stop using the affected feature or close your account.

Not subprocessors. Some services receive your data because you send it there yourself, and they act under your own agreement with them:

Your advertising accounts (for example Meta). When you ask to add a lead jar or a contact list to an audience in your Meta ad account, we send the email addresses and phone numbers to Meta hashed (SHA-256), as Meta requires. Meta's Custom Audience terms between you and Meta apply.
Your AI client (for example Claude or ChatGPT). The answers our tools return go to the AI client you connected, under your agreement with its provider. When you or your AI client ask to see a lead jar, our tools return its leads (names and contact details) to that AI client; otherwise they return counts and jar names.

5. Transfers outside the EEA

We store your personal data in the European Union. If a subprocessor ever processes it outside the EEA, we make sure a lawful transfer mechanism is in place, such as the European Commission's Standard Contractual Clauses.

6. Deletion and retention

Lead jars: each lead is deleted automatically one year after it was saved in the jar. You can delete one person (for example after an erasure request), a whole jar, or all your jars at any time. A person you deleted can be saved again later if they reach you again; we keep no list of deleted people.
Account deletion: when you delete your Datajar MCP account, all your lead jars and the leads in them are deleted.
Backups: deleted data can stay in our encrypted database backups for up to 30 days and in disk snapshots for up to 14 days, and is then deleted with them. We do not restore deleted data from backups except to recover the whole service after a failure.
Data already sent to your advertising account: deleting a lead in Datajar does not remove that person from an audience already created in your Meta ad account. Remove them there, or ask your AI client to do it with our audience tools.
Other data follows the retention described in our Privacy Policy.

7. Personal data breach

If we become aware of a personal data breach affecting your personal data, we tell you without undue delay and in any case within 72 hours, by email to your account address. We tell you what happened, what data and roughly how many people are affected, what we are doing about it, and who you can contact. We update you as we learn more. Notifying a supervisory authority or the people affected is your decision as controller; we help you with it.

8. Security measures

Lead contact details are encrypted in our database. Connection tokens for your accounts are encrypted.
Data travels encrypted (HTTPS/TLS).
Lead contact details are never written to our logs, our usage log or our audit records. They are shown only to your own account: on the Lead jars page, in a CSV file you download, and to your AI client when it asks for a jar's leads.
Each account sees only its own data; every lead jar action checks that the jar belongs to the account asking.
Lead jars are available on the Enterprise plan only.
Access to servers is limited to named Datajar staff with individual accounts.

9. Audits

On request we give you the information you reasonably need to show that we meet this DPA. Where that is not enough, you may audit us once a year with 30 days' notice, during business hours, at your cost, and under confidentiality.

10. Your responsibilities

You have a lawful basis to collect your leads and contacts and to use them as you ask us to, for example consent, or legitimate interest where the law allows it.
Your lead forms and privacy notices tell people that their details may be used for advertising, including custom and lookalike audiences.
You handle requests from the people whose data it is. When someone asks you to erase their data, you can delete them from a lead jar yourself, or ask us to.

11. Contact

Datajar, Inc. (a Delaware corporation)
Contact address: Seesener str 40a, 10711 Berlin
ali.mahmoud@datajar.co