Privacy policy

1. Data we process

PlanMyFood is a meal planner, recipe organiser and shopping-list service. Dzmitry Radyna is responsible for the service’s processing of personal data. Privacy contact: dmitry.radyno@gmail.com.

Account and household

Email address, display name, technical account ID, sign-in sessions, household membership, participants’ names or nicknames, adult/child profile type, invitations and access permissions.

Your records

Recipes, ingredients, cooking steps, photos, recipe preferences, meal plans and participants, shopping lists and shopping history. We process the content you add or save in the service.

AI and dictation

Prompts, a selected recipe and editing instructions, text recognised from screenshots or dictation, and list category names when needed for the requested feature.

Subscriptions

Product and transaction IDs, subscription status and expiry, renewal and refund information, and the link between a purchase and an account. Apple or Google processes payments; we do not receive your full payment-card details.

Technical information

IP addresses and request metadata, app and operating-system versions, and error information. Service IDs and tokens support sign-in, synchronisation and abuse prevention. If you enable notifications, we process the device push token, language, time zone and reminder settings.

If you contact support, we also receive your email address and the content of your message.

2. Why we process data

We use data to provide account access, store and synchronise records, let households collaborate, fulfil AI requests, deliver reminders you choose, verify subscriptions, provide support and fix errors. Technical information also helps protect the service and limit abuse, including free AI requests without an account.

We do not sell personal data or use household, recipe or shopping records for advertising profiles. We do not use your records to train our own AI models.

Depending on applicable law, processing is based on providing the service you request, your consent for optional features, legitimate interests in service security and reliability, and legal obligations.

3. AI, screenshots and speech recognition

AI features are optional. When you request recipe generation, editing or dictation parsing, the relevant text is sent to our server and the selected AI provider: DigitalOcean Serverless Inference or Alibaba Cloud Model Studio. The service configuration selects the provider; not every provider is involved in every request. We send the task content, not your entire household archive. We do not deliberately add your email address or payment details to AI prompts.

For recipe imports from screenshots on iPhone, Apple Vision recognises text on the device. This feature sends extracted text to AI, not the original screenshots. Photos you separately save to recipes or shopping items may be uploaded for synchronisation.

Dictation uses the device’s speech-recognition service: Apple Speech on iPhone or the available recognition service on Android. That service may process audio on the device or its servers under the platform’s settings and terms. Our shopping-parsing API receives recognised text, not a recording of your dictation.

You can use manual entry without AI, screenshot import or dictation. Camera, microphone, speech-recognition and notification permissions can be revoked in device settings. Photo features use images you select, rather than automatically uploading your entire photo library.

4. Who may receive data

Access is limited by the feature’s purpose and participants’ permissions:

• Members of your household or shared list can access shared records within their permissions. Consider who may receive an invitation link before sharing it.
• DigitalOcean hosts the website and API and stores data and photos; it may also process selected AI requests.
• Cloudflare provides content delivery and network protection through the hosting infrastructure and may process IP addresses and request metadata.
• Alibaba Cloud Model Studio may process AI requests when this provider is selected.
• Postmark (ActiveCampaign) delivers sign-in codes and receives the recipient’s email address and service-email content.
• Sentry, when diagnostics are enabled, receives technical error reports. The app filters user content, email addresses, tokens and request bodies from these reports; diagnostic screenshots and session replay are not enabled.
• Apple and Google handle store purchases, platform speech recognition and notification delivery when you use those features.
• Yandex Alice is involved only when you use the skill and connect the integration. Commands, responses and selected-list information are processed as needed to fulfil your request. You can revoke the integration’s access.

Providers receive data for the purposes described above, subject to applicable data-processing and protection terms. They are required to protect transferred data in accordance with applicable law and the purposes of the transfer. We do not authorise its use for unrelated purposes.

Additional provider terms: DigitalOcean, Cloudflare, Alibaba Cloud, Postmark / ActiveCampaign, Sentry, Apple, Google, Yandex.

Data may also be disclosed where required by law, to protect rights and security, or at your specific direction. Support access is limited to what is needed.

5. Storage and deletion

Local records are stored on your device or in your browser. Signing in synchronises records with the server. Optional AI requests send their text to the server even without an account. Account information and records are kept for as long as needed to provide the service and until you delete them. Service records may be retained longer where needed for security, purchase processing, disputes or legal obligations.

AI results may be retained temporarily to recover interrupted requests and prevent duplicate credit charges. Background processes clean up service records and photos, so physical deletion may not coincide with deletion in the interface. Backups and logs may outlast active records while needed for recovery, security or legal requirements; access is restricted.

To delete your account: open “Profile and family → Delete account”. If you administer a household, the app asks you to transfer administration or delete the household. Account deletion removes your email address, name, sign-in sessions, memberships, personal preferences and associated personal service records. Shared recipes and records belonging to a continuing household may remain available to its members without attribution to the deleted author. Deleting a household removes its shared data and queues its photos for deletion.

The deleted account’s technical ID, Apple account-linking ID and payment records may be retained to process purchase history, refunds and store notifications. They cannot be used to sign into the deleted account. Deleting your account does not cancel an App Store or Google Play subscription: cancel it in the relevant store’s settings.

Other devices lose access on their next server request; this does not remotely erase previously saved offline copies. Uninstalling the app alone does not delete the server account.

6. Your choices, rights and children’s data

You can edit records and your name, manage household membership and access, turn off reminders, revoke device permissions and integration access, avoid AI features, and delete your account. To request access to or a copy of your data, correction, deletion, restriction or to object to processing, email dmitry.radyno@gmail.com. The availability and scope of these rights depend on applicable law. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.

We may verify account ownership, for example by confirming your email address, before fulfilling a request. This protects other people’s information. You may also complain to a data-protection authority where that right applies.

The service is intended for adults managing household meals. An adult can create a participant profile marked “child”, using a name or nickname and participation in meal plans. Do not add information about other people without the necessary authority. We do not ask for a date of birth for these profiles. Contact us if a child’s information has been added without appropriate authorisation.

7. Security, processing locations and browser storage

We use HTTPS, access checks for shared records and platform-protected storage for sign-in credentials. Server-side photo access is limited by permissions and temporary links. No transmission or storage method can guarantee absolute security.

Providers may process data in countries other than your country of residence. Cross-border processing is subject to safeguards required by applicable law and providers’ data-processing terms. Contact us for information about the processing of a particular request.

The web app uses browser storage and service caching for sign-in, settings and offline use. Clearing site data may remove local records and require you to sign in again. Our public PlanMyFood website does not install advertising trackers or third-party marketing counters; hosting receives ordinary request metadata when you visit a page.

8. Policy changes and contact

The current policy is available at this address. We update its text and date when processing changes. We will communicate significant changes in the app or by another appropriate method and request additional consent where required.

Service operator: Dzmitry Radyna
Email: dmitry.radyno@gmail.com
Effective and last updated: 20 October 2026.