Your information at work
Privacy policy
What HRMS handles, how work features use it, and the choices available to you.
1. Who this covers
Farming Hub HRMS supports employees and authorised workplace users with attendance, leave, payroll, documents, communication and field work. Accounts and access are managed by the organisation. This policy covers the HRMS web application and Android app, including the web pages loaded inside the app.
The information available to you depends on your role and the features your organisation enables. Some records are entered by HR or another authorised employee; others are submitted by you.
2. Information handled and why
- Account and employment information
- Name, username, employee code, contact details, addresses, role, employment history and other employee details support account management and HR administration. Records may include date of birth, family or emergency-contact details, government identifiers and blood group when supplied for the employee record.
- Pay and work records
- Attendance, leave, salary, bank and statutory identifiers, loans, expenses, reimbursements and related documents support payroll, employment administration and operational reporting. The app can display records already held by your employer and accept entries from authorised users.
- Location and field work
- Precise coordinates, accuracy, timestamps, visit information and device details support location-based attendance, customer visits and navigation. Field/WFH tracking is a separate session you start, with location permission. Stop that session separately to stop its continuing location collection. A feature that requires location may be unavailable if permission is denied.
- Photos, files and submitted content
- Profile pictures, attendance or visit photos, receipts, documents, signatures, chat messages, posts, work notes and attachments support the features where they are submitted. HR may also upload employee documents. Free-text fields and attachments can contain information you choose to provide.
- Meetings and voice features
- Meeting participation uses your identity and room information. If you enable your microphone or camera, audio or video is sent through the meeting service to participants. Voice typing and meeting transcription are separate optional features. Consented meeting recordings remain in browser memory until the meeting ends, then audio is sent for transcription; transcript text and generated summaries can be stored in HRMS. Availability depends on the installed app, permissions and service configuration.
- Device and security information
- Login/session records, network address, device/browser details, permission status and audit events help authenticate users, secure access and operate the service. Optional device monitoring also uses an installation/device identifier, model, OS/app version and connection status.
3. Monitoring and your controls
Device monitoring is off unless your organisation enables it for your employee account. On supported Android builds, you must also accept the in-app disclosure before monitoring starts. Choose Not now to keep using HRMS without enabling it. New disclosure versions or additional collection categories require a new choice.
When enabled and accepted, monitoring may report screen-lock/inactive status and device health such as battery, memory, storage, network type and security signals. It supports workforce reporting and device security/compliance. A visible Android notification is required. Use Pause monitoring to stop it until you choose Resume monitoring. Logging out stops monitoring; pausing monitoring does not stop an independent field-location session.
The Google Play edition does not collect call logs or other apps’ usage history through device monitoring. The separately distributed private edition can, with accepted categories and applicable permissions, report current app names, new app/screen/unlock events and call metadata such as phone number, contact name, direction, time, duration and estimated ring duration. Device monitoring does not record call audio or read message content. These limits do not prevent you from deliberately joining a meeting or submitting a message.
Older Android builds need an app update before enabling the new monitoring consent controls. Android monitoring does not share your screen. Browser screen preview is separate: you approve the request and choose a screen/window, and can decline or stop sharing. Preview frames are held in memory for the active session, rather than saved as a recording.
4. Connected services
HRMS uses connected services for certain features. Which optional services are available depends on the organisation’s configuration. Information does not necessarily remain only on Farming Hub servers.
- Maps and navigation: map views request tiles from OpenStreetMap or Esri. Reverse geocoding sends coordinates to Nominatim; navigation sends your current and destination coordinates to the configured routing service, with an OpenStreetMap-based OSRM service as the default. These services can receive network/request information.
- Meetings: the configured Jitsi service receives room and participant information and carries meeting media when you join and enable those controls.
- Speech and summaries: when configured, Groq processes submitted audio for transcription and text for language conversion or meeting summaries. HRMS processes speech uploads in memory; this is not a promise about the provider’s retention.
- Optional AI assistant: when an administrator enables the configured Gemini integration, questions, recent conversation and authorised HRMS information retrieved to answer a question can be sent to that provider.
- Email and messaging: configured email accounts use their mail providers for messages and attachments. Enabled notification channels and WhatsApp integrations can send relevant contact details and message content, including configured administrator login codes.
- Files and integrations: documents may be stored locally or in configured Google Drive folders. Administrator-configured webhooks and API integrations can exchange permitted business records with their configured destinations.
Contact HR to ask which services apply to your organisation and how they handle the information involved. A feature being available in the application does not mean that every optional integration is enabled for your account.
5. Storage and access
HRMS stores work records in its database and files in configured storage. Authentication, role permissions and company/employee scope restrict access. The public HRMS service uses HTTPS; connected services and their storage or transport arrangements depend on their configuration. This policy does not claim end-to-end encryption or that every possible integration uses the same protections.
Use account and device controls to protect access. Do not send passwords, one-time codes or full financial/identity documents in a general privacy enquiry.
6. Retention, correction and deletion
Account access and employment records are managed separately. Logging out, pausing monitoring or disabling a login does not automatically delete existing work records. There is no single automatic expiry for all HRMS data.
You can ask HR to correct information, delete selected data, or delete your account and associated data. Requests are reviewed manually, including identity verification and the records concerned. Some employment, payroll, statutory, security or audit records may need to be retained where required. Ask HR which records can be deleted, which must be retained and the applicable retention basis; no fixed deletion period is promised here.
Feature-specific deletion controls do not necessarily remove every related file, historical record or provider copy. A request is not the same as completed deletion.
Request account or data deletion7. Contact HR
For privacy questions, access or correction requests, and account/data deletion requests, contact Farming Hub HR:
Using HRMS alone does not consent to optional device monitoring.