Last updated: 2026-10-22

Data Processing Agreement

These terms apply whenever ModuleDesk processes personal data on your behalf, and form part of your agreement with us. They are written to satisfy Article 28 GDPR. If your organisation needs a countersigned copy, write to support@moduledesk.app and we will sign one.

1. Who is who

You are the controller for your customers' support data: the conversations are part of your relationship with your buyers, and you decide what happens to them. We are the processor, acting only on your instructions.

Separately, we are the controller for your own account data — your email, password and preferences. That is covered by our Privacy Policy, not by this agreement.

"We" is: Pol Adrià Rué Palau, sole trader (empresario individual), NIF 47696679S, Carrer de la Llibertat 27, 2-3, 25005 Lleida, Spain — support@moduledesk.app. A countersigned copy of this agreement names the same party; an art. 28 contract has to identify the processor, so it is stated here rather than left to the footer.

2. What we process, and why

Subject matter: providing a support desk for your PrestaShop Addons business.

Duration: for as long as your account exists, and until you delete it.

Categories of data subject: your customers — buyers of your PrestaShop modules who have opened a support thread or placed an order.

Categories of personal data: names as displayed by PrestaShop Addons, shop URLs, languages, the full text of support messages, attachments, order and purchase history, public reviews, notes your team writes, and any site credentials you choose to store. No end-customer email addresses — the Addons API does not provide them.

Special-category data: we do not ask for it and no field is designed for it. If a customer volunteers something sensitive in a message, it is processed as ordinary message content. We cannot detect it and we do not try to.

Nature of the processing: reading from the PrestaShop Addons API, storing, displaying, searching, generating AI assistance, and sending your replies back.

3. Our obligations

We will:

  • process the data only to provide the service and only on your instructions, never for our own purposes, and never to train our own models;
  • keep it confidential, and bind anyone with access to the same duty;
  • apply the security measures in section 5;
  • not engage a new subprocessor without updating the published list in Subprocessors — your continued use after an update is your authorisation, and you may terminate if you object;
  • assist you with data-subject requests (see section 6);
  • notify you without undue delay of a personal data breach affecting your data, with what we know (see section 7);
  • help you with data protection impact assessments and with regulator enquiries, so far as the data we hold is concerned;
  • on termination, delete your data — which account deletion does immediately and irreversibly.

4. Subprocessors

The current list, what each receives, and whether you can avoid it, is published at Subprocessors and kept up to date. It names every third party, including the ones you might not expect: OpenAI receives message content verbatim with no redaction, and translation calls a Google endpoint before falling back to OpenAI.

Each subprocessor is bound by terms no less protective than these, and we remain liable to you for their processing.

5. Security measures

Passwords are hashed with bcrypt and never stored in recoverable form. Stored site passwords and your API keys are encrypted with a key held outside the database; if that key is unavailable the software refuses to store a credential rather than writing it in the clear. Each customer's data lives in its own database schema, so a query for one tenant cannot reach another's rows. Transport is HTTPS with HSTS. Sessions and remember-me cookies are HTTP-only, same-site and Secure. Repeated failed logins are rate-limited and blocked. Sensitive actions require your password again. Access to the server is by SSH key only.

Honest limits, so you can assess them: there is no end-to-end encryption of message content, because the product has to read it to work; the database is not encrypted at rest beyond the credential fields named above; and there is no formal third-party security certification.

6. Data-subject requests

If one of your customers asks you to erase their data, you can do it yourself: their customer page has Erase this customer's data, which removes every conversation, message, attachment, order, note, site and stored credential we hold for them, and nothing belonging to anyone else.

One limit you need to know: their conversations also exist in your own PrestaShop Addons account, which we cannot reach. If they are still there, the next sync brings them back — so the request has to be honoured in both places.

For an access or portability request, the same page has Export this customer's data: their record, conversations, messages, attachments, orders, reviews, your team's notes and their sites, as a single file. It names any credential we hold for them without printing the password.

7. Breach notification

If we become aware of a personal data breach affecting your data, we will tell you without undue delay and in any case within 48 hours of becoming aware, by email to your organisation's admin addresses. We will tell you what happened, which categories and roughly how many records are affected, what we have done, and what we recommend you do — and we will keep you updated as we learn more rather than waiting until we know everything.

Notifying your own supervisory authority within the 72 hours that Article 33 allows is your decision as controller. We will give you what you need to make it.

8. International transfers

Our own infrastructure is a single server, rented from Hetzner Online GmbH and located in Nuremberg, Germany; the database and cache run on that same machine, so the data you entrust to us is stored inside the European Union. Some subprocessors are outside the EEA — OpenAI, Stripe and the browser push services among them — and those transfers rely on the European Commission's Standard Contractual Clauses or an adequacy decision, as each provider's terms set out.

9. Audit

On reasonable notice, and no more than once a year unless a regulator requires otherwise, we will answer your written questions about this agreement and provide what we have to demonstrate compliance.

10. Return and deletion

At any time, Settings → Delete this account erases everything and cancels your subscription. It is immediate and cannot be undone. We keep one record that a deletion happened — the organisation name and the date, with no conversation content — because an audit trail that deletes itself is not an audit trail.

Export your data first if you want a copy: afterwards there is nothing left to export.

Also available in: Español