---
title: "Postcode Data Disclaimer"
product: "Delivery Zone"
version: "1.4"
last_updated: "2026-08-31"
effective_date: "2026-08-31"
status: "current"
---
Postcode Data Disclaimer — Delivery Zone
Version: 1.4
Last updated: 2026-08-31
Effective date: 2026-08-31
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. Validating the postcode against current, authoritative Finnish postcode reference information.
2. For zones that use exact postcode rules, evaluating the postcode identifier directly against your configured rules — no coordinate is required for this step.
3. For zones that use radius (distance-based) rules, resolving a representative location for the postcode and calculating straight-line geographic distance from your configured base location.
4. Returning a canDeliver boolean result and, if applicable, an indicative delivery price based on your configured rules.
---
2. Postcode Reference Data and Coordinate Sources
Delivery Zone combines authoritative Finnish postcode reference information with customer-configured
delivery rules to provide postcode-based delivery checks. We do not sell, publish, sublicense,
or redistribute the underlying reference data.
2.1 Postcode Validity
Whether a Finnish postcode currently exists, and its type, is determined against authoritative
Finnish postcode reference information. This validity check does not depend on whether a
coordinate is available for that postcode — see Section 3.1 below.
2.2 Radius Coordinates
For delivery zones that use radius (distance-based) rules, Delivery Zone resolves a representative
location for the destination postcode and for your configured base location, then calculates the
straight-line geographic distance between them.
Where Delivery Zone's own versioned geospatial dataset has processed a postcode to a sufficient
confidence level, that native representative coordinate is used. Where it has not, a licensed
third-party coordinate source may temporarily be used as a fallback, where permitted. Known
unreliable fallback records are excluded and never used as a substitute. Where no coordinate
meeting our production standards is available from either source, the radius rule cannot be
evaluated from coordinates for that postcode (see Section 3.1).
The exact vendor and licence details for the fallback coordinate source are documented internally
and are not disclosed on this public page. For attribution of the open geospatial reference sources
used to build Delivery Zone's own dataset, see our Data Sources & Attribution
page.
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. Posti does not endorse, certify, or
license Delivery Zone.
A postcode can be valid even when no radius coordinate is available for it. Postcode validity and
radius-coordinate availability are determined independently — a data gap affecting one does not
imply a data gap in the other.
3.2 Coordinate Approximation
A postcode represents an area rather than a single address point, so any representative
coordinate — whether from Delivery Zone's own dataset or a fallback source — is a postcode-level
approximation. It does not identify an exact customer location or an exact delivery address.
This means:
- Distance-based delivery rules use straight-line geographic distance from a representative
location for the postcode, which may differ from the distance to the actual delivery address.
- Distance figures are not driving, road, or route distances.
- Areas near the edge of a delivery zone boundary may return inconsistent results depending on how the zone boundary is defined.
3.3 Data Source Limitations
Postcode and coordinate reference data may be incomplete, outdated, or approximate, and may be
affected by limitations of the underlying data sources described in Section 2 above.
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. Reference data
updates do not silently rewrite your delivery-zone configuration; you remain in control of your
own zone rules.
3.6 Rural and Sparse Areas
Coverage and coordinate accuracy may be lower in rural, island, and sparsely populated areas
of Finland.
---
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.
---
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 also 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, or (for a radius zone) no coordinate meeting our production standards was available to evaluate the rule.
- 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
Postcode and coordinate reference data underlying this service, including licensed fallback
coordinate data, is 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.
---