Privacy Policy

This Privacy Policy explains how personal data is processed in connection with the Parcel Selector plugin and the hosted services operated at parcelselector.com. It also lists every external service the plugin can contact. It complements the Terms of Service.

1. Who is responsible for your data

The Parcel Selector plugin is installed and run by the online store that uses it (the "Merchant"). For personal data of the store's customers — names, addresses, order details — the Merchant is the data controller. parcelselector.com (the "Operator") provides the hosted Map Service and Label Service and acts as a data processor on the Merchant's behalf when those services handle order-related data.

For the Operator's own website and direct business contacts (for example the support form), the Operator is the data controller. Contact: [email protected].

2. Data processed locally inside WordPress

The plugin's core function — letting a customer choose a pickup point at checkout — runs entirely inside the Merchant's WordPress installation. The selected pickup point (name, identifier, address, city, postcode, country) is saved in the WooCommerce order, alongside the order itself. This data does not leave the WordPress site unless the Merchant uses the optional Label Service described below.

3. External services contacted by the plugin

Depending on configuration, the plugin can connect to the following external services. For each one, this is the data sent and the moment it happens.

3.1 parcelselector.com — pickup point map data

When the ANUNAKI map engine is active and a customer opens the locker map at checkout, the plugin requests live pickup-point data. Data sent: a country code only (e.g. "PL"). No personal or order data is sent. The Classic map engine uses bundled offline data and makes no connection.

3.2 parcelselector.com — admin and support services

From the WordPress admin area only: a version/licence check, and the in-plugin support contact form. Data sent: for the support form, the name, e-mail and message that the administrator enters.

3.3 parcelselector.com — label generation service

When a store administrator opens an order and uses the "Generate Label" flow, the label-generation interface is loaded from the Operator's servers inside an embedded frame. Data sent: order identifier, selected carrier, pickup-point identifier, and the recipient and sender name and address. Data received: a tracking number and a link to the label document.

3.4 api.parcelselector.com — label payment Oracle

From the WordPress admin area, during the label-generation flow, to register the label-payment request and report its status. Data sent: order identifier, currency, amount, dispatch context (sender and recipient names and addresses, pickup-point identifiers) and an HMAC signature. Blockchain confirmation of the payment is performed server-side by the Operator.

3.5 OpenStreetMap — map tiles and geocoding

The interactive map background is rendered from OpenStreetMap tiles, and address geocoding in the admin pickup-point search uses OpenStreetMap Nominatim. Because tiles and geocoding requests are made directly by the browser, OpenStreetMap receives the visitor's IP address and the map viewport or search text. This is standard for any externally loaded map.

3.6 CoinGecko — exchange rate

From the WordPress admin area, when an administrator opens the label payment screen, the plugin fetches the current SOL/PLN exchange rate. No personal or order data is sent — it is a single request for a public price feed.

3.7 FlagCDN — country flag images (fallback only)

Country flag icons are bundled with the plugin and served locally. FlagCDN is only a runtime fallback used if a local flag image cannot be served; on a default install no FlagCDN request is made. A flag request contains only a country code in the URL — no personal data.

3.8 Web fonts

All web fonts used by the plugin are bundled and served locally. No requests are made to Google Fonts or any other external font service, so no visitor data is sent to third-party font providers.

4. Payment data

Label fees are paid in cryptocurrency (Solana). The data involved in a payment consists of public blockchain wallet addresses, the amount, and transaction identifiers. These are recorded on the public Solana blockchain by design and are not private personal data. The Operator does not collect payment card data and does not store banking details.

5. Consent gate

No order-related data is sent to the Label Service until the store administrator explicitly accepts the data transfer in the consent control shown on each order. Until that acceptance, the label endpoints transmit nothing. Every request that is sent is HMAC-SHA256 signed and rate-limited.

6. Legal bases for processing (GDPR)

• Order fulfilment and label generation — performance of a contract (Art. 6(1)(b) GDPR): the Operator processes order data on the Merchant's instruction to produce the shipping label the Merchant requested.
• Map data feed — legitimate interest (Art. 6(1)(f)) in providing the service the Merchant installed; no personal data is involved.
• Support form — steps taken at the administrator's request and the Operator's legitimate interest in providing support (Art. 6(1)(b) and (f)).

7. Data retention

• Pickup-point selection in an order — retained by the Merchant as part of the WooCommerce order, under the Merchant's own retention policy.
• Label sessions on the Operator's side — kept up to 24 hours for an unpaid session and up to 7 days for a completed one.
• Generated label PDF files — retained up to 7 days, then removed.
• Map data requests — not logged together with personal data.

8. Your rights

Data subjects have the right to access, rectify and erase their personal data, to restrict or object to processing, and to data portability. Because the Merchant is the controller of customer order data, requests concerning that data should be addressed to the Merchant; the Operator will assist the Merchant as processor. Requests concerning data the Operator holds as controller can be sent to [email protected]. You also have the right to lodge a complaint with a data-protection supervisory authority.

The plugin integrates with the WordPress Privacy tools: Tools → Export Personal Data returns the pickup-point name, identifier and address held per order, and Tools → Erase Personal Data removes the pickup-point meta, label tracking number, label session identifier and locally mirrored PDF files.

9. International transfers

The plugin's external services are operated within the European Economic Area or by providers offering equivalent safeguards. OpenStreetMap is operated by the OpenStreetMap Foundation; map tiles and geocoding requests reach its infrastructure as described in section 3.5.

10. Cookies

The Parcel Selector plugin sets no cookies.

11. Security

Connections to the hosted services use HTTPS encryption. Requests to the Label Service are authenticated with HMAC-SHA256 signatures and are rate-limited. Label session data on the Operator's side expires automatically within the retention windows stated in section 7.

12. Third-party privacy policies

• OpenStreetMap — wiki.osmfoundation.org/wiki/Privacy_Policy
• CoinGecko — coingecko.com/en/privacy
• FlagCDN — a public flag-image CDN at flagcdn.com; no cookies, no tracking, no personal data collected.

13. Changes to this Policy

The Operator may update this Privacy Policy. The current version is always published at this address with its effective date.

14. Contact

Questions about this Privacy Policy: [email protected].

Operator: parcelselector.com
Effective date: 17 May 2026