Privacy

Minty Software is the new company name of the former provider Flyva Studios. Controller, address and processing activities remain unchanged.

A data protection officer is not required by law and has not been appointed.

We only process personal data to the extent necessary to provide our service. Below is an overview of the data categories:

• Account data (email address, hashed password, user ID)
• Authentication data (JWT token, OAuth identity token from Google or Apple)
• Nutrition and health data (diet, allergen and ingredient exclusions, only with consent)
• Location data (country, postcode and town for the EDEKA search, GPS coordinates only with consent)
• Device and push data (platform, app version, language, push token, random installation ID for app updates)
• Usage data (selected stores, recipe selection, weekly plan, cooked dishes, shopping list, flame, completed Kickstart steps, estimated savings, store suggestions, feedback)
• Voice input (audio recording when you dictate items, and the transcript recognised from it)
• Household data (membership, role, invite code, your email address as other members see it)
• Subscription and referral data (plan, expiry date, redeemed partner code)
• How you heard about Flyva (choice during onboarding, optional free text)
• In-app usage events (screens opened and time spent, recipes shown, expanded, opened and saved in the feed, filters chosen, session start and end)
• Your own recipes (title, ingredients, preparation, source link of an imported video, website or file, photo you uploaded, folders you created)
• Subscription and paywall events (paywall view, purchase, cancellation intent and the cancellation reason you give)
• Personal API (hash of the API key, expiry date, access logs)
• Review prompts (when the app asked for a store rating and, where recorded, your answer)

Website, API and database run on our own server at OVHcloud in the Limburg an der Lahn data centre (Germany). Recipe images, photos of your own recipes and database backups are stored in the object storage Cloudflare R2.

Depending on the service, the servers automatically collect technical connection data (server log files) when accessed, as required for secure operation and protection against attacks. This may include:

• IP address of the requesting device
• Date and time of access
• Requested address or API endpoint
• Browser type and version or app version
• Operating system used
• Referrer URL

This data is stored for at most 14 days and then deleted automatically. On sign-in, the authentication service logs the IP address, browser or app identifier (user agent) and email address. API logs may contain your user ID, links to imported recipes and, for voice input, the recognised transcript. We also use the IP address transiently in memory to limit the number of requests per address. This data is not combined with other data sources.

During setup the app asks our server which country the request comes from and uses it to suggest the country of your stores. The server derives the country from the IP address with the “IP to Country Lite” database by DB-IP (licensed under CC BY 4.0), which is kept on our own server. The IP address is neither stored nor passed to third parties for this, and the app only receives the country code.

Guest session: on first launch the app creates an anonymous session. It has a random user ID but no email address and no password, and is tied to that one device. Planning, saved recipes and the shopping list all work inside it. Only when you create an account is the existing session linked to your email address, which keeps your data after a reinstall and on further devices. If you delete the app without having created an account, the guest session can no longer be reached.

Flyva can be used without registering. If you create an account, we collect:

Alternatively you can sign in via Google Sign-In or Apple Sign-In. We then receive an identity token from the respective provider. Google and Apple may transmit your email address and your name. We do not process any further data from these services.

Authentication uses JWT (JSON Web Token) with an ES256 signature and JWKS verification. In the app the session is kept in the device's local storage (AsyncStorage). The token is transmitted for verification with every API request.

Personal API: on request, Pro users receive an API key with which they can retrieve their weekly plan, their shopping list and the deals of their stores. Of the key we only store a hash, together with its expiry date (twelve months) and the time it was last used. For every request we log the time, key, account, route, status, duration, a shortened user agent and the chains queried, but no IP addresses and no retrieved content. These logs are deleted after 90 days.

For personalised meal planning we collect the following preferences. Allergen and ingredient exclusions can constitute health data. We process this data only with your explicit consent:

We also store your saved recipes and folders, your weekly plan with the dishes marked as cooked, your shopping list (consolidated ingredients, checked and manually added entries), your flame with the hazelnuts collected, and the estimated savings.

If you belong to a household, the weekly plan, shopping list and saved recipes are visible and editable for all members, and members see each other's email addresses. Flyva creates the shared weekly plan from the stores and dietary settings of the person who created the household. The other members do not see these settings, but the choice of dishes may allow conclusions about them. The diet and allergen settings of the other members stay personal and do not feed into the shared plan.

