Privacy & Data Handling Policy

Last updated: September 2026 · Applies to IntelliPresta's PrestaShop modules — Marketplaces Pro and Export + Import + Update Everything — and to the IntelliPresta authorisation and sign-in services at intellipresta.com

IntelliPresta develops modules that run inside a merchant's own PrestaShop store: Marketplaces Pro, which connects the store to online marketplaces such as Amazon, and Export + Import + Update Everything, which exports and imports the store's own data and can send those files to, or read them from, the merchant's Google Drive and Google Sheets. This policy describes what data is collected, how it is used, where it is stored, how it is protected, with whom it is shared, how long it is kept, and how it is deleted.

1. The architecture, in one paragraph

Marketplaces Pro runs inside the merchant's own PrestaShop installation, on hosting the merchant controls. Marketplace data — listings, prices, stock, orders, and the buyer details needed to fulfil them — travels directly between the merchant's server and the marketplace's official API, and is stored only in the merchant's own database. IntelliPresta operates one small hosted component: an authorisation service that completes the secure connection handshake. It keeps no database and stores no data. Each merchant is the data controller for the data in their shop; IntelliPresta is not a processor of marketplace or buyer data in normal operation.

2. What data is collected, and why

2.1 In the merchant's shop (by the module)

Data	Source	Purpose
Product and listing data (titles, descriptions, attributes, prices, stock)	The merchant's own catalogue; listing status from the marketplace API	Creating and synchronising marketplace listings
Order data (order id, items, amounts, taxes, delivery speed, fulfilment channel)	Marketplace API	Creating the corresponding PrestaShop order; accounting
Buyer contact and delivery data (name, delivery address, marketplace-relay e-mail, phone where provided)	Marketplace API, under the authorisations the merchant's seller account grants	Solely to fulfil the order: address labels, carrier hand-over, invoices, and order-related communication permitted by the marketplace
Marketplace fees and settlement figures	Marketplace API reports	Margin and accounting visibility for the merchant
API credentials for the merchant's seller account (refresh token; optionally client credentials in advanced configurations)	Issued by the marketplace when the merchant approves the connection	Authenticating the shop's API calls

2.2 On IntelliPresta's authorisation service

The service at intellipresta.com processes, transiently and per request:

the one-time authorisation code the marketplace issues when a merchant approves the connection, exchanged immediately for the merchant's credentials and passed to the merchant's shop; and
the merchant shop's refresh token, presented by the shop to obtain short-lived access tokens during operation.

The service is stateless: it has no database, stores no tokens, no personal data, and no order or product data. Values exist in memory only for the duration of each request and are transmitted exclusively over TLS-encrypted connections. It sets no cookies and runs no analytics.

2.3 The Google connection (Export + Import + Update Everything)

A merchant may connect a Google account to the module to send exports to Google Sheets or Google Drive, and to import a Google Sheet or a data file stored in Drive. The connection is optional: the module works without it, and every other export and import route is unaffected.

What is requested. Sign-in (openid), the address of the signed-in account (userinfo.email), and the drive.file permission. drive.file limits the module to the files it creates itself and to the files or folders the merchant explicitly picks in Google's own file picker. The rest of the merchant's Drive is neither visible nor reachable.
What is done with it. Exported files are uploaded to the chosen folder or spreadsheet; for an import, the chosen file's current content is downloaded and imported. Nothing else is read, changed or deleted. The address of the connected account is shown in the module so the merchant knows which account is in use.
Where the data goes. The files travel directly between the merchant's server and Google. They never pass through IntelliPresta.
Where the connection is kept. The Google credentials are stored encrypted in the merchant's own PrestaShop database, on the merchant's hosting.
IntelliPresta's sign-in service completes the Google sign-in and renews access when the shop asks. Like the authorisation service above it is stateless: it keeps no tokens, no files, no e-mail addresses and no shop data.
Disconnecting. The Disconnect button in the module removes the connection from the shop and withdraws the module's access at Google. The merchant can also withdraw it at myaccount.google.com/permissions. Uninstalling the module disconnects it as well. Files already in Drive stay with the merchant.

