You share
An enquiry, or information for your app workflow.
NirmanSite / PRIVACY POLICY
Understand the difference between starting a conversation with our team and managing records in the app.
The short version
An enquiry, or information for your app workflow.
Respond to your request or provide the service.
Access and disclosure follow defined needs and legal obligations.
A guide to the full document below, not a replacement for it.
Draft for review · These pages are not final legal notices. Legal review and confirmation of service and data-handling details are required before launch.
This draft covers the NirmanSite website and app provided by Hornbook Technologies. Enquiries and app information serve different purposes. Before launch, confirm the responsible legal entity and privacy or grievance contact.
The form asks for your name, with optional mobile number, email address and a short description of what you would like help with. The current form prepares an email locally in your browser; it does not submit to a lead database. Your email provider processes the message when you send it. Hornbook receives what you send to respond to your enquiry.
Depending on the features used, app information may include account, organisation, project, worker, attendance, Kharchi, wage, expense, materials, progress and related records. The final policy must match the actual fields, attachments, technical logs and permissions implemented.
Enquiry information supports requirements discussions and related contact. App information supports customer-requested functions and operation of the service. Additional purposes, analytics or promotional communications must be described where applicable. This draft does not authorise unspecified uses.
Customers should enter information only with appropriate authority and a lawful basis, and provide notices required for their use of worker or third-party information. Do not include worker records, financial documents or sensitive information in website enquiries.
Access should be limited to authorised users and personnel or providers who need it for stated purposes. The final policy must identify actual hosting, communications and other processing providers, their roles and relevant international transfers. No unverified hosting location or exclusive-access claim is made.
Enquiry retention, account closure, operational record retention, backup expiry and deletion procedures must be confirmed before publication. Information may need preservation under a legal obligation or valid request. Immediate deletion is not promised.
Safeguards must reflect the actual architecture and access model. No online system can guarantee absolute security. Information may require preservation or disclosure in response to valid legal requirements. Final wording must reflect implemented safeguards and incident-handling obligations without unsupported certifications.
Contact the team about your information, corrections, contact preferences or applicable privacy rights. Requests concerning information managed by a customer organisation may need coordination with that organisation. Rights and exceptions depend on applicable law; finalise the process and responsible contact before launch.
Confirm providers, retention periods, privacy contacts, applicable requirements and an effective date before launch. Publish material changes clearly. This draft is for review, not a declaration that privacy compliance obligations have been completed.
Questions? contact@hornbooktechnologies.com
Contact the NirmanSite team →