Map sources and attribution
Product-specific disclosures
These pages describe the audited Studio product, not every feature present in experimental code. Google sign-in and cloud-draft synchronization are implemented. Paddle checkout is currently restricted to Sandbox/Test Mode. Optional providers run only when configured and requested. Operator identity, the working support mailbox, production retention settings and supplier permissions still require confirmation before paid launch.
Read this before publishing a map video
This guide distinguishes open geographic data, proprietary map/imagery services and the public endpoints used to obtain them. MapLibre is rendering software, not a licence to every map displayed through it. Keep the credits already drawn into exported frames; do not crop, cover or remove them. Also retain any required description/end-credit links and dataset-specific notices. Automatic credits are a starting point, not a certification that every upstream requirement has been met. The audit identified operator-side permissions and attribution gaps that must be resolved before unrestricted commercial export is offered.
OpenFreeMap, OpenStreetMap and OpenMapTiles
The default light, dark, street and fiord maps, and supported building data, use OpenFreeMap. Its service permission does not replace the underlying data licences. Retain OpenStreetMap and OpenMapTiles attribution; link to the OSM copyright page in a digital video description. For a video principally showing maps, keep readable on-screen attribution and provide accompanying/end credits as applicable. ODbL obligations for a shared derivative database are distinct from rights in the finished video; we do not require every video to be open-sourced merely because it contains OSM data.
MapTiler styles and satellite imagery — permission review
MapTiler-backed styles require a configured key and an appropriate contract, not merely a technically working key. Its standard terms include limited internet-video use for channels up to 100,000 subscribers and on-screen MapTiler attribution while maps appear; broader use can require written permission. Free-plan use is not a general commercial-production licence. We must confirm how its video allowance, export restrictions and source-specific imagery credits apply to this SaaS. We do not currently certify unlimited commercial distribution for these styles.
Terrain tiles: Mapzen/Tilezen and AWS
The Studio terrain effect uses the public Terrarium elevation dataset hosted on AWS. Another configured export path can request MapTiler elevation resources. The public terrain dataset combines sources with different notices; it is not uniformly unrestricted simply because download access is public. Retain the applicable source notices listed in Tilezen's attribution document. Current abbreviated source labels need review against that list, including any required dataset names, copyright wording and funding notices. MapTiler elevation remains subject to MapTiler terms.
Bundled geoBoundaries and ABS boundaries
Legacy or imported examples may contain bundled, simplified Australian boundary files attributed to geoBoundaries and the Australian Bureau of Statistics, with source years recorded in the project assets. For those identified CC BY 4.0 materials, retain source credit, the licence link and a statement that the geometry was simplified or modified; do not imply endorsement. Do not assume every geoBoundaries product or every ABS asset has the same licence, especially logos or separately credited third-party content.
LocationIQ searches and returned data
LocationIQ receives place-search queries from our server and may return coordinates and boundaries used in projects. The operator must comply with the actual plan, request limits and caching rules; storing response data and caching request/response pairs are not the same rule. Users should preserve the attribution attached to selected results. Underlying results may use OSM and other sources, so not every response should be labelled ODbL without checking provenance. We must verify our plan's LocationIQ attribution requirements.
Overpass and OpenRailRouting
Railway workflows can query OSM stations and relations through Overpass and request track geometry from OpenRailRouting. Preserve the supplied OSM/source credits. A track route is not a timetable or a promise that a passenger train runs along it. Public-server capacity, fair-use limits and availability are the operator's responsibility; an open-data licence does not provide an unlimited commercial API or a service-level guarantee.
Google-derived routes — unresolved integration restriction
Google Routes is conditionally mounted when configured, and its geometry can enter the current project-storage and MapLibre-rendering pipeline. Google's applicable terms restrict non-Google-map use and caching. We have not established an approved basis for unrestricted persistent storage and export through this pipeline. This is an operator integration issue, not an obligation that can be transferred to users by a disclaimer. Do not treat this page or a subscription as permission to redistribute Google route data or publish it on arbitrary basemaps.
Other optional routing and legacy sources
HERE and Geoapify are optional providers in the live Studio routing code path when their credentials are configured. Their data is not all covered by an OSM licence. The following source-specific conditions must be reviewed before enabling unrestricted retention or commercial export; a working API response is not proof of permission.
HERE routes and transit — storage review
HERE results can be returned through the configured road/transit provider chain. Its standard terms restrict retention of relevant results outside the platform, generally to 30 days with additional Japan-specific rules and contract exceptions. Our inspected project store has no provider-specific expiry mechanism. The operator must reconcile this before promising permanent project-resource storage or export reuse. Retain HERE and applicable supplier notices; do not relabel HERE content as open OSM data.
Geoapify routing
Geoapify can provide road and approximate rail fallback geometry. Its terms permit certain storage and reuse, but require OSM attribution and, on the Free plan, Geoapify attribution, plus any API-specific source notices. The actual plan and output use still matter. We do not infer an unlimited video-redistribution right from a general caching permission.
Local SeaRoute / MARNET network
Ship routes use local searoute-ts calculations, so this step does not itself send your coordinates to a SeaRoute API. The package software licence and the bundled Eurostat SeaRoute/MARNET network licence are different: the latter is identified as EUPL-1.2. Preserve its notices and assess source-availability and distribution obligations for the actual integration. Do not assume either that all material is MIT or that every exported video automatically takes the network's licence. These routes are not maritime navigation advice.
Legacy GISCO / EuroGeographics EU example
The older EU-history demonstration and its Countries 2024 boundary asset are publicly reachable, although not a primary Studio creation flow. The dataset has non-commercial conditions and prescribed source credits; commercial licensing must be checked with EuroGeographics. A noindex tag is not access control or a licence. Do not treat availability of the demo file as permission to use it in a commercial video.
Icons, imported content and publication checks
Transport graphics and other assets may have separate licences and author credits, shown in Studio's Sources & credits information. Uploading an image or importing a project does not prove that its copyright, privacy or publicity permissions exist. Before publication, review the actual style, route provenance and embedded credits, keep required notices legible, and obtain extra permission for uses outside the relevant licence. Do not use the product as a bulk extraction or resale channel for underlying provider materials where that is not permitted.
What the operator must resolve
The operator must verify supplier accounts and commercial permissions; enforce request and storage limits; ensure rendering/export carries complete notices; and remove or correct incompatible integrations. This audit flags Google Routes compatibility, HERE retention, MapTiler SaaS/video scope, public GISCO demo assets, SeaRoute network obligations and condensed attribution text. These page changes do not silently disable providers or fix those engineering issues, and are not a complete compliance certification.