This policy describes how Recipe Book handles information. The developer identified on the app’s App Store page is responsible for the app’s processing of personal data. Contact: napp.dev.support@gmail.com.
1. What stays on your device
There is no developer account or sign-in. Menus, favourites, shopping lists, cooking progress and preferences are stored on your device. A widget can read a local snapshot through shared app storage. We do not operate a cloud service that stores your personal menus or shopping lists. Device backups are controlled by your Apple settings.
The app does not request access to your contacts, photos, microphone or precise location. Notifications are local reminders and require your permission. Sharing opens the iOS share sheet; the content you choose is sent to the recipient or service you select.
2. Usage, technical and purchase data
Google Analytics for Firebase records app interactions, including recipe and collection identifiers, searches (query length and result count, not the search text), favourites, cooking timers, menu actions, shopping-list actions, onboarding, sharing events, permission responses and Premium events. Menu-planning events include guest count, occasion, menu format, selected dietary restriction flags and number of dishes. These flags can reveal food preferences; do not treat the app as a confidential health record. Free-text menu titles and shopping-list entries are not included in our analytics events.
Technical information can include app and operating-system versions, device model, language, session information, approximate region and installation or app-instance identifiers. Firebase Crashlytics processes crash reports, diagnostic information and associated installation identifiers to help us fix failures. Firebase Remote Config uses installation identifiers to deliver settings such as seasonal collections and advertising configuration.
Apple processes payments. The app receives transaction information to verify Premium access. Purchase analytics can include product, outcome, price and currency. We do not receive your full payment-card details or Apple Account password.
3. Advertising and advertising identifiers
The app integrates Google AdMob and Yandex Mobile Ads; the active network depends on availability, region and configuration. Their SDKs can process IP address, approximate location inferred from it, device and app identifiers, technical diagnostics, ad views, clicks and revenue events to deliver and measure ads and prevent fraud. Yandex Mobile Ads also integrates AppMetrica components for analytics and diagnostics.
IDFA is available only if you allow tracking in the iOS App Tracking Transparency prompt. Refusing tracking does not by itself disable all ads, analytics or crash reports. Where required, Google’s User Messaging Platform displays an advertising consent form. Advertising choices are passed to the integrated services, including Yandex and Firebase advertising consent settings. Premium removes advertising in the app. Premium does not switch off analytics or crash reporting.
4. Purposes, legal grounds and recipients
We process information to provide app features and purchases, understand feature usage, maintain reliability, configure the app, fund free access through ads and answer support requests. Depending on the processing and applicable law, the grounds are performance of a contract, consent where required, legal obligations, or legitimate interests in maintaining and improving the app where permitted. Advertising permission is not a condition of purchasing Premium.
Recipients include Apple for purchases, Google for Firebase and AdMob, and Yandex and its advertising partners when their services are used. We use service providers under their applicable data-protection terms; they must protect information as required by those terms and applicable law. Providers may process information outside your country, including in the United States and, for Yandex services, Russia and other countries. Applicable safeguards depend on the provider and jurisdiction. Details: Google Privacy Policy, Firebase privacy and security, AdMob data disclosures, Yandex Privacy Policy, Apple Privacy Policy.
5. Retention and security
Local content remains until you delete it or remove the app; copies in device backups follow your backup settings. Event data in Google Analytics for Firebase is retained for 14 months, then automatically deleted. Firebase documents a 90-day retention period for crash reports and associated identifiers before deletion begins. Advertising and Remote Config data follow the providers’ documented retention and deletion rules linked above. Support messages are kept as needed to resolve the request and meet legal obligations. An uninstall stops new app activity but does not immediately erase previously received provider data.
Network services use encrypted connections. Access to developer dashboards is restricted. No storage or transmission method can guarantee absolute security.
6. Your choices and rights
You can change tracking permission in iOS Settings → Privacy & Security → Tracking. Where required by Google UMP, reopen the consent form in the app through Settings → Ad settings. Notification permission is managed in iOS Settings. Delete local content within the app or remove the app to delete its local storage. The current app has no separate switch to disable all Firebase analytics and crash reporting; advertising consent settings affect advertising purposes rather than all collection.
Depending on your country, you may have rights to access, correct, delete or receive personal data, restrict or object to processing, withdraw consent, and complain to your data-protection authority. Write to napp.dev.support@gmail.com. We may need information that links your request to an installation; we cannot reliably identify installation data from a name alone. We will explain the available steps and respond within applicable legal time limits. Withdrawing consent does not affect the lawfulness of earlier processing.
7. Children, support and this website
The app is not specifically directed at children. We do not knowingly request personal information from children. A parent or guardian who believes a child has provided personal data can contact us.
If you email support, we receive your email address and the information you send. Please avoid sending payment credentials or sensitive health information. These documentation pages use no advertising SDKs, analytics scripts or tracking cookies. GitHub Pages, the hosting provider, logs visitors’ IP addresses for security under the GitHub Privacy Statement. External sites and your email provider have their own policies.
8. Changes and contact
We publish changes at this address with a new revision date and provide additional notice or request consent where required. Questions about privacy: napp.dev.support@gmail.com.
Some content may have been generated with the help of artificial intelligence.