DayFlow AI Privacy Policy

Effective: August 30, 2026 · Updated: October 13, 2026 · Version V2.0

Thank you for using DayFlow AI. DayFlow AI is developed and operated by Pan Xueyan, an individual developer (we / us). This policy explains how the app processes, stores, and transfers information, and how you may exercise your rights. Please read it carefully before use.

1. Information we collect

DayFlow AI is a local-first personal management app. Core records stay on your device. Data leaves the device only when you choose a custom AI model, enable iCloud sync, or complete an App Store transaction, as described in this policy.

1.1 Information you enter

Nickname, avatar — displayed in the Profile page
Events, todos — for calendar and reminders
Running plans and records — for running statistics
Transactions, monthly budgets — for spending and budget insights
Goals (budget, savings, mileage) — for progress tracking

1.2 Device information collected with permission

Location (foreground): record running route, distance, pace — only while running
Location (background): continue recording when screen is locked or app is backgrounded
Storage, Photos: pick avatar, save running screenshots, export/import data
Camera: take an avatar photo
Notifications: event reminders, running start/pause/finish cues
Calendar: optional, sync events to the system calendar
Microphone: optional, only enabled when you actively tap the voice button, for on-device speech-to-text that fills the input field

Important: DayFlow AI operates no application server and does not receive or proxy your AI content or sync files. Other than custom-model requests, iCloud sync, and App Store transactions that you actively use, we do not upload your personal data. See Section 6 for the data flows.

About voice input: voice-to-text always uses on-device (offline) speech recognition. Audio is never uploaded to Apple, Google, or any third-party server, and no audio recording is saved to disk.

1.3 Information we do NOT collect

No contacts, SMS, or call logs
No browser history or other app usage
No precise device identifiers (IDFA, MAC)
No phone number, ID number, bank card, or biometric data
No advertising, analytics, or crash-reporting SDKs

2. How we use this information

The app processes this information solely to deliver DayFlow AI features:

Display, edit, and search the events, todos, runs, and transactions you entered
Compute local statistics (monthly spending, consecutive running days, total mileage)
With your permission, write events to the system calendar and push local notifications
When you actively trigger export or import, package data as a single JSON file

We do not use your information for personalized advertising, targeted marketing, or behavioral profiling, and we do not independently sell or disclose it to third parties. Transfers initiated when you choose custom AI, cloud sync, or app-store transactions are described in Section 6 and governed by the relevant provider's policies.

3. Storage and security

3.1 Storage location

iOS: a local database inside the app sandbox
Custom-model endpoint, model ID, and API key: stored in the app's private directory on your device and never synchronized to our servers; remove or clear the AI settings to stop future use

3.2 Retention

Local data remains on your device until you delete it in Profile → Data, clear old data, or uninstall DayFlow AI. Sync files already written to your cloud account are retained under that provider's policy; disabling sync does not automatically delete existing cloud files.

3.3 Security measures

Data is stored in the OS's private app sandbox and cannot be accessed by other apps
Events, todos, running, ledger, and statistics are processed locally by default
Custom AI requests use HTTPS directly to the endpoint you enter. When you enable sync, incremental JSONL operation files are written to your iCloud container
We recommend enabling device-level passcode, fingerprint, or face unlock as a final layer

4. Your rights

Access and correction: view and edit all your data in Profile and each feature page
Delete: long-press a single record to delete; bulk operations available in Profile → Data
Revoke permissions: revoke Location, Photos, Camera, Notifications at any time in system settings
Data portability: export all data as a JSON file via Profile → Data
Account and deletion: DayFlow AI has no app account. Uninstalling deletes local data, while existing sync files must be deleted separately from the relevant cloud account

5. Third-party SDKs and open-source components

DayFlow AI uses the following client-side frameworks and system capabilities. Their access is determined by the features you enable and the permissions you grant:

Expo SDK 57: React Native runtime
expo-sqlite: local SQLite database read/write
expo-location: read GPS location for running tracks
expo-notifications: local notifications (event reminders, running cues)
expo-calendar: read/write system calendar (optional)
expo-image-picker: pick or capture an avatar image
expo-media-library: save screenshots to the photo library
expo-file-system: local file read/write (import/export)
react-native-view-shot: page screenshot capability
expo-speech-recognition: on-device speech-to-text (no audio uploaded)
expo-audio: audio session management for speech recognition

6. AI Assistant and third-party LLM services

This section describes AI-request data handling. See Section 6.6 for iCloud incremental sync.

6.1 When AI requests occur

