MazdoorLink
Privacy notice — review draft
Draft notice explaining intended account, booking, verification, messaging, assistant and support data practices for MazdoorLink.
Review status and responsible business
This privacy notice is a review draft, not a claim of completed compliance. MazdoorLink's business operator is Vikal Global techlognies. For privacy and account requests, contact support@mazdoorlink.com or +919310869994 at A-63 Sector 16 Block A, Noida, Gautam Buddha Nagar, 201301, Uttar Pradesh, India. The final notice must complete the operator's entity and registration details, designate the responsible privacy and grievance contacts, and describe the deployed product, its processors, retention periods and applicable law at the time of launch.
Information used for the service
The intended service may process your phone number, role, name, account code, chosen work areas, skills, availability, profile information and booking history. It may also process attendance, payment references, ratings, disputes, messages, support requests and technical security records. The final notice must list the fields actually collected and distinguish required information from optional profile details.
Where verification is offered, use the designated secure process. The intended design limits Aadhaar information to what is necessary, such as a last-four reference and restricted supporting document handling. Do not place a full Aadhaar number, bank credentials, passwords or OTPs in a profile, enquiry or assistant conversation. The business must confirm and document lawful verification and retention practices.
Purposes and choices
Information is intended to support account access, suitable work matching, booking coordination, attendance, payment tracking, support, fraud prevention and necessary records. Optional work goals or reminders should be under the worker's control. The platform must not infer a person's mental health, personality or vulnerability to pressure them into working.
Marketing permission must be separate from account access and essential service communications. Optional marketing choices must not be preselected or presented as a condition of receiving a necessary booking update. The final interface should explain each purpose clearly and record the relevant choice and notice version.
Messages, WhatsApp and the account assistant
WhatsApp or SMS authentication may involve the selected messaging provider. A user should understand the chosen channel and have an appropriate alternative where supported. A registration welcome is separate from promotional messaging. The final notice must identify the providers actually used and explain how to stop optional reminders or marketing without losing access to essential support.
The account assistant should receive only the information needed to answer the authenticated user's request. It must not expose another worker's identity documents, bank details or private records. If an external AI provider is enabled, the final notice must identify the relevant processing, retention and transfer arrangements before sending personal data. An assistant answer is not a substitute for an account correction or dispute decision.
Sharing and public information
A public search should show only the limited profile or aggregate information intentionally made public. Precise contact details, identity documents and banking information should remain restricted. Clients, agents and workers may receive the assignment information they need, subject to their role and relationship to that booking.
Service providers may process data for hosting, database operations, messaging, payments, storage, support or authorised analytics. The operator must maintain an accurate provider list and applicable safeguards. Legal disclosures should be limited to what is required or otherwise lawful. The final notice must address international processing locations and applicable restrictions using the actual provider configuration.
Retention, security and requests
The operator must set retention periods for account, verification, attendance, communication, financial and security records, including deletion from backups where appropriate. Data should not be retained indefinitely merely because storage is available. Records needed for a dispute or legal obligation may require a documented exception.
Access controls, secure transport, restricted document links and audit records can reduce risk but cannot promise absolute security. Provide a verified route to request access, correction, deletion, withdrawal of optional consent or grievance handling, subject to applicable law and necessary identity checks. Deleting an account does not necessarily erase records that must lawfully be retained.
Adults, changes and publication
The proposed service is intended for adults. The registration and escalation process must support that policy, and the business must decide how it will handle information submitted by a child. Do not claim age verification without implementing it.
The final notice should show its effective date and explain material updates. Because India's data-protection framework has phased commencement, counsel must check the rules and obligations applicable on the actual launch date. This draft should remain noindex and outside the public sitemap until its operator details and processing inventory are reviewed.
Cards, crew relationships and bonus verification
Creating a card is optional and shows the worker’s first name with completed-work earnings, a reviewed skill or a clearly labelled job offer. Anyone receiving its unguessable URL can view the image for seven days unless revoked earlier. Revocation cannot remove downloaded copies, screenshots or messages already shared by others. The final notice must address stored-file retention as well as public-link expiry.
Entering an optional referral code links the recruit to the referrer. The referrer can see the recruit’s first name and limited shift counts in their crew view, not private bank, identity-document or wage details. Registration copy must explain this before submission. Referral codes are not passwords or government identifiers.
Bonus checks use a server-hashed device signal, normalised UPI information already held for payments and, with device permission at check-in, optional coordinates and accuracy. No continuous location tracking is implemented. Missing or overlapping device, UPI or location evidence may put a bonus on human review; these signals can occur legitimately and do not by themselves block ordinary attendance or wages. Private check-in signals older than ninety days are pruned unless needed for a held referral review. The operator must approve purposes, access, retention exceptions and request handling before launch.
Proactive sharing invitations require optional marketing permission as well as WhatsApp opt-in. User-requested bot replies and approved account-credit updates follow the applicable messaging route. The providers, actual template approvals and processing arrangements must appear in the reviewed vendor inventory.
Operational diagnostics and account assistance
The account assistant reads only the signed-in person’s permitted records. If an AI provider is enabled, a limited account summary and the person’s question are sent for that answer; bank, identity-document and other users’ private records must not be included. The operator must review the configured model, processing terms and retention before enabling it.
Optional operational error monitoring is configured to exclude request bodies, headers, cookies, user identity, query values and AI input/output content. Error reports retain a request reference and limited technical stack/route information so support can investigate failures. The final provider inventory and retention policy must reflect the actual configured services. No advertising analytics or replay tracking is enabled by this release.
