Privacy Policy

Simmu: Recipes & Shopping List (“Simmu”, “the app”) · Last updated: 7 October 2026

This policy explains what data the app collects, why, how long we keep it and how to delete it. Simmu is published by Vladislav Carpenco (“we”, “us”). Questions: support@almalab.ai.

Using the app without an account

You can use Simmu without signing in and keep a personal kitchen on your device. Some features still use our servers: social-link imports, import history, public recipe links, collection transfers and the recipe archive described below. These requests can be associated with a device identifier even without an account. Signing in can associate device activity with your account.

Data we collect

Sign in with Apple (only if you create an account to share a kitchen or sync): your Apple account identifier, your name and your email address, which may be a private Apple relay address.
Kitchen content: recipes, saved posts, shopping list, meal plan, pantry items and photos in kitchens you sync are stored on our servers for access by your devices and kitchen members. Content used for public sharing, collection transfers or recipe archiving can also be sent to our servers without an account.
Import information: source URLs, text supplied with an import, processing results, status, timestamps, recipe identifiers, app version and diagnostic information. Import history is reported to our servers even when recipe extraction happens on your device. Social imports can also involve source captions, linked-page text, images, audio and video, as explained below.
Device, usage and diagnostic information: a random install identifier, device model, operating-system and app versions, language and time-zone settings, App Store country, in-app events, launch timing and crash reports. Events can include the source website of an import and ingredient names for which the app could not find an illustration. Our analytics platform AppHub also stores the IP address used to connect and derives a country from it; the app does not request GPS location. We use this information to run and improve the app, diagnose failures and understand our audience.
Apple Ads attribution: on first launch, AppHub sends an Apple AdServices attribution token to our server. We exchange it with Apple and store the result alongside the installation record to understand whether an App Store ad led to a download and, when provided, which campaign, ad group or keyword was involved. This does not give us information about ads viewed or clicked outside the App Store.
Purchase information: Apple transaction records that tell us whether a Pro subscription or lifetime purchase is active. We never see your payment card details; payments are handled by Apple.

When you request an import from a supported social link, the app sends the link and any accompanying text to our server. The server retrieves source content and, when needed, linked pages or media to extract a recipe. Relevant text, images, audio or video may be sent to OpenRouter, which routes requests to AI model providers. Our configured models include models developed by Anthropic, OpenAI, Google and ByteDance; the models used depend on the source and processing stage.

This processing includes any personal information present in the submitted text or source content. We keep import results and processing records as described below. The retention periods in this policy describe our storage; they do not state a retention or model-training guarantee for OpenRouter or its providers.

No tracking

We do not track you across other companies’ apps or websites, collect the advertising identifier (IDFA), or sell your data. The app does not display third-party ads or show the App Tracking Transparency prompt. Apple Ads attribution described above measures ads for Simmu on the App Store; we do not combine it with activity from other companies’ apps or websites to target or measure advertising.

How we use data

To provide the app’s features (sign-in, sync, shared kitchens, imports, sharing, collection transfers, photos and Pro access), to verify purchases and import limits, to diagnose processing failures, to keep the service secure, and to understand app usage (analytics). We do not use your recipes for advertising.

Members of your kitchen can see its recipes, saved posts, list, plan and photos and the display name you set. If you create a public recipe link, anyone with the link can view the shared recipe snapshot and its photo, including people outside your kitchen.

We use service providers for server hosting and storage, Apple for sign-in and payments, AppHub for analytics, and OpenRouter and the AI model providers involved in social imports. We may also disclose data where required by law.

Where data is stored and security

Account data, synced content and data used by the server features above are stored on our servers and in storage used by the service. Access to synced kitchen content is checked against kitchen membership; public recipe links intentionally make the shared snapshot available outside the kitchen. Session tokens are stored as hashes and the Apple sign-in refresh token is stored encrypted.

How long we keep data

Kitchen content and trash: a recipe normally remains recoverable in Trash for 30 days. When it leaves Trash, or you clear it earlier, its recipe data and photos are retained in a server archive without an automatic expiry. This also applies to recipes from a personal kitchen used without signing in. Removing a recipe from Trash removes it from the app’s collection; it does not erase the server archive.
Social-import payloads: scheduled cleanup uses default periods of 30 days from the request for detailed processing traces and supplied text, and 180 days from the request for completed result payloads. A shared cache of public-source content and cover images is eligible for cleanup 90 days after its last update. Cleanup is periodic and can be delayed by processing or storage failures. Recipes and photos you save have the separate kitchen and archive retention described above.
Import history and execution records: source URLs, identifiers, status, timestamps and processing usage and cost records do not have an automatic expiry. Clearing a result or cancelling an import does not erase all of these records. Temporary audio and video files used during processing are normally removed when the processing run finishes.
Collection transfers: server import files and results expire after 7 days; export snapshots and files expire after 24 hours. Scheduled cleanup removes expired payloads, with retries if storage is unavailable. Compact records can remain after the files expire.
Account deletion: your Apple identifier and email are erased, your display name is replaced, your sessions are revoked and you leave your kitchens. Your import request records, public recipe links and device-owned recipe archives are deleted. A kitchen where you were the only member has its synced content, recipe archive and photos deleted. Content in kitchens with other members remains available to them. The remaining account record is scheduled for removal after 30 days; removal can wait for Apple token revocation to succeed.
Records that can remain after account deletion: device and purchase records are detached from your account. Import execution and model-call records and the shared cache of public-source content are not erased by account deletion. Temporary collection files remain subject to their cleanup rules.
AppHub installation, usage, diagnostic, IP/country and Apple Ads attribution records are associated with an installation identifier. These analytics records do not have an automatic expiry and are not automatically erased by Simmu’s in-app account deletion. Contact us to request deletion of these records.

Deleting your account and data

In the app go to More → Family → Delete account. You can export your data first. Deleting your account does not cancel an Apple subscription; manage subscriptions in your Apple ID settings (see Terms of Use). Deleting the app removes its local data but does not request deletion of data already sent to our servers. This also applies if you have never signed in. Email support@almalab.ai to request access to or deletion of server data, including data associated with use without an account.

Your rights

Depending on where you live (including the UK, Australia and the US) you may have the right to access, correct, export or delete your personal data and to complain to your data protection authority. Contact us at support@almalab.ai.

Children

Simmu is not directed to children under 13 and we do not knowingly collect their personal data.

Changes

If we change this policy we will update the date above and, for material changes, notify you in the app.