The app’s data practices have not been supplied. This page must be completed and verified by the publisher before it is used as a public privacy policy or submitted to Google Play. Draft prepared: 26 September 2026. Effective date: not yet set.
This draft covers the Cook Guard website at cookguard.ydapps.com and reserves space for the Cook Guard Android app’s verified practices.
This website.
The supplied website code does not include advertising scripts, analytics trackers, embedded third-party media, accounts, contact forms, cookies, or browser storage. Fonts and illustrations are served locally. Animation preferences apply only to the current page.
When the site is deployed, the hosting and network providers may process request information such as IP addresses, requested URLs, and browser metadata to deliver and protect the site. The publisher must confirm the enabled Cloudflare services, logging, retention, and relevant provider terms before finalizing this policy.
Following a link to Google Play, the main YD Apps website, or another external website takes you to a service with its own privacy practices. Any tracking or consent tools added later must also be reflected here.
The Android app.
Publisher action required: replace this section with the app’s verified practices. The website template does not establish what the app collects or shares.
- Identify the responsible publisher or legal entity and applicable contact details.
- List data collected or accessed, its purpose, and whether it stays on the device or is transmitted.
- Document third-party SDKs and services, including any advertising, analytics, crash reporting, billing, backup, or cloud features.
- Explain permissions actually requested and why they are needed.
- Describe data sharing, retention, deletion, security measures, and any international processing.
- State the intended audience and any children’s privacy practices that apply.
- Explain applicable user rights and how requests are handled.
Do not replace these details with a “no data collected” claim unless the released app and all included SDKs support that claim. Align the completed policy with the actual release and the store’s data disclosures.
When you contact support.
Sending an email to [email protected] shares your email address and the content you choose to send with the recipient and the email service providers involved.
Publisher action required: specify who can access support messages, why they are used, which providers process them, the retention period or criteria, and how a person may request deletion. Avoid asking users for unnecessary sensitive information.
Your choices and requests.
You can contact [email protected] with a privacy question or request. Explain the request without sharing passwords or payment details.
Publisher action required: document the rights and procedures that apply to your users, any identity checks, response periods, and escalation routes. Do not promise deletion from systems you have not verified.
Policy changes.
Publisher action required: set the effective date and explain how material updates will be communicated. Keep this page at a stable URL and update it when the app, website, or service providers change.
Let’s talk.
App: Cook Guard
Website: cookguard.ydapps.com
Email: [email protected]
Responsible publisher/legal entity and address, if applicable: to be completed by the publisher.