Privacy Policy
Last updated: 14 October 2026 · Draft requiring operator review before launch
1. Who operates WORLER
WORLER is intended to be a technology connector that helps customers discover independent workers. Before public launch, the operator must publish its accurate legal/operator name, service address, working contact details, and any required grievance contact. Do not use this template as a substitute for filling in those details.
2. Information this starter may collect
Depending on how you use the site, the server may store your name, email address, password hash, phone number, optional locality, worker service-panel details, appointment requests, payment references submitted for listing-fee verification, session information, and data-deletion requests. Do not enter unnecessary sensitive information into profiles or service descriptions. The site should never ask for your password, UPI PIN, or OTP to verify a payment.
3. Why information is used
Data is used to create and secure accounts, display worker listings, support appointment requests, reveal contact details according to the site's flow, verify worker listing payments, moderate content, respond to reports, and handle deletion requests or legal obligations. Collect only information reasonably needed for these purposes.
4. Public listings and sharing
Worker listings may display the worker's name, category, service areas, starting price, and other details the worker submits for publication. Contact details should only be revealed as described in the service's interface. Do not publish identity documents, precise home addresses, financial credentials, or other sensitive information in public listing fields. Information may be disclosed where required by law or necessary to address security or abuse, subject to applicable law.
5. Location and third parties
Location is optional. If you choose browser geolocation, your device may provide coordinates and the application may send them to OpenStreetMap Nominatim to resolve a location description. You can instead type a locality manually. Review the provider's current terms and privacy practices before launch. This starter does not intentionally include advertising or analytics SDKs; any future third-party tools must be reviewed and disclosed before use.
6. Passwords, sessions, and security
Passwords are intended to be stored as bcrypt hashes, not plain text. Sign-in uses a session cookie intended to be HTTP-only. No website can guarantee absolute security. The operator must maintain access controls, secure configuration, updates, backups, incident response, and appropriate retention/deletion practices. Do not reuse passwords from other services.
7. Cookies and preferences
The site uses an essential session cookie to keep users signed in. The starter's cookie banner records a preference in browser local storage and does not itself enable advertising or analytics tracking. Browser settings can also be used to manage cookies, but disabling essential cookies may affect sign-in.
8. Children
This service is not designed for children. The operator must determine and follow applicable age, parental-consent, and child-data safeguards before allowing minors to use the service or collecting their personal data. Do not knowingly collect children's personal data unless lawful requirements and safeguards have been addressed.
9. Retention and data deletion
Information should be retained only as long as reasonably needed for platform operations, security, complaint handling, and legal obligations. Use the data deletion request page to request deletion. In this starter, requests are recorded for manual review and are not automatically completed. Some information may need to be retained where law requires it; the operator should explain the outcome to the requester.
10. Complaints and policy changes
Publish a working privacy/support contact and any grievance mechanism required by applicable law before launch. Update this policy if actual data practices change and communicate changes where required. This template is not legal advice and must be checked against the deployed code, hosting provider, third-party services, and applicable Indian law before use.