Read this notice with any specific notice shown when you submit an enquiry, create an account, request a quote, make a payment or use a particular KRIM workflow. A specific notice may explain a particular data use in more detail.
1. Scope and who operates KRIM
This notice applies to the KRIM Logistics website, digital platform, customer and partner workflows, enquiry channels and related logistics coordination activities operated under the KRIM Logistics brand. KRIM’s commercial focus is India-first; international workflows are subject to country, route, partner and regulatory validation.
“KRIM”, “we”, “us” or “our” means the business operating under the KRIM Logistics trade name in India. A carrier, warehouse, customs broker, payment provider or other supplier may have separate privacy responsibilities when it independently determines how it uses information.
Operator disclosure: The exact legal-operator details and designated privacy/grievance contact must be confirmed and published before this notice is treated as final. Do not send identity documents or sensitive information through a general enquiry unless specifically requested through an appropriate channel.
2. Information we may handle
The information depends on the feature and service request. It may include:
| Category | Examples | Typical purpose |
|---|---|---|
| Contact & identity | Name, business name, email, phone, role. | Enquiries, accounts and support. |
| Shipment & service | Origin/destination, cargo details, dimensions, weight, handling needs, references and documents supplied. | Quote assessment, routing and coordination. |
| Business & partner | Organisation, service areas, vehicle/equipment capability, capacity and onboarding details. | Partner review and business workflows. |
| Account & security | Login identifiers, authentication events, role/access records, IP and device/browser data. | Account access, security and troubleshooting. |
| Payment & transaction | Order/payment references, amount, currency, status and reconciliation records. | Payment confirmation, accounting and disputes. |
| Driver trip location | GPS coordinates, device-reported accuracy, server timestamp, shipment/assignment reference and tracking-session metadata. | Optional location sharing for a verified driver during an assigned shipment marked in transit. |
| Communications | Messages, support requests, feedback and notification preferences. | Responding and service records. |
Current GPS status (15 November 2026): Driver GPS collection is disabled by both the KRIM Driver app and server launch gates. No GPS location events are currently recorded. The browser driver workspace is read-only and does not collect device location. Native background-location capability is an internal preview only; it is not available for commercial shipment tracking until KRIM approves the precise location notice, retention period, deletion and legal-hold process, and completes real-device and end-to-end tests.
Please do not submit unnecessary sensitive personal information. Shipment documents may contain personal or commercially confidential details; share only what is reasonably needed.
3. How and why information may be used
Depending on the interaction and applicable law, information may be used to respond to enquiries; assess shipment requirements, route feasibility and partner capability; administer accounts and access; coordinate accepted services; initiate or reconcile payments; provide updates and support; protect the platform and investigate misuse; maintain audit, tax and accounting records; and improve platform reliability and workflows.
We do not treat a general enquiry as permission for unrelated marketing. Where consent is the appropriate basis for optional processing or communications, it should be requested separately and may be withdrawn through the stated channel.
Driver location: Location sharing is OFF by default. It is collected only after a verified assigned driver expressly starts a tracking session for a shipment marked in transit. The native app may continue location updates in the background only after the driver grants the required device permissions and the operating system displays its location-sharing indicator/notification. Browser sharing is foreground-only. Device, battery, network and operating-system restrictions can interrupt updates.
5. Payments and financial information
Where online payment is offered, an external payment provider may handle the payment flow. KRIM may receive transaction identifiers, payment status, amount, currency and reconciliation information. The provider may collect payment credentials under its own terms and privacy notice.
Never send card numbers, UPI PINs, banking passwords or one-time passwords to KRIM through a form, email or chat. Payment status remains subject to reconciliation with the relevant order or transaction.
6. Storage locations and international transfers
KRIM’s production Supabase project is currently configured in region ap-northeast-1 (Tokyo, Japan); database records stored in that project are hosted in that region. The exact execution region for edge functions, backup retention and provider-managed copies must be checked against the live provider configuration and contract. International shipment coordination may also require limited details to be shared with a service provider abroad for a movement separately validated and accepted.
KRIM must maintain a current provider/subprocessor inventory and obtain legal review of applicable cross-border transfer requirements, including the current Japan-hosted Supabase project, before commercial rollout or additional international data flows. A global-ready architecture does not mean every international route or country is currently commercially available.
7. How long information is retained
Retention depends on the information type, purpose, account or shipment status, security needs and applicable legal or accounting requirements. KRIM’s intended approach is to retain information only as long as reasonably necessary, then delete or anonymise it where appropriate and technically feasible.
The current system records opt-in GPS points in shipment tracking events and stores separate tracking-session consent records. An inactivity safeguard is implemented to stop an active driver GPS session after 15 minutes without a new GPS point; this stops live sharing but does not delete previously recorded coordinates. An automated GPS purge, final category-by-category retention schedule and legal-hold workflow have not yet been verified as implemented. Do not rely on a 90-day GPS deletion promise, 365-day cold archive, immutable WORM storage or NIST 800-88 erasure claim. These controls must be approved, implemented and tested before public commercial use of live GPS. Legal, tax, safety, fraud-prevention or dispute requirements may require a justified retention exception.
See the Data Retention & Deletion Notice for the current implementation status.
8. Security and access controls
KRIM aims to use proportionate technical and organisational safeguards, which may include access permissions, authentication controls, logging, secure connections, backups, rate limits and provider security features. Access should be limited according to role and business need.
No website or storage system can be guaranteed completely secure. Controls must be checked against the live platform and connected providers; this notice is not proof that every safeguard is enabled or independently tested. If you believe your account or information has been accessed improperly, contact KRIM promptly. Never include passwords or authentication codes in your report.
9. Your choices and privacy requests
Depending on applicable law and the commencement of relevant provisions, you may have rights or choices relating to access, correction, updating, erasure, consent withdrawal or grievance redressal. Some records may need to be retained where a legal obligation or necessary operational reason applies.
- Access or correction: identify the account, enquiry or record and explain what should be reviewed.
- Deletion: request deletion where available and no lawful retention exception applies.
- Consent withdrawal: use the channel stated for the relevant consent-based processing.
- Grievance: describe the concern and the interaction so it can be reviewed.
KRIM may need to verify identity or authority and ask for clarification. The designated privacy/grievance contact and response procedure must be formally confirmed and published before public launch.
10. Cookies, logs and device information
The site may use essential browser storage, session technologies, security logs and similar technical data to operate features, remember preferences, protect accounts and diagnose errors. Third-party services linked from or embedded in the site may use their own technologies.
KRIM must audit the live site for analytics, advertising pixels, embedded media and other non-essential trackers before publishing a complete cookie inventory or promising granular cookie controls. Browser settings can manage cookies, although blocking essential storage may affect functionality.
11. Children
KRIM’s logistics and business workflows are intended for people who can lawfully use the relevant service. We do not knowingly seek children’s personal information through general marketing or enquiry forms. If you believe a child’s information was submitted improperly, contact us for review.
12. Information across KRIM’s nine user types
KRIM’s platform is designed for nine distinct user types. The examples below describe possible operational context, not a promise that every workspace or feature is currently enabled.
- Customer / Shipper: contact details, shipment instructions, quotes, documents and transaction references.
- Logistics Partner / Carrier: organisation, service area, capacity, verification and accepted assignment information.
- Driver: assignment details, relevant contact and delivery instructions, milestones and proof-of-delivery records; GPS coordinates only during an explicitly started, active in-transit tracking session.
- Warehouse Operator: facility, handling, inventory and inbound/outbound coordination records.
- Customs & Trade: shipment and trade documents needed for a validated coordination task.
- Finance: invoice, payment, refund, reconciliation and settlement records relevant to a transaction.
- Operations Control Tower: shipment milestones, exceptions and coordination records required to manage operations.
- Enterprise: organisation, authorised user, shipment and workflow information within its permitted scope.
- Platform Administrator: restricted internal access for platform administration, subject to separate authorisation and audit controls; not a public account or support route.
Role labels alone do not grant access. Actual access must be enforced by authenticated identity, organisation membership, server-side permissions and applicable data policies. Do not assume a partner or other user can see every shipment or customer record.
13. Reporting a suspected privacy or security issue
If you suspect that your account, shipment information or other personal information has been exposed or accessed improperly, contact KRIM through the Contact page and select “Privacy or data request”. Describe the affected workflow and approximate time, but do not include passwords, one-time codes, payment credentials or unnecessary identity documents.
KRIM must assess the report, preserve relevant records, restrict access where appropriate and determine any notification or reporting duties under the law applicable at the time. This notice does not promise a particular response time or confirm that a specific incident-response process has been independently tested.
14. Changes and how to contact KRIM
We may revise this notice when workflows, providers, legal requirements or data practices change. The date at the top indicates the latest revision. Material changes should be communicated through an appropriate website or account notice where required.
For a privacy question or request, use the KRIM Contact page and select “Privacy or data request”. Include enough context to identify the interaction. Do not send passwords, OTPs, payment credentials or unnecessary identity documents.
Need to ask about your information?
Use the privacy enquiry type on the KRIM Contact page. Share only the details needed to identify your request.
Contact KRIM →