
KerjaKu Privacy Policy
This Privacy Policy explains how KerjaKu accesses, stores, uses, and shares data when you use the app.
Effective from: August 27, 2026App package: id.kerjaku.app
Privacy summary
KerjaKu is designed to work offline. Core data such as schedules, shifts, working hours, breaks, leave, pay profiles, pay estimates, work expenses, and work notes is stored primarily on your device. KerjaKu does not provide a KerjaKu account or its own cloud database to store this core data.
The free version may display ads through Google Mobile Ads (AdMob). These advertising services may process certain technical data according to consent, device settings, and Google's policies.
1. Who operates this app?
KerjaKu is developed and operated by Naravasi Digital.
For privacy or data questions, contact [email protected].
2. Data KerjaKu stores on your device
KerjaKu may store data you enter or generate while using the app, including:
- Job profiles and shift settings;
- Work schedules, rotation patterns, clock-in and clock-out times, breaks, overtime, and time corrections;
- Leave, sick days, authorized absences, days off, work from home, business trips, and work notes;
- Pay profiles, salary components, income estimates, deductions, allowances, and work expenses;
- Work evidence documents you deliberately select, such as images or PDFs;
- OCR results and document metadata when you use document reading features;
- App settings, Pro status, and limited local diagnostic logs.
This core data is not automatically sent to KerjaKu servers because KerjaKu does not operate an account backend or cloud database for it.
3. Documents, camera, gallery, and files
KerjaKu only requests camera, photo, or file access when you choose a feature that needs it, such as adding work evidence, payslips, schedules, or other documents. KerjaKu does not use the microphone for these functions.
Selected documents may be stored as local app files. OCR runs on the device where supported by the build and device, and results may be stored locally with document data.
4. Backup and restore
KerjaKu can create encrypted backups using AES-256-GCM. Recovery keys are stored in the device's secure storage (SecureStore) and are not included in backup files.
Backup files only leave app storage when you choose to save, share, or move them. If you select a third-party storage service, such as a cloud service through the Android file picker or share sheet, that service's processing is subject to the privacy policy of the provider you choose.
KerjaKu cannot delete backup copies or exports you have already saved to external locations.
5. Biometrics and App Lock
If you enable App Lock, biometric authentication or the device lock is handled by the operating system. KerjaKu does not receive or store fingerprint templates, Face ID data, or raw biometric data.
6. Notifications
KerjaKu may request notification permission for shift and clock-out reminders. Reminders are scheduled locally on the device. KerjaKu does not use its own push servers to send personal work schedules.
7. Ads in the free version
The free version of KerjaKu may use Google Mobile Ads (AdMob). KerjaKu uses an advertising consent mechanism before requesting ads when required by the applicable region or configuration.
The Google Mobile Ads SDK may process or share certain technical data for advertising, analytics, and abuse or fraud prevention, including IP addresses (which may be used to estimate a general location), user interactions with products or ads, diagnostic and performance information, and available device or advertising identifiers.
KerjaKu does not request precise device location permission for core features. Advertising providers may, however, estimate a general location from IP addresses under their own policies.
You can change or limit advertising choices through available consent settings, Android/Google ad settings, or by using KerjaKu Pro if the Pro version removes ads.
8. KerjaKu Pro purchases
KerjaKu Pro purchases are processed through Google Play or the relevant app store. KerjaKu does not receive or store card numbers, bank account details, or payment credentials. The app may receive information needed to determine product ownership, restore purchases, and enable Pro access.
9. Diagnostic logs
KerjaKu may store limited technical logs locally to help diagnose app issues. Diagnostic logs are designed to exclude salary amounts, company names, and user document contents. You can delete diagnostic logs through the Privacy & Data menu.
10. Data not used for core features
Under this version of the policy, KerjaKu does not request access to contacts, SMS, call history, or the microphone for core features. KerjaKu also does not provide user accounts requiring a username or password.
11. Sharing data with third parties
KerjaKu does not sell work records or users' personal salary data. Other parties may process data only in the context of features you use, such as:
- Google Mobile Ads (AdMob) for ad delivery, measurement, ad analytics, and fraud prevention in the free version;
- Google Play / app stores for purchases, purchase restoration, distribution, and app protection;
- Storage providers or sharing apps you select when you export CSV/PDF files, backups, or documents outside the app.
12. Data security
KerjaKu implements technical measures appropriate to the app, including local storage, SecureStore for certain secrets, backup encryption, and App Lock options. However, no method of electronic storage or transmission can be guaranteed to be 100% secure.
13. Data retention and deletion
Because core data is stored locally, you have direct control over it. You can delete records using available features, delete diagnostic logs in the app, or clear app data or uninstall KerjaKu to remove data stored in the app's device storage.
Backup files, CSV files, PDFs, or documents already exported or saved elsewhere must be deleted separately from those locations or services.
KerjaKu does not provide an account deletion process because it does not create KerjaKu user accounts.
14. Children's privacy
KerjaKu is intended for users managing work activities and is not specifically designed for children. If app distribution or the intended audience changes, this policy will be updated to reflect actual app use.
15. Changes to this Privacy Policy
This policy may be updated when features, third-party SDKs, data practices, or legal requirements change. The effective date at the top of this page will be updated when there are material changes.
16. Contact
This policy must remain consistent with the behavior of the released app and the answers in the Google Play Data safety form.