Privacy Policy

LavaHub, our middleware, passes data, location, and the master image to the integrated backend system. It does not trace or save identifiable or unidentifiable information except operational logs stored on Azure. The actual data is stored on the backend systems.

The device camera is used for facial recognition only while attendance functionality is being used to perform attendance actions. The user controls this action. The captured photo is not stored; it is compared with the master image already stored on the backend system to verify the user.

The phone contact list is used for the digital business card module. Uploaded contacts are synced to the user's account across logged-in devices, under the user's control.

Attendance actions can follow one of two tracking modes configured by the backend system.

• Restricted: the attendance action is taken within the range saved on the backend system.
• Flexible: the attendance action is taken and verified from anywhere for the app user.

LavaLoon, as the provider of LavaDo, does not save user data except data related to the LavaCard business card module. Business card data is encrypted at rest and is not shared or traded with third parties.

For all other data, such as HR attendance data, LavaHub passes the data, location, and master image to the integrated backend system. It does not trace or save identifiable or unidentifiable information except operational logs stored on Azure. The actual data is stored on the backend systems.