Fuji-X RecipesTürkçe

Privacy Policy

Last updated:

This policy covers the Fuji-X Recipes app for iPhone, iPad and Android, and this website, fujixrecipes.app. It says what we collect, why, who else handles it, how long we keep it and what you can do about it.

Who we are

Fuji-X Recipes is provided by Semanur Müfettişoğlu Karabulut, the seller named on the App Store and Google Play. Semanur Müfettişoğlu Karabulut is the data controller for the personal data described here. Write to privacy@fujixrecipes.app about anything in this policy.

“We” means the Fuji-X Recipes team. Fuji-X Recipes is not affiliated with FUJIFILM Corporation.

The short version

  • You can use the app without an account, as a Guest. You need an account (Apple or Google) only to share recipes, use your Library on another device or buy Pro.
  • We never use an advertising ID, never show ads and don’t track you across other apps or websites. We don’t sell your data.
  • The app collects anonymous usage statistics, session replays and crash reports. None of them is ever linked to your user ID or your account, and you can turn the statistics and replays off in PROFILE › PRIVACY.
  • What you share to the Community is public, also on the web, and search engines can find it.
  • Photos lose their location and other metadata before they leave your phone.
  • Your Library is stored in the European Union. Some services we use also process data in the United States.
  • You can export your Library and delete your account in the app.

What we collect and why

Your Library

Your recipes, collections, the photos you add to recipes, your camera backups, My Cameras, your settings and your acceptance of the warranty notice. The app keeps them on your phone and syncs them to our cloud, so they survive a reinstall and, with an account, follow you to your other devices. A Guest’s Library is synced too.

  • Recipe photos: before a photo leaves your phone, the app makes it at most 1536 px on the long edge and removes all its metadata, including the location. It keeps a summary of the shot beside it: camera, lens, focal length, aperture, shutter speed, ISO, exposure compensation and, for a Fujifilm photo, the film simulation and settings. Photos are uploaded even for recipes you don’t share; until you share, only you can see them.
  • Camera backups: the contents of your camera’s custom slots, including the slot names as the camera stores them. The camera is identified by a one-way code made from its model and serial number, never by the serial number itself. The app keeps the latest 5 backups per camera.
  • Photos on your camera’s card: the app shows them on your phone. If a photo holds a location, the app shows it on a map on your phone only; it never stores or sends it.
  • Scans: when you create a recipe from a screenshot or a photographed recipe card, the text is read on your phone. The image isn’t sent to us. We count the scanned recipes you save each month, for the Free plan’s limit.
  • Last transfer: the app remembers the most recent send or read (when, which camera model, which connection, how it ended). It stays on your phone unless you attach diagnostics to feedback.

We need this to provide the app (performance of our contract with you).

Your account and profile

  • Sign-in: when you sign in with Apple or Google, Firebase Authentication receives your Apple or Google account ID and email address, and the app may receive your name to fill in your profile. With Apple you can choose to hide your email; we then get a relay address.
  • Profile: your Username (required, public on your shared recipes), and optionally your name, your Instagram account, your role (photographer or hobbyist), a profile photo and an email address. The Instagram account and the role are shown on your shared recipes. Your name and profile photo aren’t shown to other users. The profile email is used only to reply to your feedback and is never published.
  • Staying signed in after a reinstall: the app keeps a random secret on your phone (in the iOS Keychain, or Android’s Block Store). On Android our backend keeps a copy tied to your user, so a reinstall signs you back in. Logging out or deleting the account removes it.
  • Agreements: when you accept the warranty notice and the Community guidelines, we store which version you accepted and when.

We need this to provide the app (contract).

The Community

  • Shared recipes are public. When you share a recipe, anyone can see it, signed in or not: in the app and on the web. Search engines can index those pages, and we may also show it on our official social media accounts. What is shown: the recipe’s name, settings, description, tags, shooting tips, source link and Instagram account, its approved photos with their shot summary, your Username, your Instagram account and your role, the dates and the number of Saves. Other users can save a copy to their own Library.
  • Photo review: before a shared photo is shown, Google Cloud Vision’s SafeSearch, run in the EU, checks it for adult or violent content. A photo it flags, and every photo once the month’s automatic checks run out, goes to a person on our team. No decision about your photos is made by automatic means alone.
  • Saves: we record which user saved which shared recipe, so each user counts once. Authors see the number, not who saved.
  • Reports: a report is anonymous to the author. We store who sent it, the reason, the details and when. We see who sent it.
  • Blocks: the users you block are stored in your account, so the app can hide their recipes.
  • Moderation: we keep a record of what we removed after a report, the warnings it counts as and whether an account is suspended.

We need this to run the Community (contract), and to keep it safe and lawful (our legitimate interest).

Notifications

To send push notifications, we store your device’s push token, its platform and the app’s language. Your Inbox in the app holds notifications for 90 days. Turn categories off in PROFILE › SETTINGS › NOTIFICATIONS, or all notifications in your phone’s settings. (Contract.)

Purchases

