Privacy Policy
Last Updated: October 2026 • Effective Date: October 28, 2026
workerbook.online) and the WorkerBook Android mobile application (Package: com.aistudio.workerbook.kxmpzq). It outlines how data is gathered, stored, and protected across both platforms.1. Information We Collect
A. On the Website (workerbook.online)
When you visit our website to learn about WorkerBook or download the APK, we do not require account registration. Standard non-identifying technical data may be processed:
- Basic web server logs (browser type, operating system, timestamp).
- Voluntary contact submissions (name, email address, message) when you contact our support team.
B. In the WorkerBook Android Application
WorkerBook is designed as a workforce accounting tool for contractors. Data you input into the app includes:
- Worker Details: Names, trade skills, wage rates (daily, monthly, or hourly), and optional phone numbers for quick contact.
- Attendance Records: Daily attendance states (Present, Absent, Half-Day, Overtime hours).
- Payment & Advance Records: Wage payouts, cash advances, and notes.
- Cash Book Entries: Cash In and Cash Out transactions, amounts, and business categories.
- Account Credentials: Email or phone number if you choose to sign in for multi-device cloud backup.
2. Data Storage & Offline-First Architecture
WorkerBook stores your data locally on your Android device using SQLite (via Android Room). When offline, all operations run on-device. If you sign in, your data is securely synchronized to our backend database (Supabase) to enable cross-device backup and restoration.
3. Third-Party Services
The WorkerBook Android application integrates the following third-party services:
- Google AdMob: We display advertisements in designated areas (banners, native cards, and interstitial transitions). Google AdMob may use device identifiers (such as Google Advertising ID) in accordance with Google's Privacy Policy.
- Supabase: Used for secure user authentication, database storage, and cloud synchronization.
- Firebase Cloud Messaging (FCM): Used solely to deliver operational notices and system notifications to your device.
4. Device Permissions
The Android app may request the following permissions only when required:
INTERNET&ACCESS_NETWORK_STATE: Required to synchronize cloud records and serve ads.POST_NOTIFICATIONS: Required on Android 13+ to deliver operational notifications.
5. Data Security & Retention
We implement industry-standard encryption (HTTPS/TLS) for data in transit between the app and cloud backend. You can delete your local data at any time by clearing application storage or uninstalling the app. You may also request deletion of your cloud account and synchronized data.
6. Contact Information
If you have questions regarding this Privacy Policy or wish to request data deletion, contact us at: