Privacy Policy
PingTab Privacy Policy
Last updated: September 15, 2026
This policy explains what information PingTab collects, how we use it, when we share it, and the choices available to the people who use it: operators and their teams, drivers, trip guests, and anyone who opens a public tracking link or a PingTab booking site.
1. Who This Policy Covers
This policy applies to personal information processed through PingTab in all of the places it runs: the PingTab web dashboard, the whitelabel booking sites we host for organizations, public tracking pages, and the two mobile apps, PingTab Operations and PingTab Driver. It covers information about account holders, organization administrators, invited team members, drivers, trip guests, and people who open a tracking link or a booking site.
Organizations that use PingTab decide what information they enter into the service and are responsible for it. PingTab processes that information on their behalf.
2. The Two Apps, And What Each One Can Reach
The apps are separate products with separate permissions. What one of them can do on a phone says nothing about the other.
PingTab Operations is for the business owner and their team: leads, bookings, drivers, guest chat, and the booking site. It asks for permission to show notifications, and, only if you switch on call capture, to read phone state. It has no location permission of any kind: the driver positions it draws on a map come from our servers, and the app never reads the location of the phone it is installed on. It has no contacts permission and never opens your address book. It has no call log permission and cannot see your phone’s call history. It has no camera permission. The only image it can send is a business logo you pick yourself from your own gallery.
PingTab Driver is for drivers, who are given access by an operator rather than signing up themselves. It does collect precise device location, and section 3 explains when and why. Drivers should read that section rather than this one.
The dashboard and the booking sites run in a browser and collect no device permissions beyond what a normal website uses. Cookies and advertising pixels are covered in section 8.
3. Information We Collect
Account and organization information. Names, email addresses, passwords, a mobile number where you give one, roles, organization membership, active organization preference, language, timezone, and authentication and session data. In regions where we verify a phone number before starting a free trial, we send a one-time code to that number and keep the verified number so the same number cannot be used to claim repeated trials across different organizations. Where we do not verify a phone number, no code is sent and none is kept for that purpose.
Team invitation information. Administrators may enter an invitee name, email address, role, invitation status, and expiry details.
Trip, lead, and guest information. Records may include trip and lead names, pickup and drop-off times, pickup and drop-off locations and addresses, guest names, email addresses, mobile numbers, itinerary details, fares, status, and business identity branding. Addresses are searched through our own servers rather than from the handset, so a guest address typed into the Operations app is not sent from that phone to a mapping provider.
Notes and other content you write. Notes on a lead or a booking, itinerary descriptions, and any message you send us through in-app feedback.
Messages and chat. Guest chat conversations between an organization and a guest, including message text, timestamps, and read and delivery status, together with the message text prepared for a share link. Where an organization has connected WhatsApp, messages exchanged there are processed the same way.
Driver and vehicle information. Driver names, mobile numbers, email addresses, vehicle numbers, driver tokens, driver PINs where configured, and driver trip status.
Driver location information. When a driver starts a trip in the PingTab Driver app and grants the required device permissions, PingTab receives precise latitude and longitude updates with their timestamps. Location updates are used for active trip tracking and are rejected unless the trip is in progress and the driver token matches the trip. The Operations app collects no location.
Images. Organizations may upload a business logo and pictures for their booking site, with the related file metadata. Uploading is optional and is always something you choose to do.
Captured call information. Only if an operator switches on call capture in the Operations app. Section 4 sets out in full what this does and does not do.
Device identifiers and push tokens. Each app installation generates a random identifier of its own, which ties your signed-in session to that installation: when the app renews its session, the renewal is refused if it arrives from a different installation. We also store the push registration token that Google or Apple issues for the installation. The app registers that token when you sign in, whether or not you have allowed notifications, because the permission controls whether an alert is drawn on your screen rather than whether the device is reachable. Turning notifications off, in the app or in your device settings, stops the alerts. Neither identifier is an advertising identifier. We do not collect the Android advertising ID, and we do not use any device identifier for advertising.
Usage, diagnostic, and technical information. Server logs, IP address, browser or device details, request timestamps, and security events needed to run and secure the service. The PingTab Driver app additionally reports crashes and errors to our error-monitoring provider and reports aggregate usage counts that carry no trip or driver identifiers. The PingTab Operations app contains no crash-reporting and no analytics software at all.
4. Calls Captured By The Operations App
The Operations app can tell an operator that an unrecognized number called, so that a missed enquiry becomes a lead instead of being lost. This is the most sensitive thing the app does, so here is exactly how it works.
- It is off until you turn it on. The switch lives in the app’s settings and applies to that one phone. Whoever holds the phone that rings decides.
- It does not read your call log. The app holds no call log permission. It learns of a call from Android’s call screening service while the phone is actually ringing, so it knows only about calls that arrive after you switch the feature on. It cannot see calls from before that, and it cannot see calls made from the phone.
- It does not read your contacts. The app holds no contacts permission. The number comes from the incoming call itself.
- It does not record, listen to, or transcribe anything. What it knows about a call is the number, the time it arrived, whether it was answered, and how long it lasted.
- What stays on the phone. The list of captured calls, the numbers you have marked as not a lead, and the switch itself are kept on that device and are never sent to us.
- What reaches our servers. The number on its own, and nothing else about the call. We answer whether it belongs to someone already in your organization’s records, so a call from an existing customer or one of your drivers is not offered to you as a new enquiry. We ask this for any number the app captures. When the app is open it first checks the leads and chats it has already loaded and does not ask about a number it recognizes there, but a call that ends while the app is in the background is looked up without that shortcut. We do not keep the number from that question.
- It clears itself. A captured call you do not act on is dropped from the phone within a day. Nothing you act on is kept as a call record either: it becomes an ordinary lead, with the information you chose to save on it.
Switching the feature off in settings stops the capture, and uninstalling the app removes everything it held.
5. How We Use Information
- Authenticate users, maintain accounts, and apply role-based access controls.
- Provide lead capture, quoting, booking, dispatch, driver assignment, trip tracking, guest chat, booking sites, and organization management features.
- Display trip status, location, driver, vehicle, route, and branding information to authorized users and to holders of a valid link.
- Deliver notifications you have asked for: new leads, guest messages, booking changes, trip reminders, invitations, password resets, and operational updates.
- Provide support, troubleshoot errors, monitor reliability, prevent abuse, and protect PingTab and its users.
- Analyze aggregate usage and improve the service.
- Comply with legal obligations and enforce our agreements.
We do not use any of this information for advertising, and we do not build advertising profiles from trip, guest, chat, location, or call information.
6. Public Tracking And Driver Links
Tracking links and driver links are token-protected links. Anyone with an active public tracking link may be able to view limited trip information such as trip name, status, pickup time, pickup locations, drop-off location, assigned driver name, driver mobile number, vehicle number, organization or business identity name, logo, and current driver location when available.
Anyone with an active driver link may be able to view driver-facing trip information and submit driver updates for that trip. Organizations should share links only with intended recipients and regenerate or deactivate links if they may have been exposed.
7. How We Share Information
- With organization users according to their roles and permissions.
- With drivers and public tracking link viewers when an organization shares a valid link.
- With service providers that help us host, store, and secure the service, deliver email, SMS, push, and WhatsApp messages, provide maps, monitor reliability, and support the product. They act on our instructions and may not use the information for their own purposes.
- When required by law, legal process, safety, security, fraud prevention, or to protect rights and property.
- In connection with a merger, financing, acquisition, reorganization, or sale of assets, subject to appropriate safeguards.
We do not sell personal information. We do not share trip, guest, chat, driver location, or captured-call information with advertising services.
8. Cookies And Marketing Pixels
PingTab uses cookies and similar technologies that are necessary to sign you in, keep your session secure, and remember basic preferences.
On our public marketing pages (the home page, product and pricing pages, FAQs, contact page, and account signup pages) we also load the Meta advertising pixel. It records that a browser viewed one of those pages, along with the page address and standard device and network information, and reports it to Meta. We use this to measure our advertising and to reach similar audiences. You can limit it through your Meta ad preferences or your browser’s cookie controls. Where an organization has switched on analytics for its own booking site, that site may also load the analytics or advertising tags that organization configured.
We do not load advertising or marketing trackers on the signed-in dashboard, on public tracking links, on driver links, on guest feedback pages, or on this page and our Terms of Use. The PingTab Operations and PingTab Driver apps contain no advertising software and show no ads.
9. Organization Responsibilities
Organizations decide what lead, trip, guest, driver, and vehicle data to enter into PingTab, who receives tracking or driver links, and whether to switch on call capture on their own phones. Organizations are responsible for providing required notices, obtaining required consents, and using PingTab in compliance with applicable employment, transport, privacy, and communication laws.
10. Retention
We retain information for as long as needed to provide PingTab, maintain business and security records, comply with legal obligations, resolve disputes, and enforce agreements. Lead and trip records stay available to the organization after a trip is completed, because that is the organization’s own operating history. Active tracking and driver tokens can be regenerated or deactivated by the organization at any time.
Some information has a shorter life by design. Captured calls that are not acted on are dropped from the phone within a day. Driver location points are kept for active tracking and route history and are not used for anything else.
When an account is deleted, we complete the deletion within 30 days. Encrypted backups may still contain the data for up to 90 days before they age out, and backups are never used to restore a deleted account. We keep the records that tax and accounting law requires us to keep, such as invoices and payment records.
11. Security
We use technical and organizational measures designed to protect information, including authenticated access, role-based controls, tokenized tracking links, session renewal tied to the installation that signed in, encrypted transport for all app and dashboard traffic, and restricted operational access. No system is perfectly secure, and organizations should protect account credentials and shared links.
12. Your Choices And Rights
Account holders can update account and organization information in the product. Notifications can be turned off in the app or in your device settings. Call capture can be switched off in the Operations app at any time. Drivers control device location permissions through their operating system, though disabling location may prevent live trip tracking from working. Guests can stop viewing a public tracking page at any time.
If you want to access, correct, export, or delete personal information, contact your organization administrator or write to us at support@pingtab.com. Some requests have to be handled by the organization that controls the trip or account data, and we will tell you when that is the case.
To close your account entirely, see Delete your PingTab account, which sets out how to make the request, what is deleted, and what we are required to keep.
13. International Processing
PingTab may process and store information in countries different from where users, drivers, or guests are located. When information is transferred internationally, we use safeguards appropriate to the service and applicable requirements.
14. Children
PingTab is intended for business and operational transportation use. It is not directed to children, and users should not create accounts for children.
15. Changes To This Policy
We may update this policy as the service, legal requirements, or our practices change. The updated version will be posted on this page with a new last updated date.
16. Contact
Questions about this policy, or about the information PingTab holds, can be sent to support@pingtab.com. If you received a PingTab tracking link or driver link from a business, that business is the right first point of contact for the trip information on it.