Privacy policy

Siftlet, by GRCSAC (GRCSAC LLC) · For iPhone, and for the Android edition when it is released · Last updated: 15 November 2026

What the app keeps on your phone

Everything you put into Siftlet is held in the app's own storage on the device:

• Your recipes: titles, ingredients, steps, servings, times, notes, tags, categories and collections, along with the address of any page a recipe was imported from
• Pictures: the photograph from an imported page, and any photographs or screenshots you chose to keep with a recipe
• Your kitchen inventory: the items you have added, where you keep them, and any amount, date or note you typed yourself
• Your shopping lists, and what you have ticked off
• Your settings, including dietary hints you enter and whether on-device intelligence is switched on
• Cooking history: which recipes you have cooked and where you are in a recipe you have paused

On iPhone

This data sits in the app's container and is included in your iPhone backup according to your own iOS backup settings. A link shared to Siftlet from another app is written into the app's shared container and read once by the app.

On Android

The Android edition is not released yet. When it ships it is covered by this same policy at this same address, and this section will say exactly where the same data sits on an Android phone and how your device backup treats it. Nothing about Siftlet for Android is collected or stored anywhere today, because the app does not exist yet.

The one request the app makes

When you ask Siftlet to import a recipe from a link, it fetches that page, and the picture the page names, so it can read the recipe out of it. That request goes to the website you chose and to nobody else. It happens only when you ask for an import.

• It is sent over HTTPS to public addresses only, and redirects are followed only to other public HTTPS addresses.
• It carries no cookies and no saved sign-in of yours. Siftlet has no way to sign you in to anything.
• It identifies itself as Siftlet.
• As with any request to any website, the site you are importing from can see your IP address and which page you asked for. We never see it.
• A sign-in wall, a paywall or a bot check is reported back to you. Siftlet never works around one.

Nothing you write, cook, store or buy is sent anywhere. There is no server of ours for it to be sent to.

Reading text from your photographs

Photographs, screenshots and scanned pages are read on the device. The images stay on the phone, and are kept with a recipe only if you chose to keep them. You can remove them at any time.

On iPhone

Text recognition uses Apple's Vision framework, which runs on the device. When Apple Intelligence is available and you have left it switched on, Apple's on-device Foundation Models help sort a recipe into its parts and suggest items from a photograph of your kitchen. That model runs on the phone. Nothing is sent to Apple, to us, or to anyone else for it, and the app works without it: every feature has a path that uses ordinary code instead.

On Android

Not released yet. When it is, the same rule binds it: reading text and sorting a recipe happen on the phone, and this section will name the Android equivalents it uses.

Camera and photo library

The camera is used only while you are taking a picture of a recipe or your kitchen, and the photo library only for the pictures you pick. Siftlet does not browse your library, and it reads nothing you did not hand it.

Notifications

If you start a timer in Cook Mode, the app asks your permission to send you one notification when that timer ends. It is scheduled on the phone and carries nothing anywhere. Declining it costs you nothing but the alert.

Sharing and files

Sharing a recipe or a shopping list, or exporting your data, hands the text or the file to whatever app you choose, under that app's terms. Siftlet does not send any of it anywhere itself.

What we collect

Nothing. The app has no account, no analytics, no crash-reporting service, no advertising, no tracking and no third-party code that reports anywhere. It contains no software from anyone but Apple and us.

On iPhone

If you have chosen to share diagnostics with app developers in Settings › Privacy & Security › Analytics & Improvements, Apple may give us anonymised crash reports and usage statistics. That is controlled by you and by Apple, not by the app, and it tells us nothing about your recipes.

On Android

Not released yet. The same will be true of the Google Play equivalent, Android vitals, if you have chosen to share it.

Children

Siftlet is a cooking app for a general audience and is not directed at children. Because it collects nothing, it collects nothing from children either.

Deleting your data

Everything Siftlet keeps is on your phone. We hold no copy, because there is no server of ours.

• Delete one recipe, one pantry item or one shopping list: remove it in the app.
• Remove the photographs kept with a recipe: Settings › photo storage, or edit the recipe.
• Erase everything at once: Settings › erase all data. You can export your recipes as a file first if you want to keep them.
• Delete everything together: uninstall the app. That removes the recipes, the pictures, the inventory, the lists and the settings.

There is nothing to request from us, and nobody to ask, because we never had it. If you have written to us by email and want that email deleted, ask at contact@grcsac.com and we will delete it.

Recipes you import belong to whoever wrote them

A recipe you import keeps the name of the site or the author it came from and a link back to the original. What you do with your copy is between you and the publisher; the terms of use say more.

Changes to this policy

If the app ever changes in a way that affects this policy, the new policy is posted at this address with a new date. The Android edition's release is such a change, and this page will carry it.

Contact

GRCSAC LLC · contact@grcsac.com