Privacy Policy for CookConvert

Effective date: June 4, 2026

This Privacy Policy explains how the CookConvert mobile application (“CookConvert,” “the app,” “we,” “us,” or “our”) handles information. Please read it carefully. By installing and using CookConvert, you agree to the practices described in this policy.

1. Who we are

CookConvert is a cooking measurement and unit conversion utility app for Android.

• App name: CookConvert
• Developer contact: sooyong@lucki.es

If you have any questions about this Privacy Policy or about how CookConvert handles information, you can contact the developer at the email address above.

2. Summary

• CookConvert does not require an account, login, or registration.
• The app stores your favorites and recent conversions only on your device. This information is not sent to us or to anyone else, and we never see it.
• We operate no server or backend and never ourselves receive, see, or store your data. However, because the app shows ads, the bundled Google Mobile Ads SDK collects and shares certain device data (such as the Advertising ID and IP‑derived approximate location) — see Section 4.
• CookConvert displays banner ads using Google AdMob (the Google Mobile Ads SDK). To provide and measure ads, Google and its advertising partners collect and use certain device information, including device identifiers such as the Advertising ID. This is described in detail below.

3. Information stored on your device

CookConvert lets you save favorite conversions and keeps a list of your recent conversions so they are easy to access. This data is stored locally on your device only (using your device’s local app storage).

• This data does not leave your device and is not transmitted to us or to any third party by the app.
• We have no server or backend and we never receive, see, or store your favorites or recent conversions.

Because this information stays on your device, it is under your control. See Section 8 (“Data retention and deletion”) for how to remove it.

4. Advertising — Google AdMob

To keep CookConvert free, the app shows banner advertisements through Google AdMob, using the Google Mobile Ads SDK.

To serve, display, and measure ads and to help prevent fraud, the Google Mobile Ads SDK automatically collects and shares certain information with Google (and, where applicable, Google’s advertising partners). According to Google, the Google Mobile Ads SDK collects and shares the following data types for advertising, analytics, and fraud-prevention purposes:

• Device or other identifiers — such as the Android Advertising ID (Ad ID), app set ID, and similar identifiers.
• Approximate location — estimated from your device’s IP address. (Note: CookConvert does not request any location permission. Approximate location is derived by the ad SDK from the IP address; the app itself does not access GPS or precise location.)
• App interactions — such as app launches, taps, and similar in-app interactions.
• Diagnostic information — such as app launch time, hang rate, and energy usage.

These data types are both collected (transmitted off your device) and shared with Google as a third party. Google states that all user data collected by the Google Mobile Ads SDK is encrypted in transit using the Transport Layer Security (TLS) protocol.

We do not operate any separate analytics or crash-reporting SDK. The information described in this section is collected and shared by the Google Mobile Ads SDK, not by us directly, and we do not have independent access to it.

How Google uses this information

Google uses the information it collects through the Google Mobile Ads SDK in accordance with its own policies. You can learn more here:

• How Google uses information from sites or apps that use our services: https://policies.google.com/technologies/partner-sites
• Google Privacy Policy: https://policies.google.com/privacy
• Google Advertising / How Google uses cookies in advertising: https://policies.google.com/technologies/ads
• Google AdMob: https://admob.google.com

5. Consent in the EEA, UK, and Switzerland (UMP)

If you are located in the European Economic Area (EEA), the United Kingdom, or Switzerland, CookConvert uses Google’s User Messaging Platform (UMP) to present a consent message before personalized ads are shown, in line with Google’s consent requirements and the IAB Transparency & Consent Framework.

Through this consent message you can choose whether to allow the use of your information for personalized (interest-based) advertising. If you do not consent to personalized ads, you may instead be served non-personalized ads, which still rely on limited information (for example, to support frequency capping, ad measurement, and fraud prevention).

You can change or withdraw your consent at any time. You can reset the advertising choices tied to your device using the Android Advertising ID controls described in Section 6, and a fresh consent message is shown again if you reinstall the app. If your version of the app includes a dedicated in‑app “Ad consent” / “Privacy options” control, you can also reopen the consent message from there.

6. The Advertising ID — your controls

The Android Advertising ID is a resettable identifier provided by your device that is used for advertising. You can manage it directly through your device settings:

• Reset your Advertising ID: Open Settings → Privacy → Ads (the exact path may vary by device and Android version, for example Settings → Google → Ads), then choose Reset advertising ID. Resetting it gives you a new identifier that is not linked to the previous one.
• Opt out of / delete the Advertising ID: In the same Ads settings screen, you can turn on Opt out of Ads Personalization (or Delete advertising ID, on newer Android versions). Deleting the Advertising ID causes apps to receive a string of zeros instead of an identifier, which limits interest-based advertising.

These controls are provided by the Android operating system and apply across apps on your device, not just CookConvert.

7. Children’s privacy

CookConvert is a general-purpose cooking utility intended for a general (teen and adult) audience. It is not directed to, or intended for, children under the age of 13, and we do not knowingly collect personal information from children under 13.

CookConvert is not enrolled in the Google Play “Designed for Families” program, and we do not tag ad requests for child-directed treatment. If you believe a child under 13 has used the app in a way that raises a concern, please contact us at sooyong@lucki.es.

8. Data retention and deletion

• Favorites and recent conversions are stored only on your device. They remain there until you remove them. You can delete this data at any time by clearing the app’s data/storage in your device settings (for example, Settings → Apps → CookConvert → Storage → Clear data) or by uninstalling the app. Uninstalling or clearing the app’s data removes this locally stored information from your device.
• Advertising data collected by the Google Mobile Ads SDK is handled by Google according to Google’s own retention practices. We do not store this data and cannot delete it on your behalf. You can limit and reset the identifier used for ads through your device’s Advertising ID controls, as described in Section 6, and you can review Google’s practices through the links in Section 4.

Because CookConvert has no account and no server-side storage, there is no personal data held by us to delete. For any questions about deletion, contact sooyong@lucki.es.

9. Permissions

CookConvert requests only the permissions needed to show ads and function. The Internet permission (android.permission.INTERNET) is used by the Google Mobile Ads SDK to load and measure ads, and the SDK also declares the Google Advertising ID permission (com.google.android.gms.permission.AD_ID). CookConvert does not request access to your contacts, location, camera, microphone, SMS, call logs, or other sensitive permissions.

10. Changes to this Privacy Policy

We may update this Privacy Policy from time to time, for example to reflect changes in the app, in the advertising SDK, or in legal requirements. When we make changes, we will revise the “Effective date” at the top of this policy and post the updated version at the same URL where this policy is hosted. We encourage you to review this page periodically. Your continued use of CookConvert after an update means you accept the revised policy.

11. Contact us

If you have any questions, concerns, or requests regarding this Privacy Policy or your information, please contact:

Developer email: sooyong@lucki.es