1. Information We Collect
The Operator may collect the following information in providing the Service.
(1) Information Entered or Saved by Users (User Content)
- Recipe information, including ingredients, instructions, and notes
- Tags, categories, and other content saved by Users in the Service
- When using extraction from a URL or text: the URL or text entered or shared by the User, all tags, and recipe information extracted and saved
The URL, entered or shared text, all tags, and extraction result are processed and temporarily stored in Cloud Firestore for extraction before anything is saved to the device.
Recipe information created manually by a User is generally stored on the User’s device. If the User creates an iCloud backup, the JSON backup stored in the User’s iCloud storage includes recipes, settings, device and usage metadata, import history, shopping lists, logically deleted data, image paths, and original image URLs, but not the image files themselves.
(2) Account and Authentication Information
The Service may automatically create an anonymous account to provide authentication, recipe extraction from URLs, usage-count management, and certain other features. Users may optionally link their account using Sign in with Apple. For authentication and account management, the Operator may collect:
- Identifiers issued by Firebase Authentication, such as a user ID (UID) and authentication tokens
- Anonymous Authentication: UID and related information
- Sign in with Apple: an identifier issued by Apple and an email address if the User permits its disclosure
The information collected varies depending on the sign-in method and settings.
The Operator does not require a User’s name, address, precise location, photographs, or similar information as a condition of using the Service’s core features. However, if a User voluntarily includes such information in a note or other content, it will be stored as User Content.
(3) Purchase and Subscription Information
To provide paid features, verify purchase status, restore purchases, and manage usage allowances, the Operator may collect:
- Product ID, purchase status, subscription period, renewal, cancellation, refund, and similar status information provided by the App Store and RevenueCat
- RevenueCat app user ID, entitlement information, and usage-allowance information
The Operator does not directly collect credit card numbers or other payment-method details.
(4) Device, Usage, and Log Information (Collected Automatically)
For operation, improvement, and troubleshooting of the Service, the Operator may automatically collect the following information, including information collected by third-party SDKs:
- Device information, such as device model, operating-system version, and language settings
- App usage information, such as screens viewed, features used, and interaction events
- Error logs generated during server-side processing
- IP address and other information necessary for network communications
The Service does not display advertisements and does not track Users for targeted advertising. However, Firebase Analytics may cause Google to automatically process app launches, usage activity, device and app information, and related data.
(5) Trial Eligibility and App Verification Information
Supported versions use Apple DeviceCheck and Firebase App Check to verify access from the genuine app and whether a device has received the free import trial. We process temporary verification tokens, trial eligibility and grant results, verification progress, and failure reasons. Records of the trial grant process associated with an account are stored in Firebase.
A device’s trial-received state is recorded with Apple. We do not store the temporary DeviceCheck token as a permanent device identifier or create a post-deletion trial-matching register based on Apple account identifiers or email addresses. This information is used to prevent duplicate trial grants and maintain security, not for advertising tracking.
2. Purposes of Use
The Operator uses collected information for the following purposes:
- Providing the Service, including storage, synchronization, display, backup, and migration
- User authentication and account management
- Extracting and structuring recipe information from URLs, shared text, and similar sources
- Providing paid features, verifying purchase status, restoring purchases, and managing usage allowances
- Preventing misuse, maintaining security, verifying free import trial eligibility, and preventing duplicate trial grants
- Analyzing usage, improving features, and enhancing quality
- Responding to failures and inquiries
- Responding to violations of the Terms of Service, alleged infringement of rights, and other matters necessary to operate the Service
3. URL Extraction Feature (Handling of External Website URLs)
The Service may provide a feature that extracts and saves recipe information from a URL entered by a User.
- An entered URL is used to perform extraction and provide the save feature.
- Information from an external website becomes User Content when the User saves it through the Service.
- External websites have their own terms of use and privacy policies, and the Operator is not responsible for how those websites handle information.
4. Use of External Services
The Operator uses external services provided by third parties to provide and improve the Service. As a result, User Content, identifiers, purchase information, device information, and similar data may be stored or processed through those external services.
Main External Services Currently Used
- Google Firebase
- Cloud Firestore: storage and processing of URL-extraction requests, extraction results, usage counts, account and entitlement status, and related data
- Firebase Authentication: anonymous authentication and authentication linked with Sign in with Apple
- Firebase App Check: verification of access from the genuine app
- Firebase Analytics: analysis of app launches, usage activity, device and app information, and related data
- OpenAI API
- Extraction and structuring of recipe information using text extracted from URLs, text entered or shared by Users, tags, candidate image URLs, and related data. The original URL itself is not ordinarily sent directly to OpenAI.
- Content sent through the OpenAI API is not used to train models unless data sharing with OpenAI is explicitly enabled. This Service disables ordinary response storage in the Responses API. However, abuse-monitoring logs are retained for up to 30 days by default, subject to legal and safety exceptions. Some features and caches have separate retention conditions, so this does not guarantee zero retention for every type of processing. See OpenAI API data controls.
- RevenueCat
- Management of app user IDs, purchase, subscription, and refund status, granted entitlements, and usage allowances
- Apple Services
- Sign in with Apple: authentication
- DeviceCheck: checking and recording a device’s trial-received state and verifying the genuine app
- App Store in-app purchases: payment, subscription management, and purchase restoration
- iCloud: backup and restoration initiated by the User
- YouTube Data API
- Retrieval of video titles, descriptions, thumbnails, channel information, and related data when a User enters a YouTube URL
The Operator may add, change, or discontinue external services as features change. Material changes will be announced through an amendment to this Policy or another appropriate method.
5. External Transmission of Information
The Service may transmit the following information to external service providers:
- Google Firebase: UID, URLs, entered or shared text, extraction results, usage counts, entitlement status, trial eligibility and grant-process records, app-verification information, communication and error information, plus app launches, usage activity, device and app information, and related data processed by Firebase Analytics
- OpenAI: text extracted from URLs, text entered or shared by Users, tags, candidate image URLs, and related data (the original URL itself is not ordinarily sent directly)
- RevenueCat: app user ID, product ID, purchase, subscription, and refund status, entitlement status, and related data
- Apple: authentication information issued by Apple, temporary DeviceCheck tokens and queries or updates to the device’s trial-received state, purchase information, backup data saved by the User to iCloud, and related data
- Google YouTube Data API: the identifier of a YouTube video entered by the User
- External website associated with an entered URL: the URL and information ordinarily transmitted in web communications as necessary to retrieve recipe information
This information is transmitted as necessary for authentication, recipe extraction, storage and processing, backup, payment and entitlement management, prevention of misuse, troubleshooting, and other purposes required to provide the Service.
6. Disclosure to Third Parties
The Operator does not provide Users’ personal information to third parties except in the following circumstances:
- With the User’s consent
- As required by law
- When necessary to protect a person’s life, body, or property and obtaining consent is difficult
- When a service provider handles the information on the Operator’s behalf as necessary to provide the Service, including cloud, analytics, and support services. In such cases, the Operator selects and supervises service providers to a reasonable extent.
The Operator endeavors to review the terms, data-protection policies, and security measures of external services that handle User information and to ensure protection equivalent to or greater than that required by this Policy and applicable law.
7. Use of De-Identified and Statistical Information
The Operator may process collected information so that individuals cannot be identified, create anonymized or aggregated statistical information, and use that information to improve and analyze the Service.
8. Retention Periods
- Google Analytics (GA4) event and user data retention is set to two months. Resetting user data retention on new activity is disabled. These settings do not apply to standard aggregated reports. Supported versions from 1.6.1 suspend Analytics collection during account deletion and offline-only use after deletion, and reset local Analytics data and the app instance identifier when deletion is completed on the device. Data already sent to Google is subject to Google-side retention settings and deletion procedures; resetting the device does not immediately erase that data.
- User Content on a device is retained until the User deletes it or deletes the app’s data. Even after a recipe is deleted and removed from the normal app view, logically deleted data or images may remain on the device. Complete removal may require deleting the app’s data.
- iCloud backups are stored in the User’s iCloud storage until the User updates or deletes them and may not be removed by an action on the device or in the app alone.
- Extraction requests and extracted recipes in Cloud Firestore become eligible for TTL deletion after 30 days.
- Cloud Functions error information is retained for approximately two months, per-user daily aggregates for 28 days after the last update, and expired usage-allowance history and RevenueCat audit events for 365 days.
- The main user record and current purchase, entitlement, and usage-allowance status do not have an automatic TTL. In-app account deletion in supported versions removes the account, associated server-side recipes, import history, allowances, purchase audit history, trial grant-process records, and user-linked error records and aggregates. Cumulative aggregates that do not identify individuals are retained.
- For version 1.6.1, deletion records contain the user ID, processing stages and timestamps, monthly subscription status at deletion (active, inactive, or unknown), a verification value derived from the device-held secret, and the scheduled deletion time. We retain these records for 30 days from the start of deletion to prevent data recreation, retry and verify deletion, and understand deletion trends; they then become eligible for automatic deletion. Because they contain the user ID, they are not fully anonymous. Minimal job records needed for unfinished deletion are retained until resolved and removed on completion. Cases approaching the verification deadline require operational review.
- To prevent duplicate trial grants, the device’s trial-received state held by Apple through DeviceCheck is not reset by account deletion, re-registration, or app reinstallation. Apple manages this state separately from account-related server data; its retention and deletion are subject to Apple’s specifications and policies.
- Purchase, subscription, and other information managed by Apple, RevenueCat, or another external provider is retained under that provider’s policy and for periods required for legal or operational purposes.
Daily counts of successful resumes, subscription synchronization, and initial allowance grants do not contain user IDs and become eligible for deletion 28 days after the last update. We do not add a table linking old and new accounts or a permanent device-tracking register. Failed notifications and activity on other devices may not be counted, so these counts are not used to identify an individual’s repeated use.
For version 1.6.1, RevenueCat customer deletion is requested asynchronously. Apple purchase history and DeviceCheck trial-received state, execution logs, and backups are handled separately from the live account. Execution logs normally have a 30-day retention setting and audit logs a 400-day setting. Weekly server backups have a 21-day retention setting; deleting a live account does not immediately erase existing recovery copies. Deleted accounts must not be restored wholesale from those copies. Eligibility for deletion and actual erasure may occur at different times.
9. Security Measures
The Operator implements reasonable security measures to prevent leakage, loss, or damage of collected information.
However, due to the nature of internet communications and electronic storage, absolute security cannot be guaranteed.
10. Privacy of Minors
The Service is not primarily directed to children.
As provided in the Terms of Service, Users under 18 years of age must use the Service with the consent of a legal representative.
If applicable law requires a different age threshold, consent of a legal representative, or a verification procedure, the Operator will respond in accordance with that law.
11. User Rights and Choices
Users can view, edit, and remove User Content from the normal app view using features within the Service. However, deleting a recipe in the app logically removes it from the normal view, and data or images may remain on the device.
In supported versions 1.6 and later, Users can start deleting their account and associated server data by choosing Delete account on the Account screen in the app. Users linked with Apple may be asked to authenticate again. If an older version or a connection problem prevents deletion, see the support page.
After account deletion, the records that prevent data recreation, Apple’s device state, and other information described in Section 8 remain subject to the retention arrangements stated there. Unused trial imports are not transferred to a new account. Recipes and images on the device and iCloud backups are not deleted automatically; delete them separately if needed. Account deletion does not cancel an Apple Subscription.
If a second-hand or transferred device is shown as having received the trial and this seems incorrect, please contact support. We review the circumstances rather than treating the device result alone as proof of misuse.
Users who do not wish to transmit information through the URL-extraction feature can prevent that transmission by not using the feature.
Users may also request disclosure, correction, suspension of use, deletion, or other action in accordance with applicable law. Please use the contact channel below for details.
In supported versions 1.6.1 and later, account deletion leaves the app in offline-only mode. A new server account and device information are not registered automatically until you choose Resume online use on the Account screen. You can still view and edit saved recipes. Resuming does not restore the deleted account or its balances.
Purchased extra imports do not expire while the account remains in use. Deleting the account forfeits unused purchased imports, which do not transfer to a new account. Permanent Plus unlocked through a monthly plan also does not transfer after account deletion. To keep your balance, sign out instead of deleting the account. Deletion does not automatically issue a refund. Restoring a one-time Plus purchase or an active monthly subscription is a separate process from transferring unused extra imports.
12. International Data Processing
Depending on the server locations and other arrangements of the external services used by the Service, User information may be stored or processed in regions outside Japan.
13. Changes to This Policy
The Operator may amend this Policy in response to changes in law or the Service. The amended Policy will be announced by publication through the Service or another appropriate method.
14. Contact
- Operator: Morikawa Tatsunosuke
- Address: Upon a lawful request from the data subject, the Operator will disclose the address without delay after verifying the requester’s identity.
The shared contact form collects the selected app, inquiry category and content, and device information if you choose to provide it. An email address is collected only if you request a reply. Submissions are stored in Firestore and become eligible for automatic deletion 180 days after receipt; deletion normally occurs within the following 24 hours. Information may be retained longer when required by law or for dispute resolution.
Firebase App Check and reCAPTCHA Enterprise are used to prevent spam, and Google may process device and network information to assess misuse. New-submission notifications send only the app, category, reply preference, time received, and an administrative ID to Gmail. The message, email address, and device information are not included in the notification email.
Firebase and Google may process inquiry information outside your country or region. No advertising, analytics, or tracking scripts are installed on this page or the support page.