Privacy notice

1. Who we are

Korevu is provided by MKVibe, the sole proprietorship of Robert Molenkamp, registered with the Dutch Chamber of Commerce under number 42164470. MKVibe is responsible for the personal-data processing described below.

For privacy questions or requests about your data, contact info@mkvibe.app.

This notice covers the Korevu app, including its TestFlight beta. Subscription and local recipe text recognition features described below apply to app versions that include them; their availability may differ between test and released versions. The website and waitlist are covered by the separate information on this privacy page.

2. Data on your device

The app stores your pantry, shopping lists, recipes, meal plans, ratings, settings and explicitly attached product/recipe photos on your device. Your entries may include personal information, for example in names, notes or recipe preferences.

The basic features work without creating a Korevu login. Versions with subscription support link purchase and usage records through a pseudonymous identifier as described in section 6. Manual entry and built-in recipes do not require an AI server. The app includes no advertising or tracking SDK.

Photo-based grocery recognition is not available in this version. Photos you deliberately attach to products or recipes are stored by the app. Your original library photos remain subject to your device and iCloud settings.

In versions with recipe text recognition (OCR), Apple Vision reads selected recipe photos, screenshots or scanned cookbook pages on your device. OCR does not upload images to a server or AI provider. The system photo picker may first download a selected photo from iCloud. Source images are held for the import session and are not automatically attached to the saved recipe. When you save, the app retains the original recognized text, including text you may have corrected or removed from the editable recipe, alongside the reviewed recipe and source attribution. This saved text may be included in optional iCloud sync and backups.

When you choose to share a recipe, the app prepares recipe text, including ingredients, instructions and any source attribution/link, for the system share sheet. The app or recipient you select receives the content you share and processes it under its own terms and privacy policy.

Recipe websites and cookies

When you open or import a recipe link, Korevu contacts the source website. Loading a recipe photo also contacts the image host. These websites receive ordinary connection information, such as your IP address and the requested URL. Content and scripts on visited pages may also contact other services under those websites’ privacy and cookie policies. Korevu does not send your pantry or saved recipes with these requests and does not use an AI service for import.

If you enter search words instead of a recipe link and open them in the built-in recipe browser, the app sends those words to Google Search. Google receives the query and ordinary connection information and may use browser cookies under its own privacy and cookie policies.

The built-in recipe browser retains cookies, cache and other website data on your device between visits. Websites can therefore remember your cookie choices and any sign-in sessions. You make your cookie choice on the website; Korevu does not accept cookies automatically. Direct recipe downloads use a separate session without saved cookies.

You can delete Korevu browser data in Settings → Data & privacy → Privacy & Processing → Web recipe import → Delete website data. This removes cookies, cache and other website storage from this browser. Saved recipes, pantry and Safari data remain unchanged. Websites may ask for your cookie choices or sign-in again. Deletion does not erase data already received by the websites.

3. Optional iCloud sync

If you review the explanation and enable iCloud sync, supported pantry, shopping, recipe, meal and preference data is stored in your private iCloud database. This can include notes, barcodes, recipe text and explicitly attached reduced-size photos.

Apple processes this data through iCloud under its terms and privacy policy. Your iCloud account and available storage affect whether syncing works. Korevu does not use its own central pantry database for this feature.

You can turn off sync in Settings. Turning it off does not automatically erase previously stored iCloud data. When sync is enabled, deletions may be propagated to your other devices. Sync may retain deletion markers to prevent deleted items from reappearing.

4. Encrypted backups

You can export a password-encrypted backup to a location you choose, such as Files or iCloud Drive. The backup can contain app data and attached photos. AI access credentials are excluded.

The app does not retain the backup password. You manage exported files and copies. Deleting data in the app does not delete existing backup files. Apple system backups follow your device settings.

5. AI recipes

On-device Apple Intelligence

When the app uses its Apple Intelligence option, recipes are generated on your device. This app feature does not send your recipe request to the Korevu server or enable Private Cloud Compute.

Optional Korevu Server

