Hamachmetzet

Privacy Policy

Hamachmetzet · Effective November 6, 2026

Summary

You can use all of Hamachmetzet without an account, and then everything stays on your device. An account is optional: it is needed only for community features (commenting, liking, saving your own recipes, reporting and blocking), and it syncs your data to a secure server in the European Union. The app has no ads and no cross-app tracking. We measure anonymous app usage (Google Analytics for Firebase) to improve the app, you can turn it off in Settings, and on the website it runs only if you accept. We never sell your data or share it for advertising.

Without an account: everything on your device

Your starters, feedings, reminders, notes, photos, favorite recipes, learning progress (XP, levels and badges), timers and preferences are kept in the app's local storage and are not sent to us.

So the widget can show your starters, the app shares a copy of that data with it (names, feeding times and a small thumbnail) through storage shared on the device itself (an App Group and the local keychain).

Like any app data, it is included in device backups you control (iCloud or a computer), if you have them turned on. We have no access to those backups. Deleting the app deletes its data from your device.

Optional account: Sign in with Apple or Google

When you sign in, the provider you choose sends us a unique user ID, your email address (with Apple you can choose Hide My Email, and we get an Apple relay address instead) and your name, if you choose to share it. From Google we also receive your profile picture. You can change your display name in the app. We never receive your password.

Your email is used only to identify your account and to contact you about it. It is not shown to others and not used for marketing.

What is synced and where it is stored

While you're signed in, this data is synced to your account so it appears on all your devices: your profile (display name, picture, language and settings such as the timer sound), starters (name, storage place and photo), feedings, storage moves, journal notes and their photos, progress (XP, levels and badges), guided-plan progress, favorite recipes and recipe notes. Ingredient checkmarks, timers and location are not synced.

It is stored with Supabase, an infrastructure provider that processes it only on our behalf, on servers in the European Union (Frankfurt, Germany). Traffic is encrypted (HTTPS). Your private data and photos are accessible only to your account, enforced by row-level security and private photo storage. The one exception is photos of recipes you write (see "Recipes you write").

Comments and likes (public)

Comments on recipes are visible to everyone who uses the app, including people who aren't signed in, together with your display name, profile picture and the date. Likes are counted publicly and stored with your account ID. You can edit or delete your comments at any time and remove a like.

Even when you're signed out, the app contacts our server to show comments and like counts. Those requests carry no identifier of yours, but like any web server it sees your IP address.

Recipes you write

