SwipeYum Privacy Policy
SwipeYum is an app for quick food decisions: you browse dishes, react to them with gestures, and the app builds your taste profile. We wrote this policy in plain language, because privacy is part of the product — your taste profile is calculated mainly on your phone.
1. Data controller
The data controller is LOGI LABS SP. Z O.O., ul. Rokosowska 11, 02-348 Warszawa, Poland
(District Court for the Capital City of Warsaw, 12th Commercial Division of the
National Court Register, KRS 0001226746, NIP 7011302004,
REGON 544122970), the company
that publishes SwipeYum on the App Store and Google Play. The developer's
identification details are also available on the app's public store
listings.
Privacy contact: kontakt@swipeyum.app
2. What data we process and why
- Account — the email address and basic profile from signing in with email and password, Google or Apple, your profile name and an optional photo. Passwords are handled by the authentication provider; SwipeYum never receives and cannot read them in plain text. Purpose: maintaining the account and syncing saved recipes. Legal basis: performance of a contract.
- Taste interactions — gestures (skip/like/super), saved dishes, recipe ratings. The taste profile (weekly and monthly summaries) is calculated locally on your device; only the individual signals linked to your account that the feed needs are sent to the server. Legal basis: performance of a contract.
- User content — recipes you add (title, description, ingredients, steps, metadata and photo). We review a publication request before a recipe is shown to others. If simple rules cannot decide, we may send the recipe text and photo to OpenAI for a safety and quality check; the temporary photo link may contain the author's identifier. Uncertain cases may be reviewed by a person. Legal basis: performance of a contract and our legitimate interest in protecting users.
- Fridge — the ingredients you add, an optional quantity, storage place, and the expiry or opening dates you enter. Purpose: keeping your list of supplies and showing freshness information. The last correct view of the Fridge may be stored locally on your device, separately for each account, Home and language, so that the screen opens smoothly and works during short network outages. Local data is deleted when you sign out or delete your account. The barcode scanner uses your device's camera: the image never leaves your phone, and only the scanned barcode number is sent to our server. We look the number up in our catalogue and in the open Open Food Facts database, without any of your account data. Legal basis: performance of a contract.
- Homes — a Home is a shared Fridge for people who live together. You can join a Home only by invitation. Home members can see the supplies, dates and changes in the Home's Fridge (who added, used, cooked or threw away an item, and when), the list of members and the Home chat. You can leave a Home at any time. Legal basis: performance of a contract.
- Friends and groups — profiles you follow and mutual friends, the groups and one-to-one chats you are in, and within them your votes, dish and restaurant suggestions, plans and the shared recipe book. Only members of the given group or chat can see them. Purpose: deciding together what to eat. Legal basis: performance of a contract.
- Messages — the message text, its author and time sent, the message you reply to, and a recipe attached to the message (the title and photo of a public recipe). Messages are visible only to current members of the given chat, group or Home. We also store how far you have read a chat, to show the unread count. Messages are deleted automatically after 7 days; an author can delete their message earlier, and its content is then erased immediately. Decisions made in a chat (votes, plans and the shared recipe book) do not disappear after 7 days. Legal basis: performance of a contract.
- Moderation data — acceptance of the rules for public content, reports of recipes, profiles or messages, the reason for a report, an optional description, the identifiers of the reporting and reported profiles, and profile blocks. Purpose: community safety, handling reports and limiting prohibited content. Legal basis: performance of a contract and our legitimate interest in protecting users.
- Location (optional) — only when you turn on restaurant mode and grant system permission. Used in real time to show places nearby (requests go through our proxy server to Google Places); we do not build a history of your locations. Legal basis: consent — you can withdraw it in your system settings.
- Photos (optional) — when you add a recipe photo from your gallery or camera. The app does not scan your gallery.
- AI help (optional) — works only if you turn it on. Then a photo of a Fridge shelf, a recipe card or a recipe cover, or your description when splitting a recipe into steps, is sent to OpenAI, which reads the products or the recipe from it. We do not store the photos: the photo passes through our server only for the request and is gone right after it is read, and we do not keep the AI answers on our server. OpenAI does not use this data to train models and may keep it for up to 30 days only to detect abuse. With the photo we send only a one-way hash of your account identifier (no email and no profile name), which OpenAI needs to prevent abuse. Before a photo leaves the phone, the app removes location and device data from it. We keep only a record of the scan itself: its type, time, cost, result, the number of products found and whether you kept, edited or discarded the result. It is used for daily limits, costs and quality. You can turn AI help off in the privacy settings in the app. Legal basis: consent (sending the photo to OpenAI) and legitimate interest (limits, costs and quality).
- Push notifications (optional) — with your explicit consent we store a device token (Firebase Cloud Messaging) to send notifications, for example about a new message from friends. A message notification contains the sender's or group's name and a snippet of the text; notifications are delivered by Google Firebase and, on Apple devices, also by Apple. We do not keep message content in the sending queue: it is read at the moment of sending. We do not send notifications from muted or already read chats. Legal basis: consent — you can withdraw it in the app or phone settings.
- Android launch notice (swipeyum.app website) — when you tap “Notify me”, the website opens the email app on your device with a ready-made message to wiktor@swipeyum.app. Once you send it, we receive the sender's email address and the address typed into the form. We use it once, to write to you on the day SwipeYum launches on Android — no newsletter, no ads, and no sharing with anyone. The website itself does not store the address. Legal basis: consent — you can withdraw it by writing to wiktor@swipeyum.app or kontakt@swipeyum.app.
- Visiting swipeyum.app. The website uses no cookies and no analytics or advertising tools, and it does not track visits. The website's server (Cloudflare) processes technical connection data: IP address, browser type, page address and time of the visit. It does so only to deliver the website and protect it from attacks. We do not link this data to your app account. Recipe photos load from our storage at Supabase, so this provider also sees the IP address. Fonts and scripts come from our own server. Your browser stores just one setting on your device: whether you have already watched the video at the top of the page. It is not sent anywhere and you can remove it by clearing the website's data in your browser. TestFlight buttons lead to Apple's website, where Apple's privacy policy applies. Legal basis: legitimate interest (providing the website and keeping it secure).
- Diagnostic data — crash reports without the content of your recipes, used only to fix bugs. Legal basis: legitimate interest (app stability).
3. Public content and moderation
Before you add a recipe or edit a public profile, we ask you to accept the community guidelines. Prohibited content includes, in particular, harassment, hate, sexual or violent content, illegal or dangerous content, spam, impersonating other people or brands, copyright infringement and publishing other people's private data.
Public recipes and profiles can be reported in the app. A signed-in user can also block a profile; a block removes follow relationships between the profiles and limits how that author's content is shown in the app, including their messages in chats.
The list of people who follow your profile and the list of profiles you follow are visible to other signed-in users of the app. The lists show the profile name, avatar, short bio, profile counters and the date the follow started, and show the person viewing which people on the list are their mutual friends. People who are not signed in cannot see the lists. If one of two profiles has blocked the other, neither can see the other's lists or appear on them for the other. You can hide both lists at any time in the app: Profile → Settings → Privacy and friends → Hide my follow lists. Only you can see hidden lists; follower and following counts stay visible on your profile. Purpose: finding people with similar taste. Legal basis: legitimate interest, with the right to hide the lists.
Any member of a chat can report a message in it. The report includes a copy of the reported message (and of an attached recipe), so moderators can review it even after the message itself disappears after 7 days. A message removed by moderation is no longer visible to anyone. Reports go to a moderation queue and may result in hiding the content, restricting the account, or rejecting the report if it does not break the rules.
A new recipe submitted for publication stays hidden until a decision is made; editing a published recipe triggers a new review. A rejection or a problem with the automatic review may send the recipe back for changes or to a manual queue.
4. What we DON'T do
- We don't sell data or share it with advertisers.
- We don't show ads.
- We don't track you across other companies' apps.
- Share cards (for example “Taste of the week”) contain only aggregates — no location, activity times, friends or private collections.
5. Processors
We use trusted infrastructure providers that process data on our behalf:
- Supabase — database and authentication (account, recipes, taste signals) and storage for the recipe photos shown on swipeyum.app. Data is processed in the region configured for SwipeYum's production project in Supabase; you can ask about the current region and the basis of any transfer at the contact address above.
- Google Firebase — push notifications (including for new messages) and crash reports.
- Apple (Apple Push Notification service) — delivering push notifications to Apple devices.
- Google Places — finding restaurants in restaurant mode (through our proxy server; Google does not receive your SwipeYum account identifier).
- OpenAI — automatic review of the text, metadata and photo of a recipe submitted for publication, together with the temporary photo link, and reading photos and descriptions in AI help when you turn it on.
- Cloudflare: hosting of the swipeyum.app website and protection from attacks (technical connection data).
6. How long we keep data
Account data and content — until the account is deleted. After the account is deleted we erase private recipes, Fridge data and its local cache, taste signals, ratings, the profile, your messages and push tokens. Crash logs are kept for up to 90 days.
We do not keep AI help photos at all. Scan records are kept for 90 days; after that only daily totals with no link to any account remain. When the account is deleted, its scan records lose their link to it at once.
The address from the Android launch notice — until we send the launch message; we then delete it together with that correspondence, or earlier if you withdraw consent.
Chat messages are deleted automatically after 7 days (earlier if the author deletes them). Decisions made in chats — votes, plans and the shared recipe book — remain for as long as the group or your account exists.
Moderation reports (including a copy of a reported message), the history of accepting the rules and profile blocks may be kept for up to 24 months, or longer where necessary to protect users, defend legal claims or meet legal obligations. After an account is deleted, we limit moderation data to what is needed for safety and accountability of reports.
7. Your rights (GDPR)
You have the right to access your data, to have it corrected or erased, to restrict processing, to data portability and to object. You also have the right to lodge a complaint with the President of the Personal Data Protection Office (UODO), the Polish data protection authority. For data matters, write to kontakt@swipeyum.app.
8. Deleting your account
You can delete your account in the app: Profile → Settings → Account and data → Delete account — or through the page swipeyum.app/en/delete-account, without signing in.
9. Children
SwipeYum is not directed at children under 13, and we do not knowingly collect their data.
10. Changes to this policy
We will tell you about significant changes in the app. The current version is always available at swipeyum.app/privacy (Polish) and swipeyum.app/en/privacy (English).