TaxiPik and TaxiPik Driver Privacy Policy
Version 1.0 - Last updated October 11, 2026.
WildBunny Gaming LLC, operating as TaxiPik ("we," "us," or "our"), provides TaxiPik for Riders, TaxiPik Driver for Drivers, and the related TaxiPik website and supporting services (the "Service"). This Policy explains how we handle personal information through the Service. The initial release is offered in the United States. Another user's independent conduct and an external service's own practices are not governed by this Policy.
Operator address: 550 South Harbin Drive PMB 104, Stephenville, Texas 76401, United States. Privacy/legal contact: legal@taxipik.com. Support: support@taxipik.com.
1. Our Purpose and Limits
We use information to operate the Service: accounts, passenger-selected nearby-driver discovery, ride coordination, mapping and navigation, messages, journey records, notifications, support, and the security and reliability of those functions. TaxiPik provides software for independent Drivers and passengers, not automated matching, transportation services, or transportation-payment processing.
We do not sell your personal information, precise location, journey records, or messages. We do not distribute or repurpose them for unrelated advertising, data brokerage, unrelated profiling, traffic-data resale, or other purposes unrelated to direct operation of the Service. We do not use advertising SDKs or Google Analytics in the apps covered by this Policy.
We disclose information outside the company only as necessary to provide the function you use, such as displaying information to the intended Rider, Driver, or message recipient, using necessary operational providers, or complying with a binding court order or another legal obligation we cannot lawfully refuse. Necessary provider processing is not permission to send a provider information its task does not need, or to authorize unrelated exploitation of your information.
2. Information We Handle
We handle the following categories when you use the applicable feature. Not every category applies to every user, and some settings remain only on the device.
| Category | Examples | Operational purpose |
|---|---|---|
| Account and identity information | Name, email address, account role, phone number where supplied, chosen profile photo, account identifiers | Create and manage accounts, sign-in, recovery, identification within the Service, and support |
| Authentication information | Password submitted for authentication, stored password hash, access/refresh credentials, verification or recovery codes | Protect and verify accounts and sessions |
| Driver information | Vehicle make, model, year, color, registration plate, chosen vehicle image, rates, accepted payment methods, service area, online status | Show Driver information and availability and coordinate passenger-selected requests |
| Ride information | Pickup/destination, addresses, coordinates, participants, stages and times, distance, route, fare calculations, amounts reported as paid, ratings | Coordinate and record journeys and handle related support requests |
| Communications and reports | Direct messages, ride/lost-and-found conversations, timestamps, read status, participant identities, blocking/reporting information, support submissions | Deliver communications and investigate reported problems or misuse |
| Preferences and saved information | Saved places, favorite/blocked users, notification, accessibility, appearance, map and navigation settings | Provide the settings and saved features you choose |
| Uploaded content | Profile and vehicle photos and information you deliberately submit to support | Provide the selected feature and handle your request |
| Technical and diagnostic information | IP addresses, request times and paths, account/session or installation identifiers, app/device details, operational errors and crash information | Deliver requests and notifications, protect sessions, and diagnose failures |
We receive information directly from you, from your device and app use, and from the other participant in a ride, message, rating, or report. We do not collect payment-card details to process fares or tips. A fare or payment amount recorded in the app is information about a transaction arranged outside TaxiPik, not a financial transfer through us.
Do not put payment-card details, banking credentials, government identification documents, health records, or other unnecessary sensitive information in messages or support submissions.
3. Location: Rider and Driver Use Different Conditions
Location can include precise latitude/longitude, fix time, and, where supplied, accuracy, altitude, heading, speed, and related ride/account information. Coordinates and time-linked routes can reveal sensitive places or identify a person even after a name is removed.
TaxiPik for Riders
While you use the app, location supports the map, nearby-driver discovery, pickup selection, and routing. Foreground map use does not mean we continuously retain a history of your movements outside a ride.
With the required permissions, background location can operate during the applicable pending or active ride process, including when another app is visible or the screen is off. It is not used for continuous background Rider monitoring when there is no pending or active ride. Fresh pickup-location updates are shared with the assigned Driver during the accepted/arrived pickup stages. The Rider's journey is recorded during an in-progress ride. Every nearby Driver does not receive a continuous view of every Rider's whereabouts.
TaxiPik Driver
While you are online, the Driver app sends location updates to keep availability and nearby-driver search current and support ride coordination. This can continue in the background or with the screen off when permissions and operating-system conditions allow. Online reporting does not necessarily mean you are carrying a Rider. Normal availability reporting updates your current server-side position; it is not a permanent archive of every online location report.
Ride features use location to show progress and record journey information. Standalone navigation also uses your location to operate the map and navigation; using personal navigation while offline does not by itself authorize uploading a separate online-location history.
For a specific operational support investigation, we may temporarily retain received location reports and receipt times to check reporting gaps. This remains restricted to operating and troubleshooting the Service, not traffic-data resale, advertising, or unrelated research. Such temporary diagnostic copies expire after three days unless a binding legal obligation requires retention.
Your choices and practical limits
You can manage location permissions in device settings. Drivers can use the online/offline controls when available; unfinished ride stages may limit those controls. Withdrawing permission can prevent location-dependent features from working. Stopping live reporting does not erase previously recorded journeys.
GPS reception, network outages, and operating-system restrictions can cause gaps. We do not provide emergency monitoring or guarantee continuous tracking. Required background-location disclosures and permission requests are presented separately; this Policy is not a substitute for them or for any consent required by law.
4. Device Storage, Notifications, and App Crash Diagnostics
The apps store settings, cached screens/messages, session credentials, and location points awaiting normal upload on the device. Rider uses the device's secure-storage facility for session tokens. Driver stores session tokens in app-local storage subject to the operating system's app access protections. Device or operating-system backups are separate from company backups and depend on your device/provider settings.
Both apps use Firebase Cloud Messaging (FCM). Push delivery involves an app/device token, Firebase installation information, recipient identifiers, and operational event data. We also use app-installation identifiers and notification-registration information to associate delivery with the correct account.
Push notification data can include ride, conversation, message and user identifiers, sender names, event types, and notification-registration and delivery information. We do not include message bodies, precise coordinates, or route geometry in those push notification payloads. The server's notification display text is generic. The app may show operational alerts or message information after receiving an event; notification visibility depends on app/device settings. Push delivery is not end-to-end encrypted messaging.
Rider uses Firebase Crashlytics for technical app crash diagnostics. This handles installation/session identifiers, app crash times and traces, and app, operating-system and device details. Our custom crash reports identify a general failure category; we do not add account identifiers, messages, or ride/location history to them. Crashlytics reporting applies only to the Rider app.
Providers can also handle limited technical service information, such as IP addresses, app identifiers and service usage, to deliver, maintain and protect the service they provide. This does not authorize unrelated advertising or repurposing of TaxiPik user information. Provider handling is also described in their notices linked below.
5. Permissions and Device Features
Location permissions support the uses in Section 3. Notification, sound, vibration, and display-over-other-apps access support operational messages and ride/arrival alerts. Rider camera access supports optional QR-code scanning. Profile/vehicle images are uploaded when you deliberately select them.
Audio playback for announcements is not microphone recording. We do not record microphone audio, copy your contacts, or collect unrelated device files. Any additional collection must have an actual operational purpose, appropriate disclosure, and any required permission or consent.
You can manage permissions and notification settings through the app or device where available. Certain functions cannot work without their required access.
6. Who Receives Information
Other users
Riders and Drivers receive the profile, vehicle, availability, relevant location, ride, rating, and message information needed for the particular discovery, request, journey, or conversation. Visibility depends on role, ride stage, membership and relevant settings. Photos delivered through media URLs are not suitable storage for confidential documents.
Genuine direct-message conversations retain participant name information. A recipient can copy, photograph, or retain information already delivered to them. Hiding a conversation from your list does not erase the recipient's copy or all stored messages; a later message can bring the conversation back. Account erasure and investigation holds are different operations, described below.
Necessary operational providers
We use the following services for their necessary functions, not to sell or distribute information for unrelated purposes:
| Provider/service | Information involved | Why it is involved |
|---|---|---|
| US-based hosting provider (Kansas City, Missouri area) | Information stored or transmitted through our hosted systems and necessary infrastructure/network information | Host the TaxiPik servers and supporting services |
| Google/Firebase FCM | Installation/device information, delivery tokens, limited technical service data and the operational push fields in Section 4 | Deliver app notifications |
| Google/Firebase Crashlytics, Rider only | Installation/session identifiers, app/device information and app crash diagnostics | Diagnose Rider app failures |
| OpenFreeMap map resources | Connecting IP address, requested tiles/map areas, styles, fonts/sprites and associated request information | Display maps; both apps' map styles request these resources |
| Proton Mail operational email | Sender/recipient addresses, verification or reset email contents, and support correspondence | Deliver account-related emails and handle support/privacy requests |
| Google Fonts on applicable website pages | IP address and ordinary request information associated with the requested fonts | Display the website's fonts |
Map searches, geocoding and routing send search text, bounding areas, coordinates, route endpoints and applicable heading information to the TaxiPik services that answer those requests. Requests for external map resources can reveal the area displayed; that is not a transfer of your entire stored ride history.
We limit provider use to the operational function and necessary technical processing, with appropriate terms and settings. Provider privacy notices explain their own technical handling; they do not remove our responsibility to limit what we disclose or authorize. We do not authorize optional provider integrations that repurpose user information for unrelated advertising or profiling.
Compelled legal disclosure
We do not voluntarily distribute personal information to authorities or unrelated parties for their own use. We may disclose information under a binding court order or another legal obligation we cannot lawfully refuse, limited to what it requires. Where lawful, we review requests, limit excessive disclosure, and may challenge inappropriate scope where appropriate and practicable. We provide notice when permitted and appropriate; we cannot promise notice where it is prohibited.
A future ownership change is not blanket permission to sell or repurpose personal information. Any change must comply with applicable law and these commitments, with required notice or consent.
7. Retention
We retain information for the operational purposes described here, not to create an unrelated data product. The following rules distinguish account use, screen visibility, erasure, and backups. A binding legal preservation requirement or a specific unresolved investigation can justify limited additional retention; it is not a reason to keep every category indefinitely.
| Information | Retention rule |
|---|---|
| Active account/profile and saved information | Kept while the account is used. On account deletion, identifying profile, credentials and information no longer needed are erased or removed from the operational account; a restricted erased-account reference may remain for legitimately retained records. |
| Current location and availability | Current position is replaced by later reports. Going offline stops normal online availability reporting; account erasure removes the account's current location. Ride points have the separate journey lifecycle below. |
| Ride records and associated routes/coordinates | Normally about 27 months after the last ordinary ride update: approximately 90 days in current storage, 365 days in archive, then 365 days in deep archive before expiry. Scheduled processing can add a short cleanup delay. Required case-specific preservation can last longer. |
| Open direct messages | Kept for conversation history, including participant names, while the conversation remains open. Hiding it does not start an erasure period. Account-deletion requests and reported-content exceptions are handled under Section 8. |
| Closed ride conversations and block-closed DMs | Normally visible for up to 90 days after closure and retained for up to 365 days after closure, followed by scheduled cleanup. Visibility is not the same as deletion. A reported investigation can suspend that cleanup. |
| Reported content and investigation records | Kept while needed to resolve the specific report or applicable legal preservation requirement. Reviewed when the matter ends; information without a remaining lawful operational or legal purpose is erased. |
| Push/session information | Active registrations and credentials are kept for delivery/authentication. Logout, replacement or erasure removes or invalidates relevant active ownership/credentials. Limited installation-registration information and hashed notification-token records may remain to prevent replay or unauthorized reuse. These security records can remain identifiable and are not used for advertising. |
| Profile/vehicle images and other uploaded content | Kept for the selected feature. On deletion, company-controlled files no longer needed for an approved retained purpose are removed, including superseded copies; recipient copies and backups have separate limits. |
| Support and security records | Kept while a specific request, incident or follow-up is open, then deleted unless needed for a documented unresolved dispute or legal obligation. This is not permission for indefinite unrelated profiling. |
| Temporary location-report diagnostics | Three days from the received report, subject only to a binding preservation obligation. This does not set the retention period for normal ride records. |
| Company backups | A rolling history of up to 90 days from backup creation, restricted to recovery and security. Deleted information may persist in a restricted backup until that copy expires. After restoration, applicable erasure decisions are reapplied before the information returns to ordinary use. |
Firebase publishes a 90-day Crashlytics-data retention period before removal begins; that is not a promise that deletion finishes on day 90. Firebase installation information has a separate provider deletion process and is not necessarily removed by TaxiPik logout. We handle applicable provider deletion requests as part of the privacy-request process. OpenFreeMap describes seven-day error-log retention and limited security-incident IP logging of up to 30 days. Provider retention is separate from TaxiPik's own record lifecycles; the linked notices explain those processes.
8. Account Deletion and Privacy Requests
Use the Delete Account control in either app to request account deletion. You can also request deletion without installing or signing into an app through our account-deletion page, by emailing legal@taxipik.com, or by writing to the address in Section 12. Uninstalling an app alone does not delete its server account.
We verify requests using proportionate information needed to protect your account and other people's information. Do not email your password, and do not send unnecessary identity documents. If an unfinished ride prevents the automated operation, complete or cancel it where possible, or contact support. That technical condition is not a blanket refusal of a lawful deletion request.
Account deletion disables normal account use and removes identifying profile and authentication information, saved personal information and company-controlled uploads that have no justified retained purpose. Ordinary messages authored by the erased account are removed or replaced; a recipient's independently saved copy cannot be recalled. Content held for a reported investigation may remain until the specific hold is resolved. Names are kept in genuine conversations during normal account use, not used as a reason to refuse a lawful erasure request.
Completed/cancelled journey records and their coordinates, routes and erased-account references can remain for the journey-record and case-specific purposes in Section 7. Necessary security/replay markers, applicable legal holds and restricted backups can also remain under those rules. Removing a name does not make precise coordinates or context irreversibly anonymous. We explain any applicable retained-data exception and its purpose/period or meaningful criterion when handling the request. Retention is subject to applicable law, not automatically justified just because it appears in this Policy.
You may contact legal@taxipik.com to request access to or a copy of your information, correction, or deletion. Where applicable law provides additional rights, you can also request portability, restriction, object to processing, withdraw consent, or opt out of applicable processing. We do not sell information or use it for targeted advertising. Withdrawal does not undo prior lawful processing; a feature may stop working when its necessary permission or information is withdrawn.
We respond to privacy requests without undue delay and within 45 days after receiving your request, or a shorter period where applicable law requires it. Proportionate ownership verification remains necessary, but it does not move the start date to the date verification finishes. If a lawful extension is necessary, we notify you within the required initial period, explain the reason, and extend by no more than an additional 45 days or the shorter applicable limit. A denial includes its reason where permitted. You can ask for review by emailing legal@taxipik.com with the subject Privacy Request Appeal; we provide a written appeal result within 60 days after receiving the appeal, or a shorter applicable deadline. A denied appeal explains any further complaint route required by law, including the Texas Attorney General complaint mechanism where Texas law applies. You may also contact the relevant authority.
We do not require a purchase to exercise legally protected rights or retaliate against you for doing so. Where applicable law permits an authorized agent, contact us for proportionate verification. Requests can be limited by lawful duties, the rights of others, or properly verified ownership; we explain an applicable limitation where permitted. Privacy rights are not waived by accepting our Terms.
9. Security and Processing Locations
We use authenticated access, encrypted network transport for app/server communications, password hashing for account-password storage, and access restrictions appropriate to operating the Service. Operational messages can be processed by authorized server systems; storage encryption does not make them end-to-end encrypted. No system is perfectly secure, and no policy can guarantee that a breach will never occur.
The operator is based in Texas. Our company-operated server infrastructure is hosted in a US-based data center in the Kansas City, Missouri area. Necessary external providers can process information in other countries according to the service they provide; using US-hosted TaxiPik servers does not mean every provider copy is in Texas or the United States. We do not treat use of the app as a waiver of privacy rights or blanket consent to additional purposes or transfers.
10. Adults Only
The Service is intended for adults at least 18 years old and at least the age of majority where they live, not for children. If you believe a child has created an account or supplied information, contact legal@taxipik.com so we can investigate and handle it appropriately. Do not send additional unnecessary information about the child.
11. Website and Provider Notices
Website visits generate ordinary technical request information, such as IP address, requested page and access time. The feedback form sends the contact information, subject and message you enter to the TaxiPik service for delivery to support. Applicable pages load Google Fonts as described above. We do not use website advertising or tracking cookies to profile you for advertising.
External links and provider services have their own privacy notices. Relevant information is available from Firebase, Google, OpenFreeMap, and Proton. Their notices do not authorize TaxiPik to disregard its own limited operational purposes.
12. Changes and Contact
We identify updates through the version and date above. Material changes receive appropriate notice and any consent required by law or platform rules. New purposes are not silently authorized by replacing a policy page. Expansion beyond the initial US offering is reviewed before launching in additional countries.
Questions, privacy requests, or concerns:
WildBunny Gaming LLC, operating as TaxiPik
550 South Harbin Drive PMB 104
Stephenville, Texas 76401, United States
Privacy/legal: legal@taxipik.com
Support: support@taxipik.com