What you may and may not do with Tripkoz — falsified safety records, surveillance beyond transport safety, and tenant-boundary probing are the lines that matter most.
Do not use Tripkoz to manufacture safety evidence for checks that were never done, and do not use it to track a person for any purpose other than transport safety and operations. Both put real people at risk, and both end an account.
This Acceptable Use Policy ("AUP") governs use of the Tripkoz platform operated by Tripkoz Technologies. It expands clause 9 of the Terms & Conditions and forms part of them.
It applies to everyone who uses the Service — organisation administrators, drivers, guardians and independent drivers — and you are responsible for the conduct of every user on your account.
You must use the Service lawfully, and consistently with the transport, labour, motor vehicle, privacy and data-protection laws that apply to you.
You must not:
The safety features of Tripkoz only mean something if what goes into them is true. You must not:
A falsified safety record can put a child in an unroadworthy vehicle. We treat it as the most serious breach of this policy, and it will normally lead to immediate suspension.
Tripkoz collects location data so that transport can be operated and supervised safely. It must not become a general surveillance tool. You must not:
You must tell drivers, passengers and guardians that location data is collected, what it is used for, how long it is kept and who can see it, and you must obtain any consent the law requires — including verifiable parental consent for a child.
You must not:
Without our prior written consent, you must not:
Security research is welcome under the Responsible Disclosure Policy, which sets out what testing is permitted and how to report what you find. Testing under that policy is not a breach of this section.
You must only upload personal data you are entitled to process, and only what the Service is designed to hold.
Do not upload financial account details, health records, biometric data, caste or religion, or government identity numbers of passengers. The Service is not built to protect them and they are not needed to run transport.
Keep records accurate and current — an out-of-date guardian phone number or a stale pickup point is a safety problem, not an administrative one.
SOS and incident features exist so that a real emergency reaches the right people quickly. You must not raise a test SOS on a live account outside an agreed drill, or use an emergency feature to get attention for a non-emergency.
Remember that these alerts do not reach the police, ambulance or fire services. Your own escalation procedure, not Tripkoz, is what answers an emergency.
Where we believe this policy has been breached, our response is proportionate to what happened and to the risk involved. We may:
Except where there is an immediate risk or the law prevents it, we will tell you what we believe happened and give you a chance to respond before we suspend or terminate. Suspension or termination for breach is not refundable.
If you believe someone is misusing Tripkoz — falsified records, misuse of tracking, or an account that should have been closed — write to support@tripkoz.com. Security vulnerabilities should go to security@tripkoz.com under the Responsible Disclosure Policy instead.
We treat reports in confidence, and we do not disclose the reporter to the organisation reported except where the law requires it.
This document sits alongside the rest of our published terms. Together they form the agreement that governs your use of Tripkoz.
