Morning-ish Privacy Policy
This policy explains how DayAscent Technologies, Inc. handles information when you use the Morning-ish Android app and its supporting services. For privacy questions or requests, email sia.h@dayascent.com.
Information on your device
The app stores your alarm settings, wake-up phrase, theme and personality choices, routine activities and completion records, media selections, and your reason for waking up in app storage on your device. Your motivation text and motivation photo are not sent to our photo-checking service. Medication and supplement checkmarks are stored locally and are not included in the usage events we send. Android app backup is disabled in this version.
The app does not require you to provide a name, email address, or password to use its core alarm and routine features.
Online photo check-ins
If you choose a supported photo activity, the app asks for your consent before sending that photo for an online check. It resizes and re-encodes the image as a JPEG, removing camera metadata. The image and a predefined activity category, such as a mug or toothbrush, pass through our Google Cloud-hosted server to Google's AI service. Your custom activity title, written reason, and other routine records are not included in that request.
The AI checks for a visible object and returns a result. It does not prove that you completed an activity. Avoid including faces, private writing, personal documents, or other sensitive information in check-in photos. Photographing an object can still reveal information about you or your surroundings.
Our server processes the photo in memory and does not deliberately save photo bodies to application storage or application logs. This does not mean that every service immediately deletes all data: Google's AI service may retain inputs and outputs for caching, safety, or abuse monitoring under its applicable terms and settings. See Google Cloud's AI data-governance information. Google's published terms restrict using customer data to train models without permission or instruction.
An internet connection and a successful check are required to complete a photo-mode task. If you decline upload or the check fails, you can retake, retry, defer, or skip the task, or change an eligible activity to a non-photo mode. The app deletes its temporary check-in image when the photo is discarded; interrupted sessions or the external camera app may leave separate temporary files or copies.
Optional celebration photos and sharing
After your morning routine, you can take a separate celebration selfie, choose a photo, or use artwork. Lighting effects and optional gentle skin smoothing are processed on your phone. Face detection for smoothing estimates the position of a face; it does not identify you. These detection results are not saved or sent to our server or AI photo-checking service.
Your preview includes a small Morning-ish mark and an optional personality-based caption. We do not add your task details, motivation text, or check-in photos. Choosing Share opens Android's sharing options. A selected receiving app may receive the exported image before you publish it there, and its privacy policy applies. Morning-ish does not automatically post to social networks or link your social accounts.
Temporary celebration images and exports are stored in the app's local cache. Old files are cleaned up when you next open the celebration editor after they are more than 24 hours old, except the currently selected image. Clearing app storage or uninstalling also removes that cache. Copies saved by your camera or receiving apps remain under those apps' controls. Exported images are re-encoded without copying original camera metadata.
Guest access and service protection
Online media and photo services use Firebase Authentication to create a guest account automatically. This has a unique identifier even though you do not enter an email address or password; it is pseudonymous, not completely anonymous. Firebase processes authentication and technical information such as IP addresses. Our backend uses a hashed form of the guest identifier and usage counters to enforce request limits and protect service availability.
Hosting and service providers may process network and operational information, including IP addresses, request times, URLs, response codes, and device or browser information. We do not include image bodies in our application logs. Request URLs for media may contain your search terms or selected media identifiers.
YouTube and podcasts
When you use Morning Media, our server sends selected video, playlist, podcast, or episode identifiers and podcast search terms to YouTube/Google or Listen Notes to retrieve content information. Playback connects to YouTube or the podcast publisher's hosting service; those providers receive network information such as your IP address and may use cookies or similar technology under their policies. Podcast images may also load from third-party hosts.
These providers handle information under their own policies: Google Privacy Policy and Listen Notes Privacy Policy. Other podcast hosts' policies apply to their streams. You can turn off autoplay and choose not to use Morning Media.
Optional usage and crash reports
Usage reporting and crash reporting are off by default and have separate controls under Settings → Usage & crash reports. If enabled, Firebase Analytics receives general app actions and screen names, such as completing setup or a routine, along with app-instance and technical information. Firebase Crashlytics receives crash diagnostics, such as device model, app version, and error traces. These reports use identifiers and are not anonymous.
We do not deliberately add photos, motivation text, secret phrases, task names, medication records, or media links to these reports. Advertising identifier collection and advertising personalization are disabled in this build. Turning reporting off stops future collection by these controls; it does not automatically erase information already received by providers. Unsent crash reports are deleted when crash reporting is disabled, and disabling usage reporting resets local analytics data.
Microphone, camera, and other permissions
The spoken wake-up challenge uses the microphone when you activate speech recognition. Recognition runs on-device when supported; otherwise the installed speech-recognition provider may process audio online under its own policy. Morning-ish checks recognized words rather than identifying you by your voice. You can use the pattern challenge instead.
Photo check-ins open your device's camera app, and motivation-photo selection accesses the image you choose. Alarm, notification, full-screen, vibration, and background media permissions support the features you enable. This build does not request contacts or precise-location access.
Why information is used and who receives it
Information is used to deliver requested features, verify guest access, limit abuse and service costs, diagnose problems, improve the app when you enable reporting, and respond to support requests. The current app has no advertising integration or data-sale feature. Information is processed by our infrastructure and feature providers as described above. We may disclose information when legally required or necessary to address security incidents or protect users' rights.
Our cloud backend is hosted in the United States. The AI uses a global service endpoint, and providers may process information in other countries. The current service does not promise processing exclusively in your country.
Private beta activation and feedback
If you join the private beta, activating with your invitation code associates your Firebase installation identifier with your approved tester record and starts your testing period. The beta service maintains application, approval, agreement-signing, access, activation, survey, and reward-eligibility records. Applications and surveys are submitted through Google Forms; confidentiality agreements are handled by our electronic-signature provider. These services receive the information needed to provide those functions.
When you choose Report a Bug or Send Feedback, the app sends the text you enter, an optional screenshot, your app version, device model, operating-system version, and tester identifier to DayAscent's Google Cloud-hosted beta service. Screenshots are re-encoded to remove camera metadata. Review images before attaching them and avoid passwords or unnecessary personal, health, or other sensitive information. Reports are used to investigate problems, improve the app, and administer the beta. They are accessible to authorized administrators, not other testers. Core alarm and routine features do not require a beta feedback submission.
Application and feedback records are retained for 24 months after the beta ends. Signed agreements and legally required payment records follow a separate retention policy and may need to be retained longer. To request access, correction, or deletion of your beta records, email sia.h@dayascent.com from your application email, identify Morning-ish beta records, and describe the request. We may need to verify your identity and may retain records required for legal obligations. Uninstalling the app does not delete beta records.
Retention and deletion
- Local app information: retained until changed or removed through the app, or until you clear the app's storage or uninstall it. Clearing storage or uninstalling removes saved settings and may affect alarms. Files separately saved by your camera or photo library are controlled by those apps.
- Uploaded check-in photos: not stored by our application server; Google's processing and retention are described above. We cannot promise zero retention by Google.
- Guest accounts and usage counters: remain in backend systems until removed. There is currently no automatic inactivity-deletion schedule. Counter values are reused for new limit periods rather than storing a full activity history.
- Diagnostics and infrastructure records: retained according to the applicable Firebase and Google Cloud configuration and service policies. Switching reporting off does not retroactively delete server records.
- Support messages: retained as needed to respond, resolve issues, and meet applicable obligations.
For access, correction, deletion, or other privacy requests, contact sia.h@dayascent.com. Depending on where you live, you may have additional rights under applicable law. We may need limited information to verify a request or identify a guest account. For guest access that has not been linked to a beta tester record, an email alone may not identify its records. Beta-linked installations can be identified using the verified beta application email. Do not send passwords, authentication tokens, or private photos. Uninstalling the app does not automatically delete its backend guest account.
Security, children, and changes
App service connections use HTTPS, and access to backend photo and media checks requires authentication. No system can guarantee complete security. If you believe a child has provided information that should be removed, please contact us.
We will update this policy when our practices change and revise its effective date. Material changes may also require an in-app notice or renewed consent. This policy describes the current Android test app, not unbuilt AI companion or account-sync features.
Privacy contact: DayAscent Technologies, Inc. — sia.h@dayascent.com