dietex · Your nutrition care, connected

Privacy notice

How dietex uses information to connect patients and dietitians.

Information we use

dietex processes dietitian account names and email addresses; patient names and phone numbers; age, gender, height, weight, goals, allergies, food preferences, activity levels and medical conditions; meal plans and notes; and meal, water and weight logs. Authentication identifiers and technical request information support sign-in, security and service operation.

Why we use it

We use this information to manage accounts, connect patients with their dietitian, prepare and share meal plans, record progress, provide requested AI features, protect the service and respond to support requests. Dietitians can access the patient records in their own workspace. Patients can access the records linked to their own account.

Service providers and AI

• Supabase provides authentication, database storage and backend functions.
• Vercel hosts the website and receives technical information needed to deliver it.
• Anthropic processes relevant nutrition and health information when a dietitian allows AI sharing and requests an AI feature. This can include first name, age, gender, weight history, goals, allergies, preferences, conditions, adherence, hydration and free-text instructions. When a dietitian asks AI to suggest an answer to a patient's question, the question text, its topic, the meal or plan day it is about and the dietitian's own saved answers are also sent; photos and files attached to questions are never sent to AI. Do not put unnecessary identifying details into instructions. AI output is a draft and requires professional review, and a suggested answer is only sent to the patient if the dietitian sends it.

These providers may process information outside your country. Their applicable service terms, security controls and retention practices also govern their processing. dietex does not include advertising or cross-app tracking SDKs and does not sell patient information.

Notifications and reminders

For phone notifications, dietex uses Google Firebase Cloud Messaging and, on iPhone, Apple Push Notification service to deliver them. Firebase also processes device, operating-system, app-version and SDK diagnostic information to operate the service and measure its reliability and adoption. Its SDK privacy manifests describe these diagnostics and service analytics as not linked to your identity; they are not used for advertising or tracking. Firebase processes app-installation identifiers and push tokens; Supabase stores the push token linked to your account, phone platform, app build, language, time zone and notification preferences. Notification payloads include sender names, a child’s name where relevant, event types, appointment times and record identifiers used to open the right screen. Message and question previews are off by default. If you turn previews on, their text is also sent through Google and Apple and may appear on your lock screen. Notifications are not end-to-end encrypted. You can change categories, previews and quiet hours in Profile → Settings → Notifications, or disable notifications in your phone settings. Signing out removes this phone’s push registration from dietex. Account deletion removes its notification settings and registrations. Optional meal, water and weigh-in reminders run locally on your phone; their settings are saved to your account, but each reminder is not sent through a push provider.

Your choices

AI is optional. Dietitians are asked for permission before remote AI processing and can withdraw permission in Account, privacy & support. Withdrawing permission stops future requests; it cannot undo processing already performed. A dietitian must have the appropriate permission to enter or share patient information.

Retention and deletion

Account and care records remain available while the account and workspace are active. In-app account deletion removes the account and associated records from the active dietex database. Patient deletion removes the patient profile, assigned plans and progress logs; dietitian deletion removes the entire workspace and linked patient app accounts. Shared food-library entries are not personal account records and remain available.

Data already held separately by your dietitian is outside dietex. Providers may retain backups and security records under their own retention schedules. Failed account cleanup may temporarily retain account identifiers so deletion can be completed. Contact support to ask about access, correction, deletion or provider retention that applies to your records.

Request account deletion

Security and local storage

dietex uses HTTPS for service traffic and authenticated database access rules. Sign-in sessions are stored on your device so you can return to your account. Sign out before sharing a device. No system can guarantee absolute security. Contact support if you suspect unauthorized access, and never send passwords or access codes by email.

Children and clinical care

dietex is a nutrition-care tool for use with a dietitian. For a child, a parent or legal guardian uses dietex on their own phone: the dietitian sends the invitation to the parent, and when joining the parent agrees to share the child's information with the dietitian. AI help with a child's information stays off unless the parent allows it, and the parent can change this in Profile at any time. A teenager uses dietex on their own phone only after the dietitian confirms that a parent has agreed. Where a patient cannot consent independently, the dietitian must obtain appropriate parent or guardian permission. dietex is not an emergency service and does not provide autonomous diagnosis or treatment.

Contact and changes

For privacy questions, write to support@weuxui.com. Tell us the type of request without sending medical records or passwords. We may need to verify identity before providing account information or completing a request. This notice will be updated when the service’s data practices change.

Shared media, location and appointments

You may choose to send photos, videos, files and voice notes in chat. dietex stores these in private Supabase Storage for the current conversation participants. Microphone permission is requested only when you start recording. Location permission is requested only when you choose to use your current location: to share it once in a conversation, for a dietitian to pin their clinic, or, on iPhone, for a patient to see the drive time to an in-person appointment. Manual coordinates are also available for sharing and pinning. Location sharing is a single point, not continuous tracking. Appointments store a title, place, time and response status. Opening a shared location in Maps sends its coordinates to the selected maps provider after confirmation.

Chat media is not automatically sent to AI providers. Deleted chat files are queued for removal through the Storage service; cleanup is retried if unavailable. Unsent uploads expire after 24 hours. Media may be cached temporarily on the device for playback. Files you explicitly open or download can remain in your downloads or another app until you remove them.

Signing in with your mobile number

Patients sign in with the mobile number their dietitian saved. To confirm the phone is theirs, dietex sends a one-time code by SMS through Supabase and its SMS provider Twilio, which receive the number and the code only to deliver the message. The number links the patient to the records their dietitians saved with it. Invite codes remain available instead.

Profile photo

You can add a profile photo. dietex crops it on your device and stores it privately in Supabase Storage. It is shown only to you and to the people you work with in dietex: your dietitian, or a dietitian's patients. It is not sent to AI providers. Removing or replacing it, or deleting your account, queues the old photo for deletion. A parent managing a child's record cannot add a photo of the child.

Booking and calendars

A dietitian can set working hours and a clinic location so patients book free times. A dietitian can also connect Google Calendar, Outlook or the calendars on their iPhone so patients only see times the dietitian is free. dietex uses busy and free times only: it does not read event titles, places, notes or attendees from Google Calendar, and does not store them from Outlook or the iPhone. Access to Google and Microsoft is stored encrypted and can be removed at any time by disconnecting the calendar in dietex or in the Google or Microsoft account. When the dietitian chooses, confirmed appointments (title, time, place and the patient's name) are added to a separate "Diety" calendar in their Google or Outlook account and removed when cancelled. Patients never see why a time is unavailable.

dietex's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. dietex uses Google Calendar data only to show a dietitian's free times to their patients and to add dietex appointments to the dietitian's "Diety" calendar. It does not use this data for advertising, does not sell or share it, and does not use it to develop or train AI models.

Add to calendar opens the device's own calendar screen; dietex does not read the patient's calendar. On iPhone, a patient who allows location access sees the drive time to an in-person appointment on the lock screen. To work it out, the iPhone sends the patient's current location and the clinic location to Apple Maps for a route; Apple's terms and privacy policy apply. dietex's servers do not receive or store the location used for this drive-time lookup. A location you share in a conversation and a dietitian's clinic pin are stored as described above.

Private messaging

dietex stores messages, sender identifiers, timestamps and read status in Supabase so a patient and their assigned dietitian can communicate. Messages are protected by authenticated access rules; this is not end-to-end encrypted messaging. Chat messages are not sent to AI providers, except the text of a question when the dietitian asks AI to suggest an answer. You can block messages or report a received message. Reporting makes the selected message and conversation details available to dietex support for review. Chat history, block settings and related reports are removed from the active database when the patient record or owning workspace is deleted. Resetting patient access preserves the conversation for the same patient on their new device. Messages are not an emergency service.

Questions to your dietitian

A patient can send their dietitian a question with a topic, the meal or plan day it is about, and up to four photos and two files. Questions, answers and their files are stored like chat messages and attachments, for the patient and their assigned dietitian only, and are removed the same way. A dietitian can keep saved answers to reuse; only that dietitian can see them, and they are deleted with the dietitian's account. Questions are not for emergencies.

Online appointments

A dietitian who offers online appointments saves their own meeting link (for example Zoom, Google Meet, Teams or WhatsApp). The link is shared with a patient only after an online appointment is booked, and is added to calendar entries for it. The call itself happens in that service under its own terms; dietex does not record or join calls.