Privacy Policy

MyKrom ("we", "us", "the app") is a workforce management tool built for small hospitality and retail businesses in Cambodia. This page explains, plainly, what data MyKrom touches, where it lives, and who can see it.

1. Who controls your data

MyKrom runs inside Google Sheets and Google Apps Script, hosted under the Google account of the business using MyKrom (the "Owner" account) — not under an account controlled by MyKrom's developer. This means:

• All staff records, attendance logs, leave requests, salary data, and notes are stored in a Google Sheet that belongs to your business.
• You can export, back up, or delete this data at any time, directly from Google Sheets or from MyKrom's built-in export tools.
• MyKrom's developer does not have standing access to this Sheet. Access is only granted if you explicitly share it for support purposes, and can be revoked at any time.

2. What data MyKrom processes

Depending on which features your business uses, MyKrom may process:

• Staff identity & contact info: name, username, phone, Telegram/WhatsApp, address, date of birth, national ID or work permit number, emergency contact — only the fields your business chooses to fill in.
• Attendance: check-in/check-out timestamps, and optionally an on-site verification signal (GPS proximity check or local network check) used only to confirm presence at the work site — not used for tracking, location history, or movement outside of check-in/check-out moments.
• Work data: leave requests, overtime, shift schedules, salary calculations, advances, deductions, and manager notes.
• Login credentials: passwords are stored as salted hashes, never in plain text.

3. Location data

If your business enables geofence check-in, MyKrom checks whether a staff member's device is within a configured radius of the work site at the moment of check-in or check-out. This check happens once per event — MyKrom does not track ongoing location, does not store a location history, and does not access location data outside of that single moment.

4. Google account permissions (OAuth scopes)

MyKrom requests the following Google permissions, and uses them only for the stated purpose:

• Drive (file-scope only): to create and store generated documents (such as employment contracts) that MyKrom itself creates. MyKrom cannot see or access any other file in your Drive.
• Google Docs: to generate bilingual (English/Khmer) employment contract documents on request.

MyKrom does not request access to Gmail, Calendar, Contacts, or any Drive files beyond those it creates itself.

5. What we don't do

• We don't sell or rent your data to anyone.
• We don't use your data for advertising or profiling.
• We don't share staff data with third parties, except where you've explicitly configured an export or backup destination yourself.
• We don't run analytics or tracking scripts inside the app that report usage back to us.

6. Data retention & deletion

Since your data lives in your own Google Sheet, retention is entirely under your control. You can delete individual records, clear a sheet, or revoke MyKrom's access at any time. If MyKrom's developer was given temporary support access to your Sheet, that access can be revoked the same way you'd revoke access for any collaborator in Google Sheets.

7. Self-hosted version

MyKrom is also offered as a self-hosted version (running on your own server/hardware instead of Google Sheets) for businesses that want full infrastructure ownership. In that configuration, no Google account or Google service is involved at all, and data never leaves hardware you control.

8. Changes to this policy

If this policy changes in a way that affects how your data is handled, we'll update this page and note the date above. Continued use of MyKrom after an update means you accept the revised policy.

9. Contact

Questions about this policy or your data? Reach out via ced.watch.