Ek din aap login karte hain aur account block mila hai \u2014 koi warning nahi, koi wajah nahi bataayi gayi, sirf ek generic message. Har delivery rider ke man mein yeh dar rehta hai, aur ab yeh sirf ek individual problem nahi rahi \u2014 yeh Karnataka High Court mein ek live legal case ban chuki hai, jiska outcome tay karega ki platforms ko riders ko deactivate karne se pehle kya karna zaroori hai.<\/p>\n\n\n\n
29 June 2026 ko, IAMAI (Internet and Mobile Association of India) aur kai badi platform companies \u2014 Swiggy, Zepto, Eternal Ltd. (jo Zomato chalati hai), aur Urban Company \u2014 ne Karnataka High Court mein ek writ petition file ki. Yeh petition Karnataka government ke ek notice ke against thi, jo 21 May 2026 ko diya gaya tha, aur jisme platforms ko Internal Dispute Resolution Committees (IDRCs) banane ka nirdesh diya gaya tha \u2014 matlab ek internal body jo worker ko deactivate karne se pehle uski baat sune.<\/p>\n\n\n\n
Case ka core sawaal seedha hai: kya ek gig worker ko yeh jaanne ka haq hai ki uski livelihood kyun chhini ja rahi hai, aur kya use apni baat rakhne ka mauka milna chahiye deactivation se pehle? Platforms ka stand hai ki yeh regulation unke operational flexibility ko limit karta hai. Government aur worker-rights advocates ka stand hai ki bina kisi due process ke ek rider ki income raatoraat khatam ho jaana fundamentally unfair hai.<\/p>\n\n\n\n
Case ka constitutional sawaal abhi bhi pending hai, lekin ek interim update aa chuka hai: 3 July 2026 ko, Justice M. Nagaprasanna ne Act par stay dene se mana kar diya \u2014 matlab platforms yeh nahi kah sakte ki poora law suspend ho gaya hai. Court ne iske bajaye order diya ki disputed welfare fee state government ke paas nahi, balki court registry ke paas deposit ki jaaye, aur government ko tab tak koi coercive action lene se roka gaya jab tak platforms is interim order ka paalan karte hain. Matlab abhi ke liye, IDRC jaisi due-process requirements technically effect mein rehti hain jab tak final constitutional decision nahi aata.<\/p>\n\n\n\n
Yeh problem kitni common hai? 2025 mein Human Rights Watch ne ek survey kiya jisme paaya gaya ki gig workers mein se ek-tihai se zyada logon ka account kabhi na kabhi deactivate ho chuka tha \u2014 aur un cases mein se lagbhag aadhe baad mein galti nikle. Matlab, deactivation ka decision khud hi kaafi error-prone hai.<\/p>\n\n\n\n
Workers jo complaints report karte hain, unka pattern kaafi consistent hai: complaint ko contest karne ka koi formal right nahi hota, complaint karne wale customer ki identity pata nahi chalti, aur deactivation se pehle koi hearing nahi hoti. Jab app ka glitch galat cancellation register kar deta hai, uss galat record ko correct karne ka bhi koi seedha mechanism nahi hai \u2014 aur agar aise errors ek threshold cross kar jaayein, toh account automatically block ho jaata hai.<\/p>\n\n\n\n
Yeh sirf ek platform ka issue nahi hai \u2014 yeh pattern low ratings, frequent cancellations, aur customer complaints \u2014 teenon triggers mein dikhta hai, aur zyadatar decisions automated systems lete hain, insaan nahi.<\/p>\n\n\n\n
Code on Social Security, jo 21 November 2025 se lagoo hai, gig aur platform workers ko pehli baar formal social security framework deta hai \u2014 insurance, health aur maternity support, old-age protection jaisi cheezein. Lekin yeh code specifically deactivation ke process ko cover nahi karta \u2014 matlab aapko social security mil sakti hai, lekin agar aapka account bina wajah block ho jaaye, toh usko contest karne ka koi law-backed right abhi guaranteed nahi hai. Yehi gap hai jo Karnataka case try kar raha hai fill karne ka.<\/p>\n\n\n\n
Jab tak final constitutional decision nahi aata, sabse practical protection woh cheezein hain jo aap khud control kar sakte hain. Deactivation ke sabse common triggers \u2014 low rating aur frequent cancellations \u2014 woh cheezein hain jo aap active rakh sakte hain agar aap unhe closely track karein.<\/p>\n\n\n\n
Apni rating regularly check karna aur usme drop hote hi wajah samajhna, delivery rider rating aur earnings ka connection<\/a> samajhne se shuru hota hai \u2014 kyunki rating sirf earnings hi nahi, account safety bhi affect karti hai. Aur agar aapko pata nahi ki apni current rating kaise check karein, yeh guide<\/a> step-by-step process bataata hai.<\/p>\n\n\n\n Yeh issue akela nahi hai \u2014 16 May 2026 ko Gig & Platform Service Workers Union (GIPSWU) ne ek nationwide five-hour strike bulaayi thi, jiski demands mein “protection against arbitrary account suspensions” bhi shaamil thi. Matlab yeh worry sirf aapki nahi hai \u2014 poore sector mein riders isi baat ko lekar awaaz utha rahe hain, aur ab woh awaaz court tak pahunch chuki hai.<\/p>\n\n\n\n Start Earning Today!<\/a><\/p>\n\n\n\n Karnataka High Court ka yeh case abhi decide karna baaki hai, lekin iska hona hi bataata hai ki “bina wajah deactivation” ab sirf individual complaint nahi, ek legal aur regulatory sawaal ban chuka hai. Jab tak clear outcome nahi aata, apni rating aur cancellation pattern par nazar rakhna hi sabse practical protection hai \u2014 aur is case ka result aane wale mahinon mein poore industry ke liye rules badal sakta hai.<\/p>\n\n\n\n Ek din aap login karte hain aur account block mila hai \u2014 koi warning nahi, koi wajah nahi bataayi gayi, sirf ek generic message. Har delivery rider ke man mein yeh dar rehta hai, aur ab yeh sirf ek individual problem nahi rahi \u2014 yeh Karnataka High Court mein ek live legal case ban chuki […]<\/p>\n","protected":false},"author":3,"featured_media":1935,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[518],"tags":[2795,2796,2798,2797,2776],"class_list":["post-1929","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-rider-guides-hacks","tag-account-activation","tag-algorithmic-management","tag-delivery-rider-rating","tag-gig-worker-rights","tag-karnataka-high-court"],"_links":{"self":[{"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/posts\/1929","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/comments?post=1929"}],"version-history":[{"count":1,"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/posts\/1929\/revisions"}],"predecessor-version":[{"id":1938,"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/posts\/1929\/revisions\/1938"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/media\/1935"}],"wp:attachment":[{"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/media?parent=1929"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/categories?post=1929"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/alphareach.tech\/blog\/wp-json\/wp\/v2\/tags?post=1929"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Conclusion<\/h2>\n\n\n\n
Sources<\/h2>\n\n\n\n
\n