KRIM Logistics — Global Logistics Operating System

Records governance · interim notice

Data Retention & Deletion

This page describes the retention controls currently verified for KRIM Logistics. It is deliberately limited: a retention period or deletion certification is not promised unless the corresponding technical and legal control is implemented and tested.

Reviewed 15 November 2026 · Read with the KRIM Privacy Notice.

Important implementation status: KRIM has not yet approved a complete category-by-category statutory retention matrix or verified automated archival and purge jobs. Do not rely on older statements on this page about 90-day GPS purging, 365-day cold storage, WORM archives, AES-256 custom vaults or NIST 800-88 erasure. Those claims are withdrawn unless and until separately evidenced.

1. Information currently handled

2. Driver GPS and consent records

Current implementation status (15 November 2026): GPS collection is disabled by both the KRIM Driver app and server launch gates; the production tracking table currently contains no GPS location events. The browser driver workspace is read-only and does not collect device location. Native Android background-location capability is present in an internal preview build only and is not enabled for commercial shipments.

Before any activation, the exact notice must first be approved and the app/server consent-approval gates deliberately opened. Until then, no GPS session can start and the upload endpoint rejects GPS data. After approval, a GPS point will be accepted only when the authenticated driver is verified, has active membership in the operating organisation, is linked to the shipment assignment, the driver assignment is marked in transit, and an active server-side consent session exists. The driver must explicitly consent and can stop sharing. Native background updates require device permission and an ongoing operating-system location notification.

GPS records, when enabled, may include coordinates, server timestamp, device-reported accuracy and shipment/assignment references. A separate consent-session record stores the driver, organisation, assignment, consent-notice version, exact server-controlled notice text, SHA-256 notice hash, language, platform, start time and stop state. The GPS upload endpoint checks that the archived notice matches the current server-controlled notice before accepting a point. Location can be delayed or interrupted by device shutdown, force-stop, permission changes, battery restrictions, poor GPS signal or network loss. KRIM does not promise uninterrupted or safety-critical tracking. Customer-facing views must show the timestamp and whether the latest position is live, recent or stale.

Session inactivity safeguard: a scheduled server control runs every five minutes and stops an active GPS consent session after 15 minutes without a new GPS point. This ends the live-sharing session; it does not delete previously recorded GPS points. The category-specific GPS retention and deletion period remains unapproved, so no fixed deletion deadline is promised.

3. Retention periods and legal holds

Final retention periods for enquiries, accounts, shipment records, financial records, compliance documents, proof of delivery, security logs and GPS data remain to be approved against the actual legal, tax, transport, contractual and dispute requirements applicable to KRIM and each operating corridor.

Until the schedule and corresponding automated controls are approved and tested, users should not assume that a fixed number of days applies or that data is automatically deleted at the end of a stated period. Records may need to be preserved for a lawful claim, audit, tax obligation, investigation or legal hold. Any exception should be limited, documented and access-controlled.

4. Storage and safeguards

KRIM uses a Supabase production project currently configured in ap-northeast-1 (Tokyo, Japan) for database records and server-side functions, together with GitHub Pages for public static pages. The exact execution region for Edge Functions, backup retention, processor terms, cross-border processing and service-provider controls must still be checked against the live account configuration and provider agreements. The Japan-hosted database region is a cross-border processing fact that requires documented legal review; do not describe the database as India-hosted.

KRIM uses authenticated server-side functions and row-level access controls for the tracking workflow. This is not an independent security certification and does not imply a custom immutable archive, cryptographic erasure system or a particular encryption standard beyond controls verified from the provider and deployment configuration.

5. Requests and contact

For an access, correction, deletion or retention question, use the KRIM Contact page and select “Privacy or data request”. KRIM may need to verify identity or authority and may retain information where a valid legal, contractual, safety, tax or dispute obligation applies.

6. Required before public commercial rollout

This interim notice is not legal advice and does not certify compliance with the Digital Personal Data Protection Act, 2023, its Rules or any other law. Those requirements and commencement dates must be assessed for the relevant activity and launch date.