卡路里與飲食記錄等數據僅供你個人於本機進行自主健康管理。本 App
不會將你的飲食記錄寫入或同步至 Apple Health (HealthKit) 或
Health Connect（含舊版 Google Fit）等系統健康資料庫。
自 v0.7.0 版本起，本 App 提供使用者設定選用的健康資料「讀取」功能
（唯讀，供「營養師建議」分析趨勢，詳見第三節）。
三、權限說明
相機：用於拍攝飲食照片，加上時間浮水印後存到本機。
相簿（讀取）：用於從現有照片庫匯入飲食圖片。
相簿（寫入）：當你選擇匯出時，將浮水印照片儲存到你的相簿。
健康資料（讀取、選用，v0.7.0 起）：經你同意並完成後，授權本 App 讀取
Apple Health (HealthKit) / Health Connect 近 7 日的體重、體脂、活動消耗熱量、
步數、運動、睡眠，供「請 AI 營養師建議」分析趨勢；其中體重、體脂在 Health
無資料時，會改採你在 App 內手動輸入的身體組成記錄。
唯讀 —— 本 App 絕不寫入或修改你的健康資料；資料於本機處理，
僅在你主動按下分享時隨 prompt 離開 App（目的地由你選），
不會傳送至我方伺服器。此功能預設關閉，
總開關位於「我的檔案」；逐項授權可隨時於 iOS 設定 → 健康 / Android Health Connect
設定管理或撤銷；未授權或無資料的項目會自動略過。
四、分享與匯出
本 App 提供「請 AI 估熱量」、「請 AI 營養師建議」分享功能：點擊後，
食物圖片及文字資訊會被複製到剪貼簿，並透過系統 Share Sheet 開啟。
目的地由你選擇（如 ChatGPT、Gemini、訊息等）。
我們不傳送資料至任何第三方伺服器；資料是否被第三方 App 接收、儲存或處理，
依該 App 的隱私政策規範。
關於 Firebase Installation ID (FID)：Firebase SDK 在 App
初始化時會傳送一個匿名 Firebase Installation ID 作為基礎設施識別碼。FID
與異常診斷開關無關，不能對應到你的身分，重新安裝 App 即重置。
之後可隨時於「我的 → 協助改善 App」切換開關；切換後將於下次啟動 App 時正式生效。
Firebase Crashlytics 由 Google 提供，蒐集資料由 Google 處理，
詳見 Firebase 隱私政策。
九、資料保留與刪除
解除安裝本 App 即清除本機所有飲食資料。雲端備份（Google Auto Backup / iCloud）
中的資料可分別透過 Google 帳戶管理頁面或 iPhone 設定 → Apple ID → iCloud → 管理儲存空間刪除。
十、未成年使用
本 App 適用於 4 歲以上一般使用者，無針對兒童的特別功能或蒐集。
十一、政策變更
若本政策有重大變更，App 將於更新後首次啟動時提示。
十二、聯絡管道
如你對本政策或本 App 有任何問題、回饋或反應，請透過你所安裝來源的應用商店
聯繫開發者：
iOS：App Store「飲食記」頁面 → 「開發者」聯絡資訊
Android：Google Play「飲食記」頁面 → 「開發者聯絡資訊」
十三、準據法
本政策依中華民國法律及個人資料保護法解釋與適用。
DietaryLog Privacy Policy
Last updated: 2026-05-24
1. Overview
This policy describes how DietaryLog handles your personal data.
We believe in simple, transparent practices — by default, the app does
NOT collect, transmit, or store any user data on our servers. The only
exception is the optional crash reporting feature (see §8), where
anonymous crash diagnostics are sent to Google Firebase Crashlytics
to help us fix issues.
2. Local-only Storage
All data you enter (meal records, photos, calories, captions,
timestamps) is stored solely on your device (iOS sandbox / Android
internal storage). We have no access to this data.
Calorie and meal-record data is intended solely for your personal,
local self-managed wellness logging. The app does NOT write or sync your
meal records into Apple Health (HealthKit), Health Connect (including
legacy Google Fit), or any other system-level health database.
Since v0.7.0, the app provides a user-enabled, optional health-data
"read" feature (read-only, to analyze trends for the nutritionist
advice — see §3).
3. Permissions
Camera: used to capture meal photos with a timestamp watermark,
stored locally.
Photo Library (read): used to import existing meal photos.
Photo Library (add): used to save watermarked photos to your
album when you choose to export them.
Health data (read, optional, since v0.7.0): after you
consent and complete authorization, you authorize the app to read the last
7 days of weight, body fat, active energy, steps, workouts and sleep from
Apple Health (HealthKit) / Health Connect to let the "Ask AI Nutritionist"
feature analyze trends; for weight and body fat, when Health has no data,
the trend uses the body composition records you entered in the app instead.
Read-only — the app never writes to or modifies your health data.
It is processed on-device and only leaves the app, embedded in the prompt,
when you actively tap share (to a destination you choose); it is never sent
to our servers. This feature is off by default; the master
toggle is under "Profile". Per-type authorization can be managed or revoked
anytime in iOS Settings → Health / Android Health Connect settings;
unauthorized or empty metrics are automatically skipped.
4. Sharing & Export
The app provides "Estimate Calories with AI" and "Ask AI Nutritionist"
share features. When tapped, the food photo and text information are copied
to the clipboard and the system Share Sheet opens. The destination is your
choice (ChatGPT, Gemini, Messages, etc.). We do not transmit data to any
third-party server; how those apps handle the data is governed by their own
privacy policies.
If you have enabled health-data reading (§3), the shared prompt text
will also include a 7-day health trend summary (the metrics
you authorized that have data); it likewise leaves the app only when you
tap share, to the destination you choose.
Both photo and text exports (backup) are user-initiated and the process
stays on your device.
5. Advertising
The app plans to use Google AdMob to display advertisements.
AdMob may collect device identifiers (such as IDFA / Advertising
ID) to serve ads. See
Google's policy.
On iOS, on first app launch, the system will present the
App Tracking Transparency (ATT) prompt per Apple
policy, where you decide whether to allow the identifier used for
personalized ads. In regions that require prior consent (such as
the EU), the app additionally presents a consent dialog (UMP).
6. What We Do NOT Collect
Except when you opt in to the "Help Improve the App" feature
(see §8, anonymous crash diagnostics only), the app does NOT collect:
Account or identity information
Usage analytics or behavior tracking
IP address
Geolocation
7. System Backup
Android: The app enables Google Auto Backup, which backs up
app preferences and the diet journal database to your Google
account, allowing you to restore your records when switching devices.
Diet photos are excluded from backup due to their size; photos can be
manually saved to your camera roll via the share feature.
iOS: The diet journal database is stored in the app's
Documents folder and is included in iCloud backup (subject to your iCloud
settings). App preferences stored via NSUserDefaults also follow your
iCloud backup settings.
8. Crash Diagnostics
The app offers an optional crash reporting feature, disabled
by default. On first launch, after the onboarding tutorial, you
will be asked for consent. When enabled, anonymous diagnostic data is
sent automatically only when the app crashes.
When enabled, the app collects via Google Firebase Crashlytics:
Crash stack trace
Device model, iOS / Android version, app version
Pre-crash operation steps (breadcrumb)
⚠️ NOT collected: meal records, photos, calories, captions,
account or identity information.
About Firebase Installation ID (FID): The Firebase SDK
sends an anonymous Firebase Installation ID at app initialization as an
infrastructure identifier. The FID is independent of the crash
diagnostics toggle, cannot be linked to your identity, and resets
on reinstall.
You can toggle this at any time via "Profile → Crash Diagnostics";
changes take effect on the next app launch. Firebase
Crashlytics is provided by Google; data is processed by Google — see the
Firebase Privacy Policy.
9. Data Retention & Deletion
Uninstalling the app removes all local diet data. Cloud backup data
(Google Auto Backup / iCloud) can be deleted via Google account settings
or iPhone Settings → Apple ID → iCloud → Manage Storage.
10. Minors
The app is suitable for general users aged 4 and above. It has
no special features for or data collection from children.
11. Policy Changes
Material changes to this policy will be notified on first launch
after the update.
12. Contact
If you have any questions, feedback, or concerns about this policy
or the app, please contact the developer via the app store from which
you installed:
iOS: App Store "DietaryLog" page → "Developer" contact info
Android: Google Play "DietaryLog" page → "Developer contact"
13. Governing Law
This policy is interpreted under the laws of the Republic of China
(Taiwan), including the Personal Data Protection Act.
如你對本條款或本 App 服務有任何問題或反應，請透過你所安裝來源的應用商店
聯繫開發者（App Store「飲食記」開發者頁 / Google Play「開發者聯絡資訊」）。
十一、準據法與管轄
本條款依中華民國法律解釋與適用，台北地方法院為第一審管轄法院。
DietaryLog Terms of Service
Last updated: 2026-05-24
1. Acceptance
By using the app you agree to these terms. If you do not agree,
please stop using and uninstall.
2. Permitted Use
The app provides personal meal logging, browsing, and sharing
to third-party LLM services. It is intended for personal,
non-commercial use only.
3. As-Is Software
The app is provided "as is" without warranty of any kind, express
or implied, including fitness for a particular purpose, reliability,
or data integrity.
4. AI Nutritionist Advice Disclaimer
Any response or advice obtained from AI services (such as ChatGPT
or Gemini) via the share feature is for reference only and is
NOT medical advice or diagnosis. For any health, nutrition, or
dietary concerns, consult a licensed nutritionist, physician, or
other qualified medical professional.
If you enable health-data reading (Privacy Policy §3), the shared
content may include a 7-day health trend for the AI to consider; such
AI advice informed by health data is likewise for reference only
and is not medical advice, and the health data itself may be
inaccurate due to your device, sensors, or source app — do not use it to
self-diagnose or adjust any treatment.
We assume no responsibility for the content, accuracy, or
availability of information provided by AI services.
5. User Responsibilities
Verify the accuracy of your records.
Back up important data yourself (the app uses local storage;
device damage or uninstallation will result in unrecoverable data loss).
Comply with the terms of third-party services (ChatGPT,
Gemini, etc.) when using them.
6. Intellectual Property
The app software and related IP belong to the developer. Content
you input (records, photos, captions) belongs to you; the app
asserts no claim over it.
7. Limitation of Liability
To the maximum extent permitted by law, the developer is not
liable for any direct, indirect, incidental, special, or
consequential damages (including but not limited to data loss
or business interruption).
8. Third-Party Services
The app integrates the following third-party services. Their
data processing, availability, changes, or discontinuation are
governed by the respective providers' policies; the app developer
makes no warranty or guarantee on their behalf:
Google AdMob: ad display (device identifiers
such as IDFA / Advertising ID, subject to your App Tracking
Transparency choice).
See Google's advertising policy.
Google Firebase Crashlytics: crash diagnostics
(only when you enable "Profile → Help Improve the App", collected
as described in §8 of the Privacy Policy).
See Firebase Privacy Policy.
Third-party LLM services (such as ChatGPT,
Gemini): only when YOU actively share records via the system
Share Sheet — the receiving app's privacy policy governs that data.
The app provides entry points or integrations but is not
responsible for the content, accuracy, availability, changes, or
discontinuation of these third-party services. Declining crash
diagnostics ("Help Improve the App") does NOT affect any other
feature of the app.
9. Changes to Terms
The developer reserves the right to modify these terms at any
time. Modified terms take effect upon publication within the app;
continued use constitutes acceptance.
10. Contact
For any questions or concerns about these terms or the app
service, please contact the developer via the app store from
which you installed (App Store "DietaryLog" developer page /
Google Play "Developer contact").
11. Governing Law & Jurisdiction
These terms are interpreted under the laws of the Republic of
China (Taiwan); the Taipei District Court has jurisdiction over
the first instance.