1. Who is responsible and how to contact us
SMINO is the name of the application. For privacy questions or requests, email benameurhemidi10@gmail.com.
2. Information processed
Depending on the features you use, the app may process a randomly assigned account identifier and authentication token; linked Google or Apple identity references; and profile details such as age, sex, height, weight, activity level and nutrition goals. Existing profiles may also contain a date of birth.
When you use tracking features, the app may process food records and their nutrition snapshots, water records, weight measurements, activities, steps, fasting preferences and sessions, saved foods, meals, recipes, favorites and related timestamps. Some values may be missing or estimates.
The app and backend also process technical request information needed to authenticate, validate, secure and operate the service. Debug builds can emit limited technical diagnostics. This website does not add advertising analytics or tracking scripts.
3. How information is used
Information is used to create and authenticate your account, save and synchronize the records you submit, calculate requested nutrition and progress summaries, provide food search and catalog features, support account recovery and transitions, manage subscription entitlements, protect the service and respond to support or privacy requests.
4. Health and wellness information
Profile measurements, food diaries, nutrition goals, water, activity and fasting records can be sensitive health or wellness information. They are processed to provide the features you request. Do not enter information you do not want processed. SMINO is not a medical service and its estimates are not a diagnosis or treatment recommendation.
5. AI-assisted food analysis and images
When you explicitly request camera food analysis, the selected meal image is sent to the SMINO backend and may be transmitted to Google’s Gemini service for an estimate. Results can be inaccurate. The backend processes an optimized image for analysis; successful camera-created food records can also store a food image using the configured image-storage service. Temporary camera operation and image-recovery data have code-defined expiration periods, while the food record and its image can remain with the account until removed under the applicable product process. Do not include people, documents or unrelated sensitive content in a meal photo.
6. Authentication and anonymous accounts
You can begin with an anonymous guest account. The backend assigns it an account identifier and issues an access token to the app. You may link a verified Google or Apple identity to an account using the corresponding sign-in flow. Google or Apple provides authentication assertions; SMINO uses the verified provider identity to establish the account relationship. Email addresses are not used by the backend as the identity-linking key.
7. Local storage and synchronization
The mobile app keeps some records and pending personal operations on the device to support offline use. When connectivity is available, the app synchronizes supported changes with the Laravel backend under the active account. Local storage may include food, hydration, activity, fasting and other feature data, and the app uses account-scoped storage for supported records. Subscription snapshots may also be stored locally for display of previously verified local Pro access; this does not authorize protected server operations. Protect your device and sign out when appropriate.
Notifications
When enabled, the app can schedule local fasting reminders through your device’s notification system. These reminders are scheduled on the device; no push-notification delivery provider was found in the reviewed app implementation. You can manage notification permissions in your device settings.
8. Service providers and sharing
The app uses Google and Apple for sign-in when you choose those options, RevenueCat to help manage subscription entitlements, and Google Gemini for explicitly requested AI food analysis. Apple App Store and Google Play handle in-app billing. Recipe and user-food images may use the configured Cloudflare R2-compatible object storage. The Laravel backend and configured database store account and application records. Information is shared with these providers as needed for the feature you request. Each provider’s own privacy notice explains its separate processing.
9. Purchases and subscriptions
Subscription entitlement information is reconciled by the backend using RevenueCat and store data. Billing and refunds are handled under the applicable Apple or Google Play terms. The app may receive subscription status, product identifier, store and entitlement dates needed to provide access. See the Subscription Policy for management information.
10. Retention
There is no single published retention schedule for all account records. Account data may be retained while the account remains active and as needed to provide the service, maintain operation history and meet applicable obligations. Certain temporary AI operation records and image-recovery files use configured expiry windows. A specific account-deletion processing period and record-by-record retention schedule have not been confirmed; contact us to discuss an applicable request.
11. Account and data deletion
The current backend can record a pending account-deletion request for eligible Google- or Apple-linked accounts, but it does not itself delete, deactivate or anonymize accounts or associated records. You can also email a request through the Delete Account page. A request is not completed merely by submission, and no completion timeframe has been confirmed. Store subscriptions must be managed separately with Apple or Google Play.
12. Security
The service uses authenticated sessions, account ownership checks and other technical controls. No system can be guaranteed completely secure, and we do not claim a certification or end-to-end encryption. Keep your device and account access secure and contact us if you suspect unauthorized use.
13. Children and age
SMINO processes age and wellness information. A parent or guardian should guide a minor’s use where local law requires or where appropriate. If you believe information about a child has been submitted inappropriately, contact us so we can review the request.
14. International processing
The service uses third-party providers and internet infrastructure. Your information may be processed in countries different from where you live. Contact us if you need information about a specific provider or processing location.
15. Your privacy choices and rights
Depending on your location and the applicable law, you may have rights to access, correct, delete, restrict or object to certain processing, withdraw consent where applicable, and request a copy of information. Rights are subject to legal limits and identity checks. See Privacy Choices and contact benameurhemidi10@gmail.com. The app does not currently provide a confirmed self-service export feature.
16. Legal bases
Where applicable law requires a legal basis, processing may be necessary to provide a feature or account you request, to protect and operate the service, or to meet a legal obligation; other processing may rely on consent where requested. The applicable basis depends on the processing and the law that applies to you.
17. Changes to this policy
We may update this policy when the app or applicable requirements change. The current version and effective date will be posted on this page. Material changes should be communicated through an appropriate channel.
18. Contact
For privacy questions and applicable requests, email benameurhemidi10@gmail.com. Please provide enough information to locate the account, but never send a password, access token or unnecessary health records.