Apple or Google sells Pro and handles the payment; we never see your card details. RevenueCat receives your purchases and your user ID, so the app knows you have Pro, and writes your Pro status into our database. (Contract.)

Usage statistics (Firebase Analytics)

For everyone, anonymously. The app sends Google Firebase Analytics the screens you open and what you do, such as creating a recipe, sending one to a camera, reading a camera’s slots, sharing, saving, opening the Pro screen and buying. For a transfer to or from a camera it also sends the camera model and firmware version, the app version, the connection (USB or Bluetooth) and the names of the settings the camera didn’t take or the app couldn’t read (for example “Grain Effect”), never your values, the camera’s serial number or its owner’s name. With it go a random ID for this installation, the phone model, the operating system, the app version and language, and a rough location (country or city, worked out from your IP address). It never includes recipe names, Usernames or anything you type. The app never collects an advertising ID or any ad signal, and never sends your user ID to Analytics or to Clarity.

The same camera-transfer results, again without anything about you, are added up in our own database (Google Cloud Firestore), so we can see which settings fail on which camera model and firmware.

We use these statistics to see which features work and where people get stuck. This is our legitimate interest; because the data doesn’t name you, we can’t pick out or delete one person’s share of it.

The switch SHARE ANONYMOUS STATISTICS in PROFILE › PRIVACY (on until you turn it off) stops the statistics and the session replays below. When you turn it off, the app stops sending Analytics events, resets the installation’s ID so new statistics can’t be linked to the old ones, and stops session replays at once. Crash reports stay on. What was already collected stays with Google and Microsoft for the periods under “How long we keep it”.

Session replays (Microsoft Clarity)

For everyone, anonymously, unless you turn SHARE ANONYMOUS STATISTICS off. Microsoft Clarity records how you move through the app’s screens (taps, scrolls, the screens you open) with the same events as above and a random ID of its own, never your user ID, so we can find problems. Everything you type and your photos (recipe photos, profile photos, scans, card photos and maps) are hidden in the replay. Clarity doesn’t record on Android 8 and 9. (Legitimate interest.)

Crash reports (Firebase Crashlytics)

Always on. When the app crashes, Crashlytics receives what went wrong in the code, the phone model, the operating system, the app version and a random installation ID. It doesn’t receive your user ID. We need it to fix crashes (legitimate interest).

Feedback

PROFILE › REPORT A BUG OR REQUEST A FEATURE sends us the type, your text, up to 5 screenshots (shrunk, without metadata) and an optional email address to reply to. Look at screenshots before you send them: they hold whatever was on your screen. With ATTACH DIAGNOSTICS on (it’s on by default), it also sends the app version, the platform and system version, the app language, the phone model, the camera model, firmware and connection, and the last transfer. It never sends the serial number, your phone’s name, your email (unless you enter it), Wi-Fi or Bluetooth addresses or recipe names. (Legitimate interest: answering you and fixing the app.)

Camera data

PROFILE › HELP & SUPPORT › HELP SUPPORT YOUR CAMERA, and the card the Camera tab shows for a camera the app hasn’t verified, let you send data that helps us support your camera. Nothing is sent until you agree on the BEFORE YOU START screen, each time.

  • What goes: your camera’s model and firmware, its custom slot settings, how it answered each value the app tried, its Bluetooth services, your phone’s model and the app version. The camera’s settings file goes only when the app can remove your details from it: the serial number, owner and copyright names, the Wi-Fi password, the network address and the slot names. The serial number goes only as a one-way code.
  • SHARE RAW DATA UNMASKED (off by default) also sends the serial number, the slot names and the settings file as the camera gives it. Where the app doesn’t know the file’s layout, it can hold the camera’s Wi-Fi password.

(Consent. To withdraw it for something you sent, write to privacy@fujixrecipes.app and we delete it.)

Email

When you write to support@fujixrecipes.app or privacy@fujixrecipes.app, we receive your address and what you write, to answer you.

This website

  • Hosting: Google’s Firebase Hosting serves the site. Like any web server, it processes your IP address, your browser’s details and the page you ask for, to deliver the page and protect the service. We don’t use them to identify you. (Legitimate interest.)
  • Fonts and files come from our own site. Before you choose in the cookie banner, the site makes no requests to anyone else.
  • Cookie banner: the site asks before it counts visits. ACCEPT and REJECT are equal choices, and the site works the same either way. Nothing is counted until you press ACCEPT.
  • With ACCEPT: Google Analytics (through Firebase) loads, sets cookies named _ga and _ga_… that last up to 2 years, and sends Google the pages you visit, the page you came from, your device and browser type and a rough location. Firebase also keeps a random installation ID and a record of when it last reported in your browser’s storage (IndexedDB). (Consent.)
  • Changing your choice: use “Cookie settings” at the bottom of every page. Choosing REJECT after ACCEPT removes the Analytics cookies and Firebase’s storage.
  • What your browser keeps: your cookie choice and your theme are saved in your browser’s local storage. They never leave your browser.

Who else handles your data

