01
Explain collection
Use a clear standalone notice listing data categories, purposes, retention and how users can exercise applicable rights or complain.
Privacy by design
Collect less.
Protect more.
Task coordination needs some personal information, but users should know what is collected, why it is used, who can see it and when it is deleted.
02
Minimize fields
Collect only task, account, payment and safety details needed for the selected feature. Avoid collecting sensitive IDs by default.
03
Limit access
Use role permissions and encryption; mask private data in support tools; log staff access; restrict downloads and exports.
04
Set retention periods
Separate task, payment, support and security records. Define a reason and duration for each, then delete or de-identify when no longer needed, subject to law.
05
Share by purpose
Share task address only after acceptance and only with the assigned counterpart. Share identity-check results as a status badge, not document images.
06
Prepare incident handling
Maintain breach triage, a security contact, evidence preservation, user communications and regulatory reporting procedures where required.
Do not put full names, phone numbers, bank information, address or identity-document numbers into public task listings, public reviews, analytics events or demo screenshots.
Reference: MeitY Digital Personal Data Protection Rules 2025 ↗