Privacy Policy
WFM is a workforce management platform for registered companies. Each company manages its own employees, offices, attendance rules, and feature settings. The app is for authorized employees and administrators of those companies. It is not a public social network, and it is not directed at children. By installing or using the app, you acknowledge that you have read this policy. If you do not agree, do not use the app.
1. Who this policy applies to
This policy applies to people who use the mobile app and to authorized staff who view employee data in the web administration tools. The app is intended for workplace use by people 18 or older.
2. Information we collect
We collect information needed to record attendance, verify identity where your company requires it, support field work, assign tasks, and administer employment workflows. What is collected depends on your role and on the features your company turns on.
2.1 Account and profile
- Name, employee ID, email address, phone number, and job designation
- Company, office, division, and reporting line
- Profile photo, if one is uploaded
- Password, stored on our servers only as a hash
- Role, permissions, and settings assigned by your company, including whether face verification is required for your account
2.2 Attendance, leave, and tasks
- Check-in and check-out time, attendance type, and status
- Office and field attendance photographs
- Field session status and the locations recorded during that session
- Leave requests, balances, and approval records
- Attendance correction requests and supporting photos or documents
- Proxy attendance, where your company allows another authorized person to record attendance for you
- Tasks assigned to you or by you, including title, notes, schedule, status, optional site coordinates, and photos attached to a task
- Points, badges, or achievements, if your company enables them
2.3 Location
- Office attendance. GPS coordinates at check-in or check-out, used to check that you are inside your assigned office area.
- Field attendance. Location points while a field session is active, including latitude, longitude, accuracy, time, movement status, and device battery level.
- Background location. Collected only during an active field session, and only if you grant background location permission. A session stops when it ends, when your company closes it, or when the maximum tracking time is reached. The default maximum is 3 hours. If your company sets a post-checkout window, location may continue for that short period after check-out (30 minutes by default) and then stop.
- Shared location. Coordinates and an optional note or photo when you choose to share your current location with authorized personnel.
- Task site pin. Optional coordinates saved when a task is given a work location.
Location points recorded while the phone is offline may stay on the device until the network is available, and are then uploaded.
2.4 Face data
Face verification is used only for employees whose company has turned it on. Other employees do not enroll a face and do not submit a verification selfie for matching. Face data is used to confirm that the person checking in or out is the enrolled employee, and to reduce buddy punching. It is not used for advertising, marketing, or to identify members of the public.
2.4.1 On-device face detection
Before a photograph is accepted, the app checks it on the phone. On Android this check uses Google ML Kit Face Detection included in the app. On iOS it uses Apple’s Vision framework. The check confirms that exactly one face is in the frame, that the face is large enough, and that the eyes appear open. It does not identify who you are. For this check, the photograph is processed on the device and is not sent to Google or Apple.
2.4.2 Enrollment and identity matching
If your company requires face verification, we collect:
- Three enrollment photographs: one facing the camera, one turned left, and one turned right. You can take them with the camera or choose them from your photo library.
- A new selfie at check-in and at check-out, compared with your enrollment.
- Mathematical face embeddings (numeric vectors) produced from the enrollment photographs.
- The match result, a confidence score, how many faces were detected, and related audit details such as the time of the check.
Identity matching is done on servers operated for WFM. Our application sends the photograph to a facial-recognition service that we run for this platform. That service uses the InsightFace model to create an embedding or to compare a selfie with embeddings we already store. We do not send face photographs or embeddings to Google Cloud Vision, Amazon Rekognition, or any other third-party face-identification service. Google ML Kit and Apple Vision are used only for the on-device quality check described above.
2.4.3 What is stored, who can see it, and how it is deleted
- The three enrollment photographs are stored only until they have been processed. Once all three face embeddings are created successfully, those photographs are deleted from our servers. They are not shown in the employee app after that. Only the embeddings are kept for later matching.
- While a submission is still waiting for review, or if enrollment fails, the photographs remain so an administrator can review them and you can replace them. A failed or pending submission can be deleted, including its photographs.
- Authorized administrators can see enrollment photographs only while they still exist. After a successful enrollment they see that the photos were removed and that the face template remains.
- If enrollment photographs are replaced, the previous template is discarded and new embeddings are created from the new photographs. Those new photographs are deleted again after the new embeddings succeed.
- Check-in and check-out selfies used for matching are kept until the image retention period in section 7, then deleted. The attendance record (date, time, and verification result) is kept. To remove an approved face template, ask your company administrator.
- Face photographs and embeddings are not sold, not used for advertising, and not used to train a model for any other customer.
App unlock is separate. If you turn on a PIN or Face ID / fingerprint unlock, that check is performed by your phone’s operating system. Your PIN is stored only on the device, as a hash, and is not sent to our servers. We do not receive the face or fingerprint template your phone uses for screen unlock.
2.5 Device and technical data
- A SHA-256 hash of device model and operating-system build identifiers, used to bind the account to one authorized phone. We do not store the raw hardware serial number.
- Device name, whether the device is Android or iOS, and the time it was registered
- An Expo push token so we can deliver work alerts. On Android, delivery uses Firebase Cloud Messaging. On iOS, delivery uses Apple Push Notification service.
- App version, operating system, and technical logs needed for security and troubleshooting
The app does not request microphone access and does not record audio.
2.6 Photos you choose to add
With your permission, the camera or photo library may be used to:
- Capture attendance selfies
- Upload a profile photo
- Submit the three face-enrollment photographs
- Attach photos to a field session, a correction request, a task, or a location share
3. How we use information
- Sign you in and keep the account tied to an authorized device
- Record and report attendance for your company
- Verify identity with face matching where your company requires it
- Record field routes during an active field session
- Assign and track tasks
- Process leave, corrections, approvals, and notifications
- Show maps of work locations to you and to authorized managers
- Produce attendance and workforce reports for authorized managers and administrators
- Detect misuse, such as a check-in from an unregistered device or a selfie that does not match the enrolled employee
- Keep audit logs and fix reliability and security issues
4. App permissions
A feature that needs a permission will not run unless you allow it:
- Location, including background location. Office geofence checks, and field tracking during an active field session.
- Camera. Attendance selfies, enrollment photos, and work photos. Audio recording is not used.
- Photo library. Choosing an existing image for your profile, enrollment, or a supporting attachment.
- Notifications. Attendance reminders, approvals, and other work alerts.
- Biometrics (Face ID, fingerprint). Optional app unlock on the device only. This is not attendance face verification.
- Foreground service (Android). Shows an ongoing notification while field location tracking is running.
You can revoke a permission in the phone’s settings. The related feature may then stop working. Your company may still require that feature for attendance.
5. How we store and protect data
- Account, attendance, location, task, and face-verification data are stored on servers operated for WFM, reached through https://wfm.sktv.world.
- Each company’s employee data is administered in that company’s workspace. Administrators of one company do not get access to another company’s employees through the product.
- Sign-in tokens and basic profile details may be stored on your phone so you stay signed in.
- Traffic between the app and our servers uses HTTPS.
- Access to employee records is limited to authenticated users whose role allows it, including your company’s administrators, HR staff, and managers in the reporting line.
6. Sharing
We do not sell personal information.
We share information only as needed to run the workplace service:
- With authorized administrators, HR staff, and managers in your company
- With infrastructure, map, and notification providers that process data on our instructions to host the service, draw maps, or deliver push alerts
- With a court, regulator, or law enforcement when the law requires it
Third-party services that may process data are:
- Google Maps Platform. To display maps. When a map is shown, location coordinates needed to draw that map may be processed by Google.
- Expo, Firebase Cloud Messaging, and Apple Push Notification service. To deliver push notifications to your device token.
Face photographs and face embeddings are not shared with those providers for identification. On-device face detection does not upload the photo to Google or Apple. Identity matching stays on the facial-recognition service we operate for this platform.
7. Retention
- Attendance and field photographs, correction attachments, and location-share photos. Deleted after the image retention period. The default is 45 days. An administrator can set a different period. The attendance record (date, time, and verification result) remains.
- Field location trails. Deleted after the location retention period. The default is 60 days. An administrator can change it.
- Task photos. Deleted 75 days after they are stored. The task record can remain.
- Enrollment photographs. Deleted as soon as the face embeddings are created successfully. They are not part of the selfie cleanup schedule because they are removed at enrollment time. If enrollment has not succeeded, the photographs stay until they are replaced, deleted, or successfully processed.
- Face embeddings. Kept while face verification remains part of your employment record. An administrator can delete the enrollment, which removes the template. You can delete a submission that is still pending or rejected.
- Audit logs and in-app notifications. Kept for about 60 days by default, then deleted.
- Account and attendance records. Kept for as long as your company needs them for employment, payroll, audit, or legal duties, including after you stop using the app.
8. Your choices and rights
Depending on applicable law, including India’s Digital Personal Data Protection Act, 2023, you may ask to access your personal information, correct it, withdraw consent where consent is the legal basis, or request deletion or restriction. You may also complain to the relevant data protection authority.
This is an employer-provided system. Some requests have to go through your company’s HR or IT administrator. Attendance records, and approved face embeddings while verification is required for your role, may be kept for employment and legal duties even if you ask for deletion or stop using the app.
To make a request, use the contact details in section 11. Include your name, employee ID, and company.
9. Children
The app is a workplace tool for authorized personnel. We do not knowingly collect personal information from anyone under 18.
10. International processing
Information is processed on infrastructure used to operate WFM. If a provider such as a map or notification service processes data outside your country, we take reasonable steps to put appropriate safeguards in place.
11. Contact
For questions about this policy or your personal data, contact your company administrator first. For platform-level questions, use the support page.
WFM
Privacy policy: https://wfm.sktv.world/privacy-policy
Support: https://wfm.sktv.world/support
Website: https://wfm.sktv.world
12. Changes
We may update this policy. The “Last updated” date at the top will change when we do. If a change is material, we will also notify users through the app or another appropriate channel. Continued use of the app after the update takes effect means you accept the updated policy.