DPDP for logistics and mobility, for every trip and delivery
Know whose instructions each delivery follows, track drivers only as far as the purpose needs, and erase addresses on time.
An illustration of the Logistics & mobility pack's tasks in the platform.
This is general information, not legal advice. For your own situation, speak to a lawyer.
Where DPDP bites in Logistics & mobility
Deliveries for merchants
Delivering a merchant's orders on its instructions makes you its Data Processor, under a valid contract; the merchant answers for that data as the Data Fiduciary.Source: s.2(k) · s.8(2)Drivers' and riders' location
Tracking employees for their work can rest on employment. Riders on contract may not be employees, so record the basis for each purpose, such as consent limited to what is needed.Source: s.7(i) · s.6(1)Riders' and customers' own data
For your own app's riders and customers, you decide the purpose and are a Data Fiduciary, with notice and withdrawal as easy as consent.Source: s.2(i) · s.5; R.3 · s.6(4)Breaches on the clock
CERT-In wants listed cyber incidents within 6 hours; a personal data breach also goes to the Board and each affected person.Source: direction (ii) · s.8(6); R.7
The Logistics & mobility pack
Added to the DPDP tasks every client gets, and kept up to date as data.
- Role mappingEach flow marked as yours or a merchant's, with its duties.
- Location rulesWhen tracking starts and stops, and the basis recorded for each.
- Retention rulesAddress, trip and proof-of-delivery periods, held before erasure.
- Logistics data categoriesDriver, rider, address, trip, location and proof-of-delivery records.
- Readiness questionsQuestions for logistics and mobility, added to your assessment.
Key modules
Scope & guided set-up
Answer a short profile and see only the duties that apply to youConsent & preferences
Collect, check and withdraw consent on web, apps and your own systemsRetention & erasure
Retention rules per purpose, erasure when they end, and proof of every stepBreach response
Every breach recorded, with the 6-hour and 72-hour clocks and the Board report
Questions
Are we a Data Fiduciary or a Data Processor?
It depends on the flow. Delivering a merchant's orders on its instructions, you are its processor; for your own app, drivers and marketing, you decide the purpose and are a Data Fiduciary.
Source: s.2(k) · s.2(i)
Can we track drivers after their shift?
Only where a basis covers it. Employment covers tracking for the work; beyond it, consent must be specific and limited to what the purpose needs.
Source: s.7(i) · s.6(1)
How long do we keep delivery addresses?
As long as the purpose or a law needs them, with processing logs kept at least a year. For a merchant's orders, follow the merchant's instructions.
Source: s.8(7) · R.8(3)
Official texts: MeitY's data protection page, the Gazette of India, CERT-In.
See the platform with Logistics & mobility data
We show you the platform with sample data from your sector and talk through how your team would use it.