Dietista Personal · Information and help
Cookie Policy
Website and application
This policy distinguishes website technologies from Dietista Personal's native SDKs. The website code not setting cookies does not mean the app collects no data. Controller information is provided in the legal notice.
Technologies verified on this website
| Technology / provider | Purpose and duration | Control |
|---|---|---|
| Language selector / local Edosoft code | Reads the browser language and keeps your choice in memory while the page is open. Does not write cookies, localStorage or sessionStorage in the reviewed version. | Change the selector; closing or reloading the page resets your choice. |
| HTML, images, CSS and local dictionaries / Edosoft | Display the pages. The browser may cache resources according to its settings and headers; these are not tracking identifiers introduced by the site. | Browser cache controls. |
| Website hosting / awaiting confirmation | Possible technical logs or technologies awaiting inventory. Cloudflare is confirmed for app API access; this does not confirm its role in website hosting. No duration has been verified. | Complete the production website hosting inventory. |
The code served from this repository does not integrate web analytics, advertising pixels or embedded third-party content. Store and external-source links load when followed; their own policies apply there. This description does not certify any injections or cookies that hosting might add.
App SDKs and technologies
| Service and provider | Purpose | Duration and verified controls |
|---|---|---|
| Cloudflare / API access | Handles communications with the backend according to the owner; specific data and logs remain to be inventoried. | Duration and configuration remain unverified. |
| Firebase Authentication / Google | Account access and session maintenance. | Session persistence and account data: production retention period remains unverified. Signing out does not delete the account. |
| Firebase Analytics / Google | Usage events and identifiers. | Retention and identifiers: verified configuration remains outstanding. An accept/reject dialogue exists; an accessible withdrawal control remains outstanding. |
| Firebase Cloud Messaging / Google | Installation tokens and notification delivery. | Token expiry and deletion remain unverified. Notification receipt can be controlled through system settings; this does not ensure that tokens are purged from servers. |
| Firebase Remote Config / Google; Android and iOS integration | Check the app's operational status; uses installation identifiers. | Actual retention and deletion remain unverified. User control over this SDK has not been verified. |
| Firebase Crashlytics / Google; Android integration | Crash diagnostics, subject to verification of actual collection. | Activation, duration and withdrawal of consent remain unverified. There is no evidence that the analytics dialogue controls this SDK. |
| Analytics preference / local app storage | Save the analytics_consent choice. | No explicit expiry has been identified in the preferences repository; clearing and withdrawal remain to be checked. |
Consent and withdrawal
Non-essential technologies that access or store information on the device require prior consent where Article 22(2) LSSI applies. Analytics must be as easy to reject and withdraw consent for as to accept. Authentication necessary for the account must be explained separately; it must not be presented as optional analytics.
The reviewed code disables Analytics at startup, but it remains to be checked that nothing is collected before the choice, from SDK initialisation and on all platforms. No operational subsequent withdrawal control has been found in the profile. You may request withdrawal via support@edosoft.app or in writing to the controller, although this does not replace the control that remains to be implemented in the app.
The iOS App Tracking Transparency (ATT) permission addresses Apple's tracking rules; it does not replace GDPR/LSSI consent or explicit consent for health data. If non-essential technologies are added to the website, they must be disclosed and controlled before activation. See the Privacy Policy.