App privacy policy

1. Who is responsible

ENEYO is operated by Eneyo LLC, Arizona, United States. We are responsible for the handling of personal information described in this policy. You can contact us about privacy, access to your information or deletion at support@eneyoapp.com.

This policy covers the ENEYO mobile app, its related account and processing services, and app support. Features can differ by operating system and beta version. The separate website privacy notice describes the public information website. ENEYO provides nutrition and wellness information; it is not a medical service.

2. Information ENEYO uses

The information involved depends on the features you choose. Some information stays in the app on your device; other information is sent to the services described below.

Account and access information

Your email address, sign-in information, account identifier, profile name where supplied, and session information used to keep you signed in. We also maintain account access, invitation and entitlement records.

Profile, preferences and wellness entries

Information you enter, such as age, sex, height, weight, body measurements, activity level, goals, dietary preferences, allergies, food restrictions and selected health considerations. Optional preferences may reveal health, pregnancy or breastfeeding information, or religious dietary practices.

Diary and saved content

Food and drink entries, nutrition estimates and targets, hydration, saved meals and recipes, progress photos, reports, manual workouts, and measurements such as glucose or A1C when you choose to enter them.

Content submitted for assistance

Food descriptions, selected food, pantry or menu photos, barcodes, clarification messages, voice recordings, restaurant search preferences and location information you choose to submit.

Connected health records

With your permission, supported records from Health Connect on Android or Apple Health on iOS, such as steps, energy, weight and individual glucose readings. Their handling is explained in section 5.

Garden, rewards and service activity

Points, rewards, collections, Garden progress, use of account features, and request or transaction records needed to provide those features and prevent duplicate or unauthorized actions.

Technical information

Our service providers receive information needed to process network requests, such as an IP address. Operational records can include request identifiers, timestamps, errors, performance information and usage counts. Google’s advertising services have additional technical-data practices described in section 7.

We use this information to provide the features you request, calculate and present estimates, personalize your selected app experience, maintain accounts and rewards, respond to support requests, keep services working securely, and meet applicable legal obligations.

The current beta does not enable real-money Premium purchases or collect payment-card details. Account entitlements and transactions involving in-app points can still be recorded. We will explain payment-related processing before enabling real-money purchases.

3. Device storage and account backup

Your profile, diary, saved content, progress photos, reports and many manually entered measurements are primarily stored in application storage on your device. The app keeps separate saved data for different signed-in accounts. Signing out does not erase that saved device history.

Personal account backup is off by default. If you choose a manual backup or enable scheduled backups, ENEYO sends a private snapshot to your account storage provided through Supabase. This can include your profile and preferences, diary and hydration history, reports, saved meals and recipes, progress photos, and manually entered workouts, glucose and A1C.

The personal backup holds one current saved snapshot. A new backup replaces that snapshot. Turning automatic backup off does not delete a backup already saved; use the separate delete-backup control to remove it. Scheduled backups run while the app is open or when you reopen it after a backup is due.

Raw records imported from Apple Health or Health Connect are excluded from this personal backup. A weight value that you choose to apply to your profile can become part of the backed-up profile, as explained in section 5.

Signing in alone does not upload the personal snapshot. However, account records, Garden and access records, and information you submit to cloud AI features are handled separately and can be stored on our servers even when personal backup is off. Your operating system may also back up app data according to your device and platform-account settings.

4. AI, photos and voice

ENEYO uses cloud processing, including OpenAI, when you ask it to interpret food descriptions or images, suggest meals, analyze pantry contents, or help with restaurant and menu choices. These features send the relevant content through ENEYO’s services; they are not entirely on-device processing.

Food analysis can include your description, selected images, a barcode, language and follow-up context. Meal and restaurant suggestions can also include your goals, allergies and restrictions, selected dietary or health considerations, and daily calorie and macronutrient totals and targets. Restaurant requests may include a city or ZIP code, device location you choose to share, menu links or images, budget, craving and intended eating time. Web search may be used to find relevant food, restaurant or menu information.

