KEITAKAG
Privacy Policy for RecipeCalc
keitakag (the developer) explains how the iOS app RecipeCalc handles information below.
1. Recipes and data on your device
The app stores recipe titles, ingredient names, quantities, units, calculation results, notes and instructions, and ordering on your device to register, calculate, and display recipes. Import counts, display preferences, and Pro status are also stored locally. The expiry of banner-free time earned by watching ads is stored in the device keychain.
2. Importing photos, web pages, and shared content
The app handles photos you take or select from your photo library, and images, text, or URLs shared from other apps, to assist recipe entry. Image text recognition runs on your device using Apple's Vision framework. The app's import process does not send the images themselves to OpenAI or the developer's server.
Recognized text, shared text, and text and URLs extracted from web pages are sent directly from your device to OpenAI's API to organize ingredients, quantities, and instructions. Web imports may include page content beyond the recipe. Starting a shared-content import sends information for analysis before the save confirmation screen. Cancelling the save does not undo that transmission. Please avoid importing unnecessary personal or confidential information.
When importing a URL, your device accesses the website, which receives connection information such as your IP address and the requested URL. Shared input and image files are also stored in a local area used by the app and its extensions. Failed input may be retained for retry; not all image files are deleted immediately after import.
OpenAI states that API data is not used to train its models unless you explicitly opt in to sharing. Abuse monitoring logs are normally retained for up to 30 days, with exceptions such as legal requirements. The Responses API used for imports stores response data for at least 30 days by default. See OpenAI's API data controls for details.
3. Sign-in, backup, and restore
To use backup and restore, you sign in with Apple or Google through Firebase Authentication. Authentication tokens, user identifiers, and information supplied by the sign-in provider, such as an email address or profile information, are processed by Apple, Google, and Firebase as needed for authentication.
When you back up, recipe titles, ingredients, original and calculated quantities, units, notes and instructions, ratios, and ordering are stored in Google's Cloud Firestore. Backups are associated with your Firebase user identifier and sign-in provider, together with the backup time. A subsequent backup replaces the existing recipes for the same sign-in provider. Signing out or deleting a local recipe does not delete the server backup or authentication information.
4. Recipe sharing links
Creating a sharing link sends and stores the recipe title, ingredient names, original and desired quantities, units, and notes and instructions on the developer's recipe sharing server (recipecalc.keitakag.com). The link and related shared content are passed to the app or service you choose. Anyone with the link can view the recipe without signing in, forward the link, or save a copy. Do not include information you wish to keep private.
Shared recipes become eligible for periodic deletion 90 days after creation. Cleanup normally runs daily, so access does not necessarily end at the exact 90-day point. Editing or deleting the original recipe on your device does not change a previously created shared recipe. Copies saved elsewhere must be deleted by the recipient or through the relevant service.
5. Usage analytics
The app uses Google Analytics for Firebase to improve features and understand problems. It sends Google events such as screen views, recipe additions and deletions, import methods and outcomes, backup and restore operations, ad viewing, purchases and restoration, and error types. Depending on SDK behavior and settings, device, OS, and app information, identifiers such as an app instance identifier, usage information, and approximate region are also processed.
The analytics events configured by the app do not contain recipe text, images, imported URLs, email addresses, or feedback messages. The app currently has no dedicated analytics collection switch. Analytics data is retained according to Google's service behavior and retention settings. Deleting the app does not immediately delete data already sent.
6. Advertising and your choices
The app uses Google AdMob (Google Mobile Ads SDK) for banner ads and rewarded ads you choose to watch for imports or temporary banner-free time. The advertising SDK is initialized at launch, so advertising-related communication may occur even if you do not watch a rewarded ad.
The advertising SDK may collect and use your IP address and approximate location derived from it, available device and app identifiers, ad impressions, views and interactions, and diagnostic information such as crash and performance data. Google and other advertising service providers process this information for ad delivery, measurement, fraud prevention, analytics, and service improvement. The app does not attach recipe text or images to ad requests.
Advertising identifier availability and the ads shown depend on device privacy settings, region, and applicable consent and ad-serving conditions. You can review and change camera and photo permissions and available tracking settings in iOS Settings. The app currently has no dedicated screen for reviewing or changing advertising consent choices.
A Pro purchase or an earned banner-free period can stop banner display. This does not stop all analytics or communication with external services. Information held by Google is retained and deleted according to Google's policies.
7. In-app purchases
Pro purchase and restoration use Apple's StoreKit. The app checks purchase and entitlement information supplied by Apple on your device. The developer does not receive your payment card number through the app. Purchase and restoration outcomes and Pro status may be sent as analytics events or as information accompanying feedback.
8. Feedback and service operation
Submitting in-app feedback sends its category, message, reply preference, any email address you enter, app and build versions, OS version, device model, language and region, Pro status, and your Firebase user identifier if signed in to the developer's server for database storage. For responses and investigation, the message, email address, category, reply preference, app version, and device model are also included in a Slack notification.
The app also communicates with the developer's server to retrieve import and advertising configuration. The server aggregates API request counts and response statuses for operation and troubleshooting. Connection destinations receive information such as your IP address as part of communication. Please avoid including personal information unnecessary for support.
9. Retention, deletion, and external services
You can delete local recipes in the app. To remove app data, use Delete App in iOS; Offload App retains data. Original photos, copies saved elsewhere, cloud backups and authentication information, and previously transmitted analytics, advertising, OpenAI, and feedback data are not deleted by deleting the app. The banner-free expiry stored in the keychain may also survive reinstallation.
The app has no dedicated action to delete a cloud account, cloud backup, or individual sharing link. To request access to, correction of, or deletion of information managed by the developer, contact us below. After confirming the information needed to identify the relevant data, we will handle the request in accordance with applicable law and service capabilities. The developer cannot delete copies held by others or information the developer does not possess.
Unlike shared recipes, backups and feedback have no uniform automatic deletion deadline. They are retained for the necessary period; you can contact us about deletion. External services retain and delete information according to their own settings, agreements, and policies. Information sent to external services may be processed or stored outside Japan. Communications use protective measures such as HTTPS.
- Google Privacy Policy
- How Google uses information from partner sites and apps
- Firebase privacy and security
- Apple Privacy Policy
- Slack Privacy Policy
10. Changes and contact
Changes to information handling will be published on this page. For questions about this policy or your information, contact the developer, keitakag, using the contact form.
Originally established: March 20, 2024 (English version: March 31, 2024)
Revised: November 2, 2026