Support privacy

This family pilot stores nicknames, shared meal/appointment schedules, device links and reminder responses in NutriForMe’s Supabase support service. It does not access the app’s encrypted health backup. Support AI is off by default and requires the separate permission described below.

The client owns their support plan using their NutriForMe account. Each carer uses their own account and requests access; the client approves viewing, editing and response access separately. Clients can link multiple carers, and carers can link multiple clients. Clients may revoke each link. Permission changes and plan edits record the acting account. A companion can read only its client's plan and submit responses, never edit schedules. Legal representative verification is not enabled.

Plans remain until deleted using Access. Deleting a plan removes its links and response records from the active database. Infrastructure backups may retain deleted records according to the hosting backup lifecycle. Signing out does not delete a plan.

Device credentials and the synced cache are encrypted using operating-system facilities on supported Mac/Windows installations. Anyone with access to the unlocked device can see its displayed schedule. Offline access expires after 24 hours without successful sync; revocation takes effect on the next connection. Participants can disconnect locally at any time.

Responses are self-reported. Help requests appear in the portal, not as an emergency alert. Keep existing support arrangements. No NDIS funding approval is claimed.

AI for support clients and carers

Disability and aged-care support clients can separately approve AI help for themselves and each named, approved carer. They choose shared meal plans, shared food preferences and dates. Existing support access alone does not enable AI. Requests use the client’s existing Support allowance of 60 questions per month, shared with their own app use; carers receive no additional allowance. Carers must complete account verification before using AI.

Only selected support meal planning and food preference information is used. Private health records, the encrypted backup, medication context, appointment notes and reminder responses are excluded. AI may explain food planning or prepare an ordinary meal draft for review. It cannot establish what was eaten, nutritional adequacy or clinical suitability, and it does not apply a plan or change a goal automatically. Turning permission off stops new requests and withholds in-progress results after the permission check; it cannot recall information already sent for processing or remove a result already shown.

Coaching sharing

Coaching uses separate client-approved links. Clients choose categories and dates for sharing meals, plans, exercise, weight, sleep, goals, messages and celebrations. Selecting a website role does not grant access. Coaching does not read the app’s encrypted health backup. Shared plans are separate from reported eating and completed exercise.

When sharing expires, access closes immediately. The retention policy removes inaccessible shared records, messages and pending proposals from the active sharing store 30 days after expiry. Automated cleanup is not yet active in this beta. Ending or blocking a connection removes its shared projections and messages immediately. Clients keep their own app records and accepted plans. Narrowing sharing can clear shared conversations and pending proposals; previously deleted content cannot be restored by expanding sharing again. Infrastructure backups follow the hosting backup lifecycle described above.

Coaching AI, when enabled, requires a separate client choice for the named coach, categories and dates. Requests use the client’s existing Premium AI allowance included with Coaching. Explanations use a limited selection of approved values; generic meal drafts do not need client records. Turning AI sharing off stops new requests and withholds results from requests still in progress when permission is checked again. It cannot recall a request already sent for processing or remove a result already shown. Drafts require review and do not change records or goals automatically.

Clients and coaches may report concerns or block a connection. Reports are retained for service review; submitting one does not promise a response time. Notification preferences are optional and start off. Push delivery is not active in this beta.

Your own meal library

The app syncs food-only snapshots of your saved meals to your own account so you can select them in your coach workspace. These snapshots include meal and food names, saved quantities and reported nutrition, with missing or incomplete values identified. They are separate from the encrypted health backup. Other accounts cannot read your library. Selecting a meal creates a separate draft; it does not share your entire library or change the original meal.

AI meal drafts and optional images for your reusable coach meals use your own account’s existing allowances. Image generation receives the saved meal name and ingredients, not client records. Images are illustrative and are stored in the same public image service as app recipe images: anyone with an image link can view it. Do not include personal or client details in a generic meal name or ingredients.

NutriForMe privacy policy and contact