Data & licensing.

The layered data model

A Symt deployment composes three clearly separated classes of data. They are stored separately, versioned separately, and attributed separately:

1. Base geodata. Curated open and licensed geographic datasets — road networks, administrative boundaries, terrain, and places — each used under its own documented license, with attribution metadata carried through the platform.
2. Symt proprietary layers. Data we create and license to you: curated POI enrichment, address normalization models, speed and traffic profiles, cartographic styles, and quality corrections. These are Symt’s intellectual property, licensed under your subscription or sovereign agreement.
3. Customer data. Data you load into your deployment — national address registries, private road networks, your POIs, your GPS probes. It remains exclusively yours. Symt claims no rights over it, and in self-hosted deployments we never see it.

License compliance, handled properly

Each base dataset carries obligations — attribution, share-alike scopes, or commercial terms — and we engineered the platform so you can meet them without thinking about it:

• Attribution — Symt map styles and SDKs render the required data credits by default, and the API ships attribution metadata with every tile response.
• License separation — datasets with share-alike or restricted terms are kept in separate stores, so your proprietary and customer layers never inherit obligations they shouldn’t.
• Produced works — routes, geocodes, matrices, and rendered images you generate are results you may store, cache, and build products on.

Provenance for tenders and audits

Government and enterprise procurement needs to answer one question with confidence: “Where did every byte of this map come from, and are we allowed to use it this way?” Symt answers it with engineering, not assurances:

• Every data build produces a signed provenance manifest: source datasets, versions, licenses, extraction dates, and checksums for every layer.
• Air-gapped deployments receive updates as signed offline bundles carrying the same manifests, so isolated networks stay auditable.
• The admin console exposes a per-layer license report exportable for compliance reviews and tender annexes.

What this means in practice

• You can put Symt in a public tender and attach the license report as evidence.
• You can store and reuse every API result you pay to compute.
• You can load national or private data without open-licensing it.
• Your basemap improves continuously — with every layer’s origin on record.

Questions

Licensing questions, tender support, or a copy of a current provenance manifest: legal@symt.ai.

Last updated: July 2026.