Privacy Notice
How NutriScope handles account, client, health-related, booking, payment, message, file and AI-assisted review data.
Audience: Practitioners, clinics, clients and public booking visitors
NutriScope is a UK-first client tracking and review platform for nutrition professionals. The service handles personal data and can include health-related information, so privacy is part of the product design.
This notice explains the default position designed into the MVP. It should be reviewed by a solicitor, DPO or specialist reviewer before onboarding real practitioners and clients.
Who We Are
NutriScope provides software used by nutrition professionals and clinics to invite clients, assign trackers, collect check-ins, manage bookings, keep notes, exchange secure messages and review progress signals.
For privacy questions, use privacy@nutriscopeai.com. Before launch, confirm this mailbox, registered company details and any appointed data protection contact.
Controller And Processor Roles
Practitioners or clinics are generally expected to be controllers for the client records they decide to collect and use in their own client relationships.
NutriScope is generally expected to act as a processor for practitioner-controlled client records, and as a controller for its own account administration, product security, support, service analytics, billing administration and legal compliance data.
Information We Collect
| Area | Examples | Likely sensitivity |
|---|---|---|
| Account and profile | Name, email, authentication IDs, role, locale and account settings | Personal data |
| Client relationship | Assigned practitioner, clinic, invite state, portal access and consent records | Personal data |
| Health context | Symptoms, conditions, allergies, medications, supplements, biometrics, food logs and questionnaire answers | Special category data likely |
| Trackers and observations | Submitted check-ins, measured time, structured values, reflections and adherence trend inputs | Special category data likely |
| Notes, goals and messages | Private notes, shared action-plan notes, barriers, support needs and direct conversation content | Special category data likely |
| Files and photos | Uploads, meal photos and supporting documents | Special category data likely |
| Bookings and payments | Session times, booking status, reminder state, Stripe identifiers, amount and payment status | Personal data and financial metadata |
| AI-assisted review | Source context, prompts, generated drafts, confidence metadata and review history where enabled | Special category data likely |
| Security and audit | Actor, action, target, timestamps, technical logs and device or IP data where captured | Personal/security data |
How We Use Information
- To create and secure accounts.
- To support practitioner and client access to the correct workspace or portal.
- To let practitioners invite clients, assign trackers, review submitted check-ins and manage client records.
- To let clients complete check-ins, view selected trends, receive plans and message their practitioner.
- To manage bookings, questionnaires, reminders and service notifications.
- To process hosted Stripe checkout flows without collecting raw card details in NutriScope.
- To create practitioner-reviewed summaries, draft notes or possible pattern prompts only where the relevant feature and consent model allow it.
- To maintain security, troubleshoot issues, comply with legal obligations and improve the product in privacy-preserving ways.
Lawful Basis And Health Data
Where NutriScope acts as controller, likely Article 6 UK GDPR bases include contract, legal obligation, legitimate interests and consent where the product asks for it. Where practitioners or clinics act as controllers, they must identify and explain their own lawful basis for client records.
Because the product can process health-related information, an Article 9 UK GDPR condition is also needed for special category data. The MVP currently records explicit privacy, health-data and optional AI-processing consent where the sign-up or onboarding flow asks for it.
AI-Assisted Review
AI-assisted review is designed to support practitioners with draft summaries, possible pattern prompts and session-prep context. It must not replace professional judgement or produce autonomous client instructions.
- AI processing should be optional unless a later legal and product review approves another basis.
- Generated output should be labelled as draft or generated.
- Practitioners should review generated output before use.
- Source context should be minimised to what is needed for the requested review task.
- Clients should be able to understand whether AI-assisted processing may apply to their data.
Storage, Transfers And Residency
The production Supabase backend should be provisioned in the London region where available. Some providers, including payment, email, AI, support, monitoring or video providers, may process data in other locations using their own safeguards.
Your Rights
Depending on the data and the role NutriScope has for that processing, individuals may have rights to access, correct, erase, restrict, object to processing, request portability and withdraw consent where processing is based on consent.
Clients may need to contact their practitioner or clinic for requests about practitioner-controlled records. NutriScope will support appropriate requests through the controller or, where NutriScope is controller, handle them directly.
Individuals can also raise concerns with the UK Information Commissioner's Office.
Retention
Client records are expected to be retained for the period required by the practitioner or clinic controller, their professional obligations and the active service relationship. NutriScope account, audit, security and payment metadata may be retained for different periods where needed for security, legal, accounting or dispute purposes.