Data Processing Agreement
Last updated: 16 November 2026 · Version 1.0
1. Parties
This Data Processing Agreement ("DPA") is between:
- Puduo Trading Ltd., a company registered in Ghana and in the United States, acting as processor ("Puduo", "we" or "us"); and
- the Customer, meaning the business that has a Nimdee account and has accepted our Terms of Service, acting as controller ("the Customer" or "you").
2. How this DPA applies
This DPA forms part of the Nimdee Terms of Service. The Customer accepts it when it accepts the Terms of Service. No separate signature is needed.
This DPA covers the personal data that we process for the Customer when we provide Nimdee. It does not cover the personal data of people who hold a business account or are team members, where we act as controller. Our Privacy Policy covers that data.
If this DPA and the Terms of Service disagree about personal data, this DPA applies.
3. Words used in this DPA
- Data Protection Laws means the laws on personal data that apply to the processing, including the Ghana Data Protection Act, 2012 (Act 843), the Nigeria Data Protection Act 2023, the Kenya Data Protection Act 2019, South Africa's Protection of Personal Information Act (POPIA) and, where it applies, the EU General Data Protection Regulation (GDPR).
- Customer Personal Data means the personal data described in section 6 that we process for the Customer.
- Personal data, processing, controller, processor, data subject and personal data breach have the meaning given in the Data Protection Laws that apply. Where a law uses different words (for example "responsible party" and "operator" under POPIA), those words have the same meaning here.
- Subprocessor means another company that we use to process Customer Personal Data.
4. Subject matter and duration
Subject matter: we process Customer Personal Data to provide Nimdee to the Customer.
Duration: this DPA lasts as long as we process Customer Personal Data for the Customer. It continues after the Terms of Service end, until we have deleted that data as section 14 describes.
5. Nature and purpose of the processing
We process Customer Personal Data only to provide the service. This includes:
- reading the website pages the Customer asks us to read (we follow the site's robots.txt file), and storing the files and notes the Customer adds;
- turning that content into searchable passages and search vectors;
- receiving visitors' chat messages and generating AI answers from the Customer's content;
- storing chats and visitor contact details, and showing them to the Customer's team;
- alerting the Customer's team when the assistant cannot answer, and letting the team reply in the same chat;
- keeping the service secure and fixing errors;
- deleting data at the end of its retention period or when the Customer asks.
6. Types of personal data
| Category | Personal data |
|---|---|
| Business content | Any personal data the Customer includes in website pages, uploaded files (PDF, Word, Excel, text) and notes |
| Chats | What visitors type, the assistant's answers (including which of the Customer's pages each answer used), the team's replies, and the page where the chat started |
| Visitor ID | A random visitor ID stored in the visitor's browser (local storage) so the chat continues on that browser. It is not linked to the visitor's identity unless the visitor leaves contact details. |
| Visitor contact details | Name, email address or phone number, and a note, if the visitor chooses to leave them |
The Customer should not add sensitive personal data (for example health data) to its content, or ask visitors for it, unless this is necessary and lawful.
7. Categories of data subjects
- Visitors to the Customer's website who use the chat.
- The Customer's staff, where their personal data appears in the Customer's content or in chats (for example, when a team member replies to a visitor).
- Any other people whose personal data the Customer chooses to include in its content.
8. The Customer's instructions
We process Customer Personal Data only on the Customer's documented instructions. The Customer's instructions are:
- the Terms of Service and this DPA;
- the settings and choices the Customer makes in the Nimdee dashboard;
- any other reasonable written instructions the Customer gives us, if they fit the service.
We may also process Customer Personal Data where the law requires it. In that case, we will tell the Customer first, unless the law forbids it.
If we believe an instruction breaks Data Protection Laws, we will tell the Customer and we may refuse to follow it.
The Customer's responsibilities
The Customer is responsible for:
- having a lawful reason for the processing, and any consent that its law requires;
- telling its website visitors about the chat in its own privacy notice;
- having the right to add its content, including the right to have its website read;
- answering requests from its data subjects;
- the accuracy of its content.
9. Confidentiality
We make sure that everyone at Puduo who can access Customer Personal Data:
- needs that access to do their work;
- has agreed to keep it confidential, or has a legal duty to do so.
10. Security measures
We use technical and organisational measures that fit the risks of the processing. They include:
- Encryption: data is encrypted in transit and at rest by Google Cloud.
- Separation: each Customer's data is kept separate and can only be reached through that Customer's authorised access.
- Least privilege: our service accounts only get the access they need.
- Strong sign-in: our administrators use multi-factor sign-in.
- Audit logs: we keep a record of changes made in the dashboard.
- Error monitoring: we watch for errors so we can fix problems quickly. Error reports do not store IP addresses.
We review these measures and may improve them over time. We will not reduce the overall level of protection.
11. Subprocessors
The Customer gives us general permission to use subprocessors. Today we use:
| Subprocessor | Service | Location |
|---|---|---|
| Google LLC and Google Ireland (Google Cloud / Firebase) | Hosting; database (Cloud Firestore); file storage (Cloud Storage); API (Cloud Run) | europe-west1 (Belgium) |
| Google LLC and Google Ireland (Google Cloud / Firebase) | Sign-in (Firebase Authentication / Identity Platform) | Global |
| Google LLC and Google Ireland (Google Cloud / Firebase) | Browser push notifications (Firebase Cloud Messaging); sending emails through Google Gmail | Google's global infrastructure |
| Anthropic PBC | Generates the assistant's answers. It receives the visitor's question, recent messages of that chat and the relevant passages from the Customer's content. Under Anthropic's commercial terms, API data is not used to train its models. | USA |
| Voyage AI | Turns passages and questions into search vectors, where this feature is used | USA |
| Paystack (part of Stripe) | Card and mobile-money payments for plans and wallet top-ups: the payer's name, email address, the amount and what it is for. Card and mobile-money details go straight to Paystack; we never see them. | Nigeria, and the countries where Paystack operates |
| Stripe | Card payments outside Africa. Not active yet. | To be confirmed when it opens |
We bind each subprocessor to data protection terms that protect Customer Personal Data at least as well as this DPA, as far as they apply to the service it provides. We remain responsible to the Customer for our subprocessors' work.
New subprocessors
We will tell the Customer at least 30 days before a new subprocessor starts processing Customer Personal Data. We will do this by email or in the app.
The Customer may object, on reasonable data protection grounds, by writing to admin@puduo-tech.com within those 30 days. We will then discuss the concern in good faith. If we cannot solve it, the Customer may stop using the part of the service affected, or close its account.
12. Helping with data subject requests
If a data subject asks us directly to use their rights (for example, to see or delete their data), we will pass the request to the Customer without undue delay. We will not answer it ourselves, except to tell the person that we have passed it on.
We will help the Customer answer these requests, as far as is reasonable and taking into account the nature of the processing. For example, the Customer can delete chats and contacts from the dashboard before the automatic retention period ends.
We will also give reasonable help with data protection impact assessments and with discussions with data protection authorities, where the law requires and the request relates to our processing.
13. Personal data breaches
If we become aware of a personal data breach that affects Customer Personal Data, we will tell the Customer without undue delay and within 72 hours of becoming aware of it.
Our notice will include, as far as we know at the time:
- what happened, and when;
- the types of data and the approximate number of people affected;
- the likely effects;
- what we have done or plan to do to deal with it and reduce harm;
- a contact person for more information.
If we do not have all the information at first, we will send it in stages as we learn more. We will take reasonable steps to contain the breach and stop it happening again.
14. Deletion and return of data
While the service is running:
- chats and visitor contact details are deleted automatically 90 days after the chat's last message, and the Customer can delete them earlier;
- business content is kept while its source is in the Customer's account, and is removed when the Customer deletes the source.
When the Customer closes its account, we delete its content, chats and contacts within 30 days.
Before closing its account, the Customer can ask us at admin@puduo-tech.com for a copy of its Customer Personal Data. We will provide it in a common electronic format.
We may keep data for longer only where the law requires us to. In that case, we will keep it confidential and use it only for that legal purpose.
15. Information and audits
On request, we will give the Customer the information that it reasonably needs to show that we comply with this DPA.
If that information is not enough, the Customer may carry out an audit, or ask an independent auditor to do so, under these conditions:
- the request is reasonable and made in writing with reasonable notice;
- audits happen at most once a year, unless a data protection authority requires more, or after a personal data breach;
- the auditor keeps all information confidential;
- the audit does not disrupt our service or put other customers' data at risk;
- the Customer pays its own costs.
16. International transfers
Some subprocessors process Customer Personal Data outside the country where the Customer or its visitors are, including in the USA (see section 11).
When we transfer Customer Personal Data to another country, we use safeguards that the Data Protection Laws accept, such as standard contractual clauses or equivalent safeguards under those laws.
17. Liability
Each party's liability under this DPA is subject to the limits of liability in the Terms of Service, as far as the Data Protection Laws allow.
18. Governing law
This DPA is governed by the same law as the Terms of Service (the laws of Ghana), and the courts of Accra have jurisdiction, unless the Data Protection Laws require otherwise.
19. Changes to this DPA
We may update this DPA, for example when the law changes. We will tell the Customer about important changes by email or in the app before they take effect. We will not make changes that reduce the protection of Customer Personal Data, unless the law requires it.
20. Contact
- Company: Puduo Trading Ltd.
- Email for privacy and legal matters: admin@puduo-tech.com