MazdoorLink
Cancellation and refund policy — review draft
Draft policy for unfulfilled bookings, partial fulfilment, cancellations, payment errors, replacement requests and refund tracking.
Review status and scope
This is a proposed policy for review. It is not an approved fee schedule or a promise that every cancellation qualifies for the same refund. Before production launch, the operator must confirm its legal identity, commercial model, booking charges, cancellation windows, replacement arrangements and refund decision process. The final policy must be displayed before the user pays.
Before payment
A booking should show the requested work, dates, location, headcount, worker wages, platform charges, applicable taxes and any approved additional costs. It should also state when the request becomes confirmed. An availability estimate is not a guarantee that a particular person or team has accepted the assignment.
If payment is pending or uncertain, check the existing transaction before trying again. Keep the booking and payment reference. Never share an OTP, card credential or banking password with someone claiming to arrange a refund.
Unfulfilled and partially fulfilled requests
Where a confirmed service is not supplied, review the amount charged for the unfulfilled part and the remedy available under the booking and applicable law. If only part of a team attends or only part of an agreed period is provided, the record should distinguish completed work from the outstanding service.
A replacement may be appropriate when it is available, suitable and accepted. The final policy must specify the process and any service window without claiming an unconditional replacement guarantee. A proposed replacement must not conceal the user's available refund or other statutory rights.
Client cancellations and changed scope
Cancellation terms should be clear, proportionate and disclosed before acceptance. The operator must decide any advance-notice windows and charges based on its actual model and obtain legal review. No cancellation fee should be imposed solely because a test environment contains a default value.
If a client changes the role, site or hours, confirm whether the worker can accept the new assignment and document any price change. Payment for work already completed and approved expenses should be assessed separately from a request to cancel future work. The platform must not finance a customer refund through an unexplained deduction from worker wages.
Attendance, quality and payment errors
A missing scan, late report or quality concern should be reviewed using the booking, available records and both parties' accounts. An automated status alone should not decide the outcome. Users should be able to explain an incorrect attendance entry or a difference between the advertised and actual task.
Duplicate collections, failed transactions and excess charges need transaction-level investigation. The final process should identify the responsible payment provider, the platform's decision steps and how the user will be informed. Refunds should ordinarily use the original payment route where supported, subject to provider requirements and lawful exceptions.
How to request and track a review
Use the booking support or grievance route and provide the booking reference, payment reference, date, issue and requested outcome. Avoid unnecessary identity or banking documents. The operator should acknowledge the complaint, record its review and explain the decision and calculation in understandable terms.
The final policy must separate the platform's review time from the payment provider's processing time. It must state only timeframes the operator can support and comply with applicable requirements. A refund is not complete merely because a request has been submitted; provide a reference and status when the provider makes those available.
Rights and escalation
Nothing in the final policy should remove rights that applicable law makes available to the customer or worker. This policy concerns MazdoorLink, operated by Vikal Global techlognies. The final grievance page must identify the responsible officer and escalation contact. Contact support@mazdoorlink.com or +919310869994 for refund or draft review questions; general support details do not replace the required grievance officer disclosures.
Keep this page marked as a draft, noindex and outside the public sitemap until the commercial decisions and review are complete. Publish the approved effective date and retain earlier versions so that a booking can be assessed against the terms shown when it was accepted.
Company bonus wallets
Promotional bonuses are separate from booking charges and regular worker wages. Their final terms must explain qualification, review, funding and any lawful correction or reversal. A confirmed failed bonus payout releases its reserved wallet amount once; an unknown provider outcome remains under reconciliation. These technical states do not replace booking-refund or grievance rights.
