1. Who we are and what this policy covers
All Recipes is a recipe, meal-planning, grocery, pantry, nutrition and weight-management application published by KOPCA Mobile (“KOPCA Mobile,” “we,” “us,” or “our”). This Policy applies to the All Recipes mobile app (bundle/package identifier com.kopca.allrecipes) and the legal pages we publish for the app.
Privacy questions and data requests may be sent to kopca.mobile@gmail.com. Our website is kopcamobile.com.
2. Important summary
- No All Recipes account is required. The app does not ask you to create an account with KOPCA Mobile or submit your name, email address, phone number, or password to use its core features.
- Your nutrition and planning profile is primarily stored on your device. This may include age range or age, sex selection, height, weight, activity level, goals, calorie or macro targets, diet preferences, allergens/exclusions, pantry data, equipment, household/portion settings, saved recipes, cooking notes, shopping lists, plans and weight check-ins.
- We do not intentionally send those profile values to advertising or purchase providers for ad targeting.
- Third-party SDKs do process technical, usage and purchase information. The current app uses Google Mobile Ads (AdMob), Firebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging and RevenueCat.
- No precise GPS location is requested by All Recipes. However, service providers such as Google Mobile Ads may process an IP address and infer an approximate/general location from it.
3. Information stored locally on your device
All Recipes uses local device storage so that the app can work without a KOPCA Mobile login. Depending on the features you use, locally stored information may include:
- profile and planning inputs such as age, sex selection, height, weight, activity level, goals and daily nutrition targets;
- diet style, food preferences, allergy and exclusion choices;
- Planner and Diet Journey settings, generated meal plans, replacement history, progress and weight check-ins;
- pantry inventory, meal-prep settings, grocery/shopping lists and tool history;
- saved/favorite recipes, recently viewed recipes and cooking notes;
- language, units and other app preferences.
This local information is used to personalize features on the device. KOPCA Mobile does not operate an account database that automatically uploads these profile values to our own server.
4. Information processed by third-party services
4.1 Google Mobile Ads (AdMob)
All Recipes may display advertisements through the Google Mobile Ads SDK. The current app configuration requests non-personalized ads; this does not mean that no data is processed. Google states that its Mobile Ads SDK may automatically process information such as IP address, app/product interactions, diagnostic/performance information and device or account identifiers for advertising, measurement, analytics and fraud prevention.
All Recipes does not intentionally provide your weight, calorie target, allergy selections, diet preferences, meal plan or other nutrition-profile values to AdMob for ad targeting.
4.2 Firebase Analytics
We use Firebase Analytics to understand basic app usage and improve features. App events may include app opens, screen or tool opens, recipe identifiers and Premium-page interactions, together with technical identifiers and device/app information generated by Firebase. We do not intentionally attach your local nutrition-profile values to those analytics events.
4.3 Firebase Crashlytics
We use Firebase Crashlytics to diagnose crashes and non-fatal technical errors. Crashlytics may process crash stack traces, application state, device/operating-system information and installation identifiers. Firebase states that Crashlytics retains crash stack traces and associated identifiers for a limited period under its service retention practices.
4.4 Firebase Cloud Messaging
The app includes Firebase Cloud Messaging support. If notification permission is requested and granted, Firebase may generate/process an app-installation identifier and push-notification token so messages can be delivered to the device. You can disable notifications in your device settings.
4.5 RevenueCat and app-store billing
Premium subscriptions and entitlements are managed with RevenueCat together with Apple App Store or Google Play billing. Because All Recipes has no KOPCA Mobile login, RevenueCat may use an anonymous app-user identifier. RevenueCat processes purchase/subscription history, receipt or purchase-token information, product/entitlement status and related store information needed to validate and manage Premium access.
KOPCA Mobile does not receive your payment-card number. Payment credentials and transaction processing are handled by Apple, Google and their payment systems. RevenueCat is used for entitlement and purchase-status management.
4.6 Cloudflare Pages and R2 asset delivery
We use Cloudflare to host and deliver All Recipes legal pages and may also use Cloudflare R2 and Cloudflare's delivery network to serve public recipe images and other static app assets. When your device requests a page or remote asset, Cloudflare may process ordinary network and security information associated with that request, such as IP address, request metadata and technical logs, in order to deliver, cache, secure and operate the service under Cloudflare's own terms and privacy practices.
The All Recipes legal pages included in this site do not include KOPCA Mobile advertising, analytics scripts or a KOPCA Mobile cookie system. Public recipe-image requests are used to deliver app content; we do not intentionally encode your weight, calorie target, allergy selections, diet preferences or meal-plan profile into image URLs.
5. Information we do not intentionally collect through core app features
As of the effective date, All Recipes does not require a KOPCA Mobile user account and does not intentionally request access to your contacts, microphone, camera, photo library, precise GPS location, HealthKit or Health Connect data for its core functionality.
If we add a feature that changes these practices, we will update this Policy and any required in-app/store disclosures before or when the new processing applies.
6. Why information is processed
Information is processed only for purposes reasonably connected to the app and its supporting services, including:
- providing recipes, personalized planning, grocery, pantry and nutrition features;
- saving your choices locally and restoring your on-device experience;
- providing and verifying Premium purchases and restoring entitlements;
- displaying and measuring advertising, including fraud/abuse prevention;
- understanding basic feature usage and improving app quality;
- diagnosing crashes, errors and performance problems;
- delivering notifications if enabled;
- protecting the app and complying with legal obligations.
7. Legal bases where applicable
Where laws such as the GDPR, UK GDPR or similar rules require a legal basis, processing may rely on: performance of a contract (for example, delivering Premium features you purchased), legitimate interests (such as security, basic service analytics and crash diagnosis where permitted), consent (for advertising/device-storage or other processing where consent is legally required), and compliance with legal obligations.
When consent is the required basis, you may withdraw it through the applicable consent/privacy controls or device/platform settings. Withdrawal does not affect processing that was lawful before withdrawal.
8. Advertising privacy and consent
Advertising rules vary by country and platform. Where required, appropriate consent or privacy choices must be presented before advertising-related storage or personal-data processing. You may also have platform controls for advertising identifiers and tracking.
We do not use your locally entered health, nutrition, allergy, weight or diet information to build advertising profiles.
9. Sharing and service providers
We do not sell your locally entered nutrition/profile data. Technical, usage or purchase information may be processed by service providers only as needed for the services described above. Current providers include Google (AdMob and Firebase), RevenueCat, Apple, Google Play and Cloudflare.
These providers may process information in countries other than your own. Where required by law, data transfers are subject to the provider’s applicable contractual, legal or technical safeguards.
10. Retention and deletion
- On-device data: remains on the device until you change/delete it through available app controls, clear the app’s storage, or uninstall the app. Uninstalling may not delete copies held in an operating-system backup.
- Purchase/entitlement records: RevenueCat and the app stores may retain purchase records as needed to provide subscription access, restore purchases, prevent fraud, satisfy accounting/legal obligations and follow their retention policies.
- Firebase/advertising technical data: is retained according to the relevant Google/Firebase service settings and retention policies.
- Support communications: if you email us, we may retain the message and contact information as reasonably necessary to answer the request, maintain support records, prevent abuse or comply with law.
To request deletion of data that KOPCA Mobile can control through third-party service dashboards, contact kopca.mobile@gmail.com. We may need limited information to locate the relevant anonymous purchase or installation record. Some records may be retained where required by law or necessary for fraud prevention, security, dispute resolution or store-accounting obligations.
11. Your privacy choices and rights
Depending on where you live, applicable privacy law may give you rights to access, correct, delete, restrict or object to certain processing, withdraw consent, or receive information about processing. You may submit a request at kopca.mobile@gmail.com.
You can also:
- delete local app information using app controls where provided, by clearing app data, or by uninstalling the app;
- disable notifications in the device settings;
- use platform advertising/privacy settings to reset or limit advertising identifiers where supported;
- manage or cancel subscriptions through the Apple App Store or Google Play account that made the purchase.
12. Security
We use reasonable technical and organizational measures appropriate to the nature of the app. Local profile data stays primarily on the device. Third-party SDK communications use the security mechanisms provided by those services, including encrypted transport where supported. No method of storage or transmission can be guaranteed to be completely secure.
13. Children
All Recipes is not directed to children under 13. We do not knowingly operate a KOPCA Mobile account-registration system for children. If you are under the age at which you can independently consent to relevant data processing in your country, use the app only with a parent or legal guardian as required by law.
Weight-management and nutrition features are not designed to replace pediatric or professional medical guidance. Minors should use such features only with appropriate parent/guardian and qualified healthcare-professional involvement.
14. Health and sensitive information
Information such as weight, goals, allergies and diet choices may be sensitive. All Recipes is designed so those values are used locally for personalization and are not intentionally sent to advertising networks or RevenueCat as health-profile attributes. For medical and nutrition limitations, please read the Nutrition & Health Disclaimer.
15. Changes to this Policy
We may update this Policy when the app, SDKs, legal requirements or our practices change. The “Last updated” date at the top will be revised. If a change materially affects your rights or the way sensitive information is processed, we will provide any additional notice or consent required by applicable law.
16. Contact
KOPCA Mobile
Türkiye
Website: kopcamobile.com
Privacy/support email: kopca.mobile@gmail.com