Before moving a recipe collection into an app, check its App Store privacy label, full privacy policy, requested permissions, account and deletion process, handling of imported URLs or text, analytics, and export options. The App Store label is useful, but Apple says developers report these practices themselves.

Start with the App Store privacy label

Look for data linked to you, data used to track you, and data not linked to identity. Apple’s developer guidance explains that developers disclose their own and integrated third-party partners’ practices.

Treat the label as a structured disclosure, not an independent audit. Compare it with the policy and actual permission prompts.

Ask what leaves the device during import

Importing a public URL may send that URL to a server for processing. Selected text, screenshots, or personal recipes can contain names, health-related notes, family information, or private links. Check:

  • whether processing is on-device or server-side;
  • what content is retained and for how long;
  • whether content is used to train models;
  • which service providers receive it;
  • whether private or signed-in sources are accepted;
  • whether logs preserve full URLs or recipe text.

Do not send a confidential or access-controlled recipe merely because the app offers an import box.

Evaluate every permission by the feature it enables

Camera or Photos access may support scanning. Notifications may report import completion. Tracking permission, contacts, location, microphone, or broad photo access need a clear product reason.

Prefer limited access where iOS offers it. Decline a permission and observe whether unrelated core features still work.

Check the account lifecycle

  • Can you use the app without an account?
  • How is sign-in secured?
  • Can you delete the account in the app?
  • What is deleted, what is retained, and why?
  • Can you export recipes before leaving?
  • What happens to a paid subscription after account deletion?

Privacy includes the ability to leave with your work, not only what happens during active use.

Inspect actual network and permission behavior

App Privacy Report can show how apps use granted permissions and the domains they contact after you enable the report. A contacted domain is not proof of misuse, but it gives you concrete questions to compare with the policy.

A short decision checklist

Privacy label reviewed?
Policy names import and AI processing?
Permissions proportionate?
Private sources avoided?
Deletion understood?
Export tested?
Subscription exit understood?

If an app cannot answer how your imported content is processed or how you retrieve it, do not move a valuable collection yet.

Try the workflow

Keep the source. Review the recipe. Cook from your version.

Download Mise on the App Store

Sources and further reading

  1. Apple Developer — App privacy details
  2. Apple Support — App Privacy Report
  3. Apple — privacy features

Read how we research, draft, review, and correct guides in our editorial policy.