Sub-processors and Third-Party Recipients

Last updated 17 November 2026

This is the current version. All versionsΕλληνικά

This page lists the service providers, carriers and other third parties involved in running the Pircel website (www.pircel.com) and Pircel's shipping platform (the Service). It supplements our Privacy Policy, our Data Processing Agreement and our Customer Agreement, and its sub-processor list matches Schedule C of the Data Processing Agreement.

CategoryWhat it means
Sub-processorsThird parties that Pircel engages to process personal data on its Customers' behalf, under written terms that meet Article 28 GDPR.
Third-party recipients (independent controllers)Third parties that receive personal data through the Service but decide their own purposes and means, such as the couriers that deliver.
Merchant-controlled integrationsSystems run by or for our Customers, such as their e-commerce platform. The Customer starts the data flows.

1. Pircel Sub-processors

Pircel binds each sub-processor by written data protection terms at least as protective as those it owes its Customers under the Data Processing Agreement, and stays liable to the Customer for each one.

Sub-processor (contracting entity)ServiceReceives personal data?What kindLocationTransfer safeguard
Hetzner Online GmbHHosting: Pircel's servers for the app, the Pircel API, its cache and job queuesYesAll Merchant DataGermany (Nuremberg)None needed: an EU company, with the data in Germany
MongoDB, Inc. (Atlas)DatabasesYesAll Merchant DataEU (Paris)Data Privacy Framework, for access by its staff
Mailgun Technologies, Inc. (Mailgun, EU region)Delivery status emailsYesRecipient's email and name, shipment referenceEUData Privacy Framework (Mailgun Technologies, Inc.), for group access. Not certified for Swiss data
Google Workspace (Google Cloud EMEA Limited)Email: support, and replies to delivery status emailsYesThe sender's email address and name, and the message, which can include shipment detailsAny country where Google or its sub-processors have facilities (Google's terms)Google's Cloud Data Processing Addendum: a data protection framework Google adopts, otherwise Standard Contractual Clauses
Functional Software, Inc. (Sentry)Error monitoring for the app, the Pircel API and the dashboard; in the dashboard, after the visitor's consent, also performance traces and session replaysIdentifiers onlyError and browser details, page addresses and identifiers, configured to exclude personal data values. Replays show no page text or inputs, and block images and mediaGermany (Frankfurt; Sentry's EU data region)Data Privacy Framework
Grafana Labs Inc. (Grafana Cloud, EU region)Service logs, server metrics and uptime checksYesIdentifiers only (order, shipment and store ids)EUData Privacy Framework (Grafana Labs Inc.), for access by its staff
Mistral AI SASReading PDF courier invoicesYes, while reading an invoice; it keeps nothing (zero data retention) and doesn't train on itRecipient names and addresses printed on courier invoicesNot committed: Mistral sets no location for its global endpoint, api.mistral.ai, which Pircel usesMistral's Data Processing Addendum: an adequacy decision, other appropriate safeguards, or Standard Contractual Clauses
Vercel, Inc.Hosting the Pircel dashboardYes, when shown in the dashboardRecipient dataEU (Paris); backups replicate globallyData Privacy Framework (Vercel, Inc.)
PostHog, Inc.Dashboard analytics and session replayOnly if it escapes maskingPage text and inputs masked in replaysUS entity; processing may occur in the US and elsewhereStandard Contractual Clauses
Amazon Web Services EMEA SARL (AWS Europe)Static assets, certificates, alerts, the servers' configuration secrets, and encrypted backups of the cache and job queuesIdentifiers only, in encrypted backupsIds, no values, encrypted before uploadIreland; edge locationsData Privacy Framework (Amazon.com, Inc.)
GitHub, Inc.Code hostingNo—United StatesData Privacy Framework

Some sub-processors rely on further providers of their own (for example, Amazon Web Services underlies MongoDB Atlas). The list above names the parties Pircel contracts with directly. More detail is in each provider's published documentation, and from us on request.

2. Third-Party Recipients (Independent Data Controllers)

The following third parties receive personal data through the Service as independent data controllers, not as Pircel's sub-processors.

Couriers

When a shipment is booked, the recipient's details (name, postal address, phone and email where given) and the shipment's details (such as the cash-on-delivery amount and the parcels) go to the courier chosen for it. Couriers receive this data as independent controllers for the delivery. They process it for their own purposes, keep it under their own retention rules and statutory duties, and publish their own privacy notices.

