Tofu

Privacy Policy

Updated: 31 October 2026

Tofu is provided by Francisco Pereira, Portugal. Contact geral.forgeapps@gmail.com about this policy or your data.

On your device and optional account sync

Meal planning runs on your device. Preferences, plans, shopping-list progress, saved recipes, cookbooks and notes are saved locally. Local recipe photos and receipt recognition are processed on your device; using a photo picker does not give us access to your entire library.

You can choose to save progress with Apple, Google or email. Supabase then stores the account identifier, authentication details and an account backup of your profile, plans, recipes, cookbooks and notes for syncing. This includes the allergies and household information, such as children's ages, that you entered in the profile. Local photo files are not copied by account sync. A technical guest identity may also be created for features that need secure server access, even without a permanent account.

Recipe import and AI processing

When you request an import, your chosen link and recipe text are sent to our Supabase backend. For a public video, the import may fetch the public caption, audio or video frames and process them with Cloudflare Workers AI to extract the recipe. Where the source does not provide enough detail, the app can offer a generated version and identifies it as such. Do not include people, payment details or unrelated personal information in material you import. Review ingredients and cooking instructions yourself, especially for allergies.

The backend retains request identifiers, status and the recipe response for reliable delivery and usage limits. Eligible public-source recipe results may be cached for reuse. Operational pruning removes settled request records older than 24 hours and public import-cache records older than 30 days when it runs; these are not promises of deletion at an exact time. Media is processed transiently rather than saved in the import database. Providers may keep technical service and security logs. See Cloudflare's data usage policy.

Community content

Publishing is a separate choice from saving or importing a recipe. If you publish, your chosen public name, handle, bio and recipe content are stored on our servers and can be visible to other people. Where community chats are available, they store messages, group membership, reactions, read status and the images or videos you choose to send. Group chat is disabled in version 1.1.0. Group members and administrators can see the content available to their group. Removing a local draft alone does not withdraw a published recipe. Content reports and personal creator blocks are stored privately under the account that submitted them; the reported person cannot read the reporter identity from these records.

Notifications, invitations and prices

If you allow notifications, we store a device push token, language, timezone, notification preferences and activity or subscription state needed to deliver account messages. Some meal and return reminders are scheduled locally. You can disable notifications in Profile or device settings.

Creator campaign codes and personal invitations are separate. We keep attribution and qualifying referral-reward records under the relevant app account. Creator link clicks are aggregated without storing an IP address or browser user-agent in the click counter. If you opt into contributing prices, we associate contributions with your account privately for consent, deletion and limits; public price projections omit your account identity. Confirmed price data may be contributed to Open Prices under its public-data licence when you choose that feature.

Purchases

Apple or Google processes store payments. RevenueCat and our backend process purchase history and subscription status associated with the Tofu account identifier to verify access, restore purchases and administer eligible referrals or account messages. We do not receive your full payment-card details. Account deletion does not cancel a store subscription. Store providers may retain transaction records for their subscription and record-keeping obligations.

Optional analytics

Usage analytics are on by default and you can turn them off at any time in Profile. PostHog receives limited product and purchase-funnel events, selected settings such as market and retailer, and operation durations under a random app identifier. While analytics are on, that identifier can also be attached to the same Tofu customer's RevenueCat record. These records are pseudonymous, not fully anonymous. Events exclude names, email addresses, allergy details, recipe text, photos and other sensitive free text. We do not use this for advertising or tracking across other companies' apps. Turning analytics off stops new events and unlinks the active analytics identifier from future purchase attributes.

Providers and processing locations

We use Supabase for authentication, data and storage, Cloudflare for recipe processing, RevenueCat for subscriptions, PostHog for usage analytics, and Apple or Google for store and sign-in services. The current Supabase project is hosted in London, United Kingdom, and PostHog uses its EU endpoint. Some providers process data internationally, so processing is not guaranteed to stay within the EU. Tofu account data and attribution are scoped separately from other Forge Apps products.

Retention, deletion and your choices

Account backups and published content remain while needed for your requested features, until you remove the content or request account deletion. Community messages and media also have server retention and cleanup rules. We retain bounded operational records for reliability, security, quotas and subscription administration; subscription event logs are eligible for pruning after 90 days. Provider logs and backups follow their applicable retention rules.

Use Delete account in Profile to request removal of the active backend account and its linked private data, published content and notification tokens, then clear local app data. An internet connection is required. If deletion fails, keep the app installed and retry or contact us. Media cleanup may finish asynchronously. Data in other people's own copies, your photo library, external public datasets or store transaction records is separate. Uninstalling alone does not request account deletion and does not cancel a subscription.

You can contact geral.forgeapps@gmail.com to request access, correction or deletion, ask about retention or processing locations, or raise another data-protection concern. You may also contact your local data-protection authority. The app is intended for adults planning meals, including household meals; entering a child's age does not create an account for that child.

Changes

We update this policy when our practices change and show the date above. Read the current policy before choosing an optional feature that sends data.