SiNi
Türkçe · English

SiNi — Privacy Policy

Effective date: 16 October 2026

1. Who is responsible

SiNi is published and operated by Yigit Berktaş as an individual. "We" in this policy means that. Contact: iletisim@buaksamnepisireyim.com

2. In short

3. What we process

3.1 Account data

If you choose to create an account, authentication runs through Google Firebase Authentication:

3.2 App preferences and content

With an account, the following is stored in Firestore at users/{your-user-id}/app/state and synced to your devices:

The recipes you like are counted anonymously every hour, together with the likes of every signed-in account. The server keeps only one total per recipe, shown in Recipes as "♥ Liked by 12 people"; who liked which recipe is neither stored nor shown to anyone. When you take a like back or delete your account, it leaves the total at the next count. Likes made as a guest are not counted.

3.3 A note about the dietary filters

Meatless, gluten-free, lactose-free and low-glycemic are cooking filters, not medical records. People often cook for someone other than themselves: you may set these for a child, a guest, or anyone else at the table. SiNi draws no conclusion about your health, or anyone else's, from them, and keeps no such record.

We use these settings only to filter the recipes we show you — never for profiling, advertising, or sharing with third parties. You do not have to set any of them; SiNi works without them, you can change them at any time, and deleting your account removes them entirely.

Important: these filters rely on ingredient matching in the recipe data and are not perfect. If a restriction is medically necessary — coeliac disease, lactose intolerance, diabetes — check the ingredient list yourself before cooking a recipe. SiNi does not give medical advice and is not a medical device.

3.4 Data that stays on your device

Your language choice, whether you have seen the introduction, and your daily reminder settings are stored only on your device (AsyncStorage). In guest mode, all of the preferences above stay on your device too.

3.5 Family sharing and notifications

If you join a family, the family name, your membership role, the shared weekly plan, shared shopping list and recipe reactions are shared with the other members of that family. Your personal pantry, filters and personal lists are not exposed to family members.

If you allow notifications, we store the device's Expo push token, platform, app project identifier and selected notification language in your private user area so that we can notify you when the family owner changes the shared weekly plan or shopping list. Other family members cannot see the token. We process user and current family-membership identifiers to exclude the person who made the change and deliver only to current members.

3.6 Server logs

Recipe and price data come from our own API server. That server records the IP address and requested path of each request as a technical log. These logs exist for debugging and abuse prevention, are not used for marketing, and are not linked to your account — API requests carry no account identifier.

3.7 App updates and error reports

Updates. When it starts, the app asks Expo's update service (EAS Update) whether a newer version of its own code exists, and downloads it if so. The request contains the device platform, the app version, the update channel and a random identifier that Expo generates for the installation. It contains no account data.

Error reports. When an error occurs in a version of the app installed from an app store, the app sends a report to Sentry. The report contains the error message and where in the app's code it happened, the app version, build and update identifier, the phone model and operating-system version, and the app screens visited just before. It contains no account identifier, email address, IP address (storing it is switched off), lists, settings or other content you entered, and no screenshots or recordings. Reports are stored in Sentry's EU region (Germany).

3.8 What we do not process

We do not use location, contacts, photos, advertising identifiers, device fingerprinting or cookies. The app contains no advertising tools and no third-party analytics; the only usage data is the anonymous counts in section 3.9; error reports are limited to what section 3.7 describes. Daily meal reminders are scheduled locally on your device. If you allow push notifications for family updates, only the technical notification data described in section 3.5 is processed.

3.9 Usage counts

When you open the app and when you close it, it sends our server a short line of counts: the date; whether this is the first open of the day, week and month on this device; whether you use it as a guest or with an account; the platform (Android or iOS) and app version; and how many times that day you asked for a dinner, opened a recipe, marked one cooked or liked, and added items to a list. The line contains no account identifier, no installation or advertising identifier, no names of recipes or items, and no content you entered. The server adds the numbers into daily totals; the lines themselves are deleted after 90 days. Legal basis: our legitimate interest in knowing whether the app is used.

4. Purposes and legal bases

Data Purpose Basis
Account data Creating your account and signing you in Performance of a contract
Preferences, pantry, lists Running the app and syncing across devices Performance of a contract
Dietary filters Filtering the recipes shown Performance of a contract
Taste feedback Improving suggestions for you Performance of a contract
Family data and push token Syncing shared lists and notifying you about family updates Performance of a contract and your device notification permission
Server logs Security, debugging, abuse prevention Legitimate interest
Update check Delivering fixes and improvements to the app Performance of a contract
Error reports Finding and fixing errors in the app Legitimate interest

5. Sharing and international transfers

We do not sell your data and do not share it for advertising. To run the service we use:

These providers process the data on our behalf. Transfers abroad are made under KVKK's transfer provisions and on the basis of your explicit consent.

We collect market prices from external sources to estimate recipe costs. Those requests contain no user data.

6. Retention

7. Deleting your account

In the app, go to Profilim → Hesap ve güvenlik → Hesabımı sil (Profile → Account and security → Delete my account). For security you will first be asked to sign in again with your password or your Apple/Google account. Deletion cannot be undone.

8. Your rights

Under KVKK art. 11 and, where it applies to you, the GDPR, you have the right to know whether your data is processed, to access it, to have it corrected or deleted, to object to processing, and to withdraw your consent. Write to iletisim@buaksamnepisireyim.com and we will respond as soon as possible, and in any case within thirty days.

9. Security

Authentication and preference syncing run over encrypted connections to Google Firebase. Firestore rules allow each user to read and write only their own data. The API serving recipes and prices also runs over an encrypted (HTTPS) connection.

10. Children

SiNi is not directed at children under 13 and we do not knowingly collect data from them.

11. Changes

If we update this policy we will change the effective date and announce material changes in the app.

12. Contact

iletisim@buaksamnepisireyim.com

Account deletion requests

If you cannot access the app, follow the instructions on the account deletion page.