Dayly Privacy Policy
Effective date: September 11, 2026
Last updated: September 11, 2026
Dayly is operated by Fombo Network Co., Ltd ("Dayly," "we," "us," or "our"). This Privacy Policy explains how we handle personal information when you use the Dayly mobile app, visit our Dayly legal and support pages, and contact us for support.
Contact email: fombo888@gmail.com
Dayly helps adults plan household meals, organize shopping lists, and find recipe ideas from available ingredients. You do not need to create a Dayly account. This does not mean that your use is anonymous: our service providers process app identifiers, device information, and other information described below.
1. Information we process
Information you enter or create
| Category | Examples | Purpose and handling |
|---|---|---|
| Household details | Member names or nicknames, age groups, and household size | Stored on your device to organize household preferences and estimate portions. You can use nicknames; full legal names and exact birth dates are unnecessary. |
| Dietary information | Allergies, ingredients to exclude, dislikes, dietary patterns, and custom entries | Stored on your device and used to check recipes. Combined household restrictions are also sent to Google when generating AI meal ideas. Some entries may reveal health information or religious beliefs. |
| Planning preferences | Meal days and types, cooking equipment, time limits, weekly grocery budget, preferred store, goals, and leftover preferences | Stored on your device. Relevant settings are used in AI requests; selecting a store does not provide access to your shopping account. |
| Meal and shopping activity | Generated plans, recent dishes, saved or disliked dishes, pantry ingredients, and shopping-list selections | Stored on your device to maintain your plan and avoid unwanted repetition. Relevant dish names and pantry ingredients may be included in AI requests. |
| Photos and ingredient results | A photo you take or select for the Fridge feature, and ingredients identified from it | The selected photo is sent to Google for AI analysis. Confirmed ingredients may be saved in your pantry and used to generate recipes. |
| Referral information | Where you heard about Dayly and any invitation or creator code you enter | Stored locally and sent to Google Analytics for Firebase to understand acquisition sources. |
| Support communications | Your email address, message, and attachments you choose to send | Used to respond to your request, investigate issues, and manage privacy requests. Avoid sending unrelated medical or payment information. |
Information collected through the app and its providers
Usage and analytics. We use Google Analytics for Firebase to understand app use and reliability. Events include onboarding progress, household and meal counts, the selected grocery budget, plan generation and cache results, recipe-check failure counts, photo-scan success and ingredient counts, paywall interactions, and purchase or restoration outcomes. Our custom analytics events do not intentionally include member names, full allergy lists, or uploaded photos. Referral codes are sent as entered after formatting, so do not put personal information in a code.
Technical information. Google and Adapty may process app-instance or installation identifiers, Adapty profile identifiers, device or vendor identifiers, IP addresses, approximate location derived from IP addresses, operating-system and app versions, language settings, and service activity. Advertising identifiers may be collected where available under device settings and permissions. Such identifiers can distinguish an app installation or device even without a Dayly account.
Purchases. Apple or Google processes store payments. We and Adapty receive information needed to verify purchases and provide subscription access, such as product and transaction identifiers, purchase or receipt records, subscription status, renewal or expiry information, and trial eligibility. Dayly does not receive your full payment-card number or your store-account password.
Website visits. Our legal and support pages are served from www.yangms.com. The web server may process IP addresses, requested URLs, timestamps, and browser information to deliver pages, maintain security, and diagnose errors. These pages do not include advertising pixels or client-side analytics scripts.
App security and configuration. Firebase App Check processes app or device attestation information and tokens, using Apple App Attest or Google Play Integrity as applicable. Firebase Remote Config uses installation-related information to deliver app settings. These services support abuse prevention and app operation.
Dayly does not request access to your contacts, microphone, precise device location, Apple Health, or Health Connect in this version. Photo selection and camera access are used for the features you initiate, rather than to scan your entire photo library.
2. AI processing and photos
Dayly uses Google's Gemini Developer API through Firebase AI Logic for meal-plan generation, ingredient recognition, and recipe illustrations.
For planning, the app prepares a household-level request containing relevant ingredient exclusions, dietary patterns, portion estimates, meal schedule, cooking constraints, budget, goals, and available ingredients. Recent, saved, or disliked dish names may also be included. Member-name fields and individual age-group fields are not intentionally placed in the planning request; age groups are used on the device to calculate portions. Free-text entries, photos, and generated content can still contain personal information.
For ingredient recognition, the photo you select is uploaded to Google. The app attempts to resize and compress it; a processing failure may result in the selected image bytes being sent without that additional compression. Do not include faces, documents, medication labels, addresses, or other unrelated private details. We do not promise that all image metadata is removed.
For recipe illustrations, the app sends the dish title and selected ingredients. Generated food illustrations and their titles may be placed in a shared Google Cloud Firestore cache and reused for other users. This shared cache is for generated recipe illustrations, not your uploaded fridge photos or household profile. Generated titles can reflect dietary choices, so avoid putting identifying information into custom inputs.
Google's handling of AI inputs and outputs: We use Gemini under Google's paid-service terms. Google does not use our API prompts or responses to improve its products under those terms. Google may retain and review request content for abuse prevention, security, and legally required disclosures. We have not opted into an additional AI data-sharing program.
The app does not maintain an uploaded-photo gallery on our own server. It releases its working photo reference after scanning, but copies may remain in your photo library, system or picker caches, or provider systems. Closing the screen is not a request to erase data held by Google. See Section 6 for retention.
3. How we use information
We process information to:
- Generate and display meal ideas, estimate quantities, apply ingredient restrictions, and maintain shopping lists and pantry records.
- Personalize suggestions using the preferences you provide and the dishes you keep or reject.
- Verify purchases, restore eligible subscription access, and provide trials or paid features.
- Deliver local meal and subscription reminders when supported and permitted on your device.
- Understand feature use, acquisition sources, purchase flows, and operational errors.
- Protect the app and its services, prevent misuse, answer support requests, and meet legal obligations.
Allergy and dietary information is used for the meal features described here. The app does not provide medical care, and this policy is not a statement that Dayly is a HIPAA-covered healthcare service. We do not use your allergy entries to make employment, insurance, or credit decisions.
4. When information leaves your device
| Recipient | Reason for disclosure | Information involved |
|---|---|---|
| Google: Firebase AI Logic and Gemini | Generate meal ideas, recognize ingredients, and create illustrations | AI requests, selected photos, and generated outputs described in Section 2 |
| Google: Cloud Firestore | Reuse generated recipe illustrations | Generated image, dish title, cache identifier, style version, and timestamp |
| Google: Analytics for Firebase | Measure app use and acquisition | Usage events, referral information, identifiers, and device information |
| Google: Firebase Remote Config and App Check; Apple or Google attestation services | Deliver configuration and verify app integrity | Installation information, technical request information, attestation material, and tokens |
| Adapty | Manage subscriptions, paywalls, and purchase analytics | Subscription, transaction, profile, device, and network information |
| Apple App Store or Google Play | Process payments, manage subscriptions, restore purchases, and handle store reviews | Information processed through the store and its account systems |
| Google font delivery services | Download app fonts when not already available locally | Network request information, including IP address |
| Google Gmail | Receive and respond to support or privacy emails | Email address, messages, and any attachments you send to our contact email |
| Apps and people you choose | Share a weekly plan or shopping list | The image or text you choose to share |
Additional provider information is available in Firebase's privacy information, Google's Privacy Policy, Gemini API terms, Adapty's End-Users Privacy Policy, Apple's Privacy Policy, and Google Play's privacy information. These links explain provider practices; they do not replace our responsibility for the information we control.
We may disclose information to professional advisers or authorities where reasonably necessary to comply with law, respond to valid legal process, protect rights or safety, or investigate misuse. A business transfer may involve relevant information, subject to applicable law, notice requirements, and restrictions on health data.
Advertising, sale, and targeted-advertising sharing: We do not sell personal information or share it for cross-context behavioral advertising. We do not send user data to advertising platforms such as Google Ads or Meta through advertising integrations. We use the Firebase and Adapty services described above to provide the app and understand its use. These providers may still process app or device identifiers as described in this policy. We do not use sensitive dietary information for advertising.
5. Permissions, notifications, and sharing
You can decline camera access, decline a photo selection, or change available permissions in your device settings. This limits photo features; it does not by itself erase information already uploaded.
Meal and trial reminders are scheduled locally on your device. Notification content may include a dish name or subscription information and may appear on the lock screen. You can disable notifications or previews in device settings. Reminders are a convenience; your store subscription page is the source for billing and cancellation information.
When you share a plan or shopping list, review the preview first. Shared content can reveal meal choices, budget information, or household-related details. The receiving app or person handles the shared copy under its own practices, and resetting Dayly will not recall it.
6. Storage, retention, and security
On your device. Household profiles, plans, shopping state, pantry items, favorites, disliked dishes, referral information, and certain usage counters are stored in app files or caches. The app keeps a limited recent-plan history, but favorites and preferences can persist until changed or removed. Device backups, restore settings, and operating-system caches may retain additional copies. Dayly does not offer an account-based household cloud backup or household synchronization service in this version.
AI provider records. Firebase AI Logic itself does not store AI inputs and outputs. The underlying Gemini service may temporarily retain prompts and responses for detecting abuse, maintaining security, and meeting legal requirements under its applicable paid-service terms. Deleting a local plan or photo does not immediately erase those provider records. We do not promise zero retention or a fixed deletion deadline that the provider does not offer. Contact us about a specific deletion request.
Analytics records. User-level and event-level analytics records are subject to the retention settings of our Google Analytics property and applicable provider deletion procedures. Aggregated reports may be retained separately. We use retention criteria based on the information needed to understand recent app usage, investigate issues, and compare product performance over time; records subject to an applicable deletion request are handled under Section 7. Device reset or app removal does not automatically delete historical analytics. Contact us for information about the applicable retention setting or to request deletion.
Subscription and support records. We retain subscription records as needed to provide and restore access, resolve purchase disputes, prevent fraud, and meet applicable accounting or legal requirements. We retain support correspondence for as long as needed to resolve the request and address related follow-up or legal claims. After those purposes end, we delete or de-identify the records we control, subject to applicable retention duties and provider deletion schedules. Apple and Google may independently retain their store transaction records.
Website records. Technical access and error records are retained as needed to operate the pages, investigate errors or abuse, and comply with applicable legal duties. We do not use these records to profile your dietary or health interests.
Shared recipe illustrations. Generated images and titles may be retained for reuse while they remain useful to the service. They are not linked to a Dayly user account in the shared cache and are not removed by a local reset. If an image or title contains your personal information, contact us so we can investigate and remove it where appropriate.
We use HTTPS for the app's remote service requests and app/device attestation for supported Firebase requests. Local files rely on the device's protections. No storage or transmission method guarantees absolute security. Where a security incident triggers a legal notification duty, we will provide the required notice.
7. Your choices and privacy requests
Review and correction. You can edit household details and dietary preferences in the app and manage saved meals, dislikes, and pantry items in the relevant screens.
Start over. In the You screen, “Start over” resets your local household profile, saved plan, shopping checks, favorites, pantry, recent meal history, and disliked dishes. It does not erase every app record: referral information, certain quota or review counters, image caches, SDK records, and previously transmitted data may remain. It does not cancel a subscription.
Remove local app data. Deleting the app and its data using your device controls generally removes its local app container. Offloading the app may preserve data. Backups, exported copies, and information held by service providers require separate handling. Uninstalling does not cancel a store subscription.
Requests to us. Email fombo888@gmail.com with the subject “Dayly privacy request” to request access, correction, deletion, a copy of information, or withdrawal of consent where applicable. A household member whose information was entered by someone else may also contact us. We may need proportionate information to verify the request and locate the relevant records, such as an app-generated identifier or transaction reference. Because there is no Dayly login, a name or email address alone may not identify an installation. We will explain any identification limits; we will not ask for your store password or full card details.
Depending on your location and applicable law, you may also have rights to restrict or object to processing, opt out of a sale or targeted-advertising sharing, limit certain uses of sensitive information, appeal a denied request, or complain to a regulator. Use the same contact to submit an appeal with the subject “Dayly privacy appeal.” We will respond within applicable legal deadlines and explain any lawful exception, extension, or refusal. We will not unlawfully discriminate against you for exercising your rights.
The current app has no dedicated analytics opt-out or complete cloud-deletion button. Contact us about available controls and deletion requests. Device advertising settings may restrict advertising identifiers, but do not turn off all analytics or service processing. Removing an allergy preference also affects future recipe checks; confirm your needs before relying on a new plan.
For consumer health information, also see our Consumer Health Data Privacy Policy.
8. Adults and household members
Dayly is intended for users aged 18 or older. It is not a service for children to use independently. An adult may enter information about household members only when authorized to do so, including appropriate parental or guardian authority for a child. Use nicknames and provide only the information needed for meal planning.
If you believe a child has used the app directly or that household information was provided without proper authority, contact us. We will assess the request and take the action required by applicable law, including deletion where required.
9. Processing locations
Our operator is a company in China. Your device may be in a different country from us or our providers. Information may be processed in China, the United States, and other countries where the relevant operations or providers are located; we do not promise that it stays in your country or in a single US state. We apply legally required protections to international transfers for which we are responsible.
10. Changes and contact
We will update the date above when this policy changes and provide additional notice for material changes where required. If a new use requires your consent, publishing a revised policy or your continued use alone will not substitute for that consent.
For questions or privacy requests, contact Fombo Network Co., Ltd at fombo888@gmail.com.