Recipe Dost · com.recipedost.app
Privacy Policy
This policy explains how Isbat Apps processes information when you use Recipe Dost.
1. Operator and scope
Recipe Dost is operated by Isbat Apps (“we,” “us,” or “our”). This policy applies to the Recipe Dost Android app, package com.recipedost.app, its backend processing, and support interactions. Contact us at isbatapps@gmail.com.
This legal website is static. Isbat Apps does not place analytics, advertising, tracking scripts, cookies, accounts, or data-submission forms on it. Cloudflare Pages delivers the website and may process ordinary web-request information under Cloudflare’s policy.
2. Anonymous accounts
Recipe Dost does not currently require a traditional email-and-password account. The app creates an anonymous account identifier through Supabase so saved recipes, generated recipe information, grocery lists, usage limits, and subscription access can be associated with the correct anonymous account.
The identifier is a pseudonymous account ID, not a guarantee of anonymity in every context. The app stores its session securely on the device. Clearing app data or uninstalling before deleting the account may make it harder to regain access to that anonymous account.
3. Information you submit and information the app stores
Recipe links and source metadata
When you submit a supported recipe link, Recipe Dost stores the source link and may store the source platform, title, description, creator or publisher label, thumbnail, duration, processing status, normalized errors, and related technical metadata. Saved recipe records can also include favorites, collections, tags, language preferences, and timestamps.
AI-generated recipe processing
When you request an AI recipe card, information needed for that request is processed by the Recipe Dost backend and Google Gemini. Depending on the supported source, this can include the submitted recipe link, source title and metadata, or a temporary media file obtained from the public or authorized source. Gemini returns structured recipe information such as titles, summaries, ingredients, instructions, grocery items, timing, servings, tags, safety notes, confidence, and missing or uncertain details.
The active worker stores the generated recipe result and technical processing status in Supabase. It does not provide user-facing social-video downloads or permanently store, host, or back up social-platform videos. When a temporary media file is needed, the worker deletes its local file after processing and attempts to delete the temporary Gemini file after analysis. Exact retention within a provider’s systems is governed by that provider’s terms and settings.
Grocery lists
Recipe Dost stores grocery-list titles, ingredient or item text, quantities or notes, completion state, related recipe references, and timestamps so lists remain available across app sessions.
AI-content reports
From an AI recipe card, you can report “Incorrect or misleading,” “Unsafe cooking instructions,” “Allergy or food safety,” “Offensive content,” or “Other.” A report stores your anonymous account ID, the related recipe-card ID, the selected category, an optional note of up to 500 characters, app version, build number, and submission time. The report record does not copy the recipe body or source link.
Subscriptions and access
Optional Premium purchases use Google Play Billing and RevenueCat. Recipe Dost and RevenueCat process a pseudonymous app-user ID, product and entitlement information, subscription status, relevant transaction or receipt metadata, and technical information needed to provide and restore access. Google Play processes payment details. Recipe Dost does not receive your full payment-card number.
Product analytics
PostHog receives approved product-interaction events, safe screen names, platform, app version, build number, environment, limited result or failure categories, and the anonymous account ID used as a pseudonymous analytics identifier. Automatic touch capture, automatic screen capture, session replay, surveys, remote feature flags, and automatic exception capture are disabled. Geo-IP enrichment is disabled in the app configuration.
Recipe Dost does not intentionally send raw recipe or source links, recipe titles, ingredients, instructions, grocery-list text, search text, AI prompts or responses, report notes, auth tokens, purchase receipts, or payment details to PostHog. Library and grocery search matching occurs client-side; analytics record only approved high-level outcomes, not the search text.
Crash and technical diagnostics
Sentry is used for sanitized technical error monitoring in the production app. It may receive a pseudonymous account ID from the app, app version, build number, environment, safe error type, sanitized stack-frame information, and limited operational categories. The worker also has fail-closed Sentry monitoring for unexpected production failures; it sends only when its valid production environment, branch, and Sentry settings are present. Default personal-information sending, screenshots, view hierarchies, breadcrumbs, tracing, profiling, request bodies, source context, and local variables are disabled in the configured flows.
Recipe Dost does not intentionally send raw recipe or source links, recipe ingredients or instructions, grocery-list text, search text, AI prompts or responses, report notes, auth tokens, request bodies, cookies, or secrets to Sentry.
4. How information is used
- create and maintain the anonymous account and session;
- save recipe links, source metadata, generated recipes, preferences, collections, and grocery lists;
- generate AI recipe cards and show processing results;
- apply usage limits and provide Premium subscription access;
- restore purchases and synchronize entitlement status;
- review AI-content reports and improve safety or quality;
- operate, secure, troubleshoot, and improve Recipe Dost;
- respond to support, privacy, and deletion requests; and
- comply with applicable legal obligations and resolve disputes.
5. Active service providers
| Provider | Role and broad data |
|---|---|
| Supabase privacy | Anonymous authentication, app database, server functions, and technical logs; processes the anonymous ID and stored app information. |
| Render privacy | Hosts the production media and AI worker; processes job identifiers, submitted sources, source metadata, temporary media, safe operational logs, and generated results as needed. |
| Google privacy | Google Gemini processes the recipe source information or temporary media needed to provide the requested AI feature. Google Play processes purchases and payment details. |
| RevenueCat privacy | Subscription purchase and entitlement management using the pseudonymous app-user ID and store transaction or entitlement information. |
| Sentry privacy | Sanitized app crash monitoring and, when valid production settings enable it, unexpected worker-failure monitoring. |
| PostHog privacy | Approved product-interaction analytics using pseudonymous identifiers and limited app or device metadata. |
| Cloudflare privacy | Hosts and delivers this static legal website and processes ordinary web-request and security information. |
These providers may process information in countries other than where you live. The project configuration does not establish a single processing region or a single exact retention period for every provider, so this policy does not make those claims.
6. AI-generated-content limitations
AI-generated recipes can be incomplete, inaccurate, unsafe, offensive, or unsuitable for your circumstances. Independently check ingredients, measurements, cooking temperatures, allergens, dietary restrictions, and food-safety guidance. Recipe Dost is not medical, nutritional, or professional advice. Use the in-app report action when an AI recipe is problematic.
7. Retention
Account-linked app information is kept while the anonymous account is active and as reasonably necessary to operate the service. Other records are kept only as reasonably necessary for security, fraud and abuse prevention, support, legal compliance, accounting, dispute resolution, and enforcement.
In-app account deletion permanently removes the Supabase anonymous auth user and account-linked app records that cascade from it. Verified external requests are normally processed within 30 days. Provider-controlled billing records, store transactions, and previously collected analytics, diagnostic, security, or backup records may be retained independently for the provider’s legitimate purposes or legal obligations. Deleting Recipe Dost does not itself cancel a Google Play subscription.
8. Account and data deletion
Go to Settings → Privacy & Data → Delete account & data, select Delete account & data, then confirm Delete permanently. You can also make an external request. See the Recipe Dost account-deletion instructions.
9. Security
We use reasonable technical and organizational safeguards designed for the information processed, including authenticated server functions, row-level data access controls, encrypted HTTPS transport, secret separation, and restricted observability payloads. No service or transmission method can guarantee absolute security.
10. Children and target audience
Recipe Dost is a general-audience recipe utility and is not designed specifically for children. It does not ask users to provide a name, email address, date of birth, photo, or traditional password during anonymous sign-in. If you are a parent or guardian and believe a child has provided information that should be removed, contact us so we can assess and respond under applicable law.
11. Your choices and rights
You can choose which supported recipe links to submit, whether to request AI generation, whether to add an optional report note, and whether to purchase Premium. You can delete the anonymous account in the app, request deletion externally, or contact us about access, correction, objection, restriction, or other rights available under applicable law. We may need enough information to locate and verify the anonymous account.
The Android app accepts shared text links but does not provide local photo, video, audio, or document uploads. It blocks legacy external-storage read and write permissions and does not include an advertising SDK or ad placement.
12. Changes to this policy
We may update this policy when Recipe Dost, its providers, data flows, deletion behavior, or legal requirements change. The updated page will show a revised date, and we will provide additional notice when required.
13. Contact
Operator: Isbat Apps
Email: isbatapps@gmail.com