Mobility Charter · our mission and vision
We connect the systems that move people, once, and keep them open to everyone who builds on them.
So that the people who take the journey and the people who make it happen decide better.
Digitalisation is not just about technology. It's about managing change.
It's a process, not a purchase: understanding how mobility is actually run, changing the way it works step by step, with the people who run it, and learning from every step. It starts with the systems a city or region already has.
Easy to adopt
Start from the systems you already have. Authorities act on policy now; operators manage, operate and analyse their data.
Efficient at any scale
Small cities and regions get the same insight as large ones.
Open by design
Sharing data with developers and partners is simple, so new solutions arrive and compete on quality.
Principles
Connected once
Each system connects once, in its own format; the data reaches everyone entitled to it.
Citizens, not customers
The beneficiary is the person traveling. No tracking beyond what the service needs.
One shared picture
Travelers, operators, authorities and builders see the same mobility, on the same live data.
The holder decides
Set by set: open, on terms or not distributed. The service is paid, not the data.
Same rules for all, us included
Open standards, public terms, entry on public criteria.
Free to leave
Published formats; clients keep using their data after the contract, and can give it to anyone.
AI, with people in charge
AI plans resources and estimates the impact of disruptions. Every decision that touches the network stays with a person, and is logged. First step: Replan, 2027.
Service, whenever possible
Version 1.2 · draft · 25 October 2026
The Mobility Charter
Open mobility, in practice. What we ask of a mobility solution, software, equipment or service, before we list it on tranzy.dev or recommend it to a city or an operator. tranzy.ai builds its own products by the same rules.
The five requirements
01It connects
A documented API for everything it processes and exposes, versioned, with notice. Ownership and rights of use set in the contract, as the law provides.
How we check: The documentation and a test integration.
02It can be understood
Everything it passes on is in a public specification. Where the law asks for a standard, the standard.
How we check: Validators or schema tests.
03Data rights are clear
The contract says who may do what with operational, derived and distributed data. The client keeps control.
How we check: The clauses and a test export.
04It answers for what depends on it
A committed service level, repair times and a continuity plan; parts and replacement for equipment.
How we check: The service level document.
05It declares what the law asks
Security, personal data, accessibility, AI: declared, with the client's obligations it closes.
How we check: The declaration and evidence.
Requirements 1, 2, 3 and 5 apply to every solution. Requirement 4 applies to solutions others build on.
The data: the holder decides each set
OpenAn open licence: use, re-use, redistribute.On termsApproved users, published terms, the same for everyone.
Not distributedStays between the holder and its provider.
Not openPersonal, sensitive, security data: never.On tranzy.dev the service is paid, not the data: distribution, guarantees and derived products. The same conditions for every user at the same level, tranzy.ai's own solutions included.
Five clauses for tender documents
Copy them as they are, without citing the source. Legal requirements (security, personal data, accessibility) come from the law itself.
Clause 1 · Interfaces and rights
The solution offered shall provide documented programming interfaces for all the data it processes and exposes, with a versioning policy and a declared notice period before any version is withdrawn. The contract shall set, in accordance with the applicable law, the ownership of the data and of the integration documentation, the right of the contracting authority to use the interfaces, and its right to access, extract and reuse the data through them, including after the contract ends. Where the law does not allow ownership to be transferred, the contract shall grant the rights of use needed for these purposes. The integration documentation shall be made available to the contracting authority.
Clause 2 · Public specifications
All data exposed to third parties shall be supplied in a documented, public specification, with schema, examples and version history. Standards required by applicable law or by the contracting authority's obligations shall be met and validated with the reference tools.
Clause 3 · Data rights
The contract shall distinguish operational data, derived data and distributed sets, and set the rights attached to each category. The contracting authority shall have the right to use operational and derived data for its own purposes, including after the contract ends, to export them in public specifications and to make them available through other channels. The contract shall also set the rights of the supplier and of the distributor to process, standardise and distribute the data, under the regime set by the contracting authority.
Clause 4 · Service levels
For interfaces that other solutions rely on, the tenderer shall provide a service level with committed availability during transport operating hours, response and repair times by level of criticality, periodic reporting and a continuity plan at termination. For equipment, the tenderer shall provide maintenance, spare parts and replacement for the duration of the contract.
Clause 5 · Legal compliance
The tenderer shall submit a declaration of compliance with the applicable legal obligations and a mapping between the solution's functions and the contracting authority's obligations on publishing travel data, open data, monitoring the public service contract, data protection and accessibility. For components using artificial intelligence, the tenderer shall describe the human oversight mechanism and the decision log.
Built for European rules
ITS Directive and MMTIS · travel data at the national access point, on the holder's behalfDirective 2010/40/EU, amended by 2023/2661 · Regulation (EU) 2017/1926
Open Data Directive · open sets under open licences, the same conditions for everyoneDirective (EU) 2019/1024 · in Romania, Law 179/2022- Data Act · operators take the data of their own equipment to whoever they chooseRegulation (EU) 2023/2854
- Data Governance Act · the holder sets the regime of each set; we distribute on public termsRegulation (EU) 2022/868
GDPR · no personal data in open sets; processing only on the holder's instructionsRegulation (EU) 2016/679- AI Act · AI on the network stays under human oversight, with a log of decisionsRegulation (EU) 2024/1689
No tracking: no location history, no profiles. What we count, we count in aggregate.
The Charter is reviewed periodically; changes are published with their history and apply to listed solutions after a transition period. Text published by tranzy.ai under Creative Commons BY-ND 4.0; the tender clauses may be reused without restriction. The Charter is not a certification and does not replace legal advice.