How MorselMetrics handles personal information
Operator: Jonathan Morris, operating MorselMetrics in Australia.
Last updated: 18 November 2026.
This policy explains what we collect, how we use it and the choices you have.
Subscriptions and payment information
If you subscribe, Stripe processes your payment and billing details through its hosted checkout and billing portal. MorselMetrics stores the provider identifiers, subscription status and paid-access dates needed to manage your subscription. We do not receive your full card number. We send Stripe your account identifier, email and subscription details; we do not send recipes, household nutrition profiles or personal food preferences for billing. Stripe processes information internationally, including in the United States and India, under its privacy policy.
Billing records may be retained where required for accounting, disputes or legal obligations, including after an account is deleted.
What MorselMetrics collects
You can browse published recipes without an account. The analyser shows whether a guest recipe trial is available or a free account is needed. Browser-local recipes and selected reference preferences can remain on the device where you saved them.
If you create an account, MorselMetrics may hold your email address, authentication/account identifiers, first or preferred name (requested at email signup), optional age, optional nutrient-reference sex selection, locale/unit preferences, account/plan status, saved recipes, custom nutrient targets and other settings you deliberately save to your account.
When you use the contact form, MorselMetrics collects the name, reply email address, enquiry category and message you submit. To limit spam, we keep short-lived message counts linked to a keyed, one-way digest of the network address supplied by our host, rather than storing the address in these counters. Counters older than two days are removed on the next admitted contact or traffic request. Hosting and backend providers may also process ordinary technical/security information such as IP address, browser/device information, timestamps and request logs.
When you send feedback while signed in, MorselMetrics keeps your message, the kind of feedback you chose, the page you sent it from (without its address parameters), the website version and the time, linked to your account so we can reply to your account email. Only if you tick “Include technical details” do we also keep your screen size, a general browser and system name, and up to five error messages from that page. Feedback is visible only to the operator and is deleted with your account. Feedback more than a year old is deleted the next time anyone sends feedback.
You may optionally choose an age-group nutrient reference. Pregnancy and breastfeeding references are covered below.
Date of birth
We ask for your date of birth when you create an account, or the next time you sign in if you already have one. We use it only to apply our age rules: you must be 16 to hold an account, and 18 to post, rate or share recipes. It is stored separately from your profile and from the optional age you may choose for nutrient references, is visible only to you and the operator, and is never shown publicly or used for advertising. It is kept until you delete your account. If an account turns out to belong to someone under 16, we lock it and offer a copy of its data. It unlocks automatically if they turn 16 within 12 months; otherwise we arrange its deletion within 12 months of locking it, after a final chance to export. If a date of birth was entered incorrectly, you can ask us to review it.
Community photos, ratings and shared recipes
If you take part in the community, MorselMetrics holds your public name, the photos you post and the details you choose with them (the recipe, and whether you made it as written), the recipes you share, your “Made it” taps and star ratings, the recipes you tell us you made (“I made this”, or “Made it” on the planner's card) and when, your trophies (including the private cooking trophies those recipes earn) and bonus autofills, any reports you make, and, if you turn one on, your cook page settings. Telling us you made a recipe counts you in its “Made it” total; it never records the meal as eaten, and you can undo it.
What is public: your photos, credited to your public name; shared recipes, credited to your public name; and, if you turn it on, your cook page with your photos, the covers you have won and your trophies (never your cooking trophies). A recipe's “Made it” count and star average are shown only once at least 3 people have taken part. What stays private: who recorded a “Made it”, which recipes you told us you made, and how any individual rated a recipe; we do not publicly identify any of these. Photos and shared recipes you choose to publish are visible with your public name. Nothing from your planner, household, health settings or food history is ever shown publicly.
Photos: when you upload a photo, we remove hidden data such as GPS location and camera details, make resized copies, and delete your original file. We keep a short fingerprint of each photo to flag near-duplicates. A photo held for review is kept privately until a decision is made. Withdrawn, rejected and removed photos are deleted from the site straight away and from backups within 30 days. Public photos and recipe information are included in the page data that search engines such as Google read, and search engines may keep their own copies for a time after removal.
Automated checks: before a photo appears, we send it to OpenAI's moderation service and an OpenAI image check to confirm it is safe and shows food. Before a shared recipe appears, we send its title, short description, servings, ingredients and method to OpenAI. Reported photos and recipes may also be checked this way. Automated checks assess potential safety concerns, health claims and signs of copied material; they cannot establish that content is safe, accurate or original, and they never set nutrition values. A submission may be published, rejected with a reason, or held for a person to review, and you can ask us to reconsider any decision through the contact form. We remind you of this, and that processing may occur overseas, when you upload a photo or share a recipe. OpenAI processing is described in the AI section below.
Invites: if you sign up through someone's invite link, we record who invited you, so that both of you can receive the invite reward, and to prevent abuse. Neither of you can see the other's account details through this.
Moderation records: we retain a limited record of moderation decisions for up to 2 years, unless a longer period is reasonably required by law or an ongoing dispute, to handle complaints and meet online safety obligations. The record holds what was checked or reported (by its identifier, not a copy of the photo), the decision, the reason and when. If you report something, your identity is not shown to the person who posted it.
Cook-offs: if you enter a cook-off and win, your photo and public name may be featured on MorselMetrics social media accounts.
Optional nutrition preferences
You can choose to save a meal-planning goal, eating style, foods you dislike, the number of people you cook for and country/region. Foods you dislike are used only to leave matching recipes and flavour finishes out of suggestions in your account. The nutrition-preference fields have a separate, optional consent choice. They are stored in your private account profile with the consent version and time, and can be edited or cleared from Account. They are not included in traffic analytics or copied to anonymous browser storage.
The initial account preferences provide a record you can review. Separate meal-planning preferences in Household can explicitly save dietary choices, ingredient exclusions and dated personal nutrient targets. Those settings filter and score meal suggestions; they do not establish medical needs or certify allergy safety. The introductory foods-avoided text is not automatically converted into exclusions. Skipping setup does not save the optional answers you entered.
Pregnancy, breastfeeding and sensitive information
A pregnancy or breastfeeding reference reveals health information. We use it to choose the corresponding nutrient comparisons. It is optional: you can choose another reference or skip setup. Saving one during welcome setup or in planner reference settings requires a separate consent checkbox; we record the consent version and time. Household life-stage settings also ask for permission to save the reference.
To stop using a saved reference, change or clear it in planner settings and, if separately saved there, Household. Clear suggestion history to remove earlier suggestion snapshots. You can contact us to withdraw consent or request removal of remaining health information. A consent record may remain to document the permission given; account deletion removes the account-linked record. Browser-local selections are cleared on that device.
Other preferences or recipe text may also reveal sensitive information. Only provide information you want the service to use, and only manage another person’s information with their permission. We do not ask for diagnoses, medications or clinical notes.
AI recipe reading
You choose and upload your own Cronometer export files; we do not ask for your Cronometer password, access your account or scrape it. Files are initially read in your browser. If you choose AI column help, we send OpenAI only the displayed sample: up to eight rows, with long cells shortened. This may include food names, dates and nutrient values. We do not send the filename, the rest of the export or your account profile. AI proposes column positions only; you review them before the full file is checked locally. If you tick “Use AI to match these foods” for an import, we send OpenAI the distinct food names and amounts from the meals you selected (up to the 100 most-logged foods), with candidate foods from our database; we do not send dates, meal names, other columns, the filename or your account profile. AI suggests matching foods and estimates weights, and you review the matches before saving. Each such import uses one of your monthly AI readings. Confirmed imports and their original source evidence are saved to your private recipe library, not our shared food database or public recipe catalogue. AI column help requests and their cost records are separate from recipe-reading and autofill allowances.
When AI helps interpret a recipe, we send the relevant recipe text, preparation wording and food-matching context to OpenAI. This can include personal information you put in the text. We do not include your saved household health references or payment details in these requests. AI helps interpret ingredients; our food data and calculations supply nutrient values.
When you ask Use what I have to write a recipe, we send OpenAI the ingredients you typed, the pantry staples you have marked and how many extra items you are happy to buy. We do not send your account profile or household details. Our food data and calculations supply the recipe’s nutrient values.
When you ask Make another version to rewrite a recipe, we send OpenAI that recipe’s title, servings, ingredients and method, and the change you chose (for “without”, the ingredient you typed). For a MorselMetrics recipe that is our own text. For a recipe of your own it is the text you saved, sent only when you ask for a version, and the page says so first. We do not send your account profile or household details. Our food data and calculations supply the version’s nutrient values, and our own ingredient reviews decide what is said about it.
When you describe a meal in the planner, our own code splits your sentence into ingredient lines in your browser, and nothing is sent at that point. When you then ask us to read those lines, they are handled exactly like a pasted recipe: if AI helps interpret them, we send the lines to OpenAI, and they can include personal information you put in them. We do not send your account profile, your household details or the rest of your plan.
When you type what you want into Autofill, our own code reads the sentence in your browser and fills in the form. If it cannot read part of the sentence, we send OpenAI the words you typed and nothing else: not your plan, your household details, your nutrient references or your account profile. If what you type mentions health, we do not send it, and ask you for an ingredient or nutrient goal instead.
OpenAI may process this information in the United States. We request that responses are not stored as retrievable application records. This is not zero retention: under OpenAI’s standard API policy, abuse-monitoring logs may retain content for up to 30 days, or longer where legally required. OpenAI does not use API data to train its models unless the customer opts in, and MorselMetrics has not opted in. See OpenAI’s API data controls.
Why the information is used
MorselMetrics uses personal information to create and secure accounts, provide requested product functions, save and sync recipes/settings, select relevant nutrient-reference comparisons, provide support, maintain service security, administer account status, respond to privacy requests and meet applicable legal obligations.
MorselMetrics does not collect extra medical information merely because it might be useful one day.
No selling, no advertising, no AI training
We do not sell your personal information, and we do not share it with anyone for advertising. MorselMetrics does not show ads and does not load advertising or social-media tracking.
We do not use anything you enter or save in MorselMetrics, such as recipes, plans, household details, food history, preferences or feedback, to train AI models, and we do not give it to anyone else for that purpose. Our AI requests are made only to provide the feature you asked for.
Household profiles and meal portions
If you add household members, MorselMetrics stores their nicknames, optional ages and nutrient-reference sex selections, archive status and the meal portions you assign to them. These records are private to your account and stored in Supabase. Members have no separate login. Use nicknames and only add information you are authorised to manage. Household details and portions are not included in traffic analytics or copied to anonymous browser storage.
Your “Me” member uses your existing account profile settings. Archiving a member keeps their previous portions available; deleting your account also deletes its household members and allocations. Nutrient comparisons for past dates use each person’s current reference settings.
Private food history
Previewing history sends your selected CSV files to our server for validation. Only an import you confirm is saved. Dated food entries, supplied nutrient values, original source evidence and import receipts belong to your account and do not populate our shared food database. This history flow does not send your records to an AI provider. The separate optional AI column helper is described above.
Undo changes the active history and can restore an earlier source version. Original import evidence and receipts remain for correction and recovery until account deletion. Reuse previews retain the selected records, reviewed recipes and relevant plan and household snapshots. Accepted plans and saved recipes are separate; undoing a history import keeps them. Deleting your account removes account-linked history, imports and previews.
Optional meal suggestions
Household meal preferences are saved only when you choose Save meal preferences in Household, or Save as my defaults while planning suggestions. They belong to the selected person and remain until you remove them or delete your account. Kitchen defaults — equipment you don’t have, preparation time, how often a recipe can repeat and each person’s largest portion — are saved to your account profile only when you choose Save kitchen defaults or Save as my kitchen defaults. Personal targets record a nutrient, amount or percentage, starting reference when applicable, and date range. They are separate from published nutrient references. You can clear the fields and save to remove the stored preferences. Prior suggestion snapshots can still contain earlier choices until you clear suggestion history.
When you browse recipes from a meal draft, this browser tab temporarily keeps the date, meal slot, portion quantities and any draft recipe so you can return. The return context expires after two hours, is tied to the signed-in account, and is removed when that meal is saved. Closing the tab clears its session storage.
When you request meal suggestions, you choose diet, ingredient exclusions and portions for up to two adults. Suggestions use the references already selected by your saved household settings. Requesting or accepting suggestions does not save or change household references. The person managing the account can manage references for everyone in that household; only enter information you are authorised to manage. These choices may reveal sensitive information; they are used only to calculate, review and reproduce your private meal suggestions, not for advertising or traffic analytics. They are not sent to a language model.
Saved previews include these settings, calculated food contributions, the selected dates and a snapshot of the existing plan and household. Up to 100 recent previews are kept per account. Records older than 30 days are removed the next time you generate suggestions; inactive accounts retain them until you clear suggestion history or delete the account. Use “Clear suggestion history” in Account or Suggest meals to remove them sooner, including undo history. Accepted meals remain in your planner until you remove them. References deliberately saved in Household are separate from suggestion history and can be reset there; deleting the account removes these records.
Shopping lists
Saved shopping lists contain the selected dates, ingredient quantities, source recipe references, added groceries, pantry choices and checkmarks. They are private to your account and stored in Supabase. Shopping contents are not included in traffic analytics, and private lists are not copied to anonymous browser storage.
Usage allowances
Autofill and AI recipe reading have separate usage records. These include your account identifier, the allowance period, request identifiers or content fingerprints, and when a use was reserved or completed. They help show remaining uses and avoid charging twice for retries. Manual planning, ordinary recipe edits and shopping lists do not share an autofill allowance. Service records may also include provider request identifiers, token counts, cost estimates and errors; they are not used for advertising.
Where information is stored and processed
MorselMetrics uses Supabase for account authentication, database and photo storage services. The current MorselMetrics Supabase project is hosted in Sydney, Australia. MorselMetrics also uses Vercel to host and deliver the web application. We keep private backup copies of community photos and community records in a Vercel Blob store configured in Sydney; copies are retained for up to 30 days under our backup and deletion schedule, and a restored backup never republishes content that was deleted. Vercel may also process operational data internationally. When enabled, Google sign-in supplies account identity information such as your email and name, and Cloudflare Turnstile processes technical signals to help prevent automated abuse.
When you submit the contact form, we use Resend to deliver your message. Resend processes information in the United States.
When you send feedback, we use Resend to email it to the operator, with your account email as the reply address. Resend processes information in the United States.
Plan emails: these are off unless you turn them on (after Autofill fills a week, or in Account → Planning). If you do, we use Resend to email your account address the meals in your planner for the coming seven days: the morning after you turn them on, then each Sunday morning. An email contains your preferred name if you gave one, dates, meal names and links back to MorselMetrics, and is sent as plain text with no images or tracking pixels. Resend processes information in the United States. We keep when you turned them on or off and when one was last sent, and delete this with your account. Every email has a link that turns them off at once, and you can switch them off in Account → Planning.
Our hosting and authentication providers operate internationally. Vercel may process information in the United States and through its global network. Cloudflare describes processing in the United States, European Economic Area and other locations. When you use Google sign-in, Google operates servers globally, including in the United States. These providers’ linked policies describe their international processing; an Australian database location does not mean every log, support record or service request stays in Australia.
Security
MorselMetrics uses authentication, access controls and database row-level security to separate private account data. Privileged credentials are kept server-side and are not intended to be exposed through browser variables. MorselMetrics aims to collect only information reasonably needed for current features and to avoid retaining information that is no longer needed.
No online service can guarantee absolute security. If MorselMetrics becomes aware of a data breach, it will assess and respond to the incident and meet any notification obligations that apply.
Local storage and cookies
MorselMetrics uses browser local storage for anonymous/local recipe saving and selected preferences. When you leave an anonymous recipe to sign up, a temporary draft may be kept in this tab’s session storage for up to two hours so you can return to it; it is not automatically uploaded. Supabase authentication may use browser storage/session mechanisms needed to keep you signed in. MorselMetrics uses first-party usage analytics to understand page visits and whether features work. A random browser identifier expires after 30 days; a visit identifier is kept in session storage. Events contain fixed action names, page categories, broad referral groups, device types, the site version and environment, and a staff test mark. We also record bounded event times, whether the browser reports automation, and a single observation after at least 20 seconds in the foreground with an interaction. We do not record what you type, click targets, recipe text, email addresses, full user-agent strings, URL query strings or health profiles. On our hosting platform, the server converts the connection IP into a secret-protected identifier that changes daily; raw IP addresses are not stored in these analytics. A broad browser family and country may also be recorded. Daily network identifiers and country are removed after 30 days on the next collection run. A shared network is not treated as proof of automation. Recognised staff activity is excluded from public figures. Detailed events are removed after 180 days on the next collection run. Authorised staff can view aggregate reports, and the owner can review individual visits as anonymous sequences of page categories and actions, only to separate testing and automated traffic from real use; confirmed signup counts come from account confirmation timestamps. Total account figures include current registered accounts, with confirmed and unconfirmed accounts shown separately. Do Not Track and Global Privacy Control signals disable browser event collection. You can also exclude this browser below.
MorselMetrics also uses Vercel Web Analytics, provided by our hosting platform, to count page views. It does not set cookies or keep an identifier in your browser; Vercel tells visits apart with a hash created from each request and discards it after 24 hours. A page view records the page address without query strings or fragments, the referring page, approximate location, operating system, browser and device type, and is used for aggregate statistics only. Browser exclusion, Do Not Track, Global Privacy Control and staff test marks stop these page views being sent.
For new email signups, MorselMetrics may record a broad device type (desktop, mobile or tablet) to understand which signup experience people use. The device type is kept privately with the account until account deletion; authorised staff see only aggregate counts. It is captured at account creation and is not changed by later sign-ins or confirmation on another device. No raw user agent, IP address or browser identifier is added to this record. Older accounts, Google signups and unavailable device information are reported as unknown. Browser exclusion, Do Not Track and Global Privacy Control disable this optional signup-device collection; they do not remove the account from operational account totals.
Access, correction and profile controls
Signed-in users can review and update ordinary profile information from the Account page. For access or correction requests that cannot be completed there, use the contact form and choose the privacy category.
Account deletion
The Account page includes a deliberate account-deletion flow. When deletion is configured and confirmed, MorselMetrics deletes the authentication account and deletes or de-identifies user-linked cloud records according to the current database relationships. This includes your photos, shared recipes, ratings, “Made it” taps, the recipes you told us you made, trophies and community profile; backup copies of your photos are removed within 30 days. The one exception is a shared recipe you agreed to have added to the official cookbook, which stays there credited to “a community cook”. Browser-local recipes are separate and remain on that device unless you clear them there.
Where information is no longer required, MorselMetrics will delete or de-identify it where appropriate, subject to genuine legal, security, fraud-prevention, accounting or dispute-resolution retention needs. Technical backups or provider logs may persist for a limited period according to provider processes, so MorselMetrics does not promise instantaneous erasure from every backup copy.
Privacy enquiries and complaints
Jonathan Morris operates MorselMetrics. You can make a privacy enquiry, access/correction request or complaint through the MorselMetrics contact form without the operator's private email address being displayed publicly. MorselMetrics will review the issue and respond within a reasonable period.
MorselMetrics aims to handle personal information consistently with the Australian Privacy Principles in the Privacy Act 1988 (Cth). If the Act applies to the issue and you are not satisfied with the response, you may also have rights to raise the matter with the Office of the Australian Information Commissioner.
Changes to this policy
MorselMetrics will update this policy when material data practices, providers or product features change. The “Last updated” date above shows the current version.