How MorselMetrics handles personal information

Operator: Jonathan Morris, operating MorselMetrics in Australia.

Last updated: 5 October 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.

You may optionally choose an age-group nutrient reference. Pregnancy and breastfeeding references are covered below.

Optional nutrition preferences

You can choose to save a meal-planning goal, eating style, foods you prefer to avoid, the number of people you cook for, country/region and preferred units. 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.

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

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.

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. API data is not used for model training by default. 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.

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.

Optional meal suggestions

Household meal preferences are saved only when you choose Save meal preferences. They belong to the selected person and remain until you remove them or delete your account. 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 and database services. The current MorselMetrics Supabase project is hosted in Sydney, Australia. MorselMetrics also uses Vercel to host and deliver the web application. 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.

The private contact-form email delivery service is not yet enabled in this deployment.

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 only fixed action names, page categories, broad referral groups, device types, the site version and environment that served the page, and whether the browser was marked by staff as a test browser—not recipe text, email addresses, IP addresses, URL query strings or health profiles. 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.

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. 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.

If Australian privacy law 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.