You can write your own recipes or take one over: from a cooking video on YouTube, TikTok or Instagram, from a recipe website or from a link to a PDF or Mein Kochbuch file (.rcp). In doing so we process:

A video import analyses the video whose address you pasted. Depending on the platform, our server downloads the video and hands the file to Google's Gemini models, or only the address is passed on and Google fetches the video itself. Websites and files are fetched by our server, and Google reads PDF files. Every own recipe, written or imported, is structured by Anthropic's Claude models and translated into German, English or French where needed (see the AI processing section). No details about you are sent along: no user ID, no email address, and during the import itself your IP address reaches neither Google nor Anthropic nor the platform or website. We do not store the video or the file, only the recipe extracted from it and the photo from a Mein Kochbuch file. The app loads the image of a recipe taken from a website directly from that website, whose operator receives your device's IP address in the process.

Inclusion in the general recipe database: a recipe successfully imported from a video is also copied into our general recipe database, where it may be shown to other users. Title, ingredients and preparation are automatically rewritten for that copy. The copy carries no reference to you: no user ID, no name, no email address. Only the address of the original video is stored. Your own recipe is unaffected and stays invisible to others. Recipes from websites and files are not added to the database.

If you delete your account, your own recipes, your folders and your import counter are deleted with it. A copy already created in the general recipe database remains, because it holds no personal data. You can request removal of an individual copy informally at hello@flyva.app.

Flyva only needs your location for EDEKA: each branch there runs its own deals, so you find your branch by postcode or town or, if you agree, by your GPS location. You pick all other chains without a location. The app accesses your GPS location only with your explicit consent.

Without GPS access you find your branch by postcode or town. The search first runs against our own place database; if it finds nothing, our server queries the service Geoapify (see the third parties section).

The search for stores near you runs against our own store database. Your coordinates are not transmitted to third parties for it.

Permissions: the app only asks for location permission when you want to use your location in the EDEKA search. On Android these are ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION, on iOS the permission locationWhenInUsePermission. You can revoke it in the device settings at any time.

We collect the technical details required to operate the app and to deliver notifications:

Notifications are sent via the Expo Push Service, which delivers them to your device through Apple or Google: the reminder of the dish of the day or a recipe suggestion of the day, notes about new deals and about your finished weekly plan, reminders in your first days and when you have not opened the app for a while, a note when your flame is about to go out, a weekly recap on Sundays with Pro, messages during the trial and occasional announcements. The reminders about using the app arrive about half an hour before the time you usually open it; for this we evaluate when you have opened it so far. We only send a reminder before the trial ends if you asked for it. The basis is the consent you give through the system prompt. You can turn most types off individually in the app settings, and all of them together in the system settings. For each account we log which notification was sent when, to avoid sending it twice and to limit the number of notifications.

To develop Flyva further we also record how the app is used: which areas you open and for how long, which recipes are shown, expanded, opened, saved or shared in the feed, which filters you pick, actions in the week plan and the shopping list, and the start and end of a session (app in the foreground). Subscription events are recorded too: paywall view, completed or failed purchase, counter-offers shown, cancellation intent and the cancellation reason you select or type in the form. Every event is stored in our own database with your user ID, a random session identifier, the platform and the app version, and is only evaluated in aggregate, for example as the average time spent in the feed or the frequency of a cancellation reason. A third-party analytics service is not used and the data is not passed on. The legal basis is our legitimate interest in improving the app (Art. 6(1)(f) GDPR). You can object to this processing at any time by email to hello@flyva.app. Usage events are deleted after twelve months. Paywall and subscription events are kept for as long as we need them to analyse the subscription. If you delete your account, the events remain stored only with the random user ID, without your email address or other account data.

We collect no advertising IDs, no device fingerprinting and no cross-device tracking. For app updates the app sends a random installation ID with platform and version, which is not linked to your account. The push token serves only to deliver notifications to your device. If the device can no longer be reached, for example after the app is removed, the token is deactivated, and it is deleted with your account.

For services based outside the EU (among them Google, Apple, Anthropic, OpenRouter, RevenueCat, Cloudflare, Expo, BytePlus, Resend) transfers take place on the basis of the EU-US Data Privacy Framework or, where a provider is not certified, on the basis of the EU Commission's standard contractual clauses.

For recipes, the shopping list, your own recipes, imports, voice input and reading leaflets we use AI models from Anthropic (Claude) and Google (Gemini), and for images of imported videos an OpenAI image model via OpenRouter. Depending on the feature, the following is transmitted:

