• Sesami stores your account and recipe-book data in Appwrite so your content can sync across signed-in devices.
• Recipe imports may send the content you choose to import, such as webpage HTML, recipe text, images, PDFs, source URLs, social post text, and YouTube transcript or description text, to Sesami backend functions for parsing.
• Sesami uses RevenueCat and Apple App Store services for subscriptions, Sentry for crash and error reporting, and OpenRouter, Google Gemini models, and Langfuse for AI-powered recipe parsing and AI diagnostics.
• Sesami uses Singular to measure which advertising campaigns lead to app installs and app opens. Singular may send attribution results to AppLovin when an AppLovin campaign led to the install.
• You can delete your Sesami account and app data from the app Settings screen under Account. You can also contact support@sesamiapps.com for help.

• Account information: your Appwrite user ID, guest account ID if you use guest mode, email address if you create or upgrade to an email account, authentication session information, and account labels such as premium status.
• Recipe-book content: recipes, recipe titles, descriptions, ingredients, instructions, nutrition fields, servings, prep and cook times, ratings, favorites, difficulty, source links, cookbooks, tags, grocery lists, grocery aisles, meal plans, meal-plan items, and related timestamps.
• Images and files: recipe cover images, instruction step images, imported images, and imported PDFs that you choose to add or parse.
• Import data: webpage HTML, URLs, page metadata, Instagram or TikTok post text when available, YouTube video URLs, YouTube descriptions, YouTube transcripts when available, pasted text, and parsed recipe results.
• Subscription and trial data: RevenueCat customer information tied to your Sesami Appwrite user ID, premium entitlement status, purchase or restore status, subscription-related webhook event IDs, and free-use trial counters for premium features.
• Device, app, and diagnostic data: app version, environment, operating system and device diagnostics, IP address, network status, function execution logs, crash reports, error logs, performance data, and similar technical information.
• Advertising attribution data: app install and app-open information, device and app information, IP address, campaign and click information, device identifiers such as IDFV or Android advertising ID, and IDFA only when iOS tracking permission allows access to it. When attribution identity is enabled, Sesami sends Singular a lowercase SHA-256 hash derived from your Appwrite user ID. Sesami does not send Singular your raw Appwrite user ID, email address, name, or phone number.
• Local app data: cached session data, cached Appwrite query results, image caches, pending image-upload queues, onboarding state, appearance settings, app language, recipe import language, and meal-plan week-start preferences and advertising-attribution setup state.

Sesami does not request precise location permission and does not show third-party ads in the app. On iOS, Sesami requests Apple tracking permission before starting the Singular attribution SDK. On Android, Singular starts only after you allow attribution in Sesami. The AppLovin advertising SDK is not included in the app.

• To create accounts, authenticate users, and keep sessions working.
• To save, display, sync, search, filter, update, and delete your recipes, cookbooks, tags, grocery lists, meal plans, and images.
• To import and parse recipes from websites, shared links, social posts, YouTube videos, images, PDFs, and pasted text.
• To manage premium access, trial usage, paywalls, subscriptions, and customer-center access.
• To provide support when you contact Sesami.
• To debug errors, monitor reliability, protect the service, prevent abuse, and improve the app.
• To attribute installs and app opens to advertising campaigns, measure campaign performance, prevent advertising fraud, and improve advertising spend.

When you import a recipe, Sesami processes only the content you choose to provide or share with the app. Depending on the import method, that content may include a source URL, webpage HTML, social post metadata, YouTube description or transcript text, pasted recipe text, an image, or a PDF. Sesami backend functions use parsers and AI models to turn that content into an editable recipe.

AI processing may send prompts, imported content, generated recipe output, source URLs, and technical metadata to OpenRouter and the model providers it routes to. The current backend model configuration uses Google Gemini models through OpenRouter. Sesami also uses Langfuse and Appwrite function logs for AI and backend diagnostics, which may include import content, prompts, generated outputs, source URLs, user IDs, and technical metadata.

• Camera and photo library: used only when you choose to take or select recipe images or import a recipe from an image.
• Document picker: used when you choose a PDF or file to import.
• Share extension/share intent: used when you share a link, image, or file into Sesami.
• Clipboard: used when you ask Sesami to read text or a link from the clipboard.
• Web browser and WebView: used to open links and, when needed, load webpages so Sesami can capture recipe content for import.
• SecureStore and local storage: used to store session data, preferences, caches, and upload queues on your device.
• Tracking transparency: on iOS, requested after onboarding and before Singular starts. If you deny the iOS system permission, Singular cannot access IDFA but may still perform privacy-preserving attribution using other permitted information.

Deleting the app removes local data from that device, but it does not delete cloud data stored in your Sesami account. To delete cloud data, use account deletion in Settings.

