Your information, explained.
This notice covers the app’s actual account, service, payment, location, communication and verification features. The sections below explain what is processed, why, who receives it and how to make a request.
1. Who this policy covers
This Privacy Policy applies to KROOZ Customer, operated by KROOZ, Inc., and the related account and service features on mykrooz.com. It covers passengers and customers booking rides, food pickup/delivery or package delivery.
The other KROOZ app has its own privacy notice. Features vary by account, market, operating system and enabled services. The app identifier for this Android app is com.newkroozcustomer.
This notice explains data handling; it does not replace your applicable service terms or a separate notice presented for a specific sensitive-data feature.
2. Information we process and why
We receive information you enter, information generated when you use the service, and necessary confirmations from payment, verification and communication providers. Not every category is collected from every person.
| Category | Examples | Purpose |
|---|---|---|
| Account and contact details | Name, phone number, email, profile photo if supplied, country, language, account identifiers, referral code, verification status and sign-in/security records. | Create and authenticate your account, communicate with you, and maintain account security. |
| Location and trip activity | Precise or approximate location when permitted, typed or selected addresses, pickup/drop-off coordinates, trip details, delivery instructions, recipient contact details, status and receipts. | Find pickup points, search destinations, arrange services, calculate fares and show progress and receipts. |
| Payments and financial records | Payment-provider references, card brand/last digits and expiry where saved, wallet transactions, amounts charged, tips, refunds, credits and referral activity. | Take payment, show receipts, manage refunds and wallet/referral features, prevent payment fraud and keep necessary accounts. |
| Support, safety and communications | Support tickets and messages, ratings, reports, safety-event information, correspondence and communication preferences. We also process contact details that you deliberately enter for trip-sharing or delivery features. | Provide support, investigate safety concerns and fraud, facilitate service communications and respond to your requests. |
| Device and connection information | IP address, app/device platform and version information supplied by the app or service providers, authentication and security logs, push-notification tokens and related delivery/technical information. | Keep sessions secure, deliver notifications and operate, protect and troubleshoot the service. |
3. Location, permissions and device controls
The customer app uses permitted location access to suggest your pickup and support map-based features. You can enter an address or select a pin instead of using the current-location shortcut. Pickup, drop-off and trip information that you submit is sent to the service and shared as needed with the assigned driver/courier.
These apps request foreground location; they do not request an always-on/background-location permission. Device settings let you deny access or choose approximate location where supported. Some map, matching or live-progress functions may then be limited. A device permission does not itself delete location already included in a trip record.
- Camera and photo selection: used when you choose to supply a profile/verification/document image or delivery evidence where the feature is available. Photo selection does not give KROOZ unrestricted access to your photo library.
- Notifications: used for trip, delivery, account and other enabled service messages. You can change notification permission in device settings.
- Contacts and messages: the current apps do not request access to read your full address book, SMS inbox or call history. Contact details manually entered for a trip/delivery are processed for that purpose. A phone-call action hands off to your device’s calling function.
4. Identity and sensitive information
When identity verification is required or you choose it, the current service uses Didit. Its flow may process identity-document images, a selfie or liveness capture and facial measurements to check identity and detect impersonation. It presents verification-specific notices and any required consent. KROOZ receives verification references, status and relevant results. Read the Didit privacy notice and biometric retention notice. Ask KROOZ to review provider-held data as part of a deletion request.
Driver documents, tax details and precise location receive access controls appropriate to their sensitivity. Do not place sensitive identity, financial or health information in free-text support or delivery instructions unless it is necessary and specifically requested through an appropriate secure channel. Identity or biometric information is not used by KROOZ for targeted advertising.
5. Purposes and legal grounds
We process data to deliver the service you request, administer the account, coordinate participants, collect or pay funds, provide support, prevent abuse, maintain safety and comply with relevant legal obligations.
Where a law requires a legal basis, we rely on contract performance for requested services; legal obligations for required records; legitimate interests such as service security, fraud prevention and dispute handling where those interests do not override your rights; and consent where required, including certain sensitive-data, permission or marketing uses. You may withdraw consent for future consent-based processing.
Providing account and service information is necessary to use the features that depend on it. Withholding optional data limits only the related optional feature. Withholding information required by law or to perform a service may prevent that service.
6. How information is shared
Information is disclosed according to the service being used and the recipient’s role, rather than made generally available. We do not sell personal information or share it for cross-context behavioral advertising.
| Provider or recipient | Purpose and data involved |
|---|---|
| Assigned drivers, couriers and relevant delivery participants | Pickup/drop-off and delivery information, service contact details and necessary instructions. Trip-sharing recipients receive the information exposed by the tracking link you choose to share. |
| Google Maps and map services | Addresses, search queries, coordinates and device/network information needed for maps, places and routing. See Google’s privacy policy. Where a build uses an alternative map provider, its map requests go to that provider. |
| Firebase Cloud Messaging / Apple push delivery | App-instance/device registration tokens and notification-routing information for service messages. See Firebase privacy information. Delivery also depends on the operating-system notification service; some alternative Android builds use Huawei push. |
| Payment and payout providers | Transaction, payment-method and payout details needed for the method you select. Stripe is supported; other enabled methods may use their own providers. See Stripe’s privacy notice. KROOZ stores payment references rather than full card numbers or card security codes. |
| Identity verification | Didit and any verification provider specifically identified in the verification flow process the information described in the identity section. |
| Operational providers and lawful recipients | Hosting/storage, email/SMS delivery and security providers receive data needed to operate the service. Authorized staff access relevant records. Regulators, law enforcement, advisers or parties to a business transfer may receive limited data where legally justified and subject to appropriate safeguards. |
Information another participant has already received, or that an independent payment provider must keep for its own legal duties, may be subject to that recipient’s responsibilities. We require service providers handling data on our behalf to apply protections consistent with this policy and applicable requirements, limit processing to authorized purposes, and support relevant deletion instructions. KROOZ remains responsible for the processing it controls.
7. Retention and what happens after deletion
Keeping an account active is not permission to retain every record indefinitely. We retain information for the purposes above and review deletion requests against specific legal, safety and financial recordkeeping needs. The following retention criteria apply; there is no single global duration for every record.
| Record category | What happens | Duration or retention criterion |
|---|---|---|
| Account profile and access | Kept while needed to run the account. On confirmed deletion, core profile contact fields are removed or replaced, sessions are revoked, and saved card references and push-device registrations are removed. | A minimal closure/security record may remain to demonstrate the request or prevent misuse. It is not a reusable active account. |
| Trip, delivery, payment and ledger records | Transaction records can remain after account closure. These may still contain dates, locations, amounts, service events, payment references and identifiers that are personal data. | Retained only for applicable accounting/tax or transportation obligations, unresolved refunds/chargebacks, safety matters, fraud prevention or legal claims; the relevant statutory period or open matter determines the duration. |
| Support, safety, audit and verification records | Some correspondence, reports, verification outcomes and audit evidence may remain after account closure where a specific security, legal or dispute purpose still applies. | Duration depends on the type of incident, legal duty and claim/appeal period. We review and remove or reduce identifying details that are no longer needed; retained records are not automatically anonymous. |
| Backups and service-provider records | Copies can remain in protected backups pending normal replacement, and processors may hold records under their applicable instructions or independent legal duties. | If data is restored, the deletion restrictions must be reapplied. You can ask us for the applicable backup/provider retention details and deletion review. |
Where a record is no longer needed, the applicable outcome is deletion, reduction of identifying details, or irreversible anonymization. Removing your name from an otherwise identifiable trip or financial record is not described as complete anonymization. Our deletion response explains material exceptions and their applicable retention basis or period.
Request account and associated-data deletion, or contact us if you want a specific retained record reviewed.
8. Security and international processing
Safeguards include encrypted transport for the service, authenticated sessions, restricted staff access, audit controls and encryption of selected sensitive stored information such as uploaded driver documents. No security measure makes a system risk-free. Please protect your device and do not share sign-in or deletion confirmation codes.
KROOZ is based in the United States; hosting and service providers can process information in other countries. Where a transfer is subject to data-protection restrictions, applicable lawful transfer mechanisms and contractual safeguards are required. Contact us for information about the arrangements relevant to your data. You may request details about safeguards that apply to your information.
9. Your choices and privacy rights
You can adjust device permissions, update supported account details, manage enabled communication preferences and request account deletion. Marketing choices do not prevent essential transactional or security messages.
Depending on your jurisdiction and eligibility, your rights may include access, correction, deletion, portability, restriction or objection, withdrawal of consent, and opt-out of certain advertising, sale or significant profiling. You may ask for a human review of an account or verification decision and appeal a privacy-request decision. We do not discriminate for exercising applicable privacy rights.
Send a request to admin@mykrooz.com or the contact form. We may verify ownership or an authorized representative’s authority using information proportionate to the request. We will explain a refusal or lawful exception and how to appeal by replying with “Privacy appeal”.
We respond without undue delay within applicable legal deadlines. Where GDPR applies, the usual response period is one month; for an applicable Texas consumer request, it is 45 days. Any permitted extension must be explained. You can also complain to the competent privacy authority or, where appropriate, the Texas Attorney General.
10. Age, communications and automated features
Independent accounts are intended for adults aged 18 or older, or a higher age where required by the relevant service or law. These apps are not directed at children under 13. Contact us if you believe a child provided personal information improperly so it can be reviewed and addressed.
Dispatch, fare calculation, eligibility checks and fraud controls can use automated rules based on service, location, account and verification data. They help operate and protect the platform; you can ask support to review a consequential account decision.
Permission to use the app is not blanket consent to unrelated marketing. Use available unsubscribe or communication-preference controls for optional promotions. Authentication, trip, safety and other necessary service communications may still be sent.
11. This policy site and updates
These policy pages do not set advertising cookies or load an analytics SDK. Normal hosting/security access logs may record requests. The deletion form transmits the details you submit to KROOZ support over HTTPS. If the configured abuse protection is enabled, Google reCAPTCHA is loaded when you submit the form; its Privacy Policy and Terms apply. Signing into the separate account website uses its session storage.
We may update this notice when practices, services or requirements change. The date at the top identifies the current version. Material changes requiring additional notice or consent must be communicated appropriately. Earlier policies continue to describe the earlier periods to which they applied.
12. Contact KROOZ
KROOZ, Inc. is the operator responsible for the personal information described in this notice.
Privacy & Account RequestsKROOZ, Inc.
P. O. Box 741564
Dallas, Texas 75374, United States
Email: admin@mykrooz.com
Website: KROOZ contact form
Please identify the app and the phone number or email registered to the account. Do not send passwords, one-time sign-in codes, full card numbers, tax identification numbers, or identity-document images in an ordinary email or web request. We will explain any secure verification steps that are needed.