Privacy Policy

Last updated 29 October 2026

StickyChef is a personal cookbook app operated by R Click. Contact: eliran@rclick.co.il.

What we collect

• Account: name, email, and a password hash — or Sign in with Apple / Google identifiers.
• Cookbook data you save: recipes, covers, cookbooks, tags, favorites, serving notes, and group invites you start.
• Import input you send us: a URL, pasted text, or a photo, so we can turn it into a recipe card. We keep the text you shared, and the text of the page it links to, with the import so we can improve the recipe's details later. We do not keep the photo itself.
• Recipe details we work out: cuisine, equipment, meal times, allergens, diet labels and estimated nutrition. These describe recipes, not you.
• Meal reminders, only if you turn them on: when you open the app or start cooking a recipe, and whether you are on Wi-Fi or mobile data, so a reminder can come a little before you usually cook. We never use your location. These records are deleted after 90 days.
• Preferences: language, unit system, meal reminder switches, your device's time zone, and an Expo push token if you allow notifications. Food label choices, such as showing religious labels or nutrition, stay on your device and are never sent to us.
• Crash reports and app usage: the app includes Firebase Crashlytics and Firebase Analytics (Google), without an advertising identifier. They never receive your food label choices or the filters you pick.

How we use it

We use this data to run your account, store your cookbook, extract a recipe from a share you send, and notify you when an import finishes. Recipe text may be sent to AI providers (currently DeepSeek and, if that fails, OpenAI) only to structure and describe the recipe. We do not sell personal data. StickyChef is free to use and has no in-app purchases.

Allergen, diet, kosher, halal and nutrition labels are worked out from a recipe's ingredients and are estimates: a guide, not a certification. If you have an allergy or a religious requirement, always check the actual ingredients.

Contextual sponsor offers

When sponsorship delivery is enabled, guests and registered users may see clearly labeled offers matched to the current recipe's ingredients or equipment, or filters they explicitly selected. We also use app language, approximate country supplied by trusted IP geolocation, and a broad activity band. We store the country code in advertising records, not the raw IP address. An unfiltered recipe grid does not use interests inferred from your cookbook.

Activity bands are New (account under seven days old), Frequent (at least eight active days in the last 28 days), Occasional (one to seven), or Unknown when data is insufficient. Purpose-specific daily activity records begin only after this advertising disclosure launches; we do not reuse historical meal-reminder records. We do not build personal taste profiles. Religious-label settings, allergies, health attributes and private notes are excluded from advertising targeting.

Our own backend measures deliveries, viewable impressions, offer taps, sponsor-page views, foreground engagement time, scroll depth and outbound clicks. These records are linked to your app account (including a guest account) for frequency limits, measurement and campaign hiding. Detailed advertising records are retained for 90 days; daily activity for 28 days; non-identifying daily totals for 13 months. Account deletion removes associated advertising records. Sponsors receive aggregate reports, not individual account identifiers, recipe histories or activity records.

Sponsor pages include “Why this ad?” and “Hide this campaign for 30 days.” A sponsor button uses a signed first-party redirect to an approved HTTPS destination in the system browser. Campaign tracking parameters identify the campaign, creative and placement, never you or your recipe history. The destination website may process its own visitors under its own privacy policy. We do not use advertising identifiers, third-party ad networks, tracking pixels, or track purchases outside the app.

Sharing

Recipes you type or paste, import from a photo, or import from a website stay in your cookbook unless you invite someone in the Group tab.

Discover: when you import a recipe from a link to a public social post (Instagram, TikTok, Facebook or YouTube), our server opens that link once, without any account, to check the post is public. If it is, other cooks can find the recipe on Discover with its title, cover, ingredients, steps, and a link to the original post. Your name, your notes, your cookbooks and your edits are never shown there. You can hide the recipe from Discover, or share it again, from the recipe page. Cooks who already saved it keep their copy.

Reports: if you report a Discover recipe, we keep the reason and note you give, linked to your account, so we can review it. The cook who imported the recipe is not told who reported it.

Children

StickyChef is not directed at children under 13.

Retention and deletion

We keep account and cookbook data while the account exists. The shared text behind an import that never became a recipe, or whose recipe is gone, is deleted after 30 days. In the app, open Menu → Account & privacy → Delete account. That removes your account, recipes, cookbooks, and sign-in immediately. You can also email eliran@rclick.co.il to request deletion.