Limited Use. IntelliPresta's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only to provide the features described above. It is never sold, never used for advertising or profiling, never transferred to others except as needed to provide those features or where required by law, and no human reads it except with the merchant's explicit permission for support, for security reasons, or where the law requires it. Google user data is not used to develop, improve or train generalised artificial-intelligence or machine-learning models.

2.4 Support correspondence

If a merchant contacts support@intellipresta.com, we hold that correspondence (name, e-mail address, and whatever the merchant includes) to answer and to keep a support history.

3. How data is used

Data handled by the module is used only for the purposes in the table above — operating the merchant's marketplace business. Specifically, buyer personal data obtained from the marketplace is used only for order fulfilment and permitted order-related communication. It is not used for marketing, profiling, enrichment, or any purpose unrelated to the order, and it is never aggregated across merchants — the architecture makes that impossible, since each shop holds only its own data.

4. Where data is stored

Merchant and buyer data: in the merchant's own PrestaShop database, on the merchant's hosting, in the location the merchant chose.
IntelliPresta's authorisation service: nothing stored (see 2.2).
Support correspondence: in IntelliPresta's e-mail system.

5. How data is protected

All connections between the merchant's shop, the authorisation service and the marketplace's API use TLS (HTTPS) encryption in transit.
Buyer personal data requested from the marketplace uses the marketplace's restricted-data mechanisms: access tokens are scoped to the specific order and data element, obtained per operation, and never stored.
The module stores credentials in the shop's configuration, never in source code, and its administration screens never redisplay stored secrets.
The authorisation service holds its own credentials in server-side configuration files outside the web root's readable scope, with access restricted to IntelliPresta administrators.
Within PrestaShop, access to order and customer data is governed by PrestaShop's own employee-permission system, under the merchant's control.

6. With whom data is shared

IntelliPresta shares no marketplace or buyer data with anyone — it does not hold any. From the merchant's shop, data flows only to: (a) the marketplace's own API, as required to operate the integration; and (b) parties the merchant themselves engages (for example their carrier, for delivery). IntelliPresta uses a hosting provider for intellipresta.com; because the authorisation service is stateless, no personal data is stored with that provider. No data is sold, rented, or disclosed for advertising purposes — by design there is nothing to sell.

7. How long data is kept

In the merchant's shop: retention is under the merchant's control, subject to their legal obligations (e.g. tax law for order records). The module adds no retention of its own beyond the shop's.
Authorisation service: per-request only; nothing is retained.
Support correspondence: kept while relevant to an open licence or obligation, then deleted.

8. How data is deleted

Disconnecting: the merchant can revoke the marketplace authorisation at any time from their seller account, or with the module's Disconnect button, which clears the stored credential. A connected Google account is disconnected the same way, from the module or from the merchant's Google account settings (see 2.3).
Uninstalling: uninstalling the module removes the module's database tables — staged orders, listing data, logs and settings — from the merchant's shop. Orders already created in PrestaShop remain part of the shop's normal order history, under the merchant's own retention rules.
Buyer deletion requests: merchants are responsible for honouring data-deletion obligations for their own shops; PrestaShop's customer-erasure tooling covers records the module created. Where marketplaces send account-closure notifications, our endpoint acknowledges them; as no data is held centrally, no central deletion is required.
Support correspondence: deleted on request to support@intellipresta.com.

9. Your rights

For data in a merchant's shop, the merchant is the controller — buyers should direct requests (access, correction, deletion) to the shop they bought from, or to the marketplace they used. For the little that IntelliPresta itself holds (support correspondence), you can request access, correction or deletion at any time via the address below.

10. Changes to this policy

Material changes will be published on this page with an updated date above.

11. Contact

Questions about this policy or data handling: support@intellipresta.com.