How Ntex handles information when you build battery profiles, track replacement cycles, manage spare stock, and review local history on your device.
Ntex is a personal utility for recording battery-powered devices at home, estimating the next replacement date from the cycle you set, surfacing overdue or upcoming items, keeping spare battery counts, and logging replacements. You can use Ntex without creating an account. There is no mandatory sign-in, no cloud profile, and no forced identity layer to open the tabs or save entries.
This notice explains the kinds of information that may exist on your device while you use those flows, why that information is processed, which system permissions may appear, and the choices you retain. It is written for the app as shipped, not for features Ntex does not offer.
When you add or edit a device, you may supply a name, category, battery model text, battery count, replacement cycle in days, last replacement date, optional maintenance notes, and an optional photo. Ntex uses these fields to calculate the next suggested replacement date, sort lists by urgency, show status on Home and Reminders, and display detail screens.
Inventory entries may include battery model labels, quantities, favorite flags, and update timestamps. Favorites can appear as quick-fill options when you create or edit a device so you do not retype common sizes such as AA, AAA, or coin cells.
When you mark a battery change, Ntex may store a history record with the device identifier, a name snapshot, battery model and count, replacement time, optional note, and whether stock was reduced. If a device is later removed, history may keep the snapshot so past events remain readable even if the live archive is gone.
If you attach an image, Ntex may store a compressed JPEG copy in the app documents area under a device-photo folder and keep only a filename reference in your archive data. Photos are used to identify devices in lists and detail views. You can skip photos entirely; category icons are used as placeholders.
The app may rely on on-device timestamps, calendar calculations for remaining days, and simple derived metrics such as cycle days divided by battery count for a lightweight home comparison. These values are produced from your entered data and are not readings from Bluetooth hardware or third-party energy monitors.
Camera access may be requested if you choose to capture a device photo. Photo library access may be requested if you choose an existing image for a device card. These prompts appear only when you start those actions. Declining a permission limits the related photo feature; the rest of the archive, reminder, inventory, and history tools can still be used with text fields and placeholders.
Ntex does not need microphone access, tracking across other companies apps, continuous background location, or account credentials to operate its core battery workflow.
Device lists, inventory, and history are designed to persist as structured data in the app documents space on your device, typically as a local JSON file. Device photos, when present, are stored as separate image files in an app documents subdirectory. First-run sample entries may be seeded so you can explore the interface; you can clear or replace that content from within the app controls that remove or restore sample data.
Because the primary store is on-device, uninstalling the app or clearing the app container generally removes that local dataset, subject to how iOS manages backups and residual files. If your device participates in system backups, copies of app documents may be included according to your system backup settings.
The core archive, reminder, inventory, and history flows are built for local use. Ntex does not require you to upload device batteries data to an Ntex account service to mark a replacement or view reminders.
If the distributed build includes optional system or store frameworks, those components may process limited technical events according to their own rules and your device settings. When you email keepspark@ntexloop.app, the contents of your message and standard email metadata are processed so we can reply.
We do not sell your battery archive contents. We do not operate a social feed or household sharing room inside Ntex that would publish your device list to other users.
Entries remain until you edit or delete them, clear data through in-app options that wipe devices, inventory, and history, or remove the app from the device. You can update a device, remove inventory lines, and continue using history snapshots after a device deletion as the product currently behaves.
Because there is no mandatory Ntex login, there is no separate cloud account dashboard for remote wipe. Control is exercised on the device through the app screens and system settings for permissions and storage.
Ntex is meant for general household organization. It is not directed at children under 13 as a primary audience. If you believe a child has provided personal information to us by email, contact keepspark@ntexloop.app and we will take reasonable steps to review and delete what we hold in that correspondence, where applicable.
We apply reasonable technical and organizational measures appropriate to a local utility of this type, such as keeping primary archives in the app sandbox and compressing photos before storage. No method of storage or transmission is free from risk. You should protect your device with a passcode or biometric lock and keep iOS updated.
If Ntex features or data practices change in a material way, we may update this page. Continued use after an update means you have had an opportunity to review the revised notice. When we publish a meaningful change, we will refresh the effective timing stated in the closing statement below.
For privacy questions about Ntex battery archives, photos, inventory, or history, email keepspark@ntexloop.app. Please include enough detail for us to understand the screen or action involved.