Some of that context can be sensitive. For example, a dietary preference may disclose a religious practice, and a selected consideration may reveal pregnancy, breastfeeding or a blood-sugar concern. Choose only the information you want used for the feature. ENEYO does not automatically attach raw connected-health records, glucose histories or A1C histories to food or meal AI requests.

Selected pantry and menu images may be uploaded to private service storage and made available to the AI processor through time-limited links. The expiry of a link does not by itself mean the underlying image has been deleted. AI requests, recommendations and related session information may be stored with your account to deliver results and operate the service.

Progress photos are handled separately: they are stored in your local profile and can be included in an optional personal backup. They are not automatically submitted for food analysis.

If a supported version offers voice dictation and you choose to use it, the selected recording is sent through ENEYO’s transcription service hosted on Netlify to OpenAI for conversion into text. The resulting text can then be submitted for food interpretation when you choose that action.

AI providers can retain some data for service operation, security and other purposes under the applicable service terms and account settings. This policy does not promise zero provider retention or that all AI records disappear when a result is displayed. See OpenAI’s API data controls for its published explanation.

5. Connected health information

Connecting Health Connect or Apple Health is optional and requires your permission. The current integrations read supported information; they do not write measurements back to those health stores. If Fitbit or another application shares data into a supported health store, ENEYO may read that data through the health store you authorize.

Imported records are stored in ENEYO’s device storage and used for the health and wellness features you enable. Raw imported records are not included in ENEYO’s personal account backup and are not supplied as raw records to Google advertising or food AI.

Applying a measurement to your profile is different from keeping its imported history. If you apply a connected weight measurement to your profile, ENEYO uses that profile value for its estimates, and the value can be included in an optional account backup. Nutrition targets derived from your profile can be included in meal or restaurant requests. Manually entered health measurements can also be included in optional backup.

You can disconnect a health source, remove imported copies in ENEYO, or revoke permissions in your operating system. These are separate actions: disconnecting stops synchronization but does not automatically remove existing imported copies. Removing ENEYO’s copies does not delete the original records in Apple Health, Health Connect or the source app, and does not necessarily remove a weight you have already applied to your profile.

6. Location and device permissions

For nearby restaurant search, you can enter a city or ZIP code, or explicitly request your device’s location. If you permit device location, coordinates are sent with that search. Precision depends on your platform and permissions. The current Android integration requests foreground approximate location and does not continuously track location in the background. Typed search locations may be remembered in the app.

Camera and photo access support the images you choose to capture or select. Microphone access supports recordings you choose to make for dictation. Health access supports the connections described above. You can manage these permissions through your device settings; declining permission may limit the relevant feature.

Reminders are optional and disabled by default. In the current app, enabled reminders are scheduled on your device using your chosen settings and relevant local app activity.

7. Advertising and privacy choices

ENEYO integrates Google AdMob for banner and optional rewarded ads. The current Android test build uses Google demo ad units and requests non-personalized ads. Test advertising still involves communication with Google’s services.

Google’s Mobile Ads SDK can collect and share an IP address, which can indicate general location; interactions such as app launches, taps and video views; diagnostic and performance information; and device or account-related identifiers, including advertising and app-set identifiers where available. Google describes these uses as supporting advertising, measurement and fraud prevention. Non-personalized advertising does not mean that no technical information is processed.

ENEYO does not include your food diary, progress photos, weight or other profile details, glucose readings, A1C, connected-health records, or restaurant search coordinates in its ad-request parameters. ENEYO does not use those records to select ads. Google can receive technical information independently through its SDK, as described above.

ENEYO checks ad-privacy status before starting ads. Where a consent message or privacy-options form applies, you can use it to make or revise your choices. Look for Ad privacy choices in the app’s Privacy & Data area. Available choices and the form displayed depend on your region and the applicable configuration. You can also manage your device’s advertising identifier in device settings.

When you choose a rewarded ad, ENEYO uses the completion result to determine whether to grant the corresponding in-app points and to prevent duplicate rewards. This does not require sending your food or health records as ad-request parameters.

Read How Google uses information from sites or apps that use its services and Google’s Privacy Policy. Google’s Mobile Ads SDK data disclosure provides further detail.

8. Service providers and sharing

