MeByDay is developed by Mu Tang. This policy covers the MeByDay iPhone and iPad app.
No developer collection or tracking
We do not collect your journal data through the app. MeByDay has no separate user account, advertising, analytics SDK, tracking, or developer-operated photo server. We cannot browse your private CloudKit records. The app does not score your appearance, identify you, or build a biometric profile.
Your journal and device storage
Photos, their recorded dates, plan dates and names, date-stamp styles, and app settings are stored in the app’s local container. The app assigns random identifiers to records and the recording device to coordinate synchronization and recording ownership. Photos are normalized as JPEG images without carrying over location metadata. MeByDay does not request your location.
Confirmation locks an individual original and its recorded date. You may still change its date-stamp appearance. An ended plan can remain on the device for viewing and export.
Optional private iCloud synchronization
If you enable private sync, the app sends journal photos and metadata to your app-specific CloudKit private database, hosted by Apple and associated with your system Apple Account. The app uses Apple’s CloudKit identity to prevent mixing different accounts’ journals. This is not an iCloud Drive folder, a public database, a shared photo feed, or a developer-accessible photo service.
Apple handles iCloud under its own terms and privacy policies. Private database access is not a promise of additional end-to-end encryption by MeByDay. iCloud availability, account settings, network connectivity, and storage quota affect synchronization. Local saves and completed sync are shown separately. Sync runs when the app is active or when you request it; background real-time delivery is not promised.
Permissions
Camera permission lets you take a daily photo. Optional notifications remind you to record. Optional device authentication uses Apple’s system authentication prompt, including Face ID where available; MeByDay does not receive face templates, biometric data, or your device passcode. Permission settings can be managed in iOS Settings.
Deletion, backups, and exports
You may end a plan and retain its records, or permanently delete the entire project. Project deletion removes its local content and queues deletion of synced content. When offline, the cloud operation remains pending until the app reconnects. A minimal revocation marker containing a random project identifier and deletion state remains in the private cloud database to prevent an old device from restoring deleted content. Offline devices apply deletion when they next sync.
Exports, time-lapse videos, and complete journal backups go to destinations you choose through system sharing and file controls. These copies remain until you remove them separately. Other apps and services handle received copies under their own policies. Device backups and restoration are controlled by your Apple settings. Removing the app alone is not the same as requesting project deletion from iCloud.
Purchases and support
Apple processes the one-time App Store purchase. MeByDay has no subscription or in-app purchase and does not receive payment-card details.
If you email support, we receive the address and message you send and use them to answer your request. Please do not send private journal photos, passwords, or identity documents. A description or fictional example is preferred.
Children and policy updates
MeByDay does not knowingly collect children’s personal information. This policy may be updated when the app changes; its effective date is shown above.
Contact
For support or privacy questions, email [email protected].