Privacy Policy

Last Updated: July 2026

nü (the "App") is a personal food journal and nutrition tracker. It is built around a simple principle: your data is yours. The developer does not run any server, does not have any account system, and never receives, collects, stores, or sells your information. Everything you log lives on your device. This policy explains, permission by permission, exactly what the App accesses, why, and how you can decline anything you don't need.

The short version: We (the developer) never collect your data. Health data read from Health Connect — including blood glucose and sleep — is used only to draw charts on your own device. It is never sent to us or to any third party, and never leaves your device except to your own Google Drive, and only if you choose to turn on backup. Every Health Connect permission is optional: deny any one and you simply lose that one feature; the rest of the App keeps working.

1. What We Collect

Nothing. Specifically:

2. Where Your Data Lives

All meal logs, nutrition data, goals, and any health data the App reads are stored locally on your device as JSON files in the App's private internal storage. This data stays on your device unless you choose to enable Google Drive backup (see Section 5), in which case it is copied only to your own Google Drive account, which the developer cannot access.

3. Device Permissions

Camera

Used to scan barcodes on food packaging and, optionally, to photograph nutrition labels for the label-scan feature. The camera feed is processed to read the barcode or label; no photo is saved to your gallery or sent anywhere except as described for the optional AI label scan in Section 5.

Deny it and you can still add foods by searching or typing them manually — only barcode and label scanning are unavailable.

Internet

Used to look up nutrition information from public food databases, and, only if you enable them, for optional Google Drive backup and optional AI label scanning. What is sent in each case is detailed in Section 5. No personal profile or identifier is ever attached to these requests.

Without a connection the App still works with foods already in its database and anything you enter manually.

4. Health Connect Permissions

The App can read data from Android's Health Connect to visualize how your nutrition relates to your body and activity. Each of these is a separate, optional permission. The App only reads them — it never writes to Health Connect — and the data is used purely to draw charts on your device. You can grant or revoke each one individually at any time in the Health Connect app, and denying one only disables the single feature that uses it.

Blood glucose READ_BLOOD_GLUCOSE

Powers the App's core glucose-response feature: your blood glucose is plotted over time so you can see how the meals you logged affected it.

Deny it to turn off the glucose chart entirely; everything else in the App is unaffected.

Sleep READ_SLEEP

Overlays your sleep periods on the glucose chart, so you can see how sleep relates to overnight and next-day blood sugar.

Deny it and the glucose chart simply omits the sleep overlay.

Exercise READ_EXERCISE

Overlays your workouts (type and duration) on the glucose chart, so you can see how physical activity affects your glucose response.

Deny it and the chart omits workout markers.

Active calories burned READ_ACTIVE_CALORIES_BURNED

Shows the calories you burned during activity, both against your intake and as the calorie figure for each workout.

Deny it and calorie-burn figures are hidden.

Total calories burned READ_TOTAL_CALORIES_BURNED

Used only as a fallback for a workout's calorie total: some trackers (for example Fitbit) record total calories burned rather than active calories, and this lets the App still show a calorie figure for those sessions.

Deny it and workout calories may be unavailable if your tracker only records the total figure.

Body weight READ_WEIGHT

Displays your body weight alongside your nutrition log so you can track it over time.

Deny it and weight is simply not shown.

5. Third-Party Services

Some optional features send a minimal, specific piece of data to an outside service. None of them receive an account or identifier for you, and the developer never sees any of this traffic.

6. Health Data Handling

Health data read from Health Connect — including blood glucose and sleep, which Google treats as sensitive — is used solely to render visualizations on your device. It is never transmitted to the developer, never used for advertising, never sold, and never shared with any third party. It leaves your device only if you enable Google Drive backup, and then only to your own Google Drive account.

7. Children's Privacy

Because the App does not collect any personal data, it is compliant with the Children's Online Privacy Protection Act (COPPA) and is safe for users of all ages.

8. Changes to This Policy

If this policy changes, the "Last Updated" date above will be revised. Material changes will be reflected here before they take effect.

Contact Us

If you have any questions about this privacy policy, please contact the developer at:

faberest.development@gmail.com