We use these providers to run the service. They process data on our behalf and under contract:

  • Google (Firebase Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, Analytics, Crashlytics, Remote Config, Cloud Messaging and Hosting; Google Cloud Vision; Sign in with Google).
  • Apple (Sign in with Apple, App Store purchases and the delivery of push notifications).
  • Google Play (purchases on Android).
  • RevenueCat, Inc. (the state of your purchases).
  • Microsoft (Clarity session replays).
  • Cloudflare, Inc. (receives mail for support@fujixrecipes.app and privacy@fujixrecipes.app and forwards it to us) and Google (Gmail, where we read and answer it).

Other users see what you share to the Community. We may disclose data when the law requires it. We don’t sell or rent personal data and don’t share it for advertising.

Where your data is

Your Library, profile and Community data are stored in Google’s EU multi-region, and our server code runs in Belgium. Photo review uses Google Cloud Vision’s EU service. Firebase Authentication, Analytics, Crashlytics and Cloud Messaging, RevenueCat and Microsoft Clarity can process data in the United States and other countries.

For transfers out of the EU/EEA or the UK, we rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission’s standard contractual clauses. For transfers out of Turkey, see the Turkish version of this policy.

How long we keep it

  • Your Library and profile: until you delete them or your account. A deleted recipe leaves only a marker that it was deleted and when, until the account goes.
  • A Guest’s data: deleted with everything in it after 12 months in which the app wasn’t used online.
  • Shared recipes: until you unshare or delete them, delete your account, or we remove them.
  • Saved Copies others made of your recipes: they stay in their Libraries. When you delete your account, they lose your Username and your photos.
  • Inbox notifications: 90 days.
  • Push tokens: until you log out, or the token stops working.
  • Feedback and camera data: 12 months, or until you delete your account.
  • Reports: kept as our record of moderation. If the person who sent one deletes their account, the report no longer names them.
  • Moderation records: until the account is deleted. If we delete an account for breaking the rules, we keep a short record of the removals and the deletion.
  • Usage statistics: 14 months. The camera-transfer counts in our database hold nothing about you and are kept as long as we need them.
  • Crash reports: 90 days.
  • Session replays: for Microsoft Clarity’s retention period, at the time of writing 30 days for most recordings.
  • Purchase records: RevenueCat, Apple and Google keep them as their own policies and tax laws require.
  • Emails: as long as we need to handle your request, and at most 12 months after it’s closed.
  • Website: cookies as stated above; your choice stays in your browser until you clear it.

Your choices

  • Anonymous statistics: PROFILE › PRIVACY › SHARE ANONYMOUS STATISTICS. Off: no statistics are sent and Clarity stops.
  • Notifications: PROFILE › SETTINGS › NOTIFICATIONS, or your phone’s settings.
  • Diagnostics in feedback: turn off ATTACH DIAGNOSTICS before you send.
  • Camera data: sent only when you agree; SHARE RAW DATA UNMASKED stays off unless you turn it on.
  • Sharing: unshare or delete a recipe at any time; it leaves the Community and the web.
  • Blocking: PROFILE › BLOCKED USERS lists the people you blocked.
  • Your Library as a file: PROFILE › EXPORT & IMPORT LIBRARY makes a .fxr file of your recipes, collections and photos.
  • Deleting your account: PROFILE › EDIT PROFILE › DELETE ACCOUNT deletes your profile, Username, Library, shared recipes, feedback and camera data. If you signed in with Apple, it also removes the app’s access to your Apple ID. You can keep a copy of your recipes on the phone. Deleting the account doesn’t cancel a subscription: cancel it in your App Store or Google Play settings.
  • Website cookies: “Cookie settings” at the bottom of every page.

Your rights

Wherever you live, you can ask us what data we hold about you, and ask us to correct or delete it. If you’re in the EU/EEA or the UK, the GDPR also gives you the right to:

  • get a copy of your data, and receive the data you gave us in a portable format;
  • have it corrected or deleted;
  • restrict how we use it;
  • object to what we do on the basis of our legitimate interest;
  • withdraw a consent at any time, without affecting what happened before;
  • complain to a data protection authority, especially where you live or work.

Write to privacy@fujixrecipes.app. To protect your account, we may ask you to write from the email in your profile or to confirm your Username. We answer within one month. If you’re in Turkey, the Turkish version of this policy explains your rights under Law No. 6698 (KVKK).

Children

Fuji-X Recipes is not meant for children under 13, and we don’t knowingly collect their data. Where the law of your country sets a higher age for agreeing to data use on your own (16 in some EU countries), you need a parent’s or guardian’s consent below that age. If you think a child gave us data, write to privacy@fujixrecipes.app and we delete it.

Security

Data travels encrypted. Our database and storage rules let each user read only their own private data. Only the Fuji-X Recipes team can open feedback, camera data and reports. No system is perfectly safe; if a breach puts your data at risk, we tell you and the authorities as the law requires.

Changes

When this policy changes, we update the date at the top. If a change matters, we tell you in the app before it applies.

Contact

Semanur Müfettişoğlu Karabulut, privacy@fujixrecipes.app. For anything else: support@fujixrecipes.app.