ORPLUM HRM mobile app.
What the ORPLUM HRM app collects from employees who check in with it, why, where it is kept and the choices you have – including how optional face recognition works.
This notice is specific to the ORPLUM HRM mobile app (Android package com.orplum.attendance; iOS edition when available) and the attendance service it connects to. It supplements our general privacy notice, which covers this website and the ORPLUM platform as a whole. Where the two differ for something the app does, this notice applies.
Who is responsible for your data
Your employer (the organisation that invited you to the app) decides why and how your attendance data is processed. In data-protection terms it is the controller. It chooses which features are on – face check-in or a PIN instead, geofencing, evidence photos, kiosk tablets – and it is your first point of contact for questions and requests about your data.
ORPLUM builds and hosts the app and the HR system behind it. We process your data only on your employer's instructions as its processor (service provider), under a written agreement with the employer. We do not use your data for our own purposes, we do not sell it and we do not use it for advertising.
What the app collects
| Data | What exactly | Why |
|---|---|---|
| Account | Your name, employee ID, work email and/or phone number, role, department and site – entered by your employer's HR, not by you. A sign-in token kept on your device. | To know whose attendance is being recorded and to sign you in. |
| Attendance records | Date and time of each check-in and check-out, direction, how it was made (own phone, kiosk, assisted by a colleague, PIN), the device used, your IP address at the time and any flags the system adds (for example "outside the geofence" or "late"). | Attendance, timesheets, shift and overtime rules set by your employer. |
| Face data (only if your employer uses face check-in) | Described in full below: a mathematical face template (512 numbers) computed on the device from your enrolment photos and at each face check-in, the enrolment sample photos themselves and – if your employer turns it on – a small photo taken at the moment of each check-in as evidence. | To verify that it is really you checking in and to let HR review disputed punches. |
| Precise location | Your GPS position at the moment you tap check-in or check-out on your own phone, when your employer requires you to be at a work site (geofence). Location is never read in the background, when the app is closed or at any time other than the punch itself. Kiosk tablets do not use location. | To confirm you are at the work site your employer defined. |
| Presence proofs | Where your employer enables them: whether the internet address your phone connects from belongs to the office network your employer registered, and whether a kiosk tablet's Bluetooth beacon is in range. Bluetooth is used only to detect the employer's own tablet; the app declares to Android that it never uses Bluetooth to derive your location. | Alternatives to GPS for proving you are on site. |
| Photos | Evidence photos at check-in (see above) and, for enrolment, the face sample photos you take. Nothing from your photo library is read unless you pick a file yourself, for example to attach to a message to HR. | Verification and HR review. |
| Voice notes and messages | Text, voice recordings and attachments you choose to send to HR through the Questions feature. The microphone is used only while you hold the record button. | To deliver your message to HR. |
| Device and app information | Phone model, OS version, app version, push-notification token and language. For kiosk tablets additionally: a device identifier used to bind the tablet to your employer's account, battery level and temperature, and a camera health status – all about the tablet, not about any person. | Security (one account per device), updates, push notifications, keeping shared tablets running. |
Face recognition – how it works and your choice
Face check-in is optional for the employer; many organisations use the app with a PIN or a plain tap instead. When your employer does enable it:
- Enrolment. You (or HR, with you present) take a few photos of your face in the app. On the device, the app finds the face and converts it into a template: 512 numbers that describe facial geometry. The template cannot be turned back into a picture of you. The enrolment photos and templates are sent to your employer's account and must be approved by HR before face check-in works.
- Check-in. The camera image is analysed on the device (Google ML Kit face detection running locally and an on-device neural network); no video or images are sent to Google or any AI provider. The new template is compared with your approved templates. On your own phone the server repeats the comparison as a safeguard; on a kiosk tablet the comparison happens on the tablet against templates it has downloaded for the staff at that site.
- Liveness checks. To stop photos or videos being used instead of a real person, the app may ask you to blink or turn your head, briefly flash colours on the screen and run an on-device "real face" scoring model. The resulting scores are stored with the punch.
- Learning. When a check-in matches with high confidence, your employer's settings may allow the server to keep that template as an additional reference so recognition stays reliable as your appearance changes. These are capped per person and replaced automatically.
- Storage. Templates are stored encrypted (authenticated encryption, key kept outside the database) in your employer's isolated tenant. Enrolment samples and evidence photos are kept in private cloud storage reachable only through short-lived signed links, visible only to your employer's authorised HR users.
- Your choice. Where the law requires consent, your employer records it in the app before enrolment (date, device, notice version). Your employer must offer a non-biometric way to record attendance for anyone who does not want to use face check-in. You can ask HR to delete your templates at any time; switching an organisation to "no biometric check" permanently erases every template and sample photo for that organisation.
Face templates are biometric data under the UK and EU GDPR, the Illinois Biometric Information Privacy Act and similar laws. Your employer is responsible for the notices, consents and retention schedule those laws require; this notice describes what the technology does so that those notices can be accurate.
Legal basis
Your employer determines the legal basis for processing. Typically: performance of your employment contract and the employer's legitimate interest in accurate attendance; the employer's legal obligations for payroll and working-time records; and, for face data, your explicit consent and/or the employment-law conditions available in your jurisdiction, as documented by your employer. Where consent is the basis, refusing or withdrawing it must not disadvantage you, and the non-biometric alternative applies.
Where your data is stored and how it is protected
- Hosting: Amazon Web Services, US West (Oregon), United States. Employers outside the United States are informed of this in their service agreement and rely on the applicable transfer mechanism (for example the UK International Data Transfer Addendum or the EU Standard Contractual Clauses).
- Every organisation's data is held in a separate, isolated tenant; one employer can never see another's data.
- All traffic between the app and our servers uses TLS (HTTPS); the app refuses unencrypted connections.
- Face templates are encrypted at rest with authenticated encryption, with the key kept outside the database; photos and voice notes are in private storage reachable only through signed, expiring links.
- Access by ORPLUM staff is limited to what is needed to operate and support the service, is logged, and never includes decrypting face templates for any purpose other than the matching described above.
- Shared kiosk tablets hold only the templates of the staff at that site, in the app's private storage that other apps cannot read; revoking a tablet in the HR system erases them from the tablet at its next contact and locks it out.
Who else sees your data
We share data only with the service providers needed to run the app, each bound by contract to process it solely for us:
| Provider | Purpose | Data |
|---|---|---|
| Amazon Web Services | Servers, database, file storage, email delivery | All data described above, protected as described |
| Google Firebase Cloud Messaging | Push notifications | Push token and the notification text (for example "HR replied to your question"). No face, location or attendance data. |
| Google Play / Apple App Store | App distribution and crash statistics | Standard store telemetry under Google's and Apple's own policies |
We never sell personal data, never share it for advertising and never give face data to third parties. Face detection and recognition run on the device; no images leave it for recognition purposes. We may disclose data if required by law, after informing your employer where permitted.
How long data is kept
- Attendance records: for the period your employer sets, usually the statutory payroll or working-time retention period in its country.
- Face templates and enrolment photos: until your employer deletes your employee record, removes your face data or turns face check-in off for the organisation – each of which erases them permanently. Learned templates are capped per person and replaced automatically.
- Evidence photos at check-in: only collected when your employer turns the option on, and kept with the attendance record for the retention period above.
- Messages and voice notes to HR: until your employer deletes them or your account is removed.
- Technical logs (IP addresses, device information, errors): up to 90 days.
- When an employer ends its subscription, its data is exported or deleted as described in our general notice.
Your rights
Depending on where you live, you may have rights to access, correct, delete or receive a copy of your data, to object to or restrict processing, to withdraw consent and to complain to a supervisory authority (in the UK the ICO; in the EU your national authority; in US states the relevant attorney general). Please contact your employer's HR team first – they control your account and can act on most requests directly in the HR system (view your records, delete face data, export, remove the account). We assist employers with every request and forward any request we receive to your employer promptly. Accounts are created and removed by your employer; you cannot delete an account from inside the app, but you can remove the app and its data from your device at any time, and asking HR to remove your account deletes your profile, face data and login.
Children
The app is for employees and contractors aged 18 or over and is not directed at children. We do not knowingly collect data from anyone under 18.
Device permissions the app asks for
| Permission | Used for |
|---|---|
| Camera | Face enrolment and check-in, evidence photos; kiosk tablets keep the camera on while in kiosk mode to notice when someone steps up. |
| Location (precise, while using the app) | Geofence check at the moment of a punch from your phone. Never in the background. |
| Nearby devices / Bluetooth | Detecting the employer's kiosk beacon (phones) or advertising it (tablets). Declared as "never for location". |
| Microphone | Voice notes to HR, only while recording. |
| Notifications | Replies from HR and shift reminders. |
| Photos / files | Only when you choose to attach a file to a message. |
| Display over other apps, start at boot | Kiosk tablets only: lets a shared tablet return to the attendance screen after a power cut or restart. Never requested on an employee's phone. |
Changes
We will post any revision here with a new effective date. Material changes – for example a new category of data or a new sub-processor – are announced to employers in advance so they can inform their staff.
Questions
Email sales@orplum.com or write to ORPLUM, 12611 Hiddencreek Way, Cerritos, CA 90703, USA. For anything about your own records, start with your employer's HR team.