• For recipe suggestions, the current deal items of your stores (Anthropic)
• For recipe suggestions, your diet, allergen and ingredient exclusions and the number of portions (Anthropic)
• Existing recipe titles, to avoid repetition (Anthropic)
• Ingredients you enter in pantry mode (Anthropic)
• For voice input, the audio recording of what you said (Google)
• Leaflet pages of the retail chains for deal recognition (no user data)
• On a video import, the video including its audio track, or its address (Google)
• The title, ingredients and preparation of your own recipe, to structure it, check it and translate it into German, English or French (Anthropic)
• On a PDF import, the file (Google)
• Your shopping list entries when you have the list cleaned up (Anthropic)
• For the image of a recipe imported from a video, the recipe's title, description and ingredients (OpenRouter)

Important note on health and voice data:

The transfer happens without your user ID, email address or IP address. Diet and allergen settings are only sent as filter criteria. We do not store audio recordings; the transcript recognised from them stays in our log.

Internally we log the model, token usage, estimated cost, duration and errors for each operation together with your user ID, and for voice input also the recognised transcript. These logs are deleted after 90 days. We keep the full inputs and outputs of an operation, without audio and image files, for 30 days for error analysis. The logs do not leave our systems.

Payments are handled exclusively through the app stores (Apple App Store, Google Play) and the service RevenueCat. We do not store any payment information such as credit card numbers or bank details ourselves.

We only store:

Since version 2.0.0 there are two plans, Free and Pro. The former Plus plan is no longer sold; existing Plus subscriptions are still stored and are treated as Pro.

If you redeem a partner's code, we store the mapping of your account to that partner as well as the commission resulting from your payments. The partner receives no personal data about you, only aggregated settlement figures.

Flyva sets no tracking or advertising cookies and embeds no advertising or tracking networks. On flyva.app we measure reach ourselves and without third parties: per visit a random session identifier is placed in the browser's sessionStorage and stored together with the page view, path, referrer, language and the campaign's UTM parameters.

The session identifier is discarded when the browser tab closes, is not merged across devices and is not linked to an account. We do not store IP addresses for this. You can object to this measurement at any time (see the section on your rights).

• Encrypted transfer of all data via HTTPS/TLS (enforced)
• Passwords are stored hashed only (Supabase Auth)
• JWT-based authentication with ES256 signature and JWKS verification
• Row Level Security (RLS) — users can only access their own data
• Service role keys are used server-side only, administrative access is additionally protected by a separate secret
• Request rate limiting per IP address, where the address is only held transiently in memory
• Database (PostgreSQL) on our own server in Germany, SSH access by key only; backups encrypted at rest (Cloudflare R2)
• Daily automatic database backups in object storage, of which only the last 14 are retained

We store personal data only as long as necessary for the respective purpose or as long as statutory retention obligations apply:

The session records of the reach measurement on flyva.app carry no account reference and cannot be attributed to a person. They are evaluated in aggregate and kept for channel comparison.

You have the right at any time to:

The competent supervisory authority is the State Commissioner for Data Protection and Freedom of Information of Rhineland-Palatinate, Hintere Bleiche 34, 55116 Mainz, Germany.

You can delete your account in the app at any time, also as a guest. Once you confirm, the associated data is removed immediately and automatically:

• Profile data (country, location, diet and allergen preferences, notification settings)
• Saved recipes, weekly plans, cooked dishes and flame
• Shopping lists
• Selected stores and store suggestions
• Registered devices, push tokens and the notification send log
• Household membership; deleting the creating account also removes the household itself
• Subscription status, feedback entries, review prompts and AI logs
• Your own recipes, recipe folders and the counter of imports used
• Personal API keys

Deleting your account does not end a running subscription, because it is managed in the App Store or on Google Play. Cancel it there separately. The following remain: usage, paywall and subscription events, which are then only linked to a random identifier without an email address (usage events for at most twelve months); a statistics entry on the deletion (time of sign-up and deletion, platform, app version, language, sign-in method, whether a subscription existed); personal API logs for up to 90 days; server log files and database backups for up to 14 days; your identifier and purchase history at RevenueCat; and copies of imported recipes in the general recipe database, because they carry no reference to your account (see the section on your own recipes).

How to delete your account, even without access to the app, is described on our account deletion page.

For questions about data protection, access requests or the withdrawal of consent you can contact us at any time: