Meal Planner · StudioSphere Inc.
Privacy Policy
Effective: October 14, 2026. Last updated: October 15, 2026.
This policy explains how StudioSphere Inc. handles information for Meal-Planner.online, its Meal Planner apps and authorized connections. It covers this wellness service, not the company’s other products. Contact the Meal Planner Privacy Officer at privacy@meal-planner.online.
- Your household profile, private plans and Recipe Book are account-linked. Accepted household members can access shared content as described below.
- We use named hosting, AI, payment and email providers. Processing may occur outside Québec and Canada.
- An uploaded recipe file is a temporary processing copy. Its transcription and saved recipe have different retention rules.
- You can manage preferences, withdraw optional permissions, export your own saved recipes, and request account deletion.
On this page
Providers, hosting and technology
Our website uses WordPress, PHP and a database with a custom Meal Planner plugin and theme. Python services generate plans and handle scheduled delivery and privacy cleanup on a separate private Linux processing host, internally called Praxis. Administrative access uses secure connections, including Tailscale. The native app uses Swift/SwiftUI and Apple system frameworks. These are operating tools, not a public feed of your recipes. We do not publish infrastructure addresses, credentials or private storage paths.
| Provider | Purpose | Information involved |
|---|---|---|
DreamHost |
Website/database hosting and support mailbox; US hosting. | Account records, private content, support correspondence and hosting/security logs. |
Google GenAI / Gemini |
AI meal plans, recipe translations and illustrative food images. | Planning preferences and notes needed for the request, selected recipe facts and recent recipe-title context. We do not need to send your password or payment card. |
Anthropic / Claude API |
Optional photo/PDF transcription after your explicit upload consent. | The selected file and its contents, which can include embedded metadata; not your entire library or household profile. Provider retention is described below. |
Postmark |
Transactional weekly plans and account/service delivery where configured. | Recipient addresses, message content, delivery/bounce events and operational message identifiers. |
Buttondown |
Separately opted-in marketing newsletter. | Subscriber address, confirmation/unsubscribe state, product/campaign tags and recorded delivery, open or click metrics. Opening/click data may be affected by mail-client privacy features. |
Stripe |
Website subscription payments, billing portal, refunds and subscription reconciliation. | Payment and billing information submitted to Stripe. We retain the customer/subscription and transaction references needed to administer access, not full card details. |
Instacart |
Optional grocery-list handoff when an eligible user clicks the shopping control. | Ingredient names, quantities and a plan link used to create a shopping-list destination. Your shopping account, address, checkout and orders are handled with Instacart/retailers. |
Apple |
iOS distribution, system permissions and purchases when offered through the App Store. | Apple handles its device/store services under its own policy. Meal Planner may receive transaction/entitlement references needed to validate an Apple purchase; we do not receive your Apple Account password. |
Cloudflare / cdnjs |
Font Awesome interface icons loaded by the website. | Your browser requests public style/font assets, exposing ordinary network information such as IP address and browser headers to the CDN. Account recipes and credentials are not included in those asset URLs. |
Providers may have independent legal obligations and their own stated retention. We require service providers handling information for us to apply protections consistent with this policy and applicable privacy requirements, and remain responsible for our own handling and oversight. We do not claim that using a named provider establishes a certification or guarantees Canadian-only storage.
Provider information: DreamHost privacy, Google API data terms, Anthropic retention, Postmark privacy, Buttondown privacy, Stripe privacy, Instacart privacy, Apple privacy, Cloudflare privacy.
Permissions, cookies and your choices
The iOS app stores its authentication token in device-only Keychain storage. Owner-scoped preference drafts use local app settings; private image caches and temporary scan files are separate from your server Recipe Book. Signing out or changing account/access clears private app state. Your original Photos or Files remain on your device. Local cleanup, server deletion, recipient emails and provider retention are different processes; device permission alone is not consent to send a file for AI processing.
- AI generation: your meal-planning preferences and notes are used for personalized AI processing, including by Google. Avoid medical histories or other sensitive details. Optional Anthropic upload analysis requires its separate explicit consent; declining an upload does not require you to upload the rest of your library.
- Camera and files: when available in the app, camera/scan permission captures a recipe you choose. A system photo or file picker selects individual documents instead of requiring access to your entire library. You can decline or revoke device permission in iOS Settings and continue using features that do not need it. The original file in your own Photos or Files remains yours.
- Website cookies and local settings support login sessions, security, language and requested interface choices. Hosting logs can include IP address, browser information, request time and referrer. Blocking essential cookies may prevent account features. Recognized campaign labels can be saved with your account; we do not retain arbitrary tracking query text as campaign data.
- We do not sell household profile information, place third-party ads inside subscriber plans or the Recipe Book, or use that content for cross-company advertising tracking. Newsletter delivery and measured opens/clicks are distinct from advertising tracking. We do not claim to collect no data.
- MCP/API connections and exports: a client you authorize can receive the information its permitted tools return. Keep tokens private and revoke an unwanted connection in your account. Your chosen assistant/provider can retain copies under its own policy; revocation stops future authorized access but cannot recall copies already exported. Public recipe catalogs do not expose private household plans or the saved library.
- Optional marketing consent can be withdrawn with the newsletter unsubscribe link without canceling Plus. For other optional processing, stop using the feature, revoke the relevant permission/connection, or contact the privacy address. If information is needed to provide a requested feature, withdrawing it can prevent that feature; it does not remove your statutory rights.
Google Gemini planning requires your explicit permission. You can allow or withdraw it in Account → Security. Withdrawal pauses new personalized AI planning and translation; it does not cancel Plus or remove subscription-authorized access to your existing plans and recipes. Photo/PDF imports require separate permission to send the selected file to Anthropic.
Mobile import recovery can retain non-content operation identifiers and processing states to recover a preview and prevent duplicate paid analysis. Erasing recipe drafts/results does not erase the opaque replay marker; account deletion removes that account’s markers. Saved recipe provenance may include an original-text transcription, file format/hash and provider request reference, not a retained scan archive.
Information and retention details
Meal-Planner.online is a subscription-funded dinner planning service. We do not sell household profile data or place third-party ads inside subscriber meal plans.
Information we collect
- Account details such as name, email address, login credentials, and subscription status.
- Household meal-planning preferences such as adults and children counts, avoid notes, cuisines, budget ranges, preferred stores, pantry notes, weekly tune-up notes, and delivery email addresses.
- Meal plan and grocery-list generation inputs and outputs.
- Payment identifiers from Stripe, such as customer and subscription IDs, but not full card details.
- Technical information needed to operate, secure, debug, and improve the site.
How we use information
- Create and manage accounts.
- Generate weekly dinner plans, recipes, and grocery lists.
- Deliver account emails, weekly meal plan emails, support replies, and subscribed newsletter messages.
- Process subscription status and billing access through Stripe.
- Maintain site security, troubleshoot errors, and prevent misuse.
Private Recipe Library
Active Plus includes a private Recipe Book with room for 200 recipes total, including generated Meal Planner favourites and reviewed imported copies where the photo/PDF pilot is enabled for your account. Generated favourites use the heart button on a recipe. The pilot may be limited to approved accounts; this policy does not promise general availability. It stores saved recipe text, source and capture details, and your edits. Existing saved content remains subject to the access and retention rules below. Manual entry, pasted recipes, external recipe-link fetching, bulk imports and Mealime account migration are unavailable.
Your library is private to your verified account and household members you explicitly invite. A household delivery address or shared meal-plan link alone does not grant Recipe Book access. Invitations are bound to the invited email, expire after seven days and require acceptance through that person’s verified account. Accepted members can read and cook from your saved recipes and private weekly plans while your Plus access is active. You retain control of favourites, imports, edits, export, deletion and billing. Membership is identified by the member’s account name and email; their own retained recipes are not shared back. Removing website access or the household recipient revokes shared access. Leaving a household also removes that member’s delivery email. We do not publish saved recipes in public search, guides or assistant recipe catalogs, or place third-party ads in the library. Generated recipes and AI transcriptions are not kitchen-verified; check ingredients and instructions before cooking.
While paid access is active, you can view and edit saved recipes and add eligible recipes within the shared 200-recipe limit. A cancellation scheduled for the end of a paid period keeps paid access until that period ends. After paid access ends, saved content is retained, but you cannot view, edit or add recipes. Resubscribing restores access to retained content. You can still sign in as the owner to export or delete retained content through the Recipe Book privacy controls after paid access ends.
Review drafts expire after 30 minutes. Account deletion removes your active account, saved recipes and drafts, family preferences, household delivery settings and sharing links, private plans and API/MCP connections. Deleting a subscriber account deletes its shared library and revokes household access. Deleting a member account removes that member’s data, invitations and membership; the subscriber’s recipes remain. Checked cleanup of delivery-host copies and the verified primary-email Meal Planner newsletter record is queued after account removal and normally attempted within 15 minutes. Failed cleanup remains queued for retry; newsletter ownership that cannot be verified requires a separate privacy review. Provider-held data follows each provider’s own retention policy. Contact support if you need confirmation that queued cleanup has completed.
Photo and PDF recipe-import pilot
When enabled for your active Plus account, the pilot accepts one JPEG, PNG or unencrypted PDF at a time, up to 5 MiB and 10 pages. You must confirm that you own the recipe or have permission to upload it and explicitly consent to sending the file to Anthropic for AI transcription. Crop out personal details first. We do not send your saved library or household profile with that request.
These limits help keep recipe imports reliable as the service grows:
- Up to 3 recipe uploads per day and 20 per month.
- Wait at least one minute between uploads.
- Failed or incomplete uploads do not count toward these limits.
- A complete preview counts after its temporary processing file has been removed. Saving the recipe is a separate step.
The allowances refresh automatically. A separate service-wide processing allowance can pause imports even when your account has uploads remaining. Releasing a failed member upload does not refund any provider processing cost. Historical allowance counters are retained because earlier failures cannot reliably be identified.
The result is an editable, unverified preview. Check the title, ingredients, instructions, servings and times against your original, correct errors, and explicitly review and confirm before saving. Dietary suitability and AI timing proposals remain unverified; proposed timing does not automatically replace source timing. Incomplete transcriptions can be corrected through your private preview. Nothing is added to your saved library before confirmation.
Original files are private temporary processing copies, not a Recipe Book archive. Normal processing deletes them when the request finishes. Interrupted uploads become eligible for scheduled cleanup once at least 10 minutes old; cleanup attempts run every 5 minutes. A processing or deletion failure may require a retry or support review. The Book retains the transcription, source evidence and capture details, and the recipe text you confirm until you delete the recipe or account. Previews expire after 30 minutes. Keep your original files and independent backups for comparison; we do not provide original-file recovery.
Anthropic normally deletes API inputs and outputs within 30 days, with exceptions for legal obligations, usage-policy enforcement or other applicable retention arrangements. We do not claim zero data retention. Deleting a recipe or account here does not immediately erase Anthropic’s separately retained request data. See Anthropic’s commercial data retention policy. Existing earlier pilot copies follow these access and deletion rules; this does not guarantee that every historical temporary copy has already been removed.
Account deletion and retained records
Canceling a subscription retains your content under the access rules above; deleting the account is a separate permanent action. Website Stripe billing is canceled before deletion completes. Apple-managed subscriptions must be canceled separately through Apple; deleting an app or account does not cancel an Apple subscription. Minimal billing and refund transaction records legally required for accounting may remain for six years from the end of the relevant tax year, or longer where a legal dispute requires it. Recipe content and discretionary support text are not retained as financial records.
App-managed database and upload backups expire within 30 days. Hosting-provider backups follow the host’s own retention. Deleted-account replay receipts contain only an opaque job ID, account ID and completion/expiry timestamps and expire within 30 days; they prevent a quarantined backup restore from reopening a deleted account. Previously delivered emails cannot be erased from recipients’ inboxes. Processor copies and legally required records are separate from active Recipe Book storage.
After account deletion, an unlinked hash of an Apple purchase chain remains to prevent that deleted purchase from being rebound to another account. The marker contains no account ID, account-binding token or recipe content. It is separate from the time-limited deletion receipts described above and is not used to restore your account.
Support requests
The support form stores your supplied name, reply email, topic, relevant plan week and message in a private, administrator-only queue, with a request reference and review/notification status. A supplied email is not proof of account ownership. Admin notifications sent to our support inbox include your supplied name, reply email, topic, relevant plan week and message, along with the reference and a protected review link. The Reply-To address uses your supplied email so support can respond directly. These email copies follow the mail provider’s and support inbox’s separate retention; deleting a request or account on the site does not recall email copies or replies. Do not submit passwords, tokens, private links, card details, medical history or original recipe files. Requests remain available while they are being handled; resolved requests become eligible for permanent removal after 30 days by scheduled daily cleanup. Account deletion removes associated signed-in requests and guest requests matching your verified primary account email. Provider email records and app/hosting backups follow their separate retention rules above.
To protect support intake from spam, we keep a bounded rate-limit history of keyed hashes of IP addresses and supplied email addresses, plus submission times. Raw IP and email addresses are not stored in that history. Limits use the preceding hour; accepted submissions remove older entries, and daily cleanup removes inactive history. Rejected requests do not create support tickets or send notification email. A temporary limit response returns the entered message to your browser for retry without saving an additional draft on the server.
Incoming support emails and our sent replies may also be copied from the support mailbox into the private WordPress ticket history. We use request references and email thread headers, together with sender or recipient matching, to link conversations. Unmatched messages and changed participants wait in an administrator-only review queue; unlinked copies expire after 30 days. We copy bounded message text and attachment names and sizes; attachment files remain in the mailbox. The sync uses read-only encrypted mailbox access, does not mark messages read or send automatic replies, and does not treat a supplied email address as verified account ownership. Deleting a ticket removes its synced conversation text; verified-primary account deletion also removes matching unmatched correspondence. Opaque replay keys and deletion cutoff timestamps remain for up to 31 days to prevent recent mailbox imports from restoring erased text. Original mailbox copies follow the separate email retention described above.
AI generation providers
We use Google GenAI APIs to help generate meal plans, recipes, grocery lists, and related images from the preferences and plan information you provide. Optional Anthropic recipe analysis is described above.
Service providers
We use service providers, including hosting, email, payment, and AI generation providers, only to operate Meal-Planner.online. These providers may process information for the service functions they provide. Examples include website hosting, email delivery, payment processing, and meal-plan generation.
Cross-border processing
Our service providers may process information outside your province, state, or country. Privacy protections and lawful access rules may differ in those places.
Payments
Payments are processed by Stripe. Meal-Planner.online stores Stripe customer and subscription identifiers needed to keep account access in sync. Meal-Planner.online does not store full card details.
Household and delivery emails
Only add delivery email addresses for people in your household who have agreed to receive the weekly meal plan. Marketing emails require separate opt-in and can be unsubscribed from without cancelling the subscription.
Children and households
Meal-Planner.online is intended for adults managing household meal planning. Do not create accounts for children or enter children’s names or other child-identifying details unless necessary for meal planning. Prefer household counts and age ranges over child names, and do not enter child diagnoses, medical details, school details, or unnecessary identifiers.
Sensitive information
Do not enter medical diagnoses, medication instructions, detailed health history, or other sensitive information that is not needed for dinner planning.
Meal-planning notes
Meal-Planner.online can respect allergy and avoid notes you enter, but you remain responsible for checking ingredient labels, substitutions, store products, and cross-contact risks.
Private links and access tokens
Private meal plan links and access tokens should be treated as shareable links. Anyone with a valid link or token may be able to view the associated plan until access changes.
Retention, access, correction, and deletion
You can ask us to access, correct, or delete personal information. Deletion may be limited by legal, tax, billing, security, backup, fraud-prevention, and operational obligations.
Your choices
You can update your dinner profile, household delivery emails, and account settings from your account pages. You can manage or cancel billing from Account > Billing or by contacting support. Newsletter emails include an unsubscribe option.
Privacy rights and contact
You can ask to access or correct personal information, obtain a copy or a portable format where applicable, withdraw consent for optional uses, request deletion, or raise a privacy complaint. We verify identity proportionately before disclosing or changing account data; a supplied email alone does not prove ownership. We respond within the time required by applicable law and explain any lawful refusal or retention exception. Recipe export is available to the verified owner through Recipe Book privacy controls, including after paid access ends; contact us for a broader account-data request.
We restrict administrative access and use safeguards appropriate to the information, including encrypted transport and private access controls. No system can guarantee absolute security. When a confidentiality incident creates notification obligations, we assess the incident, take protective measures, keep required records and notify affected individuals and the competent authorities as required. Our recipe suggestions are automated assistance, not decisions about legal rights, credit or medical treatment.
English and French versions are available. We date policy updates and notify users of material changes as required, obtaining new consent for a new purpose or disclosure when required. You can contact the Commission d’accès à l’information du Québec or another competent privacy authority if your concern remains unresolved.
Privacy Officer — StudioSphere Inc., Meal Planner serviceprivacy@meal-planner.online
Meal Planner Support and account assistance