Privacy Policy
CheckIn — Solopreneur Tracker · Effective and last updated: 26 July 2026
This policy explains how the CheckIn Android app (listed on Google Play as “CheckIn - Solopreneur Tracker”) handles your information. CheckIn is developed by Nexus AI Technology Labs, a brand of AI Nexus Consulting FZ-LLC. For any question about this policy or your data, contact us at saksham@nexusai.world.
The short version: your attendance data never leaves this device unless you export it yourself. CheckIn has no account, no login, and no server operated by us. We receive no data about you or your use of the app.
Data safety at a glance
- We collect nothing. There is no account, no backend, and no path by which your records reach us.
- We share nothing. We operate no analytics service and no advertising, and we hand your data to no one.
- One exception, named plainly. Google’s ML Kit library, which CheckIn uses for offline face detection, sends its own technical diagnostics to Google. It carries none of your attendance data and no camera frames, and we never see it — details below.
- All processing is on-device. Your attendance records and camera frames are processed only on your phone.
- You are the only export route. The single way attendance data leaves the device is the CSV export, which you start and you direct.
Network access
CheckIn has no backend and no account. The app makes no network calls of its own. Its only outbound actions are handing a link to your browser, a draft to your email app, or a listing to the Play Store when you tap one of those.
CheckIn does bundle Google’s ML Kit library for on-device face detection, and ML Kit brings its own diagnostics component with it. That component is why Android lists an internet permission for CheckIn even though CheckIn’s own code never connects.
Google documents what that component reports to Google: device information (manufacturer, model, OS version and build, and available ML hardware accelerators), the app’s package name and version, a per-installation identifier, performance metrics such as latency, the detector’s configuration and version, event types such as initialisations and detection events, and error codes. Google states that this is encrypted in transit and is not passed on to third parties, and it publishes no way for an app to switch it off. Nothing on that list is your attendance data, your camera frames, or anything about a detected face, and none of it reaches us — we have no console, no dashboard, no analytics service, no advertising, and no server of any kind.
Permissions
CheckIn’s own manifest declares five permissions:
CAMERA— the presence check described below.POST_NOTIFICATIONS— the notifications described below.FOREGROUND_SERVICEandFOREGROUND_SERVICE_SPECIAL_USE— the ongoing timer notification shown while you are checked in.USE_BIOMETRIC— the device-unlock fallback described below.
Five more are merged into the installed app by the Google libraries it bundles, not declared by CheckIn: INTERNET, ACCESS_NETWORK_STATE, WAKE_LOCK and RECEIVE_BOOT_COMPLETED come from the diagnostics component inside ML Kit’s face-detection library, and USE_FINGERPRINT comes from androidx.biometric. If you inspect CheckIn’s permissions in Android settings, this is why an internet permission appears there.
Camera
When you check in or out, the front camera captures a single frame. It is written to CheckIn’s private storage on your device for only as long as the on-device face check needs it, then deleted as soon as that check resolves — whether it succeeds or fails. Deletion does not depend on you staying on the screen, and the app sweeps its own storage at startup to clear anything a crash or a forced stop could have left behind.
The image is never displayed, never uploaded, and never shared, and it is never written to your photo gallery. Face detection runs entirely offline using a model bundled inside the app — there is no model download and no server round-trip, and no image or result is ever sent anywhere. CheckIn checks that a face is present. It does not identify you, does not match you against a stored face, and keeps no face data of any kind.
Biometrics
After three consecutive failed camera checks, CheckIn offers your device’s standard unlock as a fallback, handled entirely by Android’s BiometricPrompt (BIOMETRIC_STRONG or DEVICE_CREDENTIAL). The operating system performs the match; the app only receives a pass/fail result and never receives or stores any fingerprint, face, or other biometric data.
Information stored on your device
- Attendance records — your check-in and check-out times and the derived daily totals, in a local database on your device only. They are used solely to show your attendance, hours, and compliance status inside the app.
- Settings — including your tracking start date and the history of your daily targets.
- Notification bookkeeping — a small separate local database covering the app’s own notifications. It never holds attendance data, and nothing in it is sent to us.
Notifications
CheckIn shows three kinds of notification:
- An ongoing timer notification while you are checked in.
- A mid-session presence check reminder. This defaults on and is configurable — you can turn it off, and you choose whether an unanswered check pauses your timer.
- Optional encouragement nudges. These are opt-in and default to off, both as a master switch and for each individual nudge.
Sending feedback
“Send feedback” opens your own mail app with a pre-filled draft, so nothing is transmitted until you press send there. The draft body includes, as plain readable text you can delete before sending: the app version and build number, your device manufacturer and model, and your Android version and API level. It is in the visible body on purpose rather than in an attachment or a hidden header, so you can see exactly what you would be sending.
Exporting your data
The CSV export is started by you. CheckIn writes the file to its own cache directory and hands it to the Android share sheet, so it goes wherever you choose to send it. This is the only path by which attendance data leaves your device, and where it ends up is your choice.
Links out of the app
Tapping “Privacy policy” opens this page in your browser, and “Rate on Google Play” opens the Play app. CheckIn hands these to the system as intents; from that point the browser or the Play app is handling the request, under its own privacy policy.
Retention and deletion
- Your attendance data stays on your device until you remove it.
- Individual sessions cannot be edited or deleted — that is deliberate, so the record reflects what actually happened.
- You can delete everything at any time by clearing the app’s storage in Android Settings or by uninstalling CheckIn.
Backups and device transfer
CheckIn’s attendance database is excluded from Google cloud backup, so your attendance records are not copied to Google’s servers. If you move to a new phone using Android’s direct device-to-device transfer, the database is included, so your history moves with you — that transfer happens directly between your devices.
That exclusion covers the attendance database specifically. The app’s settings (such as your tracking start date and daily-target history) and its notification bookkeeping database are not excluded, so they may be included in Android’s backup if you have it enabled.
Children
CheckIn is a general productivity tool intended for adults and is not directed at children.
Third-party components
We do not sell, rent, or share your information with any third party. There is no advertising in CheckIn, and no analytics that we added or receive — we have no console, no dashboard, and no way to see anything about you or your use of the app.
For completeness, these Google libraries ship inside the app, pulled in by ML Kit’s on-device face detection: com.google.mlkit:face-detection, com.google.android.datatransport (transport-api, transport-runtime, transport-backend-cct), com.google.firebase (annotations, components, encoders, encoders-json), com.google.android.gms (play-services-base, play-services-basement, play-services-tasks, play-services-mlkit-face-detection), and com.google.android.odml:image. No Firebase product is configured or initialised by CheckIn, and none of these components is given your attendance records or your camera frames beyond the offline face check itself.
Changes to this policy
If this policy changes, we will post the updated version on this page and revise the effective date above. Material changes will be highlighted here.
Contact
Nexus AI Technology Labs (a brand of AI Nexus Consulting FZ-LLC). Questions about this policy or your data: saksham@nexusai.world.