PRIVACY POLICY – LAZYMONKYAI EMP APP
Effective Date: 01 April 2025 Last Updated: 20 August 2026 Version: 1.1.0
Application: LazyMonkeyAI EMP App Organization: LazyMonkeyAI Privacy Contact: info@lazymonkyai.com
1. INTRODUCTION
LazyMonkeyAI EMP App (“App”, “Application”, “we”, “our”, or “us”) is an employee, workforce, attendance, field-activity, institution-inspection, and operational management application intended for authorized employees, officers, supervisors, administrators, inspectors, field personnel, and other authorized users.
The App may provide functionality including:
Employee authentication.
Employee profile management.
Attendance management.
GPS/location-based attendance verification.
Field visit management.
Institution inspection.
Inspection photographs and supporting evidence.
Work/activity reporting.
Document uploads.
Task and work management.
Operational dashboards.
Management reports.
Administrative monitoring.
Identity and attendance verification.
This Privacy Policy explains what information may be accessed, collected, transmitted, processed, stored, retained, shared, and deleted when an authorized user uses the App.
We recognize that employee information, precise location, photographs, inspection records, and identity-verification information may be sensitive. Accordingly, the App is designed to process such information only for legitimate organizational and operational purposes.
2. WHO THIS PRIVACY POLICY APPLIES TO
This Privacy Policy applies to authorized users of the LazyMonkeyAI EMP App, including:
Employees.
Officers.
Supervisors.
Inspectors.
Field personnel.
Managers.
Administrators.
Other users authorized by the organization.
The App is not intended for general public use.
Where the App is deployed by an organization for its employees, the organization may determine the specific purposes, access permissions, retention requirements, and operational policies applicable to employee information.
LazyMonkeyAI may provide the technology platform, application, infrastructure, hosting, maintenance, and technical support services.
3. INFORMATION WE COLLECT
Depending on the modules enabled by the organization, the App may collect or process the following categories of information.
3.1 Employee Information
Employee name.
Employee ID.
Employee code.
Mobile number.
Email address.
Designation.
Department.
Organization.
District/region.
Office/institution.
Employee status.
Reporting authority.
Work-related information.
User account information.
3.2 Attendance Information
Attendance date.
Check-in time.
Check-out time, where applicable.
Attendance status.
GPS coordinates.
Location accuracy.
Workplace/institution.
Attendance verification result.
Approval/rejection status.
Exception or remarks.
3.3 Location Information
Latitude.
Longitude.
GPS accuracy.
Date and time of location capture.
Attendance location.
Field-visit location.
Institution-inspection location.
3.4 Camera and Image Information
Where enabled:
Profile photographs.
Attendance verification images.
Identity-verification images.
Institution inspection photographs.
Field-visit photographs.
Work-related photographs.
Supporting evidence photographs.
Documents captured using the camera.
3.5 Device and Technical Information
Device model.
Operating system.
OS version.
Application version.
Technical identifiers where required.
Error information.
Crash information.
Diagnostic information.
Login/session information.
4. WHY THE APP USES PHOTOGRAPHS AND IMAGES
One of the primary purposes of image collection in the App is to document legitimate employee and organizational activities.
Images may be captured for:
Employee profile photographs.
Attendance verification.
Identity verification.
Institution inspections.
Field visits.
Infrastructure verification.
Asset verification.
Facility-condition documentation.
Inspection evidence.
Supporting work reports.
Documentation of deficiencies or observations.
Proof of work performed.
Other authorized organizational activities.
Images are not collected merely for general-purpose photo access.
The App seeks to access images only when the relevant functionality requires them.
5. IMPORTANT: HOW INSPECTION IMAGES ARE HANDLED
Institution and field inspection images are treated as work-related records.
When an authorized user captures an image during an inspection, the image may be associated with:
Employee/inspector ID.
Institution ID.
Institution name.
Inspection ID.
Inspection date.
Inspection time.
GPS location.
Inspection category.
Inspection findings.
Inspection remarks.
Other relevant inspection information.
This association allows the organization to determine when, where, by whom, and for which institution the photograph was submitted.
Inspection photographs may therefore form part of an official inspection or operational record.
6. ARE INSPECTION IMAGES SAVED?
6.1 Images Submitted Through the App
When an authorized user intentionally captures or selects an image and submits it as part of an inspection or work-related activity, the image may be transmitted to the application's authorized backend/server infrastructure.
Once successfully submitted, the image may be stored as part of the relevant organizational record.
The image may therefore remain available after the user closes the App or removes the image from the device.
6.2 Why Images May Be Stored
Images may be stored to:
Maintain an inspection record.
Verify inspection activities.
Support audit requirements.
Review inspection findings.
Allow authorized supervisors to verify submissions.
Generate inspection reports.
Compare current and previous inspection conditions.
Support follow-up actions.
Maintain organizational records.
Investigate disputes or fraudulent submissions.
6.3 Images Are Not Automatically Stored Merely Because the Camera Opens
Opening or using the camera does not by itself mean that every photograph taken with the device becomes part of the organization's database.
Images are intended to become an organizational record when the user captures/selects and submits them through the relevant App functionality.
7. ARE IMAGES SAVED TO THE USER'S PHONE GALLERY?
The App's handling of device photographs depends on the operating system and implementation of the specific feature.
Where the App captures an image directly through its camera interface, the image may be temporarily processed by the App for submission.
The App does not intentionally copy every inspection photograph into the user's personal photo gallery unless such functionality is explicitly implemented.
Where a user selects an existing photograph through the device's photo picker or file-selection mechanism, the App accesses the selected item for the requested operation rather than obtaining unrestricted access to the user's entire personal photo library.
The App does not intentionally scan or collect unrelated personal photographs.
8. DOES THE APP ACCESS ALL PHOTOS ON THE DEVICE?
No.
The App's intended use of photographs is limited to legitimate application functionality.
Where the operating system provides a system photo picker or equivalent mechanism, the App may allow the user to select a specific photograph rather than requiring unrestricted access to the entire photo library.
The App does not intentionally:
Scan the user's complete personal gallery.
Build a personal photo database.
Collect unrelated photographs.
Upload unrelated personal photographs.
Analyze unrelated photographs for advertising.
Sell photographs to third parties.
Apple specifically emphasizes data minimization and recommends using out-of-process pickers where possible instead of requesting broad Photos access. Google has likewise restricted broad Android photo/video permissions where occasional access is sufficient.
9. WHERE ARE IMAGES STORED?
Submitted images may be stored in the application's authorized backend infrastructure.
Depending on the organization's deployment and technical architecture, this may include:
Application servers.
Secure cloud infrastructure.
Object/file storage.
Database-associated storage.
Backup infrastructure.
Images are not intended to be stored in publicly accessible locations.
Access to stored images is restricted through application authentication and authorization controls.
10. WHO CAN SEE INSPECTION IMAGES?
Inspection images may be accessible only to authorized users based on organizational roles and permissions.
Depending on the organization's configuration, authorized personnel may include:
The employee who submitted the inspection.
Assigned supervisor.
Authorized inspecting officer.
Department administrator.
District/region administrator.
Authorized management personnel.
Authorized technical administrators where required for system support.
The App does not make inspection photographs publicly searchable.
Inspection photographs are not intended to be shared through public social-media platforms or publicly accessible websites.
11. CAN LAZYMONKYAI EMPLOYEES SEE THE IMAGES?
Access by technical/support personnel is restricted to legitimate operational requirements.
Where technical support, troubleshooting, security investigation, maintenance, backup management, or system administration requires access to application data, access may be controlled through appropriate authorization mechanisms.
Technical personnel are not permitted to use employee or inspection photographs for personal, advertising, marketing, or unrelated commercial purposes.
12. ARE IMAGES SHARED WITH THIRD PARTIES?
We do not sell inspection photographs, employee photographs, or work-related images.
Images may be processed by infrastructure or service providers where technically necessary to provide the App's functionality, such as:
Secure hosting.
Cloud storage.
Backup.
Infrastructure management.
Security.
Technical support.
Such providers are expected to handle information only for authorized service-related purposes.
Images are not intentionally shared with:
Advertisers.
Marketing companies.
Data brokers.
Social-media companies for advertising.
Facial-recognition companies for commercial profiling.
13. ARE IMAGES USED FOR AI TRAINING?
Images submitted through the App are collected for the specific organizational purposes described in this Privacy Policy.
They are not intended to be used to train general-purpose commercial artificial-intelligence models or sold as datasets.
Inspection photographs are not intended to be repurposed for unrelated AI model training without an appropriate legal basis, authorization, disclosure, and where required, user consent.
14. ARE IMAGES USED FOR FACIAL RECOGNITION?
An image submitted for an institution inspection is not automatically treated as biometric information merely because the image may contain a person.
Inspection images are intended to document the relevant institution, facility, equipment, infrastructure, or work activity.
Where the App separately provides authorized employee face/identity verification, that processing is governed by the Face Data section of this Privacy Policy.
Inspection photographs are not intentionally processed to create commercial facial-recognition profiles.
15. FACE DATA AND BIOMETRIC INFORMATION
Where face-based attendance or identity verification is enabled, the App may use the camera to capture a live image or image sequence for authorized identity verification.
The purpose may include:
Employee identity verification.
Attendance verification.
Fraud prevention.
Unauthorized-access prevention.
The App does not intentionally create or maintain:
Commercial facial profiles.
Facial advertising profiles.
Facial-recognition databases for unrelated purposes.
Biometric identifiers for sale.
Where the actual deployed implementation performs only temporary face processing and does not store biometric templates, such processing is discarded after completion of the relevant verification process.
Important technical requirement: This statement must match the actual implementation. If the backend stores face images, embeddings, templates, or other biometric information, this section must be revised before publication.
16. IMAGE RETENTION PERIOD
Inspection photographs and other submitted images may be retained for as long as reasonably necessary to fulfill the purpose for which they were collected.
Retention may depend on:
Organizational policy.
Inspection requirements.
Audit requirements.
Legal requirements.
Regulatory requirements.
Dispute resolution.
Security investigations.
Historical inspection comparisons.
Record-management requirements.
Images may therefore remain available after an inspection has been completed.
They are not automatically deleted immediately after submission.
When the applicable retention period expires, images may be deleted, anonymized, archived, or otherwise disposed of according to applicable organizational and technical procedures.
17. WHY IMAGES MAY NEED LONGER RETENTION
Inspection photographs may be retained for legitimate reasons such as:
Demonstrating that an inspection occurred.
Supporting official inspection reports.
Tracking deficiencies.
Monitoring corrective actions.
Comparing conditions over time.
Responding to complaints.
Conducting internal audits.
Meeting record-retention requirements.
Investigating suspected fraudulent reporting.
Supporting legal or regulatory requirements.
Therefore, users should understand that a photograph submitted as official inspection evidence may become part of an organizational record.
18. CAN A USER DELETE AN IMAGE AFTER SUBMISSION?
Depending on the organization's workflow, users may or may not be able to directly delete an image after submission.
Once an image becomes part of an official inspection record, deletion may be restricted to protect:
Audit integrity.
Organizational records.
Investigation evidence.
Compliance requirements.
Historical inspection records.
Where deletion is permitted, the user may request deletion through the applicable organizational administrator or privacy contact.
Deletion requests may be subject to applicable legal, regulatory, contractual, employment, and record-retention requirements.
19. IMAGE DELETION REQUESTS
A user may contact:
info@lazymonkyai.com
to raise a request concerning an image or other personal information.
The request may require:
User identification.
Employee ID.
Relevant inspection ID.
Institution name.
Approximate date of submission.
Description of the image or record.
We may need to verify the requester's identity before taking action.
Where the information must legally or operationally be retained, the request may be handled in accordance with the applicable retention requirements.
20. WHAT HAPPENS IF AN IMAGE IS ACCIDENTALLY UPLOADED?
If a user accidentally uploads an unrelated or incorrect photograph, the user should report the issue to the organization's authorized administrator or contact:
info@lazymonkyai.com
The organization may determine whether the image can be removed, replaced, restricted, or retained based on applicable policies.
21. IMAGES AND GPS LOCATION
Inspection photographs may be associated with GPS information when the inspection feature requires location verification.
This may allow the organization to determine:
Where the inspection was performed.
When the inspection occurred.
Which employee submitted it.
Which institution was inspected.
Location information is used for operational verification and is not intended for advertising or commercial profiling.
22. IMAGE METADATA
Depending on the device, operating system, camera implementation, and upload process, an image may contain technical metadata.
Such metadata may potentially include:
Date/time.
Device information.
Image dimensions.
Location metadata where provided by the device.
The App may process or remove certain metadata as part of image upload or server-side processing.
Users should not assume that every technical metadata field is removed unless the application's implementation specifically performs such removal.
23. INSTITUTION INSPECTION DATA
The App may collect the following information during an institution inspection:
Institution Details
Institution name.
Institution ID/code.
Address.
District.
Region.
Department.
Institution type.
Registered GPS location.
Inspector Details
Employee name.
Employee ID.
Designation.
Department.
Assigned jurisdiction.
Inspection Details
Inspection date.
Inspection time.
GPS coordinates.
Location accuracy.
Inspection checklist.
Observations.
Findings.
Deficiencies.
Compliance status.
Remarks.
Recommendations.
Follow-up actions.
Evidence
Photographs.
Documents.
Supporting files.
Other authorized evidence.
24. FIELD VISIT DATA
Field visits may include:
Employee information.
Visit date/time.
GPS location.
Institution/worksite.
Purpose of visit.
Work performed.
Remarks.
Photographs.
Documents.
Approval information.
This information is used for workforce and operational management.
25. ATTENDANCE DATA
Attendance records may include:
Employee ID.
Date.
Time.
GPS location.
Workplace.
Device information.
Verification result.
Attendance status.
Approval information.
Attendance records may be retained for organizational administration and audit.
26. LOCATION DATA IS NOT SOLD
We do not sell, rent, or commercially trade employee location information.
Location information is used for legitimate application functionality such as:
Attendance.
Field visits.
Institution inspections.
Work verification.
Operational reporting.
Fraud prevention.
Google classifies precise location as sensitive user data and requires developers to accurately disclose its use. Google also applies additional requirements to background location access.
Apple similarly requires location use to be directly relevant to the app's functionality and requires notification/authorization for location collection.
27. CAMERA PERMISSION
The camera may be used when the user performs a function requiring image capture.
Examples include:
Attendance verification.
Employee verification.
Institution inspection.
Field inspection.
Work evidence.
Profile photograph.
The App does not intentionally activate the camera for advertising, marketing, or unrelated monitoring.
28. PHOTO LIBRARY / FILE ACCESS
Where the App allows users to select photographs or documents, access is limited to the functionality for which the user chooses the file.
The App does not intentionally collect the entire contents of a user's personal photo library.
Where supported by the operating system, the App may use system-provided photo/file selection mechanisms to minimize access to unrelated personal content.
29. DEVICE SECURITY
Users are responsible for protecting the device used to access the App.
We recommend:
Using a device PIN/password.
Keeping the operating system updated.
Keeping the App updated.
Not sharing the device with unauthorized persons.
Not sharing login credentials.
Reporting lost/stolen devices.
Logging out where appropriate.
30. DATA SECURITY
Reasonable security measures may include:
HTTPS/TLS encryption.
Secure API communication.
Authentication.
Role-based access control.
Server-side authorization.
Database security.
Restricted administrative access.
Audit logging.
Security monitoring.
Backup controls.
Access management.
Security updates.
No electronic system can guarantee absolute security.
31. DATA SHARING
We do not sell personal information.
Information may be shared only where necessary with:
Authorized organization personnel.
Authorized supervisors.
Authorized management.
Authorized administrators.
Infrastructure/service providers.
Legal/regulatory authorities where required.
The exact persons who can access information depend on the organization's role and permission structure.
32. THIRD-PARTY SERVICE PROVIDERS
The App may depend on third-party infrastructure providers for:
Cloud hosting.
Database hosting.
File/image storage.
Backup.
Security.
Monitoring.
Crash reporting.
Technical infrastructure.
Where third parties process information, they should provide protections appropriate to the information being processed and use it only for authorized purposes.
Apple specifically requires privacy policies to identify third-party sharing and to ensure that third parties receiving user data provide equivalent protection consistent with the app's stated privacy practices.
33. NO ADVERTISING USE OF EMPLOYEE DATA
The App is not designed as an advertising platform.
Employee:
Name.
ID.
Mobile number.
Email.
Location.
Attendance.
Inspection records.
Photographs.
Face-verification information.
are not intended to be used to create advertising profiles or sell targeted advertising.
34. NO SALE OF IMAGES OR PERSONAL INFORMATION
We do not sell:
Employee photographs.
Inspection photographs.
Location information.
Attendance records.
Institution inspection records.
Employee contact information.
Face-related information.
Work activity information.
35. DATA RETENTION – SUMMARY
36. ACCOUNT DELETION AND DATA DELETION
Where account deletion is applicable, users may request account deletion through the organization or applicable account-management mechanism.
Account deletion may not automatically mean that all historical organizational records are immediately erased.
Records such as:
Attendance.
Inspection reports.
Inspection photographs.
Audit logs.
Compliance records.
may need to be retained where required by applicable organizational, legal, regulatory, security, or audit requirements.
Any deletion process will be handled according to the applicable retention and deletion policy.
Google Play currently requires apps offering account creation to provide a clear and accessible account-deletion mechanism and to delete associated user data when a valid deletion request is made, subject to applicable exceptions. This should therefore be implemented consistently with the actual account model of your app before submission.
37. CHILDREN'S PRIVACY
The App is intended for authorized employees and workforce users.
It is not directed toward children.
We do not knowingly collect information from children for child-directed services.
38. INTERNATIONAL DATA PROCESSING
Depending on the hosting and infrastructure configuration, information may be processed or stored in India or other jurisdictions.
Appropriate technical and organizational safeguards should be maintained for information processed through external infrastructure.
39. DATA ACCURACY
Users and organizations are responsible for providing accurate information.
Users should ensure that:
Inspection photographs correspond to the correct institution.
Inspection findings are accurate.
GPS/location information represents the actual work activity.
Documents are relevant.
Attendance submissions are genuine.
Field activity information is accurate.
False, misleading, or fraudulent submissions may be subject to organizational action.
40. FRAUD AND SECURITY PREVENTION
The App may process information to detect or prevent:
False attendance.
Unauthorized attendance.
Fake field visits.
False institution inspections.
Unauthorized account access.
Duplicate submissions.
Suspicious activity.
Unauthorized changes to records.
Such processing is intended to protect the integrity of organizational records.
41. AUDIT TRAILS
Certain application activities may create audit records.
Audit records may include:
User ID.
Date/time.
Action performed.
Record affected.
Approval/rejection information.
Device or technical information where necessary.
Audit trails help maintain accountability and investigate unauthorized activity.
42. USER QUESTIONS REGARDING IMAGE STORAGE
Q1. Does the App save my inspection photographs?
If you intentionally submit an inspection photograph through the App, it may be transmitted to authorized application infrastructure and stored as part of the relevant inspection record.
Q2. Does the App save every photograph from my phone?
No. The App is not intended to collect the user's entire personal photo library.
Q3. Can the organization see submitted inspection photographs?
Authorized organizational personnel may be able to access submitted photographs according to their assigned roles and permissions.
Q4. Can other employees see my inspection photographs?
Not by default. Access is controlled according to organizational roles and permissions.
Q5. Are photographs sold to advertisers?
No.
Q6. Are inspection photographs used for advertising?
No.
Q7. Are photographs used to train commercial AI models?
They are not intended to be used for unrelated commercial AI model training.
Q8. Are photographs automatically converted into biometric face data?
No. An inspection photograph is not automatically converted into a biometric profile merely because it contains a person's face.
Q9. How long are inspection photographs retained?
They may be retained according to the organization's applicable record-retention and operational requirements.
Q10. Can I request deletion of an inspection photograph?
You may submit a deletion request to the organization or privacy contact. Deletion may be restricted where the photograph forms part of an official record that must be retained.
Q11. Does the App access my camera without my knowledge?
The App is designed to request and use camera access for authorized functionality. Apple requires user consent and appropriate indication for camera use.
Q12. Does the App secretly record video?
The App is not intended to secretly record video. Camera access is used for the disclosed application functions.
Q13. Does the App upload photographs automatically?
Photographs may be transmitted when they are captured/selected and submitted as part of a relevant application function. The App is not intended to upload unrelated personal photographs.
Q14. Can an administrator download inspection photographs?
Authorized administrators may be able to view or download records where the organization's configured permissions and functionality allow it.
Q15. Can technical support staff access images?
Technical access may occur where necessary for legitimate maintenance, troubleshooting, security, backup, or infrastructure operations and should be subject to access controls.
43. QUESTIONS REGARDING LOCATION
Q1. Why does the App need my location?
Location may be required to verify attendance, field visits, or institution inspections.
Q2. Is my location used for advertising?
No.
Q3. Is precise GPS collected?
Where GPS verification is enabled, precise location may be collected.
Q4. Is background location collected?
Only where the deployed version technically requires and is authorized to use background location functionality.
Q5. Can I disable location?
Users may control permissions through their device settings. However, disabling location may prevent location-dependent functions from operating.
44. QUESTIONS REGARDING INSTITUTION INSPECTION
Q1. What information is recorded during an inspection?
The App may record institution details, inspector details, date/time, GPS location, checklist responses, findings, remarks, photographs, documents, and follow-up actions.
Q2. Why are photographs required?
Photographs may provide evidence of the condition of an institution, infrastructure, equipment, facility, or other inspected item.
Q3. Why is GPS recorded during inspection?
GPS may be used to verify that the inspector was physically present at the institution.
Q4. Can inspection records be changed?
Depending on the workflow, records may be locked, approved, modified, or corrected according to organizational permissions.
Q5. Who can approve an inspection?
Approval permissions are determined by the organization's configured hierarchy.
45. DATA MINIMIZATION
The App seeks to collect only information reasonably necessary for the functionality being provided.
For example:
Camera access is used for image-related functionality.
Location access is used for location-dependent functionality.
Inspection photographs are collected as inspection evidence.
Employee information is used for workforce administration.
The App does not intentionally collect unrelated personal information.
46. CONSENT AND DEVICE PERMISSIONS
Where required, the App requests permission before accessing protected device resources.
Users may manage permissions through their device settings.
If a permission is denied, the corresponding functionality may not work.
For example:
Camera denied: camera-based attendance or inspection photographs may not work.
Location denied: GPS attendance or inspection verification may not work.
Photo/file access restricted: selecting existing photographs or documents may not work.
Apple requires apps collecting user or usage data to obtain appropriate permission and to provide clear purpose descriptions.
47. CHANGES TO THIS PRIVACY POLICY
This Privacy Policy may be updated from time to time.
Updates may occur because of:
New application functionality.
New inspection features.
New security measures.
Changes in infrastructure.
Changes in applicable law.
Changes in Apple or Google platform requirements.
Changes in organizational requirements.
The latest version will display the applicable “Last Updated” date.
48. CONTACT US
For questions regarding privacy, images, inspection photographs, location information, employee data, or deletion requests:
LazyMonkeyAI
Application: LazyMonkeyAI EMP App
Email: info@lazymonkyai.com
Users may also contact their organization's designated administrator or data-management officer.
49. FINAL PRIVACY COMMITMENT
LazyMonkeyAI is committed to responsible handling of employee and organizational information.
The App uses personal information, location, camera functionality, photographs, documents, and inspection information only for legitimate functionality and organizational purposes.
In particular:
Employee information is used for workforce management.
Location is used for attendance, field activity, and inspection verification.
Inspection photographs are used as work-related evidence.
Submitted images may be stored as part of official inspection records.
Unrelated personal photographs are not intentionally collected.
Inspection images are not sold.
Employee information is not sold.
Employee information is not used for advertising.
Inspection images are not intended for unrelated commercial AI training.
Face verification, where enabled, is used for authorized identity/attendance verification.
Biometric face templates are not intentionally retained where the implemented verification process performs temporary processing only.
Access to organizational records is controlled according to user roles and permissions.
Retention and deletion are governed by applicable organizational, legal, regulatory, and operational requirements.
50. PRIVACY POLICY SUMMARY
Application: LazyMonkeyAI EMP App
Primary Users: Authorized employees and organizational personnel
Primary Purposes:
Employee management.
Attendance.
GPS verification.
Field visits.
Institution inspections.
Inspection evidence.
Work/activity management.
Operational reporting.
Security and audit.
Potentially Sensitive Data:
Precise location.
Employee information.
Photographs.
Inspection records.
Face-related information where face verification is enabled.
Advertising: No sale or targeted advertising based on employee information.
Inspection Images: May be transmitted to authorized backend infrastructure and retained as part of official inspection records.
Personal Gallery: The App does not intentionally collect unrelated personal photographs.
Third-Party Sharing: Limited to authorized organizational personnel and service providers necessary to operate the system, plus disclosures required by law.
Face Data: Used only for authorized identity/attendance verification where enabled; no commercial facial profiling.
Retention: Based on the applicable organizational, legal, regulatory, audit, and operational requirements.
Privacy Contact: info@lazymonkyai.com
EFFECTIVE DATE AND VERSION
Effective Date: 01 April 2025 Last Updated: 20 August 2026 Version: 1.1.0
LazyMonkeyAI LazyMonkeyAI EMP App Email: info@lazymonkyai.com