Nexus AI LogoSleeves Up

Privacy Policy

Sleeves Up · Effective and last updated: 20 August 2026

This policy explains how the Sleeves Up Android app handles your information. Sleeves Up is the product’s name from version 3.0; releases before it were listed on Google Play as “CheckIn - Solopreneur Tracker”, and the app is the same one under both names. Sleeves Up 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 records never leave this device unless you export them yourself. Sleeves Up 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. No third-party component in the app sends anything anywhere.
  • The app cannot reach the network. Sleeves Up holds no internet permission at all — not one it declares, and not one merged in by a library it bundles.
  • No photo is ever taken. The presence check reads a face count reported by your camera hardware. No image is produced, so there is none to store, display, transmit or delete.
  • You are the only export route. The single way your session data leaves the device is the CSV export, which you start and you direct.

Network access

Sleeves Up has no backend and no account, and it holds no internet permission at all — neither one it declares nor one merged in by a library it bundles. It therefore cannot upload your data, or contact any server, as a matter of what the operating system will permit rather than a promise about how the code behaves.

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. Each is a request to an app you already have, and from that point that app is handling it under its own privacy policy.

This is a change from earlier versions of this policy. Sleeves Up previously used Google’s ML Kit for offline face detection, and ML Kit brought a diagnostics component that reported technical information to Google and carried an INTERNET permission with it. The presence check is now performed by your camera hardware directly, and that entire stack — ML Kit, Google Play services, the datatransport and Firebase encoder libraries — has been removed from the app. With it went the only third-party data flow Sleeves Up ever had.

Permissions

Sleeves Up’s own manifest declares six permissions:

  • CAMERA — the presence check described below.
  • POST_NOTIFICATIONS — the notifications described below.
  • FOREGROUND_SERVICE and FOREGROUND_SERVICE_SPECIAL_USE — the ongoing timer notification shown while you are checked in.
  • USE_BIOMETRIC — the device-unlock fallback described below.
  • RECEIVE_BOOT_COMPLETED — so a session left open across a restart keeps its timer and still closes at midnight.

Three more are merged into the installed app by the AndroidX libraries it bundles, not declared by Sleeves Up: USE_FINGERPRINT comes from androidx.biometric, and WAKE_LOCK and ACCESS_NETWORK_STATE come from androidx.work, which schedules the app’s own background housekeeping. ACCESS_NETWORK_STATE allows reading whether a connection exists; it grants no access to the network, and Sleeves Up has none. Nine permissions in total, and INTERNET is not among them — you can confirm this in Sleeves Up’s entry in Android settings.

Camera

When you check in or out, Sleeves Up opens a front-camera preview and asks the camera hardware to report how many faces it can see. No photo is taken. The frames stay inside the camera pipeline and are never delivered to the app; what the app receives is a number, arriving as metadata alongside each preview frame.

You see a live preview on screen while the check runs, so you can tell what the camera is doing. That preview is only ever drawn — it is not recorded, and it is gone the moment the check ends. No still image is produced at any point: nothing is written to storage, nothing is uploaded or shared, and nothing is saved to your photo gallery, so there is nothing a crash, a forced stop or a bug could leave behind. Earlier versions of Sleeves Up did briefly write a frame to private storage and delete it after analysis; that mechanism no longer exists.

The distinction that matters is that the app’s own code never receives the picture. Detection happens inside the camera system, and what crosses into Sleeves Up is a count of how many faces were seen — so this is a property of how the check is built, not a promise about what the app chooses to do with an image it was given.

The check runs entirely offline, and it confirms 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

Sleeves Up offers your device’s standard unlock as a fallback: at once if your camera cannot check for a face at all, and otherwise after about ten seconds of looking without finding one. It is 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. If your device has no screen lock set up, Sleeves Up points you at the Android settings screen that creates one rather than leaving you stuck.

Information stored on your device

  • Session records — your check-in and check-out times and the resulting durations, in a local database on your device only. They are used solely to show your sessions and hours inside the app.
  • A small amount of app state — such as whether a one-time introductory screen has already been shown, and a mirror of the running timer so the notification survives the app being closed.
  • Notification bookkeeping — a small separate local database recording which of its own notifications the app has shown, so it can keep to its own frequency limits. It never holds your session data, and nothing in it is sent to us.

Notifications

Sleeves Up shows three kinds of notification:

  • An ongoing timer notification while you are checked in, with a Check Out action.
  • A session reminder while a session is running, asking whether you are still checked in. Ignoring it costs nothing.
  • Check-in reminders, if you have not checked in that day — at most twice a day, hours apart.

Each of the three is a separate Android notification channel, and the channel is the switch: a long press on any notification opens its channel and turns it off in one tap. Sleeves Up deliberately keeps no in-app duplicate of those switches, because an app setting can only agree with the system one or contradict it.

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. Sleeves Up 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 your session 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. Sleeves Up 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 session 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 Sleeves Up.

Backups and device transfer

Sleeves Up’s session database is excluded from Google cloud backup, so your 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.

The running timer’s state and the record of which one-time prompts have been shown are excluded from cloud backup too, since both describe a specific device. The notification bookkeeping database is not excluded, so it may be included in Android’s backup if you have it enabled; it holds no session data.

Children

Sleeves Up 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 Sleeves Up, 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.

The libraries Sleeves Up bundles are Google’s AndroidX components — Jetpack Compose, Room, CameraX, androidx.biometric and androidx.work — plus two open-source typefaces. These are ordinary open-source building blocks for drawing the interface, storing data locally, running the camera and scheduling background work. None of them is an analytics or advertising SDK, and none could transmit anything in any case, since the app holds no internet permission. A full list is in the app itself, under About → Open source licences.

No Google Play services, ML Kit or Firebase component is present. Those were removed when the presence check moved to the camera hardware, and with them the diagnostics reporting that earlier versions of this policy disclosed.

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.

← Back to Sleeves Up overview