We use service providers to perform the functions described in this policy. The current implementation includes:

• Supabase for authentication, account records, backend processing, private uploads and optional account backups.
• OpenAI for the AI and transcription requests described in section 4.
• Netlify for web delivery and the implemented voice-transcription service.
• Google for optional Google sign-in and AdMob advertising and consent services.
• Apple and Google platform services for permissions, supported health-store connections and device-controlled features.

These providers process information needed for the relevant service. Their responsibilities and independent practices can differ. Further information is available from Supabase’s data processing information, OpenAI’s business-data privacy information, Netlify’s privacy notice, Google’s privacy policy and Apple’s privacy information.

We may also disclose information when needed to comply with a legal obligation, investigate misuse, protect rights and security, or carry out a business transaction involving the service, subject to applicable protections. If you export, share or send information outside ENEYO yourself, the recipient’s handling of it is outside ENEYO’s control.

9. Retention and deletion

We retain information according to the purpose for which it is used, the features you choose, account and support needs, security and fraud-prevention needs, and any applicable legal requirements. The current beta does not promise a single automatic deletion period for all data.

• Local app information remains on the device until you remove the relevant information or clear app storage. Signing out is not deletion. Platform backups and copies you export or keep elsewhere may remain separately.
• Optional account backup remains until it is replaced, explicitly deleted or removed as part of completed account deletion. Switching scheduled backup off does not remove an existing copy.
• Account, Garden and access records are kept to operate your account, preserve transactions and resolve access or support issues, subject to deletion requests and any justified retention.
• AI requests, images, sessions and recommendations may remain in service storage after a result has been delivered or a temporary session or image link has expired. Expiration is not a guarantee of physical deletion.
• Security logs, support records and provider backups may have separate retention based on their operational purpose, provider terms and applicable legal requirements.

You can request deletion through the contact method below. We may need to verify that a request concerns your account before disclosing or deleting information. Where some information must be retained for a legal or security reason, we will explain the applicable limitation when responding, as required by law.

Removing ENEYO data does not delete original records from an external health store, revoke operating-system permissions, erase a copy on another offline device, or remove an export you have saved or shared. Manage those copies and permissions separately.

10. Your choices and privacy requests

You can edit the information and preferences exposed by the app, remove individual entries or photos where the relevant control is available, choose whether to use AI features, manage backup, disconnect health sources, manage permissions, and revisit available ad-privacy choices.

To request access, a copy, correction or deletion of personal information, email support@eneyoapp.com with the subject ENEYO privacy request. Identify the account involved and describe your request. Do not send your password or unnecessary health information.

Supported app versions may provide in-app export and account-deletion controls. These controls are still being validated for the current beta; if an option is unavailable or fails, use the contact method above. Uninstalling the app or signing out does not by itself request deletion of server-side account information.

Depending on your location, you may have additional rights to restrict or object to certain processing, withdraw consent, obtain a portable copy, opt out of certain data uses, appeal a response, or complain to a relevant privacy authority. Contact us to exercise rights that apply to you. Withdrawing a permission or optional choice can affect the related feature.

11. Security and international processing

ENEYO uses authenticated requests and account-based access controls for private account services, and network requests to its configured cloud services use HTTPS. Device-local information also depends on your device’s security, account access and backup settings. Protect your device and any files you export.

No online service, storage system or transmission method can be guaranteed completely secure. The current beta should not be treated as a substitute for keeping your own important records.

Eneyo LLC is based in the United States, and service providers may process information in the United States or other countries where they operate. This policy does not promise that all information remains in one particular country. Contact us for information about the processing and protections relevant to your request.

12. Children and younger users

ENEYO is intended for people aged 16 and older. You must be at least 16 to create an account or use the app.

If you believe someone under 16 has supplied personal information to ENEYO, contact support@eneyoapp.com so we can review the situation and respond to a request to remove that information.

13. Changes and contact

We will update this policy as ENEYO’s features and data practices change. The date at the top of this page shows when it was last updated. We will provide additional notice or choices when required for a material change.

Eneyo LLC
Arizona, United States
support@eneyoapp.com