Privacy Policy

1.The two kinds of people in this policy

TLDP is used by businesses to move parcels to their customers, so personal information reaches us in two different ways — and our responsibilities differ in each case.

• Account holders. The merchants, couriers, fleet operators, riders and developers who register and sign in. We decide how their information is handled, and this policy is our direct promise to them.
• Delivery recipients. The people a parcel is addressed to. Their name, address, phone number and delivery instructions reach us because a merchant asked us to arrange a delivery. We handle that information on the merchant's instructions, to carry out the delivery they asked for. The merchant's own privacy policy governs why they collected it in the first place.

If you received a parcel and want your information corrected or removed, start with the business you bought from — they hold the relationship. We help them act on it, and we will point you in the right direction if you write to us instead.

2.What we collect

Only what the platform needs to do its job.

• Account details — name, email address, phone number, the business you belong to and your role in it. This is what signs you in and decides what you can see.
• Business details — company name, registration and verification documents where a courier or fleet is onboarded, and payout details so earnings can reach the right account.
• Delivery details — pickup and destination addresses, recipient name and phone number, parcel weight and contents description, and any delivery instructions.
• Location — while a rider is carrying a parcel, their device shares location so the sender and the recipient can follow it. This is tied to an active delivery; it is not continuous tracking of a person, and a rider controls it from their own app.
• Proof of delivery — a photograph, a one-time code or a signature captured at the door, kept against the shipment so a dispute has an answer.
• Technical records — API requests, sign-in events, device and browser information, and IP address. These keep the platform secure and let us investigate what happened when something breaks.

We do not ask for, and do not want, card numbers or bank credentials. Payments are handled by regulated payment providers; we receive a reference and an outcome, not the instrument.

3.Why we use it

• To run deliveries — quote a price, dispatch a courier or rider, route a parcel, and prove it arrived.
• To keep accounts secure — authenticate you, spot suspicious access, and keep one business's data out of another's reach.
• To settle money — calculate what each courier and rider earned and pay it out.
• To support you — answer questions and investigate a delivery that went wrong.
• To improve the service — understand where the platform is slow or failing, in aggregate.
• To meet legal obligations — tax, accounting, and responding to a lawful request.

We do not sell personal information, and we do not share it with advertisers.

4.Who we share it with

Only the parties who need it to complete the job you asked for.

• The courier or rider carrying the parcel — they receive the delivery address, the recipient's name and phone number, and the instructions. They cannot see the merchant's other orders.
• The merchant who sent the parcel — they see the delivery's progress and its proof.
• Payment and payout providers — to take a payment and to move earnings to a bank or mobile money account.
• Our hosting, infrastructure and communications providers — who process information on our behalf, under contract, and may not use it for their own purposes.
• An operator you signed up through — where you reached TLDP through a partner running the platform under their own brand, that operator administers your account.
• Authorities — where the law requires it, and to protect people or property from harm.

5.How we protect it

• Information is encrypted in transit and at rest.
• Access is separated at the data layer — a business can only reach its own records, enforced by the platform rather than by each screen remembering to check.
• Every API key is stored as a one-way hash. If a key is lost it can be revoked, but never recovered.
• Administrative access is limited to the staff who need it, and requires a second factor.
• A sandbox mode lets developers build against isolated test data, so real deliveries and real people are never used for development.

No system is perfectly secure. If a breach affects your information we will tell you and the relevant regulator, without undue delay, and explain what happened and what to do about it.

6.How long we keep it

• Account information — while your account is open, and for a period afterwards to settle anything outstanding.
• Delivery and shipment records — kept as a business record, because they evidence what was carried, by whom, and what was paid.
• Proof of delivery — kept for the period in which a delivery can be disputed.
• Financial records — kept for as long as tax and accounting law requires.
• Technical logs — kept for a short operational window, then discarded.
• Sandbox data — deleted automatically on a rolling schedule; it is test data and not meant to persist.

7.Location, specifically

Live location is the most sensitive thing we handle, so it is worth being precise about it.

• It is shared by a rider's device only while they are carrying an active delivery.
• It is visible to the merchant who sent that parcel and, through the tracking page, to whoever holds the tracking number.
• A rider turns sharing off from their own app, and it stops when the delivery completes.
• We do not build a movement history of a rider outside their deliveries, and we do not sell location data.

8.Your rights

Depending on where you live, you may have the right to ask for a copy of your information, to correct it, to have it deleted, to restrict or object to how we use it, and to take it elsewhere in a portable form.

Where to ask. If you hold a TLDP account, write to privacy@tybritelabs.com and we will handle it directly. If you are a delivery recipient, ask the business you bought from — they decide what happens to the information they collected, and we act on their instruction.

Some information we must keep even after a deletion request — a completed delivery and its financial record are evidence of a transaction, and tax law sets how long they are held. We will tell you when that applies rather than quietly keeping it.

9.Where information is held

TLDP is run as a global platform and our infrastructure and support may be located in a different country from you. Where information moves across a border, it moves under contractual protections that hold our providers to the standard described in this policy, and it stays subject to the same limits on use.

10.Cookies and similar technologies

We use cookies and local browser storage to keep you signed in, to remember a preference such as which notifications you want, and to understand how the site is used in aggregate. The public tracking page works without an account and sets nothing beyond what it needs to display the page. You can clear or block these in your browser, though signing in will stop working if you block the ones that hold your session.

11.Children

TLDP is a platform for businesses and the people who work with them. It is not intended for children, and we do not knowingly collect information from anyone under 18. If you believe a child has given us information, write to privacy@tybritelabs.com and we will remove it.

12.Who we are, and how to reach us

TLDP is operated by TYBRITE TECHNOLOGIES LIMITED, trading as Tybrite Labs.

• Privacy questions and rights requests — privacy@tybritelabs.com
• Anything else — support@tybritelabs.com

If you are not satisfied with how we have handled a request, you may complain to the data protection authority where you live.

13.Changes to this policy

We update this policy when the product changes or the law does. The effective date at the top always tells you which version you are reading, and we will give account holders notice of a change that materially affects them rather than quietly republishing the page.