You need to be signed in to save your own recipe. We store what you wrote (name, details, ingredients, steps, timers and tips), the photo if you added one, the visibility you chose and when it was created and edited, together with your account ID. The recipe is also kept on your device.

  • A private recipe is visible only to you, enforced by row-level security. No other user sees it, and it is not run through the word filter.
  • A public recipe is visible to everyone who uses the app, including people who are not signed in, together with your display name, and can be liked and commented on. An automatic filter checks its text.
  • Recipe photos are stored in public photo storage (in your account's folder) so they can be shown to everyone. This means anyone who has a photo's address (URL) can open it, even outside the app. The address contains long random IDs and is not listed anywhere public, but don't put anything in a recipe photo that you wouldn't want to be public, even on a private recipe. Starter and journal photos stay in private storage.
  • Private and public recipes are deleted when you delete them in the app (recipe editor › Delete recipe) or delete your account. Deleting a recipe also deletes its photo, likes and comments.

Reports, blocks and moderation

When you report a comment or a public recipe, we keep the report (the content, the reason, any details you wrote and who reported it) so we can review it. The author doesn't see who reported it. When you block someone, the block is stored in your account to hide their comments and recipes from you, and they are not notified. An automatic filter checks comments, public recipes and display names for offensive words. Hidden content is kept for moderation until it is deleted.

Retention and deletion

Server data is kept for as long as your account exists. Signing out keeps your data on the device and in your account.

Deleting your account in the app (Settings › Account › Delete account) permanently removes from our server your profile, comments, likes, reports and blocks, the recipes you wrote and their photos, all synced data and photos, and the account itself. You can choose to delete the data on your device too. Copies in the provider's automatic backups are erased within 30 days at most. If you can't access the app, see Delete account.

Photos

Photos are chosen with the iOS photo picker, so the app receives only the photo you pick, not access to your library. Without an account, the photo stays on your device. With an account, starter and journal photos are uploaded to your private storage, for syncing only. A photo of a recipe you write is uploaded to the public recipe photo storage (see above).

Sharing achievements

Share cards (for example a new level or a finished bake) are created on your device and sent only through the iOS share sheet, to the app you choose. We send nothing and don't know what you shared. What happens next is governed by the app you chose.

Location and weather

Location is optional. It is requested only when you use weather-timed feeding, and only while you are using the app. The app takes a single location fix, rounds it to two decimal places (about 1 km) and sends those rounded coordinates to Open-Meteo to get an hourly temperature forecast. The request carries no account or identifier of yours.

We do not receive or store your location, and it is not synced to your account. Like any web server, Open-Meteo also sees your device's IP address when the request is made. Its use is governed by Open-Meteo's terms and privacy policy.

You can decline and enter your room temperature by hand, and revoke permission anytime in Settings › Hamachmetzet › Location.

Usage measurement (Google Analytics for Firebase)

To learn what works in the app and what to improve, the app sends usage events to Google Analytics for Firebase: which screens were opened and which actions were taken (for example opening a recipe, starting a timer, feeding a starter, or leaving the recipe editor before saving). Events carry content ids, counts and flags only, never names, comments, text you wrote or photos.

Measurement uses a random install id and Apple's identifier for vendor (IDFV), and Google derives a general region (city or country) from the IP address. We never read the advertising identifier (IDFA), never link this data to your account, and never use it for ads or tracking. Google keeps the data for up to 14 months, under Google's privacy policy.

You can turn measurement off at any time: Settings in the app › "Share anonymous usage data".

Usage measurement on the website (Google Analytics)

The browser version of Hamachmetzet (hamachmetzet-web.vercel.app) uses Google Analytics only if you accept it in the notice shown on your first visit. Before you accept, nothing loads from Google and no cookies are set. If you decline, your choice is saved in the browser and we won't ask again on every visit.

If you accept, Google receives which pages and screens were opened, which actions were taken (for example opening a recipe, starting a timer, feeding a starter), what you searched for in the recipe list, content ids, counts, the site language, and whether you are signed in (yes or no). Names, email addresses, your account id, comments and photos are never sent. Page addresses are sent without parameters and without your starters' ids.

Google stores two cookies in your browser (_ga and _ga_ plus the measurement id) holding a random id, and derives a general region (city or country) from the IP address. We never link this data to your account. Google Signals and ad personalization are off, and the data is never used for ads. Google keeps the data for up to 14 months, under Google's privacy policy.

You can withdraw at any time: Settings on the website › "Share anonymous usage data". Measurement stops right away and the cookies are deleted. Data already sent is deleted by Google at the end of the retention period. The choice is saved in this browser only, so if you clear the site's data we will ask again.

Notifications, timers and Live Activities

Feeding reminders, timers, alarms (AlarmKit) and the Lock Screen Live Activity are all created and scheduled on your device. There is no notification server and no push notifications.

Who we share data with

Only providers that help run the app: Supabase (storage, in the EU), Apple and Google (sign-in only, as you choose), Open-Meteo (rounded location, if you choose), and Google (anonymous usage measurement: in the app unless you turn it off, on the website only if you accept). We don't sell data, share it for advertising, or track you across apps or websites. We disclose data to authorities only when the law requires it.

Your rights

You can ask to access, correct, receive a copy of, or delete your data, and object to its processing, under Israel's Privacy Protection Law and, in the EU, the GDPR. Most of this you can do yourself in the app (edit your name, delete comments, delete your account). For anything else, email Nirpoliti@gmail.com. We process your data to provide the service you asked for, and for community safety (moderating comments). You may also complain to the Israeli Privacy Protection Authority or your local data protection authority.

Children

The app is not directed at children. Accounts may not be created by anyone under 13 (or the minimum age in your country). If we learn a child has created an account, we will delete it.

Changes

If this policy changes, the updated version will be posted on this page with a new date, and we'll let you know in the app about material changes.

Contact

Developer and data controller: Nir Politi, Israel. Privacy questions: Nirpoliti@gmail.com