Beta Delivery Zone is in private beta and not yet open to customers — public launch coming soon.
Legal

Postcode Data Disclaimer

Last updated: 2026-05-17 Effective: 2026-05-13

Postcode Data Disclaimer — Delivery Zone

Version: 1.2 Last updated: 2026-05-17 Effective date: 2026-05-13

Please read this disclaimer carefully. The accuracy of delivery checks provided by this service depends directly on the quality of postcode reference data and on the rules you have configured. Understanding these limitations is important for operating your delivery business correctly.

1. What Postcode Checks Do

The Delivery Zone service checks whether a destination postcode falls within one of your configured delivery zones. It does this by:

  1. Looking up the postcode in a reference database to identify its geographic coordinates and locality data.
  2. Evaluating those coordinates (or the postcode identifier directly) against your configured delivery zone rules (e.g., postcode lists, distance bands).
  3. Returning a canDeliver boolean result and, if applicable, an indicative delivery price based on your configured rules.

2. Postcode Reference Data

Delivery Zone uses licensed third-party Finnish postcode reference data and customer-configured delivery rules to provide postcode-based delivery checks. We do not sell, publish, sublicense, or redistribute the underlying postcode database.

2.1 Licensed Finnish Postcode Data

The service uses postcode reference data licensed from a third-party Finnish postcode data provider. This data is used exclusively for internal delivery-zone calculations. The exact vendor and licence details are documented internally and are not disclosed on this public page.

2.2 Customer-Uploaded Custom Datasets

Customers can upload their own postcode datasets via the admin panel. The accuracy of delivery checks based on custom-uploaded datasets is the customer's sole responsibility. We perform format validation only and do not validate the geographic or operational accuracy of uploaded data.

Customers are responsible for ensuring they have all necessary rights, permissions, and lawful bases to upload and use any custom postcode datasets or delivery-zone data they provide to the Service.

2.3 Postcodes and Personal Data

A postcode alone may not always identify a person, but it can become personal data when combined with other information held by the Customer, such as an order, account, address, or delivery instruction. Customers acting as data controllers for their end customers' personal data should refer to the Privacy Policy and Data Processing Addendum.

3. Known Limitations

3.1 We Are Not an Official Finnish Postcode Authority

Delivery Zone is not Posti Group Oyj (Finnish Post) and is not an official source of Finnish postcode information. Official, authoritative postcode data for Finland is maintained and published by Posti Group Oyj. If your use case requires officially certified, authoritative postcode data, you should obtain it directly from Posti.

3.2 Coordinate Approximation

Geographic coordinates associated with postcodes may be approximate centroid values. They may not reflect the precise geographic extents of a postcode, which are typically complex polygon shapes rather than a single point.

This means:

  • Distance-based delivery rules use distances to the centroid, which may differ from the distance to the actual delivery address.
  • Areas near the edge of a delivery zone boundary may return inconsistent results depending on how the zone boundary is defined.

3.3 Third-Party Data Limitations

Postcode data may be incomplete, outdated, or approximate, and may be affected by limitations of the underlying third-party data source.

3.4 New Postcodes

Newly introduced or recently modified Finnish postcodes may not appear in the reference dataset immediately. A negative result for a recently introduced postcode may reflect a data gap in the reference dataset rather than a zone configuration issue.

3.5 Retired and Reassigned Postcodes

Postcodes that have been retired, merged, or reassigned in the official Finnish postcode database may still exist in older reference data, or may have been removed before a customer updates their configuration. Neither scenario can be prevented by this service.

3.6 Rural and Sparse Areas

Coverage and coordinate accuracy may be lower in rural, island, and sparsely populated areas of Finland.

3.7 Customer-Uploaded Data

The accuracy of delivery checks based on custom postcode datasets is entirely the customer's responsibility. We perform format and schema validation only. We do not verify whether uploaded postcodes are valid, current, or correctly associated with geographic coordinates.

4. Customer Responsibilities

As a customer of this service, you are responsible for:

  • Configuring your delivery zones accurately based on your actual operational delivery capabilities.
  • Verifying edge cases manually — particularly for postcodes near zone boundaries, new postcodes, or rural areas where data quality may be lower.
  • Communicating your actual delivery limitations clearly to your end customers, including any known gaps or edge cases.
  • Keeping your delivery zone rules up to date as your operations change.
  • Accepting that postcode check results are advisory, not definitive. You must apply your own business judgement before making binding commitments to end customers.
  • Uploading accurate data if you choose to use custom postcode datasets, and ensuring you hold all necessary rights and lawful bases to do so.

5. No Guarantee of Delivery

A positive result (canDeliver: true) from the API means:

  • The postcode matches one of your configured delivery zones based on current reference data.
  • It does not guarantee that a physical delivery will be completed.
  • Actual delivery depends on your logistics capacity, scheduling, staffing, vehicle availability, and other operational factors entirely outside this service.

A negative result (canDeliver: false) from the API means:

  • The postcode does not match any active delivery zone in your current configuration.
  • It does not mean the address is permanently undeliverable.
  • It may reflect a misconfiguration, a data gap, or a postcode that simply has not been added to your zones. Review your zone configuration and this disclaimer if you believe the result is incorrect.

6. Prohibited Use of Postcode and API Response Data

The postcode reference data underlying this service is licensed from a third-party data provider. API responses derived from that data are subject to the use restrictions in our Terms of Service, API Terms of Use, and Acceptable Use Policy.

Customers must not:

  • Store, persist, copy, cache, scrape, harvest, bulk download, export, or otherwise retain Delivery Zone API responses for the purpose of creating, enriching, replacing, or reconstructing any postcode database, delivery-zone database, geographic dataset, distance table, address dataset, or similar derived dataset.
  • Use automated scripts, bots, batch jobs, systematic queries, enumeration techniques, or other methods to extract, map, infer, or reconstruct the coverage, postcode, distance, or delivery-zone data behind the Service.
  • Resell, sublicense, publish, disclose, share, redistribute, make available, or provide third-party access to Delivery Zone API responses, datasets, derived datasets, or validation outputs, whether directly or indirectly.
  • Use the Service or API responses to develop, train, improve, benchmark, or operate a competing product, data product, postcode validation service, delivery-zone validation service, logistics dataset, or similar commercial service.

Temporary in-memory processing necessary to complete a single user transaction or retry a failed request is allowed, provided it is not used for persistence, bulk collection, database enrichment, or dataset reconstruction.

API responses are provided for real-time postcode, delivery-zone, and delivery-availability validation within the Customer's own checkout, logistics, or operational workflow only.