Tare Support

Current availability

Tare 1.0 (31) is VALID, attached to an editable App Store version, and assigned only to internal TestFlight. It supports iPhone and iPad on iOS 17 or later, with an Apple Watch companion on watchOS 10 or later. There is no public TestFlight acquisition link, public App Store listing, authorized price, or territory claim.

The retired web address shows retirement information only. It is not a supported Tare web app, sign-in page, export portal, or route to the native health store.

No Tare account or web sign-in

Native Tare opens without an account. Your Apple Account may provide private CloudKit sync and Apple Health may provide approved records, but neither is a Nintek-managed Tare account. Support will never ask for an Apple password, verification code, App Attest token, or iCloud credential.

Troubleshoot Apple Health and private iCloud

Apple Health

• Review Tare’s Health permissions in Apple Settings or the Health app.
• Open Tare or return it to the foreground after enabling access, then useSync now if you need an immediate check.
• Weight, glucose, and dietary water can sync both ways; sleep and steps are read only. Manually entered weight and glucose values take precedence over imports. Water is the exception — Tare re-totals the day’s figure from Health after writing to it, so it does not preserve an entered override.
• Apple Health authorization is a system control. Reinstalling Tare does not guarantee that Apple will present the same permission prompt again.

Private CloudKit

• Confirm the device is signed in to the intended Apple Account.
• Check iCloud availability, network access, and free iCloud storage.
• Open Tare on each device and allow Apple time to deliver changes.
• Do not delete the app while troubleshooting if a device may contain the only local copy of records you need.

Nintek cannot inspect, merge, force, or restore a private CloudKit database.

Troubleshoot optional AI features

AI is off until you accept the current consent scope. Confirm AI is enabled under Tare’s privacy settings, the device is online, and the selected input is within the feature’s stated scope. A changed scope asks for consent again.

If a request fails, retry once after reconnecting. The relay keeps no request or answer database, so support cannot retrieve a failed transcript. Report the feature name, time, app build, and visible error without sending a full health database, medication history, or unredacted lab document.

Generated output can be wrong and is not medical advice. Do not use it to choose a medication, dose, diagnosis, or treatment.

Anthropic processes the scoped input as the processor behind these features, under its ownCommercial Terms of Service. See the Tare Privacy Policy for the full data-handling and retention detail.

Backup, restore, export, and offline limits

Tare exports a JSON backup containing all 16 data tables and can restore a compatible native or former web backup. It keeps one rolling local backup per day for 14 days and attempts a separate safety copy before every restore. Keep an independent copy before a device migration or destructive troubleshooting step. The file contains health information; store and share it accordingly.

Core records remain usable offline. CloudKit, Health delivery between services, and optional AI wait for the required Apple or internet service. Nintek does not hold a native server backup and cannot recreate a lost local store from the relay.

Deletion and the retained legacy web database

There is no native Tare account to delete. Deleting the app removes its local data from that device, but private CloudKit data, Apple Health records, and exported backup files have separate controls. Tare has no in-app erase-all control.

The former web database is separate and has not yet been destructively removed. Cleanup is waiting for physical-device validation, completion and review of the active soak, native-successor acceptance, and explicit confirmation. Emailprivacy@nintek.com about access to or deletion of a retained legacy copy. Do not use obsolete web login instructions; the web product is retired.

General troubleshooting

1. Confirm the device meets the iOS, iPadOS, or watchOS requirement.
2. Install the newest private build available to the authorized Apple Account.
3. Force-quit and reopen Tare, then restart the device if needed.
4. Check free device storage before importing or creating a backup.
5. For Apple Watch delivery, keep Bluetooth and Wi-Fi available, open Tare on the iPhone, and allow queued entries time to transfer.

Avoid deleting Tare as an early recovery step when the device may hold the only local copy of important records.

Contact and legal documents

Email hello@nintek.com with the device model, operating-system version, Tare build, affected feature, and recovery steps already tried. Do not send credentials or more health data than the issue requires.

Read the Tare Privacy Policy for data locations, providers, retention, and deletion boundaries. Use of Tare is subject to theNintek Terms of Use.