Morning-ish Privacy Policy
iOS & TestFlight Beta
This policy explains how DayAscent Technologies, Inc. handles information when you use Morning-ish for iPhone, including its TestFlight beta and optional online services. It is separate from our Android privacy notice. Contact us at sia.h@dayascent.com with privacy questions or requests.
Information stored on your iPhone
Morning-ish stores your routine activities, task check-ins, alarm preferences, wake-up phrase, language, theme, personality, companion preferences, media selections, and your reason for waking up in the app’s local storage. A reason photo you select is also stored locally. The built-in companion uses locally supplied dialogue; it is not an online chatbot and does not send your motivation text or routine to a chat service.
Your reason text, reason photo, wake-up phrase, and medication or supplement check-ins are not included in the app’s media or object-photo requests. The app does not integrate with HealthKit. You do not need to enter an email address or password to use routine and alarm features.
Local app information may be included in iCloud or computer backups, depending on your device settings. Copies in backups are managed through Apple and your backup settings; “stored locally” does not mean “excluded from backup.”
Optional online photo checks
For supported activities, you may take an object photo and choose “Check photo online.” Before each upload, the app asks you to confirm. It resizes and re-encodes the image as a JPEG without copying the original camera metadata. The image and a predefined activity category are sent to our Google Cloud-hosted service and Google’s AI processing service to check for a matching object. The request does not include your custom task title or other routine records.
Removing metadata does not remove information visible in the image. Photograph objects only, and avoid people, private writing, medication, documents, or other sensitive details. An object match does not prove that an activity was completed. You may decline the upload, retake, defer, or skip the activity.
Our photo service is designed to process the image without saving raw photo bodies to application storage or application logs. This is not a promise of zero retention by every provider. Google may retain processing data for caching, safety, or abuse monitoring under the terms and settings applicable to the service. See Google Cloud’s AI data-governance information. The app releases its in-memory task photo when the photo-check view is dismissed; it does not add these photos to a routine photo history.
Reason photos, celebration photos, and sharing
Your saved reason photo is separate from object checks and is not uploaded by that feature. You can remove it under “My reason to wake.”
The optional celebration editor uses a separate camera image, a photo you select, or artwork. Image effects run on your iPhone. The Fresh effect can locate face regions for smoothing; it does not identify a person or create a saved face-identity profile. Face-location results are not sent to our server. Task-check photos are not reused in the celebration editor.
Choosing Share opens the iOS share sheet. A destination you select receives the exported image and handles it under its own policy. Morning-ish does not automatically post it. The app creates temporary JPEG exports; exports older than 24 hours are removed the next time you share another celebration image, rather than on a guaranteed 24-hour timer. Copies you save or share elsewhere remain under those destinations’ controls.
Guest identifiers and online services
Optional media and online photo checks use Firebase Authentication to create a guest identity automatically. Although Firebase calls this anonymous authentication, the identifier can distinguish your guest account: it is pseudonymous, not completely anonymous. Google and our service process authentication, network, and operational information to provide access and protect the service, including IP addresses, request times, status information, and usage-limit records.
Media request URLs include search terms or selected media identifiers and may appear in infrastructure records. The app does not send your entire routine as part of these requests. See Firebase’s privacy and security information. Signing out of guest access or uninstalling does not by itself request deletion of the backend guest record.
Optional YouTube and podcasts
With your external-media consent, the app uses your podcast searches and selected video, playlist, podcast, or episode identifiers to retrieve content through our service and providers such as Google/YouTube and Listen Notes. Playback connects to YouTube or the podcast host. Those services receive network information, including your IP address, and may process playback information or use cookies and similar technologies under their own policies.
The embedded YouTube player uses a nonpersistent web-data store, but providers still receive network requests. See the Google Privacy Policy and Listen Notes Privacy Policy; individual podcast hosts’ policies also apply. You can turn off autoplay or use “Remove saved media & consent” in Morning Media. Withdrawing media consent does not undo previous provider processing and is separate from confirming an individual photo upload.
Microphone, speech, and permissions
The voice wake-up challenge listens when you activate it and grant microphone and speech-recognition permission. This iOS build requires on-device speech recognition; if it is unavailable, the app offers the pattern challenge instead of falling back to online recognition. It checks recognized words against your phrase, not your voice identity. The app does not upload audio or transcripts or save a recording history.
Camera access supports photos you choose to take. The system photo picker gives the app the image you select. Alarm permission supports alarms you schedule. You can manage these permissions in iOS Settings. This build does not request contacts or precise-location access.
Local diagnostics and TestFlight
The optional “Local diagnostics” setting stores a few counters on your device, such as setup or routine completion and media failures. You can turn it off and use “Clear diagnostics.” This iOS build does not include Firebase Analytics or Crashlytics reporting.
TestFlight is separate. Apple automatically collects beta usage and crash information and shares it with us. This can include your invitation email, installation status, device and OS information, sessions, and crash logs. Feedback you submit, including screenshots and comments, is also shared with us. The app’s local-diagnostics switch does not disable TestFlight collection. We use this information to support testing and improve Morning-ish. Review Apple’s TestFlight privacy notice before participating, and avoid including sensitive content in feedback.
Purposes, recipients, and location of processing
We use information to provide the features you request, authenticate guest access, limit abuse and service costs, investigate problems, manage the beta, and respond to support or privacy requests. Service providers receive information as described above. Information may also be disclosed when required by law or necessary to address security incidents or protect rights. TestFlight information is handled subject to Apple’s restrictions.
This iOS beta has no advertising SDK or cross-app advertising-tracking integration. We do not sell personal information or use it for targeted advertising. Our application backend is hosted in the United States; Google, Apple, and media providers may process information in other countries. Processing is not guaranteed to remain in your country.
Retention and your choices
- Local routine and preference data: retained until changed, removed, or the app and its data are deleted. Offloading the app may preserve data. Backups and separately shared images require separate management.
- Photo processing: handled as described above. Provider processing and retention are governed by the applicable service terms and configuration; we do not promise immediate deletion from every provider.
- Guest records, service limits, and infrastructure logs: retained under the applicable backend configuration and provider policies. Disabling optional features stops future requests from those features, but does not automatically erase earlier server records.
- Beta records and support: we retain records as needed to administer testing, investigate issues, respond to requests, and satisfy applicable obligations. Apple controls retention in its own TestFlight service; its notice describes its separate retention practices.
For access, correction, deletion, or other privacy requests, email sia.h@dayascent.com. Depending on where you live, applicable law may provide additional rights, including the right to complain to a privacy regulator. We may need limited information to verify your request and locate relevant records. Because guest access does not associate your email with your guest identifier, an email alone may not identify that guest record. Do not send passwords, authentication tokens, or private photos. We cannot remotely erase data stored only on your iPhone or in backups you control.
Security, children, and policy changes
App-service connections use HTTPS, and online photo and media requests require guest authentication. Local routine files and saved reason photos use iOS file protection. No system can guarantee complete security.
If you believe a child has provided information that should be removed, contact us. This notice does not authorize a child’s participation in the beta; eligibility is governed by the beta’s applicable participation requirements.
We will update this notice when the app’s data practices change and identify the effective date of the updated policy. Changes requiring consent will be presented through the applicable feature or permission flow.