Scope and the short version
This policy explains how Nintek (“we”, “us”) handles information inTare. Tare is a native GLP-1 and metabolic-health tracker. Its former browser app has retired; the only live web service used by the product is the consent-gated AI relay described below.
Tare has no account or sign-in. Native records stay on your device and may sync through your private Apple CloudKit database. Nintek cannot browse either store. Optional AI features send only the inputs needed for the selected operation through a stateless relay to Anthropic. Tare has no ads, analytics SDK, crash-reporting SDK, or cross-app tracking.
Health information can be sensitive. This policy distinguishes the native store, Apple-controlled data, transient AI processing, backup files, and the separate legacy web database instead of treating them as one system.
SwiftData on device and private CloudKit
Tare stores weights, glucose readings, injections and doses, meals and macros, well-being, side effects, measurements, lab results, vitals, diagnoses, medications, procedures, photos, settings, and related history in SwiftData on the device.
When iCloud is available, Apple’s SwiftData and CloudKit integration can sync that store through the private CloudKit database associated with your Apple Account. The app continues with local storage when CloudKit is unavailable. Nintek does not operate the account, receive a server copy, or have a console for reading your private CloudKit records.
Widgets, Live Activities, complications, and the Apple Watch app receive limited local snapshots through Apple App Group and device-to-device mechanisms. Those surfaces do not create a Nintek account or health-record server.
Apple Health
If you grant permission, Tare can read weight, glucose, sleep, steps, and dietary water from Apple Health, and can write weight, glucose, and dietary water back to Health. Sleep and steps are read only. Water is handled differently from weight and glucose: rather than preserving exactly what you entered, Tare re-totals the day’s water straight from Health after writing to it, so the figure reflects every source contributing to that total. After you enable access, Tare checks for approved Health data when the app opens or returns to the foreground, and a manual Sync now control remains available.
HealthKit access is controlled by Apple’s permission interface. Tare does not receive your Apple Account credentials, and Nintek does not receive a server copy of the HealthKit exchange. A Health record is not automatically included in an AI request merely because Tare can read it; the selected AI operation and consent scope control what is sent.
Optional AI processing
AI features are off until you enable them. Tare presents the categories of information needed for an operation and asks again when that scope changes. You can turn AI access off in the app’s privacy settings.
When you deliberately use an enabled AI feature:
- Tare sends the prompt, selected photo or document, or scoped record values needed for that operation over an encrypted connection to the Nintek relay.
- For questions about your records, the model can produce a query for the device to run locally. The device returns the query result needed for the answer rather than uploading the entire database.
- The relay verifies the app with Apple App Attest, forwards the request to Anthropic, returns the result, and does not store a transcript database, request body, or answer.
- Anthropic processes the scoped input as the processor for this feature. Anthropic’s currentCommercial Terms of Servicestate that it may not train models on this content. Anthropic may still retain provider-side records under its own data-retention, trust and safety, legal-hold, or model-specific policies — Tare’s stateless relay does not add any further retention on top of that. Those provider terms can change independently of this page.
AI-generated nutrition estimates, summaries, reports, and answers can be wrong. Tare does not provide medical advice, diagnosis, treatment, or dose selection. Use a qualified healthcare professional for care decisions.
Backups, export, and offline use
Tare exports a readable JSON file containing all 16 data tables and can restore the same envelope from a native or former web backup. It also keeps one rolling local backup per day for 14 days in Application Support. Before a restore replaces the store, Tare attempts a separate pre-restore safety copy; those safety copies are not removed by the 14-day rolling trim.
Native records and core tracking remain available without a network connection. CloudKit sync, Apple Health delivery, and optional AI processing may wait for the relevant Apple or internet service.
A backup file goes wherever you choose to save or share it. Nintek does not receive a copy merely because Tare created it. Protect the file as health data and use the destination provider’s privacy and deletion controls.
Deletion, retention, and account boundaries
Native Tare has no app account to close. Device deletion, private CloudKit deletion, Apple Health controls, backup-file deletion, provider retention, and legacy web cleanup are separate actions. Tare has no single in-app erase-all command.
| Data or control | Where it lives | Export or backup | Deletion and retention |
|---|---|---|---|
| Native health records and settings | SwiftData on your iPhone or iPad. Nintek does not operate a Tare account or native health-record database. | Tare exports an interchangeable JSON backup containing all 16 native data tables and can restore a compatible native or former web backup. | Tare has no in-app erase-all control. Delete individual records where offered or delete Tare to remove local app data from that device. Exported files remain wherever saved. |
| Private iCloud copy | Your private CloudKit database under the Apple Account signed in on the device. | The native backup is created from the local Tare store; iCloud itself is controlled through Apple. | Deleting the app from one device does not by itself promise deletion of Apple-held CloudKit data. Use Apple’s iCloud controls for the synced copy. |
| Apple Health data | Apple Health on your device and any Apple-controlled Health sync you have enabled. | Apple provides Health export and account controls. Tare does not receive a server copy of HealthKit data. | Change Tare’s Health permissions or manage the records in Apple Health. Deleting Tare does not delete the underlying Health records. |
| Optional AI request and answer | Sent through a stateless Nintek relay to Anthropic only for the operation you request. The relay keeps no transcript database. | AI output appears in the app and may be included only where the app’s own record or backup behavior says so; the relay offers no transcript export. | The relay does not retain the request or answer. Anthropic’s current commercial terms state it may not train models on this content, but Anthropic may still retain provider-side records under its own data-retention, trust and safety, legal-hold, or model-specific policies. |
| Retired web-app database | A separate, legacy per-user database in protected Azure storage. It is not connected to the native SwiftData or CloudKit store. | The former web backup format remains compatible with native migration. The retirement page does not offer a web login or new export session. | Destructive cleanup has not run. Physical-device verification, the current soak, cleanup review, and explicit confirmation must finish first. Contact Nintek about the retained legacy copy. |
| Support correspondence | Nintek’s support mailbox when you choose to email. | You can keep your sent message and request a copy of correspondence that Nintek still holds, where applicable. | Nintek may retain correspondence as needed to answer, secure, document, or meet legal obligations; you may request review or deletion. |
Scroll horizontally to read all four columns →
The retired web product
The former Microsoft-sign-in browser app is retired and its live surface is now an informational retirement page. Retired API paths no longer provide a supported login or health-record session. The native app and relay do not connect to the legacy per-user database.
Legacy databases have not been represented as deleted. They remain intact while physical-device App Attest and operation checks, the current 24-hour soak, native-successor acceptance, cleanup dry-run review, and explicit authorization finish. This deliberate hold avoids destructive cleanup before the native migration path is accepted.
To ask about a retained legacy copy, emailprivacy@nintek.com. A request does not delete the Microsoft account itself or Microsoft-held sign-in records.
Children, changes, and contact
Tare is intended for a general adult audience and is not directed to children. We do not knowingly create Tare accounts for children; native Tare has no account system.
We may update this policy when the app, relay, provider configuration, or retirement state changes. The dates at the top identify this version.
Questions about data handling can be sent toprivacy@nintek.com. Product help is available on Tare Support. Use of Tare is also subject to the Nintek Terms of Use.
Evidence note. Reviewed against the Tare relay-only deployment, immutable Tare-for-iOS release-visual authority 9154a7e, and the active web-retirement runbook on August 23, 2026. Legacy web-data cleanup is prepared but has not been executed.