Privacy Policy
ModuleDesk is a support desk for PrestaShop Addons sellers. It reads your support conversations from your own PrestaShop Addons account, keeps a working copy, and helps you answer them.
This page describes what the software actually does, verified against the code rather than written from a template. Where something is a limitation, it says so.
Who we are
The controller for your account data, and the processor for your customers' support data, is:
- Pol Adrià Rué Palau, sole trader (empresario individual)
- NIF: 47696679S
- Address: Carrer de la Llibertat 27, 2-3, 25005 Lleida, Spain
- Email: support@moduledesk.app
There is no Data Protection Officer: a one-person business is below the threshold that requires one (art. 37 GDPR). Write to the address above for anything covered by this policy, including a data request.
You can complain to the Spanish supervisory authority, the Agencia Española de Protección de Datos (www.aepd.es), or to the authority of the EU country where you live or work.
Two kinds of data, and two different roles
Your own account data. You are the subject; we are the controller. This is your email address, your password (hashed with bcrypt — we never hold the password itself), your language and timezone, your signature, your working hours if you set a schedule, your organisation's name and VAT number, and your Stripe customer and subscription identifiers.
Your customers' support conversations. Here you are the controller and we are your processor: the conversations belong to your relationship with your buyers, and we hold a copy so the product can work. We act on your instructions and we do not use this content for our own purposes.
What we store about your customers
Pulled from the PrestaShop Addons API with the key you provide:
- the thread subject, the customer's display name, their shop URL, their language and PrestaShop version;
- the full text of every message, in both plain and original form;
- attachments — filename, type, and the file itself, cached on our disk;
- order and purchase history: product, order id, amount, currency, date, support-expiry dates and entitlement counters;
- public reviews, with the reviewer's name and text;
- notes your team writes about a customer;
- credentials you choose to store for a customer's site: the username and connection details in plain text, and the password encrypted with a key held outside the database.
We also derive AI artefacts from that content: summaries, classifications, draft replies, translations and embeddings. These contain customer content by construction.
One thing we do not hold: there is no end-customer email address anywhere in the database. PrestaShop Addons does not give us one.
Who else sees it
Every third party below receives data because a feature needs it. None of them receives it for advertising, and there is no analytics or tracking of any kind in this product.
OpenAI — for drafts, classification, summaries, proofreading and translation. A draft request sends the last ten messages of the conversation verbatim, a summary, a classification, product knowledge, documentation snippets, and excerpts of similar resolved conversations from your other customers. Embedding requests send conversation text. Attachments are never sent.
Stated plainly: there is no redaction step. Names, shop URLs, order numbers and anything else inside a message body go to OpenAI as written. We do not set a training opt-out flag in code — anything on that point rests on OpenAI's own API terms, not on something this product does. If that matters to you, do not use the AI features; everything else works without them.
Google Translate — message translation tries Google's public translation endpoint first and falls back to OpenAI. This sends the message text.
Stripe — payments. Receives your admin email address, your organisation name, and the plan. We never see or store a card number; only Stripe's customer, subscription and invoice identifiers are kept here.
Resend — transactional email, by SMTP. Only ever to you and your team: email verification, password resets, invitations, security notices and payment failures. We never email your customers. Out-of-office auto-responses are posted back through the PrestaShop Addons API, not by email.
VirusTotal — only when you click an unchecked link in a conversation, and only on the MAX plan. It receives the URL and nothing else. Note that VirusTotal publishes URLs submitted to it, which is why this is a deliberate click rather than something that runs by itself.
Push notification relays — if you enable browser notifications, a notification goes through your browser vendor's service (Google, Mozilla, Apple or Microsoft, depending on the browser). The payload is encrypted end to end, but it contains the ticket subject and a short preview of the latest message.
EU VIES — VAT number validation, which sends the number to the European Commission's service.
Your own shops and servers — the site checker requests your customers' shop URLs from our server, and an FTP/SFTP test connects to the host you entered, using the credentials you stored.
Google Fonts — our pages load an icon font from Google, which means your browser's IP address and user agent reach Google on every page view, including this one. The ticket page also loads its editor from a public CDN.
Infrastructure — DNS is served by Cloudflare, which does not proxy or see your traffic. Code is deployed from GitHub.
Where it runs
ModuleDesk runs on dedicated server infrastructure. The PostgreSQL database and the Redis cache run on that same machine and are not shared with any third-party database service. Each customer's conversation data lives in its own database schema, separate from every other customer's.
The server is rented from Hetzner Online GmbH (Industriestr. 25, 91710
Gunzenhausen, Germany) and runs in their Nuremberg, Germany data centre
(nbg1). All processing therefore takes place inside the European Union; we do
not replicate or back up your data outside the EEA. If we ever move the machine
to another location we will update this page and tell existing customers.
How long we keep it
Your conversations are kept for as long as your account exists. There is no automatic expiry, and we would rather say that than imply a retention period the software does not enforce.
Two things do expire on their own: cached attachment files are removed from our disk after 30 days, though the attachment stays listed and is re-fetched if you open it; and URL safety results are kept for seven days before being rechecked.
On the Free plan, conversations older than 30 days are hidden rather than deleted, and reappear if you upgrade.
Your rights, and how to actually use them
Access and portability. Settings → export your data produces everything we hold about your account. It asks for your password first.
Erasure. Settings → Delete this account erases your organisation, your team, every conversation, note, attachment and stored credential, and cancels any active subscription. It asks for your password and for you to type your account name, and it cannot be undone.
One thing to understand about erasure: your support conversations also exist in your own PrestaShop Addons account. We only ever held a copy, and deleting your account here removes our copy — not the original.
Your customers' rights. Your buyers' data reached us through you, so a request from one of them should come to you, and you can act on it in the product. If you need help with a specific request, write to us.
Rectification and objection. Write to us and we will act on it.
Security
Passwords are hashed with bcrypt. Stored site passwords and your API keys are encrypted with a key kept outside the database; if that key is unavailable the software refuses to store a credential rather than saving it in the clear. Sessions and remember-me cookies are HTTP-only, same-site, and marked Secure when served over HTTPS. Repeated failed logins are rate-limited and blocked. Sensitive actions require your password again, even when you are already logged in.
Cookies
Two, both strictly necessary: a session cookie and, so you stay logged in, a remember-me cookie. Both last 30 days. A CSRF token is kept inside the session.
There is no analytics, advertising or tracking cookie in this product, and no third-party script that sets one.
Changes, and getting in touch
The date at the top of this page is the last change. For anything here — including a data request — write to support@moduledesk.app.