Privacy Policy — My Daily Goal

Effective date: September 20, 2025

App: My Daily Goal
Developer/Entity: My Daily Goal (individual developer)
Contact: [email protected]
Launch region: Worldwide

1) Who we are

My Daily Goal is developed by My Daily Goal (individual developer). Contact: [email protected].

2) What this app does

Each day you set one tiny intention, optionally add a quick plan, review it tomorrow, and (optionally) record a simple mood. The app is designed to work without an account and keep data on your device by default.

3) What data is stored (on device)

• Daily entries (local database): boundary date, status (open/done/missed/partial), optional felt score (1–5), optional mood label/energy/tone, selected barriers, optional planning fields (when‑window start/end/anchor), timezone offset minutes, created/reviewed timestamps. Optional free‑form intention/note text is stored locally. The default CSV export excludes free‑text fields.
• Preferences (local): day boundary hour, daily reminder time/toggle, App‑Lock setting, locale/region for help resources, optional feature flags for LLM helpers, and the last selected calendar id (if you choose to create calendar events).
• Safety flags (local): compact numeric flags that indicate whether certain phrases may need support. Triggering text is not stored because checks run on‑device by default.

4) What we don’t collect by default

• No accounts, no cloud sync, no ads, no third‑party analytics SDKs.
• No contacts, microphone, or precise location.
• We do not transmit your intentions or notes to our servers (we don’t run any).

5) Optional features & permissions

• Notifications: You can enable/disable in Settings. Reminders are scheduled at your selected local time. Text is neutral (e.g., “Add today’s goal”) and never includes your intention.
• App‑Lock (FaceID/TouchID/Passcode): Optional; protects in‑app access.
• Calendar (optional): If you choose, the app can create calendar events (requires calendar permission). We only read the list of writable calendars to let you pick one and store the last selected calendar id locally.
• Purchases (subscriptions): Uses RevenueCat to manage trials/entitlements with the App Store/Google Play.
• Network: Used for purchases/subscription validation, to refresh regional help resources, and to open links you tap.
• Export: You can export a CSV (biometric confirmation may be requested by the OS) and share it using the system share sheet.

6) Purchases & subscriptions (RevenueCat)

We use RevenueCat to manage free trials and subscriptions. When you view the paywall, purchase, or restore, RevenueCat processes:

• App store receipts / purchase tokens, product identifiers, price and currency, and basic device/app metadata (e.g., platform, app version) to validate entitlement.
• An anonymous app user identifier (we do not set our own user id). We do not receive your payment method details; Apple/Google process payments.

RevenueCat is used only to determine your entitlement (e.g., “Pro” access) and for anti‑fraud/analytics at the purchase infrastructure level. No intention text or app content is sent to RevenueCat.

7) Safety & crisis resources

The app isn’t a crisis service. If you’re in danger, call your local emergency number. When certain phrases are detected, the app shows regional support options; those checks run on‑device and do not store the triggering text.

8) Legal bases (EU/UK)

• Core app processing happens on device under your control.
• Notifications, calendar access, and LLM helpers are by consent (opt‑in; you can change this in Settings).
• Purchases/subscriptions are performed to fulfill a contract; store receipt validation and limited anti‑fraud by RevenueCat are our legitimate interests.
• For optional LLM helpers (disabled by default), if enabled we may send minimal text snippets or categories to a model provider or a self‑hosted relay to generate suggestions; this runs under consent and you can keep it off.

9) Your rights

You can export or delete all data in the app at any time. For questions, email [email protected]. If we add account/sync in the future, we will update this policy with full GDPR/CCPA details.

10) Security

Data stays on your device and benefits from your device’s encryption. App‑Lock can add a biometric gate. No system is perfectly secure, but we limit scope and avoid unnecessary collection.

11) Retention

Data remains until you delete it or uninstall the app. We keep no server copies.

12) Children

The app is intended for ages 13+ and general wellness. It is not medical advice.

13) LLM‑assisted features

The app may send minimal text to a model provider or a self‑hosted relay for:

• Goal classification (broad/specific) or divisibility suggestions: short text of your goal and non‑identifying context; outputs are small labels/suggestions. Caching may occur on‑device.
• Safety classification (self‑harm): if enabled, a clipped portion of text (≤160 chars) may be sent for a numeric risk rating. We do not store your text server‑side.

14) Changes

We may update this policy as features evolve. Material changes will be noted in‑app. Effective: September 20, 2025.