Mindful Solutions LLC
Privacy Policy
1. Introduction
This Privacy Policy explains how Mindful Solutions LLC ("Mindful Solutions," "we," "us," or "our") collects, uses, stores, shares, and protects information in connection with our mobile application TailoredPlate (the "App") and related services (together, the "Services").
Mindful Solutions LLC is a limited liability company organized under the laws of the State of Michigan, United States, and is the data controller responsible for your information under this policy. TailoredPlate is our product.
By using the App, you agree to the collection, use, and storage of information as described in this Privacy Policy. If you do not agree, please do not use the App. The App is intended only for users who are 18 years of age or older; see Section 14.
2. Information We Collect
We collect only the information needed to operate the App, sync your data across your devices, and generate recipes tailored to your needs. The categories below describe what we collect and where it is stored.
2.1 Account and Identity Information
We use Amazon Cognito (a service of Amazon Web Services) to manage sign-in. You can sign in with Apple, Google, or an email address and password. For your account we store: We also collect your name at account creation (or from your sign-in provider) to manage your account and provide support.
- Your email address;
- Your name, if you choose to provide it (for example, when signing in with Apple or Google);
- Your sign-in method (Apple, Google, or email/password) and a unique account identifier.
If you create an email-and-password account, your password is handled and stored in hashed form by Amazon Cognito; we never see or store your actual password.
Your email is your account identity. If you sign in using more than one method that share the same verified email address, we treat them as the same account, so your data stays with you no matter how you sign in.
If you use Apple's Hide My Email feature, we only ever receive the private relay address that Apple provides — we do not see your real email address.
2.2 Your Profile and Synced Content
When you are signed in, the App stores the following on our servers and syncs it across the devices where you use your account:
- Your dietary profiles, including your allergen and ingredient exclusions and your dietary sensitivity flags (such as low-FODMAP and low-histamine settings), along with diet selections and taste preferences;
- Recipes you save, including ratings and personal notes, and the AI-generated image for a saved recipe;
- Your pantry and staples list;
- Your shopping list.
Your allergen exclusions and dietary sensitivity flags are health-related information. We treat this data with particular care — see Section 4.
How and where this data is stored, secured, and kept accessible only to you is described in Section 3.
2.3 Recipe Inputs
When you generate a recipe, your dietary context for that request — such as your exclusions, preferences, relevant pantry contents, and any free-text description of the meal you want (typed or spoken) — is sent through our servers to third-party AI providers to produce the recipe. Terms derived from your exclusions (for example, safe phrasings of an ingredient you exclude) are included with the request so the recipe respects your restrictions. This data flow is described in Section 6.
2.4 Usage Information
To administer plan limits and subscriptions, we keep a count of the recipes generated by your account on our servers, associated with your account identifier. We use this solely to enforce the limits of your plan and to operate the Services.
Acceptance and consent records. When you accept our Terms of Service and this Privacy Policy, or give or withdraw a consent in the App (such as your consent to our use of your health-related information), we record which version and when, with your account identifier. We keep these records after you delete your account, for as long as needed to show what was agreed and to establish or defend legal claims.
2.5 Push Notification Data
To keep your devices in sync, we store a device push token and a per-installation device identifier for each device where you are signed in. These are used only to send your other devices a silent "data changed — please refresh" signal. This identifier is used solely to route sync notifications; it is not used to track you or your activity across apps or over time. See Section 7 for how these notifications are delivered.
2.6 Subscription and Purchase Information
When you purchase a subscription, the transaction is processed by the Apple App Store or Google Play, and subscription status is managed through RevenueCat (a subscription-management service). We receive information about your subscription status (for example, which plan you have and whether it is active). We do not collect or store your payment-card number or full payment details — those are handled by the app stores and their payment processors.
2.7 Device Permissions
The App requests the following device permissions, each used only for the stated purpose. You can grant or deny these in your device settings.
- Camera — to scan food barcodes and to let you photograph your own dishes. When you scan a barcode, the barcode number is sent to Open Food Facts, a third-party public food database, to look up the product name. The request we send contains only the barcode number; no account information or dietary data is included. See Section 8.
- Microphone and speech recognition — to let you use voice input: for example, to add ingredients, to describe a meal you want, or to modify a recipe. When you use voice input, your device's speech-recognition service converts your speech to text. Depending on your device, platform, and language, this processing may happen on your device, or the platform's speech service (Apple on iOS or Google on Android) may receive the audio of your voice input to return the transcribed text. We receive and use only the resulting text, and only for the action you were performing; we do not store or receive your voice audio. See Sections 6 and 8.
- Photo library — to let you add your own photos to recipes.
- Notifications — to send sync and cooking-timer alerts.
The App does not request access to your location, contacts, or calendar.
2.8 Information Stored Only on Your Device
Some information stays only on your device and is not uploaded to our servers: your authentication tokens (kept in your device's secure storage), your active-profile selection on that device, and photos you attach to your own recipes. Photos you attach to your own recipes are stored on your device. AI-generated recipe images for recipes you save are stored on our servers (see Section 2.2) so that a saved recipe keeps its image over time and across your devices; AI images for recipes you do not save are held only temporarily.
2.9 Sharing a Recipe
When you share a recipe, the recipe content (its name, description, ingredients, steps, servings, time, and image if one exists) is stored on our servers for up to 90 days so the link works for the recipient, and then it expires automatically. Shared recipes contain recipe content only — no account information, none of your dietary or allergen information, and nothing linked to you — and anyone with the link can view them. Because shared recipes are not connected to your account, share links you have created remain live until they expire, including after you delete your account.
3. How We Store and Sync Your Data
The App is designed to sync your data across your devices. When you are signed in, the profile and content described in Section 2.2 is stored on our servers — this is core functionality that lets your dietary profiles, recipes, and lists follow you from one device to another. It is not optional telemetry, and it is not advertising data; it is your own data, stored so the App can give it back to you wherever you sign in.
This data is:
- Stored on Amazon Web Services (AWS) infrastructure in the United States;
- Encrypted in transit (HTTPS/TLS) and at rest;
- Linked to your authenticated account and accessible only to the signed-in account it belongs to.
See Section 12 for more on how we secure and isolate your data.
4. Sensitive Dietary and Health-Related Data
Some of the information you provide is health-related and therefore sensitive. This includes your allergen and ingredient exclusions and your dietary sensitivity flags (such as low-FODMAP and low-histamine settings). We handle this information with particular care:
- Purpose limitation. We use it only to provide the Services — to generate recipes that respect your restrictions and to store and sync your profile across your devices. We do not use it for any other purpose.
- No sale, no marketing. We do not sell this information and do not share it for advertising or marketing.
- Limited sharing. We share it only with the infrastructure and AI providers necessary to operate the App, as described in Sections 6 and 8, and only for the purposes described there.
- Security and access. It is stored encrypted, on access-controlled infrastructure, tied to your authenticated account so that only you can access it (Section 12).
- Deletion. When you delete your account, it is deleted from our live systems right away, and remaining copies are removed within 90 days (Section 11).
You choose what dietary information to provide. You may omit certain restrictions, though doing so may affect how well the App can tailor recipes to your needs.
5. How We Use Information
We use the information described above to:
- Create and manage your account and authenticate you;
- Store your profile and content and sync it across your devices;
- Generate recipes based on your inputs and preferences;
- Send silent notifications so your devices stay in sync;
- Enforce the limits of your plan and manage subscriptions;
- Operate, maintain, and improve the App;
- Respond to your requests and provide support;
- Comply with legal obligations and enforce our Terms of Service.
We do not use your information for advertising or cross-app tracking.
6. Recipe Generation and AI Providers
TailoredPlate generates recipes using third-party artificial-intelligence providers. When you generate a recipe, your dietary context for that request (Section 2.3) is sent through our own servers to these providers, which return the recipe text and image. The App does not contact the AI providers directly. Our current providers are:
- Google (Gemini) — our primary provider for recipe text and images;
- Anthropic (Claude) — a fallback provider for recipe text when the primary provider is unavailable.
Voice input (speech recognition). Separately from recipe generation, when you use voice input, speech-to-text is handled by your device's operating system, not through our servers. Depending on your device, platform, and language, the processing may happen on your device, or your device's platform speech service (Apple on iOS, or Google on Android) may receive your voice audio to transcribe it, governed by that provider's privacy policy. Either way, we receive only the transcribed text.
We send these requests through the providers' business APIs under terms that limit their use of the data to generating the response for us; they are not permitted to use your inputs for their own purposes, such as advertising. We also keep a per-account count of recipes generated, on our servers, to enforce plan limits.
7. Push Notifications
We send silent push notifications to tell your other signed-in devices that your data has changed and should refresh. These notifications carry no personal data — they are only a signal to wake the App and sync. To deliver them, we use the device push token and installation identifier described in Section 2.5, sent through:
- Expo's push notification service, which routes notifications to the platform services below;
- Apple Push Notification service (APNs) on iOS; and
- Google Firebase Cloud Messaging (FCM) on Android.
On Android, we use Firebase solely to deliver these notifications. Firebase Analytics is disabled, and we do not use Firebase to collect analytics or usage data.
8. How We Share Information
We share information only with the service providers necessary to operate the App. We do not sell your personal information, and we do not share it for advertising or marketing. The only third parties involved are infrastructure and processing providers:
- Amazon Web Services (AWS) — hosting, authentication (Amazon Cognito), and storage of your account, profile, and synced content.
- Expo, Apple (APNs), and Google (FCM/Firebase) — delivery of sync push notifications; Apple and Google also provide sign-in.
- Google (Gemini) and Anthropic (Claude) — recipe generation only, as described in Section 6.
- RevenueCat and the Apple App Store / Google Play — subscription status and payment processing. RevenueCat receives our internal account identifier along with subscription events, and your name and email address as customer attributes so we can identify your account when you contact us for support. RevenueCat processes this information on our behalf. Records held by RevenueCat and by the app stores are retained under their own policies; if you provided them, these records include your name and email address.
- Apple and Google speech services — when you use voice input, your device's platform speech service (Apple on iOS or Google on Android) may receive your voice audio to transcribe it to text, or the processing may happen on your device, depending on your device, platform, and language (Section 2.7). This is handled by your device's operating system.
- Open Food Facts — when you scan a product barcode, the barcode number is sent to this third-party public food database to look up the product name (Section 2.7). The request contains only the barcode number; no account information or dietary data is sent.
We may also disclose information if required to do so by law, or to protect the rights, property, or safety of Mindful Solutions LLC, our users, or others.
9. What We Do Not Do
We want to be plain about this, because it is a deliberate choice:
- We do not use analytics, usage-tracking, or telemetry SDKs.
- We do not display advertising or use any advertising services.
- We do not use advertising identifiers (Apple's IDFA or Android's Advertising ID) and do not track you across other apps or websites.
- We do not sell your personal information or share it for marketing.
10. Data Retention
- Your account, profile, and synced content (dietary profiles, saved recipes, pantry/staples, and shopping lists) and your usage count are retained for as long as your account is active.
- Device registrations (push tokens and installation identifiers) are retained while the device remains registered and are removed when you sign out on that device or delete your account.
- Recipe inputs sent for generation are processed to produce your recipe and are not retained by us as a durable record beyond what is needed to operate and meter the Services. Separately, we keep a library of the generated recipes themselves to operate and improve the Services; it is organized by recipe, not by user, and any internal account reference on a recipe is removed when you delete your account; for a recipe made in the last moments before you delete, it is removed within 30 days.
- Device-only information remains on your device until you delete it, delete your account, or uninstall the App.
- Metering records. We keep a per-delivery record that a recipe was delivered to your account: an internal account identifier, a timestamp, the number of recipes, and which allowance was charged (for a delivery on a paid plan, this includes the subscription identifier). These records contain no recipe content and none of your dietary information. They are retained after account deletion, for as long as we operate the service, so that we can account for service usage over time. Within our own systems, that identifier no longer resolves to a person once your account is deleted: the identity records that connect it to you (such as your email address) are deleted with your account. Separately, our subscription provider and the app stores retain their own records of past purchases under their own policies, as described in Section 11.
- Acceptance and consent records (Section 2.4) are kept after you delete your account, for as long as needed to show what was agreed and to establish or defend legal claims.
- The record of a deleted account. For 60 days after you delete your account we keep one record of it: a one-way code derived from your former account identifier, and the date it expires. It is used to refuse requests that arrive late from the deleted account. It holds nothing else.
- Operational and diagnostic logs. Our servers keep technical logs so we can operate the Services, diagnose failures, and keep the App's checks working. These logs can include account identifiers such as your email address, the exclusion terms applied to a generation request, and, when a generation fails our checks, short excerpts of the generated recipe text around the detected ingredient. These excerpts are taken from model output and can occasionally include words from your own request. Logs are stored in our own cloud infrastructure, are not shared with third parties, are not visible in the App, and are deleted automatically within 90 days, most of them within 30 days. Individual log entries cannot be selectively deleted, including when an account is deleted; they expire on that schedule.
11. Account Deletion and Your Rights
11.1 Deleting Your Account
When you delete your account we remove your data from our live systems right away. Remaining copies, such as server logs and short-lived security records, are removed automatically within 90 days. When you delete your account from within the App, we remove from our servers:
- your account itself;
- all of your synced data — dietary profiles (including allergen exclusions and sensitivity flags), saved recipes and their stored images, pantry/staples, and shopping lists; and
- your device registrations (push tokens and installation identifiers).
The App also clears the information stored locally on your device. This deletion runs immediately when you confirm it. What it does not reach: the metering records, the acceptance and consent records, the record of a deleted account, and the operational and diagnostic logs described in Section 10, which are retained or expire on the schedules stated there; recipe-generation job records, which briefly hold your request (including your exclusion terms) and the generated recipe together with the internal account identifier, and which self-expire within 24 hours of creation rather than being removed by deletion; share links you have created, which remain live until they expire (up to 90 days) and contain nothing linked to you (Section 2.9); and records held by our subscription provider (RevenueCat) and by Apple or Google in connection with past purchases, which those companies retain under their own policies. If you still have an active subscription with Apple or Google when you delete your account, their systems may continue to send us subscription events, which can re-create a minimal billing record keyed to your former account identifier; it contains no personal content. Within our own systems, the internal account identifier on retained records no longer resolves to a person after deletion.
11.2 Other Rights
Depending on where you live, you may have rights to access, correct, delete, or restrict the processing of your personal information. To make a request, contact us using the details in Section 16. You can also change the App's access to your camera, microphone, photo library, and notifications at any time in your device settings.
12. Data Security
We take reasonable measures to protect your information. Communications with our services use encryption in transit (HTTPS/TLS); authentication tokens are stored in your device's secure storage; and server-side data is stored on access-controlled cloud infrastructure with encryption at rest.
Your profile and content are tied to your authenticated account: our systems associate stored data with your account identity, and a request can only return data belonging to the authenticated account that makes it. There is no facility for one user to request or access another user's data.
However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.
13. International Users and Data Transfers
Mindful Solutions LLC is based in the United States, and the information we collect is processed and stored in the United States. If you access the App from outside the United States, you understand that your information will be transferred to and processed in the United States.
14. Children's Privacy
The App is intended only for users 18 years of age or older and is not directed to children. We do not knowingly collect personal information from children under 13 (or the equivalent minimum age in your jurisdiction). If you believe a child has provided us with personal information, please contact us and we will take appropriate steps to delete it.
15. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. When we make material changes, we will take reasonable steps to notify you — for example, within the App or by other appropriate means — and we will revise the "Last updated" date above and post the updated policy at this page. Your continued use of the App after changes become effective constitutes acceptance of the updated policy.
16. Contact Us
If you have questions about this Privacy Policy, or wish to make a privacy request, contact us at:
Mindful Solutions LLC
support@mindfulsolutionsllc.ai