Cloud recipe generation requires your external-AI sharing consent. In versions with subscription support, Automatic gives Korevu AI Server priority for an active Korevu AI or Complete subscription, even when on-device Apple Intelligence is available. If current consent has not been given, the app asks before sending a recipe request; buying or restoring a subscription does not itself give that consent. Previously given current consent may still apply, so a new prompt is not shown for every request. You can explicitly select Apple Intelligence only. Without an active subscription, select Korevu AI Server to use the available cloud trial. Older builds use tester activation; in those builds, Automatic prefers Apple Intelligence and may use the server when it is unavailable and external access is enabled.

Recipe requests contain the full valid pantry snapshot: ingredient names, available amounts, units, categories and a use-soon indicator, plus language, measurement system, meal occasion and your recipe preferences. Local pantry IDs, pantry notes, photos and exact expiry dates are excluded from these recipe requests. Text you enter in ingredient names or recipe preferences is included.

Older tester builds send recipe requests to our gateway at openai.mkvibe.nl. Versions with subscription support send them first to the configured Korevu subscription service, which checks access and usage and forwards the recipe request through that gateway to OpenAI. Test builds may use subscriptions-staging.korevu.com; this is a staging service, not a statement that released builds use that environment. See the OpenAI API data controls information. MKVibe operates the gateway and its other servers itself in the Netherlands. The OpenAI project uses the Global setting, so processing is not restricted to the Netherlands or the EEA. Personal data processing through the API is governed by the OpenAI Data Processing Addendum. For transfers outside the EEA, it provides for European Commission standard contractual clauses or an applicable adequacy decision. You can request more information about these safeguards at info@mkvibe.app.

We retain session logs on our gateway for three days to investigate technical issues. These logs contain the generated prompts for recipe requests, without location data or IP addresses as log fields. User-entered text in a prompt may still contain personal information. We do not share these logs with third parties. This is separate from sending recipe requests to OpenAI for processing.

Only MKVibe’s owner has access to our logs. The reverse proxy retains session logs for three days.

OpenAI has its own retention policy. The project’s Data retention setting is None: no special Zero Data Retention or Modified Abuse Monitoring controls are enabled. Under the standard policy, OpenAI may retain abuse-monitoring logs containing request content for up to 30 days, with exceptions for legal obligations or protection against harm. Disabling audit logging does not change this.

Gateway backups also contain prompt logs and are overwritten daily. A log deleted from active storage may therefore remain in a backup until the next daily overwrite.

Sharing API data with OpenAI for model improvement is disabled for the gateway project described here. The gateway and reverse-proxy log periods and gateway backup schedule above do not establish retention periods for the separate subscription service, its diagnostic logs or its backups; see section 6.

You can disable external AI or disconnect it in Settings. This prevents new cloud recipe-generation requests unless you consent again. It does not stop automatic StoreKit and subscription access/balance checks, or settlement/recovery requests for an earlier generation, and does not automatically erase previously processed data from the services. Use manual entry and built-in recipes if you do not want external AI. Do not include unnecessary personal or sensitive information in AI requests.

6. Purchases, subscriptions and tester access

Apple handles in-app purchases through StoreKit. In versions with subscription support, the app checks purchase entitlements and the cloud trial/subscription balance automatically at launch, when returning to the foreground and on purchase updates, as well as during purchase, restore and relevant settings flows. These checks can occur without a paid subscription and while external AI is disabled. They do not contain your pantry or a recipe-generation prompt.

The app sends Apple-signed app-transaction evidence and available signed Lifetime/subscription transactions to the Korevu subscription service. The service verifies this evidence and checks current purchase/subscription status with Apple. It links a hashed app-purchase identifier, a stable account token also used with StoreKit purchases, original transaction identifiers, allowance periods and usage records. This is pseudonymous account linking, not anonymous processing, and does not require a Korevu email login. The service also handles connection information, such as IP addresses, for request handling and abuse prevention.

The subscription service keeps several separate record classes: account/purchase links; trial and subscription allowance records; generation request identifiers, timestamps and settlement status to prevent duplicate use; abuse-prevention records; temporary generated recipe results; and technical diagnostic logs. Its usage ledger does not store pantry prompts. Diagnostic events include request route, status, timing, error codes and balance/settlement information, excluding signed evidence and request/response bodies from these application logs.