RecipientRoleHeadquarters / Data location
ACS Courier S.A.Greek courier: domestic and selected international deliveriesGreece (EEA)
BCS Courier / HermesGreek courier: domestic deliveriesGreece (EEA)
BoxNowOut-of-home locker delivery networkGreece / Cyprus (EEA)
Geniki Taxydromiki (DPD Group)Greek courier (part of DPD Group): domestic and internationalGreece (EEA); DPD Group is EU-based
Speedex S.A.Greek courier: domestic deliveriesGreece (EEA)
TCS / EvresisGreek courier: domestic deliveriesGreece (EEA)
DHL GroupInternational express deliveryGermany (EEA)
FedExInternational express deliverySee below
UPSInternational express deliverySee below

FedEx and UPS:

  • for rate quotes, they receive no street, name or contact details, only what's needed to price the parcel, such as the postcode, town, region and country;
  • for bookings, through the Customer's own account: FedEx through its Greek company, and UPS through UPS of Greece, Inc., a US company with a branch in Greece. The Customer is the controller and exporter of what it discloses (Data Processing Agreement, clause 9), and each courier may transfer data onward under its own arrangements.

Pircel doesn't control the couriers' security practices, retention periods or onward disclosures.

Google Maps Platform

Google LLC (Google Maps Platform: the Geocoding, Address Validation and Places APIs), for address checks and lookups: an independent controller under its Maps Platform terms (EEA Terms of Service §4.5; Controller-Controller Data Protection Terms §4.1(a)). United States, on Google's own Data Privacy Framework certification and the Standard Contractual Clauses in its controller terms.

3. Merchant-Controlled Integrations

The following systems are run by, or for, our Customers. The Customer starts the data flows between them and the Service, as the data controller. We don't list them as sub-processors because we don't engage them; the Customer does.

PlatformRoleOperator
Shopify, Inc.E-commerce platform: the hosted store whose orders the Customer may sync to the ServiceShopify, Inc. (Canada/US)
WooCommerce (Automattic, Inc.)E-commerce plugin for WordPress, typically self-hosted by the CustomerCustomer-hosted; plugin author Automattic, Inc. (US)
Magento (Adobe Commerce)E-commerce platform, typically self-hosted by the Customer or hosted on its behalfCustomer-hosted; software by Adobe Inc. (US)
PrestaShop, S.A.E-commerce platform, typically self-hosted by the CustomerCustomer-hosted; software by PrestaShop, S.A. (France, EEA)

When the Customer connects one of these platforms, the Service exchanges data with it under the Customer's authorisation, for example to read product data and receive orders. The Customer is the controller of the data held in that platform.

5. Notifications of Changes

  • Pircel gives as much notice as it receives of an added or replaced sub-processor, and at least 30 days where its own agreements allow. It updates this page, as a new dated version, and emails every Customer's account contact.
  • A Customer may object on reasonable data protection grounds within the notice period, as clause 6 of the Data Processing Agreement sets out.
  • Every version of this page is kept unchanged at its own address.

6. Changelog

DateChange
17 November 2026Hosting moved from Salesforce, Inc. (Heroku) to Hetzner Online GmbH, on servers Pircel operates in Nuremberg, Germany. Redis Ltd. (Redis Cloud) removed: the cache and job queues now run on those servers. SolarWinds (Papertrail) replaced by Grafana Labs Inc. for service logs, held in the EU. Amazon Web Services also holds the servers' configuration secrets and encrypted backups of the cache and job queues. The first column now names the entity Pircel contracts with; the transfer safeguard column names the certified entity where it differs. Amazon Web Services is named as Amazon Web Services EMEA SARL (AWS Europe), the AWS entity Pircel contracts with.
26 October 2026Aligned with Schedule C of the Data Processing Agreement: the certified entity named for each sub-processor; Sentry's row covers the dashboard; SolarWinds (Papertrail) and Google Workspace added; Vercel, PostHog, Redis and Mistral rows corrected; Google LLC (Google Maps Platform) moved to the independent controllers; MongoDB, Inc. (Atlas Charts) removed; FedEx and UPS described as Schedule C does; notice of changes follows the Data Processing Agreement's clause 6.
14 January 2025Initial publication of this page.

7. Contact

Questions about this page, our sub-processors, or any data processing described here: Pircel P.C., 32 Voukourestiou Street, 106 71 Athens, Greece; privacy@pircel.com.