This article is practical hygiene for CA, IT, law, company secretary, and agency teams. It is not legal advice on DPDP or any other regulation. For obligations that apply to your firm, consult qualified counsel.
The risks that show up in real firms
- Lost or stolen devices with unlocked email and file sync
- Ex-employees who still reach shared drives or SaaS tools
- WhatsApp forwards of PAN, Aadhaar, contracts, or payroll extracts
- One shared admin login for “the firm’s” CRM or project tool
- Client data in personal Google Drive or email because it was faster
Most incidents are mundane: access that should have been removed, or copies that should never have left the system.
A baseline checklist that fits 10–100 person teams
1. Named accounts, not shared logins
Every person who needs access gets their own user. Shared passwords destroy accountability and make offboarding guesswork.
2. Role-based access by default
Partners and delivery leads do not all need every client’s files. Give access by role and engagement need; review quarterly. Narrower defaults beat heroic trust.
3. Offboarding within one business day
When someone leaves or a contractor ends, remove SaaS access, shared drives, email groups, and device access on a checklist owned by a named person.
4. Device basics
Screen locks, full-disk encryption where available, and a rule against storing client exports permanently on personal machines. Prefer working inside approved systems.
5. Sharing rules
No open links with “anyone can view” for client documents. Prefer named recipients and expiry. Avoid forwarding signed engagement letters and KYC packs through personal chat as the archive of record.
6. Retention you can explain
Keep client data for the engagement life plus a hold period your partners approve. Delete or archive stale exports. Hoarding “just in case” expands breach impact.
7. Backup and recovery awareness
Know where systems are backed up and who can restore. A folder on one laptop is not a backup strategy.
8. Vendor awareness
Know which tools hold personal data, who admins them, and how you export if you leave. Read permission prompts when connecting new apps.
Make it a monthly 30-minute habit
Security programmes die when they are annual speeches. Try a light monthly pass:
- Any leavers still in tools?
- Any shared passwords still circulating?
- Any client folders with overly broad access?
- Any open external links older than they should be?
Record what you fixed. Patterns matter more than perfection.
DPDP-minded framing without the scare script
India’s DPDP regime raises expectations around purpose, access, and care with personal data. Even before you finalize policies with counsel, the habits above move you in a safer direction: less sprawl, clearer owners, fewer copies. Soft reminder again—this is operational guidance, not legal advice.
Where Workplate fits
Access control is easier when client work is not scattered across five unrelated products with five admin models. Workplate offers Projects, CRM, eSign, Invoice, and AI Chat under one login, account, and bill for Indian professional services firms. Aadhaar eSign is available for suitable commercial documents; it is not a path for DSC/MCA statutory filings. Use role-minded access inside whatever systems you run—including Workplate—so client data is reachable by those who need it and not by everyone else.
Soft next step
This week: kill shared logins, confirm last month’s leavers are removed, and replace one habitual “forward the PDF on WhatsApp” path with storage in the engagement record. When you want client work and access under a calmer modular stack, see workplate.io.