The first-use AI notice explains the feature. Accepting it or this Privacy Policy is not permission to share data with a third-party AI service
Before a custom-model request, a separate notice identifies the actual recipient, endpoint, provider privacy policy, data categories and purpose. Data is sent only after you select Allow sending. Declining does not affect non-AI features
Connection tests authorize fixed test text only. Conversations and additional local records have separate permission scopes. Broader scopes or changes to the recipient, endpoint, model or policy require renewed permission
You actively start a conversation, test a connection, or generate a report; DayFlow AI does not call a model in the background on a schedule
Apple on-device mode requires no endpoint or API key. Only custom models require an endpoint and key configured by you; DayFlow AI does not obtain, collect, or bundle keys

6.2 What is sent

In custom-model mode, your device sends the content needed for the current request to your chosen endpoint. Apple on-device mode processes it on the device without sending it to an external model provider. A request may include:

The question text you typed, plus the most recent turns of the current conversation
After permission for local records, relevant summaries selected for the feature and period: event titles and times, todo titles and completion state, run dates / distance / pace, transaction dates / amounts / categories / merchants / notes and aggregate figures. Weekly or monthly reports and historical queries may include the selected historical period, not just the last seven days
Text-only conversations do not attach additional local-record summaries, but necessary conversation history may include personal information, record receipts or earlier query results
Your API key is transmitted to the configured endpoint for authentication; it is not added to model prompts
The current date, weekday, and UI language, so the model can correctly interpret words like yesterday or this month

6.3 What is NOT sent

Your nickname or avatar image is not automatically read and attached
Not GPS track coordinates (only aggregate values such as distance and pace)
Device identifiers, system accounts and contacts are not automatically read and attached. Personal information you put in messages or records may be transmitted with the relevant content
No direct upload of the entire database or backup file. Summary scope depends on the feature, selected period and necessary conversation history

6.4 Who receives it and who is responsible

The recipient depends on the mode you select in AI Settings. DayFlow AI operates no relay server and does not bundle a custom-model API key, endpoint, or model ID. Custom requests go directly from your device to the provider you specify; we cannot inspect or retain their content. Two modes are available:

Apple on-device models: on supported devices, Apple Intelligence processes prompts and local summaries on-device. They are not sent to DayFlow AI or an external model provider. Availability depends on device, OS, language, Apple Intelligence settings, and system model status
Custom model: you enter the endpoint URL and API key yourself. Choose either the OpenAI-compatible protocol (/v1/chat/completions) or Anthropic Messages (/v1/messages). AI Settings requires the actual recipient name and a valid HTTPS privacy-policy URL. These are shown before sending; protocol or model names are not treated as the recipient identity

Whatever you send is also governed by that provider's own privacy policy and terms, including whether they retain logs or use content for model training. We cannot make commitments on a provider's behalf, so please read their policy before entering a key. If you do not want any data to leave your device, use Apple on-device models (this is the factory default) and do not configure a custom endpoint.

6.5 Turning it off and withdrawing consent

Use Profile → AI Settings → Data sharing and permission to withdraw third-party AI permission. New requests are blocked immediately and in-progress requests are aborted where possible. Already-sent data cannot be recalled. Records and endpoint settings remain; sending again requires renewed permission
Stop using a custom model, clear its API key, or switch to Apple on-device mode to avoid future use of that custom endpoint
Content already sent is handled by the provider under its own policy; request deletion directly from that provider
Local chat history can be cleared on the AI Assistant screen

6.6 About cloud sync

When you enable it, DayFlow AI writes incremental JSONL operation files to your iCloud container, so devices signed in to the same Apple ID can read them. Sync content may include events, todos, transactions, and complete run records including route coordinates. It never passes through our servers. Disabling sync stops future reads and writes but does not delete existing cloud files; export a local JSON backup before uninstalling or changing devices.

7. Minors

DayFlow AI is primarily intended for adults. If you are below the minimum age required in your country or region, use it only with a parent or guardian's consent and supervision. We do not knowingly collect children's personal information; if we learn of collection without appropriate consent, we will address it promptly.

8. Changes

We may update this Privacy Policy from time to time. When material changes occur, we will notify you conspicuously in-app (e.g., presenting the privacy consent screen again).

9. Contact

Personal information handler: Pan Xueyan (individual developer). For questions, complaints, or suggestions about this policy or the handling of your personal information, contact us at dayflow.cn@outlook.com. We will respond within 15 working days.

10. Governing law and local rights

This policy is governed by the laws of the developer's place of establishment, without limiting any mandatory privacy, data-protection, or consumer rights available where you live. Where local law provides stronger or non-waivable rights, that law prevails. Disputes should first be addressed through good-faith discussion and, if unresolved, by a court with lawful jurisdiction.

DayFlow AI · V2.0 · 2026-10-13