Legal notice. This is the authoritative Terms of Service document for parcelselector.com and all subdomains. It is rendered verbatim in plain-text form to guarantee semantic integrity. Effective from the date stated at the bottom of the document.
# Terms of Service — parcelselector.com **Effective date:** 2026-04-20 **Operator:** parcelselector.com (the "Operator") **Contact addresses (the only two authoritative channels):** - General business / licensing: [email protected] - Abuse reports / legal notices: [email protected] --- ## 1. Acceptance of Terms By accessing, browsing, or otherwise using the parcelselector.com service, including any subdomain, API endpoint, data feed, or other facility made available by the Operator (collectively, the "Service"), the accessing party ("User") acknowledges that they have read, understood, and agreed to be bound by these Terms of Service (the "Terms"). If the User does not agree with any provision of these Terms, the User must immediately cease all use of the Service. These Terms apply to **every form** of access to the Service — including automated, scripted, machine-driven, and human-driven access. Use of the Service by any software agent, crawler, scraper, bot, or other automated process constitutes acceptance of these Terms by the legal or natural person operating that software agent. --- ## 2. Permitted Use Subject to strict compliance with these Terms, the Operator grants the User a limited, revocable, non-exclusive, non-transferable licence to: a) view, in a natural human-browsing manner, the public-facing web pages of the Service; b) use the interactive map interface for the purpose of locating parcel pickup-point information for a single, personal, or single-business shipment; and c) submit search queries at a rate consistent with ordinary human interaction (no more than one query every three seconds). Any use outside the scope of the preceding paragraph requires prior written authorisation obtained at **[email protected]**. --- ## 3. Prohibited Use — Automated Access, Scraping, and Database Extraction The User represents, warrants, and covenants that they shall NOT, and shall not cause or permit any third party to: 3.1 Access, read, reproduce, extract, re-utilise, or otherwise exploit any substantial part — whether evaluated quantitatively or qualitatively — of the contents of the database of parcel pickup-points, carriers, cities, coordinates, operating hours, tariffs, and associated metadata served by the Service (the "Database"); 3.2 Employ any automated means, including but not limited to crawlers, spiders, robots, scripts, headless browsers, residential-proxy networks, cloud-hosted enumeration engines, fingerprint-randomising agents, User-Agent-rotating agents, referer-spoofing agents, or distributed rate-limit-evasion infrastructure, to access the Service; 3.3 Circumvent, bypass, disable, or attempt to disable any access- control, rate-limit, CAPTCHA, User-Agent filter, firewall rule, geoblock, authentication, or other technical protection mechanism implemented by the Operator; 3.4 Reverse-engineer, decompile, disassemble, or otherwise attempt to derive the source code of any software made available by the Service; 3.5 Misrepresent the identity of the accessing software or natural person — including, without limitation, by falsifying the HTTP User-Agent header, HTTP Referer header, HTTP X-Forwarded-For header, TLS fingerprint, or any other protocol-level identifier; 3.6 Download, replicate, mirror, store, transfer, or otherwise make available to any third party any portion of the Database, other than: (i) isolated results of an authentic single-shipment search executed by a natural person; or (ii) under an express written licence obtained from the Operator; 3.7 Re-sell, re-distribute, re-publish, or commercially exploit any data obtained from the Service, in any form or medium, without the prior express written licence of the Operator; 3.8 Use any data obtained from the Service to train, fine-tune, benchmark, or otherwise contribute to the development of any artificial-intelligence, machine-learning, or large-language- model system; 3.9 Submit requests at a rate that, in the Operator's reasonable judgement, imposes or is capable of imposing a disproportionate load on the Service's infrastructure, regardless of whether such rate actually results in service disruption. --- ## 4. Intellectual Property, Database Rights, and Applicable Criminal Law 4.1 **Database rights (Poland / EU).** The Database is a protected database within the meaning of Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and of the Polish Act of 27 July 2001 on the protection of databases (Dz.U. 2001 nr 128 poz. 1402, as amended). The Operator holds all sui generis database rights in and to the Database for the territory of the European Economic Area. 4.2 **Database rights (United Kingdom).** The Database is additionally a "database" within the meaning of sections 3 and 3A of the UK Copyright, Designs and Patents Act 1988 (as amended) and a "database in which database right subsists" within the meaning of the UK Copyright and Rights in Databases Regulations 1997 (SI 1997/3032, as amended post-Brexit). The Operator is the "maker" and "owner" of the database right for the purposes of those Regulations and asserts those rights to the fullest extent in the territory of the United Kingdom and its overseas territories. 4.3 **Trademarks and copyright.** All trademarks, logos, service marks, designs, photographs, text, source code, and graphical elements of the Service are the exclusive property of the Operator or of its licensors, and are protected by: a) the Polish Copyright Act of 4 February 1994 (Dz.U. 1994 nr 24 poz. 83, as amended); b) the UK Copyright, Designs and Patents Act 1988 (as amended); c) the EU Trade Mark Regulation 2017/1001 and the UK Trade Marks Act 1994; d) the WIPO Copyright Treaty and the Berne Convention for the Protection of Literary and Artistic Works. 4.4 **Criminal-law exposure.** Any act described in Clause 3 may, in addition to civil liability, constitute a criminal offence under (non-exhaustive): a) Polish Criminal Code (Kodeks karny) art. 267 (unauthorised access / interception), art. 267a (illegal access to telecommunications), art. 268 (destruction or alteration of computer data), and art. 268a (interference with the operation of a computer system); b) United Kingdom — Computer Misuse Act 1990, sections 1 (unauthorised access), 2 (unauthorised access with intent to commit or facilitate further offences), 3 (unauthorised acts with intent to impair operation of a computer), and 3A (making, supplying or obtaining articles for use in such offences); c) United Kingdom — Fraud Act 2006, sections 2 (fraud by false representation, e.g. spoofed User-Agent / Referer) and 11 (obtaining services dishonestly); d) United Kingdom — Data Protection Act 2018, section 170 (unlawful obtaining etc. of personal data); e) the United States Computer Fraud and Abuse Act 18 U.S.C. § 1030 (exceeding authorised access); f) corresponding provisions of the national criminal codes of any other country from which the unauthorised access is technically initiated or operationally orchestrated. 4.5 Nothing in these Terms shall be construed as granting, by implication or otherwise, any licence or right to use any trademark, logo, or other intellectual-property element without the prior express written consent of the rightholder. --- ## 5. Liquidated Damages — Unauthorised Automated Access 5.1 **Acknowledgement of damage.** The Parties acknowledge and agree that an accurate quantification of the damage caused to the Operator by any violation of Clause 3 is impractical at the time of entering into these Terms, inter alia because: (i) the Database represents a long-term accumulation of commercial effort; (ii) the value of each record extracted cannot be reliably disaggregated from the whole; (iii) the Operator's infrastructure is shared with third- party merchants (online shops, couriers, fulfilment partners, and payment processors) whose business continuity depends on the availability of the Service — every second of service degradation caused by unauthorised traffic translates directly into: (a) abandoned shopping carts, (b) failed pickup-point selection at check-out, (c) delayed or cancelled shipments, (d) loss of payment-gateway conversions, and (e) reputational damage measurable in reduced returning-customer cohorts; (iv) the Operator is contractually liable to those merchants for uptime and, in the ordinary course of business, indemnifies them for demonstrable losses arising from infrastructure unavailability — making the Operator's damage a cascading multiplier of merchant losses; (v) attacks on the Service's infrastructure, including — but not limited to — automated scraping, enumeration, and denial-of-service traffic, **directly prevent the Operator's customers and business partners from completing orders**, and thereby generate **quantifiable financial losses** for which the Operator is entitled to full indemnification from the infringing party. The Parties therefore agree on the following **liquidated damages** as a reasonable pre-estimate of loss, which shall not exclude the Operator's right to pursue recovery of actual merchant-cascade damages under Clause 5.4. 5.1a **Attack-induced merchant losses.** In addition to all other remedies under these Terms, the User shall indemnify and hold the Operator harmless against any and all claims made by, or losses, costs, fines, or settlements incurred in respect of, the Operator's merchants, partners, payment-service providers, carriers, or customers, to the extent that such claims or losses are attributable — in whole or in part — to the User's violation of Clause 3. The Operator shall be entitled to pass through, dollar-for-dollar, any amount it pays or becomes liable to pay to such third parties as a direct or indirect consequence of the infringement, and to add such amounts to the debit note issued pursuant to Clause 5.5. 5.2 **Session Lump Sum — USD 100,000 per infringement session.** 5.2.1 DEFINITION. A "Session" means a single continuous period of unauthorised access ending when no further unauthorised request is received from the same User, from the same /16 IP block, or from the same infrastructure-provider customer account, for a period of at least sixty (60) consecutive minutes. Any period of activity shorter than sixty minutes, or any calendar day on which at least one unauthorised request occurs, counts as one Session. Multiple discrete Sessions on the same calendar day, separated by at least the 60-min gap, count cumulatively. 5.2.2 AMOUNT. For each Session, the User shall pay the Operator a lump sum of **USD 100,000 (one hundred thousand United States dollars)**. Payment may be made, at the Operator's election, in US dollars, in Pound Sterling at the exchange rate published by the Bank of England on the first day of the infringement, or in Polish zloty at the exchange rate published by the National Bank of Poland on the first day of the infringement (the "Session Lump Sum"). 5.2.3 LEGAL BASIS. The Session Lump Sum is agreed as liquidated damages (kara umowna) under: - Article 483 of the Polish Civil Code (Kodeks cywilny) — reasonable pre-estimate of loss, non-excluded by Article 484 where the infringement is deliberate and planned (which spoofed UAs and rotating IPs conclusively establish); - the law of England and Wales on liquidated damages as restated by the UK Supreme Court in *Cavendish Square Holding BV v Makdessi* [2015] UKSC 67 — enforceable where the amount is a genuine protection of a legitimate commercial interest and not extravagant relative to that interest. 5.3 **Per-Request Surcharge — USD 2,500 per unauthorised HTTP request.** 5.3.1 DEFINITION. An "Unauthorised HTTP Request" means any single HTTP request (GET / POST / HEAD / PUT / DELETE / OPTIONS / PATCH / any method) transmitted to any URL hosted on any parcelselector.com subdomain or associated IP address of the Operator, by a User acting in violation of any provision of Clause 3 of these Terms. Each request is counted separately even where multiple requests are transmitted within a single TCP connection, HTTP/2 stream, or HTTP/3 QUIC flow; each retry of a request that previously returned a 5xx status code also counts separately. 5.3.2 AMOUNT. In addition to the Session Lump Sum payable under Clause 5.2, the User shall pay the Operator **USD 2,500 (two thousand five hundred United States dollars)** per Unauthorised HTTP Request as a liquidated surcharge (the "Per-Request Surcharge"), payable in US dollars, Pound Sterling, or Polish zloty in accordance with Clause 5.2.2. 5.3.3 PROOF OF COUNT. The count of Unauthorised HTTP Requests shall be established by the Operator from: - nginx access logs (`/var/log/nginx/access.log`) retained on the Operator's infrastructure; - aggregated forensic datasets (CSV export) derived therefrom; - structured JSON event logs emitted by the Operator's `security/attack_detector.py` real-time module. Such logs shall be admissible as a business record under Article 308 of the Polish Code of Civil Procedure and under section 9 of the UK Civil Evidence Act 1995. 5.3.4 LEGAL BASIS. Per-request liquidated damages for automated access are expressly contemplated by the sui generis database right regime: see Recital 42 and Article 7 of Directive 96/9/EC, Article 7 of the Polish Act of 27.07.2001, and Regulation 16 of the UK Copyright and Rights in Databases Regulations 1997 (each recognising "repeated and systematic extraction" as an independent act of infringement). 5.3a **Commercial Reuse Surcharge — USD 1,000,000 per dataset.** 5.3a.1 If the User, or any third party to whom the User has transmitted scraped data, uses, publishes, re-sells, re-distributes, licenses, incorporates into any other database, trains any artificial-intelligence or machine-learning model with, benchmarks against, or otherwise exploits commercially any part — however small — of the data obtained in violation of Clause 3 (the "Scraped Dataset"), the User shall pay the Operator a flat sum of **USD 1,000,000 (one million United States dollars)** per calendar year (or part thereof) during which any such commercial exploitation takes place (the "Commercial Reuse Surcharge"). 5.3a.2 This surcharge is PAYABLE IRRESPECTIVE OF, AND IN ADDITION TO, the Session Lump Sum (Clause 5.2), the Per-Request Surcharge (Clause 5.3), and any Additional Damages under Clause 5.4. It reflects the destruction of the Operator's exclusive right to license the Database under Directive 96/9/EC Article 7(1) and the corresponding UK / Polish provisions, and the Operator's lost opportunity to negotiate a licence under ordinary commercial conditions. 5.3a.3 The Commercial Reuse Surcharge is triggered even if the original Scraped Dataset has been anonymised, normalised, merged with other datasets, or transformed, as long as it would not have existed in the User's possession but for the act of infringement. 5.3b (Reserved — see Clauses 5.3 and 5.3a above for the full definition of the Per-Request Surcharge and Commercial Reuse Surcharge respectively.) 5.4 **Additional damages.** The Session Lump Sum and Per-Request Surcharge shall not exclude the Operator's right to pursue compensation for additional damages on general principles, including but not limited to: a) statutory damages for database-right infringement under Art. 11–12 of the Polish Act of 27.07.2001 on the protection of databases; b) statutory damages under Regulations 12–19 of the UK Copyright and Rights in Databases Regulations 1997; c) statutory damages for copyright infringement under Art. 79 of the Polish Copyright Act of 04.02.1994 and sections 96–99 of the UK Copyright, Designs and Patents Act 1988 (additional damages for flagrancy, account of profits, delivery-up orders); d) compensation and administrative fines for processing of personal data in violation of the EU General Data Protection Regulation (Regulation (EU) 2016/679) under Articles 82 and 83 — and where the affected data subjects are in the United Kingdom, under the UK General Data Protection Regulation as incorporated by the Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019, read with the Data Protection Act 2018; e) compensation under Art. 18 of the Polish Unfair Competition Act of 16.04.1993, and under the common-law tort of conversion / interference with goods and the equitable remedy of breach of confidence under the law of England and Wales; f) an account of profits, injunction, and delivery-up of any scraped data or derivative database, as available under UK Chancery equitable jurisdiction; g) exemplary / aggravated / additional damages where the infringement is shown to be flagrant and committed with knowledge that it was unauthorised (a condition routinely satisfied by the deliberate spoofing of User-Agent and Referer headers and by the rotation of thousands of IP addresses to evade rate-limiting); h) all reasonable costs of forensic investigation, legal representation (including counsel of the Operator's choice in any jurisdiction the matter is prosecuted in), firewall deployment, third-party CDN / DDoS-mitigation fees, and service-restoration costs arising from the infringement; i) compensation for reputational harm, loss of goodwill, and SEO / search-ranking degradation evidenced by sustained upstream 5xx responses served to Google's and Bing's crawlers during the incident. 5.5 **Pre-action procedure — amicable settlement, then litigation, then criminal prosecution with 10× claim multiplier.** 5.5.1 AMICABLE STAGE (pro-forma invoice). Promptly after detection of an infringement, the Operator shall send to the User (or, where the User's identity cannot yet be ascertained, to the User's infrastructure provider as joint-and-severally liable party under Clause 5.6) a **pro-forma invoice** ("faktura pro-forma") itemising in full: (a) the Session Lump Sum under Clause 5.2 (USD 100,000 × number of Sessions); (b) the Per-Request Surcharge under Clause 5.3 (USD 2,500 × number of Unauthorised HTTP Requests); (c) the Commercial Reuse Surcharge under Clause 5.3a (USD 1,000,000 × number of years of commercial reuse, if applicable); (d) a preliminary estimate of Additional Damages under Clause 5.4, marked "estimated — subject to final quantification". The pro-forma invoice shall specify a payment term of **fourteen (14) calendar days** from the date of dispatch. Settlement at this stage is offered without admission of liability and without prejudice to the Operator's right to audit the final amount. 5.5.2 FORMAL LETTER BEFORE ACTION. Where the pro-forma invoice under Clause 5.5.1 is not paid in full within the 14-day term, the Operator shall serve a formal letter before action ("wezwanie do zapłaty" / "letter of claim"), compliant with: - Articles 455 and 476 of the Polish Civil Code (putting the debtor in default); - the Civil Procedure Rules of England and Wales, Practice Direction — Pre-Action Conduct and Protocols (and any specific Pre-Action Protocol that the court may direct to be followed); - the corresponding pre-action rules of the jurisdiction in which proceedings are ultimately commenced. The letter before action shall set a further payment term of fourteen (14) calendar days. 5.5.3 LITIGATION STAGE. Where payment is not received within the further 14-day period, the Operator may — without any additional notice and without any further obligation to negotiate or mediate — commence civil proceedings in any one or more of the fora enumerated in Clause 7, claiming the full amounts itemised in the pro-forma invoice, plus statutory interest from the date of each infringement, plus all costs of collection (including counsel's fees on an indemnity basis where the forum permits). 5.5.4 CRIMINAL PROSECUTION AND TENFOLD INCREASED CLAIM. Where payment is not received within the further 14-day period of Clause 5.5.2, the Operator shall additionally be entitled, in its sole discretion and in parallel to or instead of civil proceedings under Clause 5.5.3, to: (a) FILE A CRIMINAL COMPLAINT ("zawiadomienie o podejrzeniu popełnienia przestępstwa") with the Polish prosecutor under Article 304 § 1 of the Code of Criminal Procedure in respect of offences under Polish Criminal Code articles 267, 267a, 268, 268a, 287, or any other applicable provision; (b) LODGE A REPORT with the UK National Crime Agency / Action Fraud in respect of offences under the UK Computer Misuse Act 1990 sections 1–3A and Fraud Act 2006 sections 2 and 11; (c) NOTIFY the competent data-protection supervisory authority (the President of the Personal Data Protection Office in Poland and/or the UK Information Commissioner) of the breach, seeking administrative fines under GDPR Articles 82–83 or UK-GDPR equivalents; (d) COMMENCE a civil action in which the AMOUNTS CLAIMED under Clauses 5.2, 5.3, 5.3a, 5.4 and 5.6 are each **INCREASED TO TENFOLD (×10) the sums originally quoted in the pro-forma invoice**, as an agreed supplementary liquidated contribution toward the Operator's substantially increased cost of enforcement (including counsel, experts, court filing fees, cross-border service-of-process costs, forensic-accounting work, and the disruption occasioned by criminal-process cooperation). The User ACKNOWLEDGES AND AGREES that the tenfold escalation in Clause 5.5.4(d) reflects the legitimate commercial interest of the Operator in incentivising the User to pay the original pro-forma amount without forcing the Operator into the expensive, time-consuming and uncertain sphere of contentious cross-border litigation. In light of the magnitudes involved (infringements typically running to tens of thousands of requests) this escalation is proportionate within the meaning of Cavendish Square Holding BV v Makdessi [2015] UKSC 67 and is not excluded by Article 484 § 2 of the Polish Civil Code because the infringement is conclusively established to be deliberate (see Clause 4.4 above on the criminal-law exposure of User-Agent / Referer spoofing). 5.5.5 NO OBLIGATION TO MEDIATE. The Operator shall not be required to engage in mediation or any other form of alternative dispute resolution prior to the commencement of proceedings under Clauses 5.5.3 or 5.5.4. The 14-day pro-forma-invoice window in Clause 5.5.1 is deemed sufficient amicable opportunity. 5.6 **Joint and several liability of infrastructure providers.** Where the unauthorised access is conducted from infrastructure rented or otherwise provided by a cloud-hosting or Internet service provider whose Acceptable Use Policy prohibits such access (including, without limitation, Alibaba Cloud Limited, Alibaba Cloud (UK) Limited, Alibaba Cloud (Singapore) Private Limited, Alibaba Cloud Computing (Beijing) Co. Ltd., Amazon Web Services Inc., Amazon Web Services EMEA SARL, Microsoft Corporation, Microsoft Ireland Operations Limited, Google LLC, Google Ireland Limited, and any successor in interest or affiliated entity of the foregoing), the infrastructure provider shall be jointly and severally liable with the User for the sums due under this Clause 5, on the basis of: a) Article 441 § 1 of the Polish Civil Code (co-liability of tortfeasors); b) Article 82 of Regulation (EU) 2016/679 (joint liability of controllers and processors); c) sections 3 and 3A of the UK Computer Misuse Act 1990 (making or supplying articles for use in commission of offences); d) the doctrine of joint tortfeasance at common law (UK and other common-law jurisdictions); e) the doctrine of accessory liability in equity where the infrastructure provider is shown to have been recklessly indifferent to customer abuse. The Operator shall be entitled to pursue the infrastructure provider directly for the full amount and the infrastructure provider shall bear the burden of seeking contribution or indemnity from its customer. --- ## 6. Monitoring, Logging, and Evidence 6.1 The Operator continuously monitors all access to the Service and records each request — including source IP address, timestamp, HTTP method, Uniform Resource Identifier, response status code, response size, HTTP User-Agent header, and HTTP Referer header — for the purpose of operating the Service securely, investigating abuse, and documenting any infringement of these Terms. The lawful basis for this processing is the Operator's legitimate interest within the meaning of Article 6(1)(f) of Regulation (EU) 2016/679 (GDPR). 6.2 Logs and derived forensic datasets (including, without limitation, per-request CSV export, aggregated IP-frequency tables, and timeline reconstructions) are retained for a period of up to twelve (12) months from the date of recording and may be extended for the duration of any proceedings in which they constitute evidence. 6.3 Such logs and datasets may be transmitted, in whole or in part, to: a) the User's hosting or Internet-service provider, pursuant to an abuse complaint; b) competent law-enforcement authorities, pursuant to a criminal-procedure request or to a voluntary notification under Art. 304 § 1 of the Polish Code of Criminal Procedure; c) the User's counsel and the Operator's counsel, for the purpose of civil proceedings; d) supervisory authorities under GDPR (the President of the Office for Personal Data Protection) in support of a complaint under Art. 77 GDPR. --- ## 7. Governing Law, Jurisdiction, and Parallel Proceedings 7.1 **Dual governing law.** These Terms shall be governed by and construed in accordance with: a) the laws of the Republic of Poland and the directly applicable Regulations and Directives of the European Union, for all matters concerning EU/EEA-sited access, EU-sited data subjects, and the Operator's Polish operational base; and b) the laws of England and Wales, for all matters concerning UK-sited access, UK-sited data subjects, and the corporate seat of any infrastructure provider registered in the United Kingdom (including, without limitation, Alibaba Cloud (UK) Limited, company no. 11081503, registered office 4th Floor, 30 Finsbury Circus, London EC2M 7EB). Both legal systems shall apply cumulatively; where a protection exists in one and not the other, the User shall be bound by the stricter. 7.2 **Cumulative (non-exclusive) jurisdiction.** The User acknowledges and agrees that the Operator may, at the Operator's sole election, commence and maintain parallel proceedings arising out of or in connection with these Terms in any one or more of the following fora: (a) **Republic of Poland** — the common court having competence over the Operator's registered seat, under Articles 17, 34 and 37¹ of the Polish Code of Civil Procedure; additionally — because the damaging act was committed against an infrastructure located in Poland — under Article 7(2) of Regulation (EU) No 1215/2012 of the European Parliament and of the Council (Brussels I bis Regulation) and Article 4 of Regulation (EC) No 864/2007 on the law applicable to non-contractual obligations (Rome II Regulation); (b) **United Kingdom** — the High Court of Justice of England and Wales (King's Bench Division or Chancery Division as appropriate), under: - the Civil Jurisdiction and Judgments Act 1982 (as amended, post-Brexit); - the Civil Procedure Rules Part 6.36 and Practice Direction 6B para. 3.1(9) (tort — damage sustained within the jurisdiction where a UK-registered infrastructure provider is joined as defendant); - the Hague Convention on Choice of Court Agreements of 30 June 2005 (where applicable); (c) **The User's country of domicile or effective operations, OR the country in which the User's infrastructure provider has its registered seat, OR the country from which the unauthorised traffic is shown to have originated** — in each case under the procedural law of that forum and any applicable bilateral / multilateral enforcement treaty (notably the Hague Convention, the New York Convention on the Recognition and Enforcement of Foreign Arbitral Awards 1958 where damages are liquidated by arbitration, and the Lugano Convention 2007 where applicable). Where the same cause of action is pursued in more than one forum, the Operator will treat recoveries as cumulative up to the full amount of its loss; any amount recovered in one forum shall be credited against the claim in another, preventing double recovery, but shall not extinguish the claim until the full loss is satisfied. 7.3 **Waiver of forum non conveniens.** The User expressly and irrevocably waives any objection based on forum non conveniens, lis pendens in a less protective forum, or any analogous doctrine, in each of the fora enumerated in Clause 7.2. 7.4 **Sequence of enforcement.** a) Before commencing contentious proceedings, the Operator shall attempt amicable resolution strictly in accordance with Clause 5.5 — first a pro-forma invoice with a 14-day payment term, then a letter before action with a further 14-day term. b) Should no payment be received within the aggregate 28 calendar days, the Operator shall be entitled — without any further notice — to commence proceedings for the full amount due, plus interest at the statutory maximum rate, plus costs, in any or all of the jurisdictions enumerated in Clause 7.2. c) The Operator shall additionally be entitled to apply for urgent interim or injunctive relief (including worldwide freezing orders under Section 37 of the UK Senior Courts Act 1981 and security for costs / zabezpieczenie roszczeń under the Polish Code of Civil Procedure art. 730 et seq.) at any time, without exhausting the pre-action procedure, where immediate protective measures are required to preserve evidence or prevent dissipation of assets. 7.5 **Service of process.** Service of any document required to be served on the User may be effected, at the Operator's election: a) on the User's domicile address disclosed by the applicable whois / RIPE / APNIC / ARIN records for the source IP address(es) of the infringing traffic; b) on the registered office of the User's infrastructure provider, where the User has concealed its identity by operating through anonymising infrastructure; c) by the methods permitted in the procedural law of the forum in which proceedings are commenced (including, in appropriate cases, alternative service by email under UK CPR 6.15 or Polish k.p.c. art. 131¹). --- ## 8. Severability, Amendment, and Entire Agreement 8.1 If any provision of these Terms is held to be unenforceable by a court of competent jurisdiction, such provision shall be reformed to the minimum extent necessary to render it enforceable, and the remaining provisions shall continue in full force and effect. 8.2 The Operator reserves the right to amend these Terms at any time. The amended Terms shall become effective upon publication at https://parcelselector.com/terms and shall apply to all subsequent access to the Service. 8.3 These Terms, together with the Operator's Privacy Policy and the site-specific robots.txt file, constitute the entire agreement between the Operator and the User with respect to the subject matter hereof and supersede all prior understandings. --- **Document ID:** TOS-PS-20260420 **Canonical URL:** https://parcelselector.com/terms **Last revised:** 2026-04-20