The subscription service implementation clears temporary recipe results during settlement/cancellation and when expired-reservation cleanup runs. That cleanup does not delete the account links or historical usage records. No fixed retention period for those records, subscription-service diagnostic logs or backups is specified here, and disabling AI, cancelling a subscription or removing the app does not automatically delete them. For a deletion request, use the contact in section 10 so we can identify the linked records and explain which data can be removed and any data that must still be retained.

If confirmation of a generated recipe is interrupted, a recovery copy and request identifier can remain in device-only Keychain until saved or discarded. This recovery copy is excluded from Korevu iCloud sync and app backups.

Legacy tester access in older builds

In older builds, tester access is activated per device through api.pantrychef.mkvibe.nl. An activation code and recovery secret are sent for this purpose. The activation service records information including access status, expiry and hashed code/recovery values. The services also receive ordinary connection information, such as an IP address, for request handling and security.

The app stores credentials in device-only Keychain. They are excluded from Korevu iCloud sync and app backups. Contact the tester administrator if access expires or is revoked.

These legacy tester records are separate from subscription records. The activation server retains logs for three days. Tester activation and deletion of activation records are managed manually. We delete activation records no later than 30 days after access expires or is revoked. Backups are overwritten daily; a deleted record may remain there until the next overwrite.

7. Barcodes and other Apple features

When you look up a barcode, it is sent over an encrypted connection to Open Food Facts. That service also receives ordinary connection information, such as your IP address, and an app-version/project header. The app does not send your full pantry, photos or recipe text with barcode requests. You can enter products manually instead. See the Open Food Facts privacy information.

Local expiry reminders are optional. Siri, dictation, the system photo picker, iCloud and device system backups also follow Apple's settings and terms. See Apple's privacy policy.

8. Feedback and contact

If you email us, we process your email address and message to respond and investigate the issue. Share only the information needed for that purpose.

During TestFlight testing, Apple may process testing, crash and feedback data and make it available to the developer. Do not include activation codes, passwords or unnecessary private information in feedback or screenshots.

For crash reports and feedback/support messages received by email, we use automatic inbox rules. Crash reports are moved to trash 30 days after receipt; feedback and support messages are moved to trash 90 days after receipt. Trash is emptied automatically each day, so permanent deletion from the mailbox follows no later than one day afterward. Any separate working copies are retained for no longer than the same period. Backups are overwritten daily; deleted data may remain there until the next overwrite.

These periods apply to our own copies; data managed by Apple is subject to Apple’s retention policy.

9. Why we process data

We use data to provide the features you choose, handle sync and recipe requests, manage access, respond to questions and secure the services.

We request consent for optional iCloud sync and external AI. You can disable these features again; this does not affect the lawfulness of processing previously based on consent. We process necessary data to provide requested services and support in performance of our agreement with you. For necessary security and abuse prevention, we rely on our legitimate interest in keeping the services reliable, taking your interests into account.

10. Retention and deletion

Local app data remains until you delete it or clear the app's local storage. Removing the app does not automatically delete all iCloud copies, Keychain credentials or exported backups. Manage these separately. Processing by Apple and Open Food Facts is also described in their own privacy information.

The retention periods and deletion procedures above apply only to the record classes and services specified. They are not a single retention period for all app or server data. Email info@mkvibe.app for requests about data managed by MKVibe. Describe whether your request concerns tester access, purchases/subscription usage, AI requests or other app data. We may ask for information needed to locate the records and verify your request and identity. Do not send passwords, secret access codes or signed transaction evidence.

11. Your rights

Depending on the processing, you may request access, correction, deletion, restriction or portability of your personal data. You may withdraw consent and object to processing based on legitimate interests. Contact info@mkvibe.app to exercise these rights. You may also complain to the Dutch Data Protection Authority.

12. Changes

We update this notice when the app or its data processing changes. The date above identifies the latest update. Where a change requires new consent, we ask for it before enabling that processing.