• Appwrite: provides authentication, database storage, recipe image storage, backend functions, and function logs. Appwrite processes account IDs, email addresses when provided, sessions, user-created recipe-book data, images, imported content sent to functions, premium labels, trial counters, IP addresses, and technical logs.
• RevenueCat: manages subscription status, paywalls, customer-center features, entitlement checks, and subscription webhooks. Sesami uses your Appwrite user ID as the RevenueCat App User ID so paid access can be matched to your Sesami account.
• Apple App Store, TestFlight, and App Store Connect: process app distribution, testing, subscriptions, in-app purchases, and payment-related information for iOS. Sesami and RevenueCat receive subscription or transaction status needed to unlock premium features, but Sesami does not receive your full payment card details from Apple.
• Sentry: provides crash and error reporting. Sentry may process crash reports, error messages, stack traces, app version, environment, device and operating system diagnostics, and the Sesami user ID. Sesami configures Sentry with default personal information collection disabled.
• Singular: provides mobile advertising attribution and campaign measurement after the applicable permission or choice described in this policy. Singular may process install and app-open information, device and app information, IP address, campaign information, IDFV, Android advertising ID, the pseudonymous SHA-256 account identifier, and IDFA when iOS permission allows it. The pseudonymous account identifier is set in Singular on iOS only when Apple tracking permission is granted at login and on Android only after you allow attribution in Sesami.
• AppLovin: provides advertising campaigns used to promote Sesami. When an AppLovin campaign is attributed to an install or app open, Singular may send AppLovin an attribution postback containing campaign, install, session, and device-related information. The AppLovin SDK is not included in Sesami.
• OpenRouter and AI model providers: process recipe import prompts and outputs for AI-assisted parsing. This may include pasted text, webpage content, source URLs, YouTube data, images, PDFs, and generated recipe data.
• Langfuse: provides AI tracing and observability for backend recipe parsing. Langfuse may receive prompts, model outputs, usage metadata, source URLs, user IDs, and operational trace data.
• Google/YouTube APIs: used when you import YouTube content. They may process video IDs, URLs, metadata requests, page requests, transcript-related requests, and related technical information.
• Imported websites and social platforms: when you ask Sesami to import from a website or social link, your device or Sesami backend may request content from that site. Those sites may receive normal request information such as IP address, user agent, requested URL, cookies or page state available in the browser context, and other information governed by their own policies.

Sesami shares information with service providers only as needed to run the app, process subscriptions, parse recipes, store data, provide support, monitor reliability, protect the service, or measure advertising attribution. Sesami may also disclose information if required by law, to respond to valid legal process, to protect rights and safety, or to investigate abuse or fraud. Sesami does not sell your personal information.

On iOS, Apple tracking permission is requested before Singular starts. Denying it prevents access to IDFA and cross-app tracking, while Singular may still perform privacy-preserving attribution using permitted information. Denying permission prevents Sesami from setting the pseudonymous account identifier at login. You can change Apple tracking permission in the iOS Settings app and log out of Sesami to remove the identifier from Singular. On Android, Sesami asks before starting Singular and stores your choice locally on the device.

Sesami keeps account data and user-created content for as long as your account is active or as long as needed to provide the app. Operational logs, crash reports, AI traces, advertising attribution records, subscription records, and payment records may be kept by Sesami or third-party providers for debugging, security, fraud prevention, financial, legal, or service-operation needs according to their retention practices. Advertising-attribution setup state is stored locally on your device until you remove the app.

Sesami instructs Singular to remove the current pseudonymous account identifier after logout or account deletion. Singular may retain previously created attribution records according to its retention practices.

You can delete your account and Sesami cloud data in the app by opening Settings, selecting Account, and choosing Delete Account. The app sends a deletion request to the Sesami backend, signs you out, and schedules cleanup of your Appwrite account, recipe images, recipe rows, cookbooks, tags, grocery data, meal-plan data, and premium trial usage data.

If you need help deleting data, contact support@sesamiapps.com. Subscription and purchase history managed by Apple or RevenueCat may need to be managed through those services separately.

Sesami is not intended for children under 13. Sesami does not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information to Sesami, contact support@sesamiapps.com.

Sesami uses technical and organizational safeguards to protect information, including authenticated access to user data, Appwrite row security for user data tables, file security for recipe images, and device secure storage for session data. No method of transmission or storage is completely secure, so Sesami cannot guarantee absolute security.

Sesami may update this Privacy Policy from time to time. Updates will be posted on this page, and the Last updated date will be changed when the policy changes.

If you have questions about this Privacy Policy or Sesami privacy practices, contact support@sesamiapps.com.