DispHub / Legal documents
DispHub Terms of Use
Terms for evaluating the platform and cooperation between the software provider and a transport company.
Parties and purpose
DispHub is software for transport companies. These terms describe a business customer relationship; the provider’s legal name, registration details and contacts must be completed before they take effect.
The relevant transport service performs transport, delivery and interactions with passengers and drivers. It sets its own fares and rules and is responsible for required permits, personnel, taxes and service performance.
Request, demonstration and commencement
A demonstration request allows the parties to arrange a platform presentation. Submitting it does not create a paid subscription, guarantee an automatic trial account or require a purchase.
Before commercial launch, the parties agree the services, brand, configuration, operating area, acceptance process, payment and start date. Individually agreed terms prevail for the particular order; mandatory law remains applicable.
Access and acceptable use
The customer receives a right to use the agreed platform components within the agreement. It is responsible for its accounts, staff authorisation, information accuracy and access security.
Unlawful use, disruption, bypassing security and unauthorised access to others’ data are prohibited. APIs and external integrations are used within the agreed scope. Rights that cannot legally be restricted remain unaffected.
Platform fee
When a company creates and completes an order itself, it pays DispHub 1% of the full order value once. When the order is passed to another company and completed by that company, the company that passed it on and the company that completed it each pay DispHub 1% of the full value of that order. The fee is calculated from the full value of a completed order, not from the company’s commission or profit.
There is no subscription or separate per-driver fee. The billing period is a calendar month, and invoices are payable within 14 days. Support, maintenance and planned updates are included. Invoice currency, taxes and associated bank charges are specified in the agreed commercial documents.
Branding and additional work
One-time branding costs $500 for each of four applications: passenger Android, passenger iOS, driver Android and driver iOS. The complete package costs $2000. A branded administration panel is provided as a gift; the dispatcher interface is included.
Custom development, SEO, PPC management and social media advertising are agreed and paid separately. Scope, schedule, materials, acceptance and payment are recorded before additional work begins. App store and other provider timelines are not automatically DispHub delivery commitments.
Partner network and advertising
Participation in the partner network is voluntary: the service selects partners and the cooperation area and can disable participation. The services separately agree their revenue split. Reconciliation and intercompany settlement use the calendar month.
For an order passed to another company and completed by that company, the company that passed it on and the company that completed it each pay DispHub 1% of the full order value. This fee is calculated separately from the partners’ agreed shares. All in-app advertising revenue belongs to the transport company; DispHub’s share is 0%.
Payments and third-party services
Maps, acquiring, communications, app stores and other integrations may depend on a separate provider, country and agreement. Listing a service on the website does not guarantee availability for every business.
Passenger refunds, transport disputes, provider fees and payment acceptance responsibilities are governed by the relevant agreements. Planned fiscalisation does not imply an available integration or certification.
Materials, intellectual property and data
The customer’s brand, logos and materials remain its materials. The customer grants the rights needed for agreed branding and operation and confirms its right to provide those materials.
Payment for branding or access does not itself transfer source code or exclusive platform rights. Publishing an individual case study and using materials in it require agreement with the customer. Personal data roles and obligations for the operational platform are defined in a separate data processing agreement.
Support, changes and confidentiality
Support and planned updates are included in the platform fee. Specific support hours, response deadlines, guaranteed availability or service credits apply only when separately agreed in writing.
The parties must use non-public cooperation information only to perform their obligations, restrict access and observe lawful disclosure requirements. Material changes to agreed services or commercial terms are communicated through the agreed process.
Suspension and termination
Notice, termination of access, final billing and data return and deletion arrangements must be agreed before launch. Security violations, unlawful use or non-payment may justify restrictions within the agreement and applicable law.
Payment for completed work, possible refunds of unused amounts and export formats depend on actual services, agreed documents and the law. This draft does not impose automatic penalties or an unconditional no-refund rule.
Liability and disputes
Each party is responsible for its contractual obligations and breaches under applicable law. Liability limitations, courts or other dispute procedures must be agreed after the provider and registration country are identified.
This draft does not select a foreign jurisdiction, arbitration or a numerical liability cap. It does not restrict rights or liability that cannot legally be excluded.
Versions and electronic acknowledgements
Before paid use begins, the customer receives the final documents and agreed commercial parameters. Acceptance must identify the person, authority, time, language and document version.
Reviewing this draft on the demonstration website does not accept an effective contract. Final contacts, effective date and prevailing document language must be determined before launch.