Bir az əminlik. Həyat sizi hara aparırsa aparsın.Tibbi məlumat kartlarına Birləşmiş Kralıq daxilində pulsuz çatdırılma

Policies & information

Safeguarding policy

Safer sharing, profile controls and how to raise a safeguarding concern.

Safeguarding policy

Version 2.4 · Published 17 November 2026

Organisation and policy owner: MyMedicalSupport UK Ltd, operating Tapiie.
Effective date: 17 November 2026.
Next scheduled review: 17 November 2027, or sooner after an incident, relevant legal change or material product change.
Publication approval: authorised by Scott on 17 November 2026.

Who provides your products and medical platform

Nexcura Ltd sells Tapiie products and is responsible for product orders, payment for those orders, delivery, returns and sales enquiries. MyMedicalSupport UK Ltd operates the medical-profile platform and is the controller responsible for medical-profile information, profile sharing, platform administration and requests concerning that information.

Buying a product does not give Nexcura Ltd access to your private medical profile or uploaded medical files. Access provided to medical-platform administrators is authorised by MyMedicalSupport UK Ltd, not by Nexcura Ltd in its role as product seller.

Purpose and scope

This policy sets the safeguarding requirements for MyMedicalSupport UK Ltd’s operation of Tapiie. It covers children and adults at risk, parent-managed and other representative-managed profiles, information disclosed through products and shared links, About Me and Support, uploaded files, customer support, staff conduct and partner demonstrations. It applies to directors, staff and contractors acting for MyMedicalSupport UK Ltd. Partners must follow the safeguarding responsibilities applicable to their own activities and agreements.

We aim to prevent abuse and inappropriate disclosure, recognise concerns, respond proportionately and involve the appropriate safeguarding authorities. Safeguarding includes physical, sexual, psychological and financial abuse, neglect, exploitation, domestic abuse, coercive control, discriminatory abuse and misuse of personal information. Staff must consider digital risks, including a person being identified as vulnerable through a profile or being controlled through account access.

Tapiie provides access to information entered by users or authorised representatives. It is not an emergency-response service, a safeguarding authority or a substitute for professional assessment, medical advice or emergency care.

Report a concern or immediate danger

If someone is in immediate danger in the UK, call 999. Outside the UK, contact the appropriate local emergency service. Do not wait for an email reply, proof of abuse or internal permission before taking necessary emergency action.

Report a safeguarding concern to info@wearmeditech.com. Scott Mardon and Jessica Mardon monitor this inbox Monday–Friday, 9am–5pm, London time (GMT/BST). There is no absence cover, and these hours are not a guaranteed response time or continuous emergency cover. For an urgent concern when a safe internal response is unavailable, contact the relevant local safeguarding service or police directly.

Responsibilities and safeguarding contacts

Both have accepted their roles. Jessica leads safeguarding decisions and referrals; Scott provides deputy support. Jessica and Scott monitor the reporting inbox. MyMedicalSupport UK Ltd’s management is responsible for resources, oversight, appropriate training and implementation of this policy. The safeguarding lead must arrange safe handover and cover for absence, identify any limits on availability, and maintain current official referral contacts. Inbox receipt alone is not a completed safeguarding response.

The person responsible for technical operations must contain inappropriate-access risks and preserve necessary evidence. The person responsible for data protection must assess information-sharing and breach duties. Every staff member and contractor must report concerns promptly and follow the directions appropriate to their role.

If a concern involves Scott or access to his email, contact Jessica directly. If it involves Jessica, contact Scott directly or the appropriate external authority. If both are implicated, internal reporting is unsafe, or a concern is not being addressed, contact the relevant safeguarding authority or police. Do not copy an alleged abuser into a report.

Principles and people covered

A child is anyone under 18 for this policy. The legal criteria for adult safeguarding differ across the UK; staff must apply the relevant national and local framework. Scotland’s adult protection framework can apply from age 16 where its statutory criteria are met, alongside relevant child-protection arrangements. A disability, autism or a medical diagnosis does not by itself establish that a person lacks capacity.

Our decisions must respect safety, dignity, autonomy and the person’s wishes. We support accessible communication, consider children’s views according to their understanding, minimise information shared and avoid assumptions about a person’s abilities. Staff must consider whether contacting an account manager, family member or alleged representative could increase risk.

Tapiie sharing controls and their limits

A person who can tap or scan a product, or obtain its sharing link, may be a member of the public. A scan or an access code does not verify professional identity. Encryption, a time-limited view or search-engine exclusions do not prevent someone copying information they can see.

The Emergency View Organiser allows an authenticated profile owner to control whether age and city appear in ordinary scan views, exclude supported sections and arrange their order. Supported sections cover uploaded documents, medical conditions, allergies, About Me and Support, emergency contacts, personal information and medical history. Name and urgent alerts remain visible.

Age and city choices apply to ordinary scan views. They may still appear in code-authorised views, subject to other applicable restrictions. Excluded sections remain out of scan-page rendering after a code is entered, including separate history responses. These display choices do not delete stored information or universally revoke separate authorised account, file or API permissions.

Existing profiles retain their earlier sharing choices until reviewed. Organiser-aware profile creation routes can start with city hidden and age awaiting a choice; these initial settings are not applied automatically by every registration route. Supported sections start selected, subject to existing access controls. There is no automatic child-specific mode that makes every child’s profile private. Account managers should review the saved ordinary scan preview after changing settings.

About Me and Support entries default to private, with choices to share a summary or fuller content. A summary can still identify someone. Free text, photographs and documents may reveal identity, school, location, routines or vulnerability even when a structured field is hidden. Review them before sharing. Screenshots and information already copied cannot be recalled.

Requirements for children and public disclosure

Before enabling or extending disclosure for a child, staff and the account manager must consider the ordinary audience, the child’s understanding and wishes, the emergency benefit and foreseeable misuse. Share only details necessary for the intended purpose. Age can provide context to a responder, but profile information is not a verified clinical record or a medication-dosing instruction.

Where the Children’s Code applies, high-privacy defaults are required unless a compelling reason for a different default is documented in the child’s best interests. Offering a parent optional switches does not alone satisfy that requirement. Parent-managed accounts are not an automatic exemption. The safeguarding and privacy leads must assess names, photographs, ages, locations, alerts and combinations of details, including existing profiles.

MyMedicalSupport UK Ltd must document the necessary assessments, implement proportionate safeguards and review any gaps in already-live processing promptly. A child-focused campaign or relevant product change must not proceed where a required assessment or safeguard is missing. These are organisational requirements; they are not a claim that all authority checks or child-specific defaults are automated. Risk acceptance cannot waive a legal duty.

Parent and representative managed accounts

Establishing authority

In Tapiie’s product-linked web registration flow, users must select the age-or-legal-authority declaration and accept the Terms and Privacy & Data Use information. The server checks both selections and a valid registration form. A successful new registration saves a declaration record linked to the account and its initial medical profile, including the server-recorded acceptance date and time in UTC, the exact checkbox wording displayed in the chosen language, its version and language. Registration does not complete if the declaration cannot be saved.

The age-or-authority declaration records what the user asserted; it does not independently verify age, parental responsibility or legal authority. Supporting evidence is not routinely requested. This recording applies to new registrations through that flow after its introduction on 17 November 2026. It is not evidence that existing users accepted that wording, and does not automatically cover other registration routes or profiles added later. MyMedicalSupport UK Ltd must assess whether its authority checks are sufficient for the purpose and risk and arrange proportionate additional checks where required, including uncertain or disputed authority.

Only manage another person’s information with appropriate authority. An authenticated account establishes technical access, not parental responsibility or legal authority. A relative, carer, school or charity must not automatically receive profile access. Staff handling representative onboarding, recovery, transfer or disputed access must establish who the subject and manager are, the decision being made and the scope of the representative’s authority.

Use proportionate declarations and checks, record the decision and minimise retained evidence. Where authority is uncertain, obtain appropriate advice and limit disputed access while the issue is resolved. Do not request identity documents or complete medical files through an ordinary shared inbox by default. This policy does not assert that the application performs automated parental-responsibility verification.

Children and developing understanding

Explain sharing in a form the child and responsible adult can understand and consider the child’s views. Where an information-society service is offered directly to a child and consent is the basis relied on, the UK Article 8 threshold is 13; below that threshold, parental authorisation and reasonable verification efforts are required. This threshold is not a universal rule for all medical or privacy decisions and does not give parents automatic control until age 18.

Review arrangements as understanding develops, before adulthood and when family or care circumstances change. Consider how the subject can take control or authorise continued support. Do not automatically continue parental access or transfer private notes solely because an account was originally parent-managed.

Adults and supported decisions

Presume capacity and support communication before considering decision-specific incapacity. Next of kin or a carer has no automatic decision-making authority. Establish the person’s authorisation or legally effective authority and its limits; a power of attorney must cover the relevant decision and circumstances. Apply the Mental Capacity Act 2005 where relevant in England and Wales and the appropriate frameworks in Scotland and Northern Ireland.

Recovery and disputed access

Do not disclose medical information to an alleged representative before resolving authority. Check whether contacting the current account manager is safe. Account recovery must not bypass authority checks or use sensitive medical content as an identity question. Review affected sharing after a lost product, compromised account, change of carer or safeguarding concern, and record any restrictions and their verification.

Receiving and recording a concern

A first report should briefly describe the concern, immediate risk, relevant account or profile reference if known, and a safe way to reply. Avoid unnecessary medical records or attachments. Concerns do not need to use legal terminology or arrive with proof.

Staff must listen without judgment, preserve the person’s own words, avoid leading questions and explain the next appropriate step. Do not promise secrecy, question a person repeatedly or attempt a safeguarding investigation. Record the receipt time, facts, source, immediate danger, safe contact method and actions taken. Separate observations from assumptions. Take communication and accessibility needs into account.

Response escalation and external referral

The lead or deputy must assess the immediate safety needs and whether to involve statutory services. Technical containment may include restricting disputed access or a compromised sharing route. Preserve relevant evidence securely and consider whether an action could alert an alleged abuser, destroy evidence or remove important emergency information. Refer necessary protective decisions to the appropriate qualified service.

  • England: use the relevant local authority children’s social care or adult safeguarding service, and police where appropriate.
  • Wales: use local social services and the relevant Welsh safeguarding procedures.
  • Scotland: use local social work, child or adult protection services, or police as appropriate.
  • Northern Ireland: use the relevant Health and Social Care Trust gateway or adult safeguarding service, or PSNI as appropriate.

Use current official contact details and local out-of-hours arrangements. Consider the person’s location when choosing the referral route. For cases outside the UK, seek the appropriate local service and advice. A non-emergency police or email route is not a substitute for emergency action.

Where an allegation concerns someone who works with children in England and meets the relevant threshold, follow the local authority designated officer arrangements without delay; Working Together specifies notification within one working day. Follow other national allegations-management procedures where applicable. The lead must check any applicable mandatory reporting or referral duty and its deadline. Internal fact-finding must not delay a required external report.

Agree safe follow-up with the person affected where appropriate, unless that would increase risk or prejudice a lawful investigation. Record referrals, information shared, decisions not to refer and their reasons. Assign an owner to follow-up actions and escalate unresolved risks.

Confidentiality and lawful information sharing

Share safeguarding information only with those who need it for a lawful, defined purpose. Information must be relevant, necessary, proportionate and as accurate as reasonably possible. Do not promise absolute confidentiality. Explain sharing where safe and appropriate; do not seek consent where doing so would place someone at risk or undermine necessary protective action.

A refusal or inability to consent must not automatically prevent a justified safeguarding referral. Equally, safeguarding is not blanket permission to disclose or process any information. Record the applicable Article 6 lawful basis, and for health or other special-category information an Article 9 condition and any necessary Data Protection Act 2018 condition. Ordinary storage and chosen public sharing require their own assessment; the safeguarding condition is not a universal basis for routine platform operation. Maintain an appropriate policy document where the relied-on condition requires one.

Where explicit consent is relied on, it must be specific, informed, validly authorised and evidenced, with a practical withdrawal route. Do not infer consent from a purchase, discount, general terms acceptance or a person merely entering data. Verify affected access routes when restricting disclosure; do not promise universal revocation because a section was hidden.

Data incidents and safeguarding records

A safeguarding incident may also be a personal data breach. The responsible person must establish the awareness time, affected information and people, likely harm and containment, and keep a decision record. Report to the ICO without undue delay and within 72 hours where required, unless the breach is unlikely to risk people’s rights and freedoms. Explain any delay and supply further details in phases where needed. Inform affected people without undue delay where a high risk requires it, subject to applicable legal exceptions.

Safeguarding case records must be restricted to authorised people who need access, with a record of necessary disclosures. Record facts, actions, referrals, reasons, review dates and outcomes. Do not place completed concern records in public documents, demonstration accounts or general customer correspondence. The reporting inbox is an intake route, not authority for unrestricted long-term circulation.

MyMedicalSupport UK Ltd must maintain justified retention and review arrangements for safeguarding evidence, consent records, medical information, logs and backups. Keep information only as long as necessary for its purpose and applicable obligations, apply lawful holds where needed, and arrange secure deletion. Safeguarding case records are normally retained for 12 months after case closure. A continuing safeguarding concern, legal claim or legal obligation may require longer retention, with a recorded reason and review date. Medical records, declaration evidence and other logs require their own justified retention rules. Erasure and restore procedures must account for derived copies and backups.

Staff conduct training and allegations

Use approved business channels, maintain professional boundaries and avoid private contact with children or requests for unnecessary personal information. Never use real customer medical profiles for training, public demonstrations or sales presentations. Do not browse health records without an authorised operational purpose. Apply proportionate access permissions and access review.

Scott Mardon has reported completing Care Skills Training’s Level 2 Safeguarding Children and Vulnerable Adults course on 17 November 2026. Jessica Mardon is undertaking the same course, with completion expected on 18 November 2026. Jessica’s completion remains pending; certificates and course scope must be recorded and reviewed.

Management must arrange role-appropriate safeguarding induction, training, refreshers and supervision, and assess any legally applicable recruitment or vetting requirements. Do not describe every software role as regulated activity or assume eligibility for an enhanced DBS check. Record training and completion actions. Concerns about staff, directors, contractors or partners must be handled promptly, with external referral where required and protection for good-faith reporting.

Product assurance and partner work

The safeguarding, privacy and technical leads must assess public disclosure, authority, misuse, file permissions, translations and other relevant processing through a maintained DPIA and proportionate technical checks. Review the Children’s Code and applicable duties for online services, including whether the Online Safety Act applies. Take specialist advice where needed and consult the ICO before relevant processing proceeds where unmitigated residual high risk requires prior consultation.

Assess suppliers, processor terms, processing locations, international transfers, retention and security. Necessary authorised technical processing can involve access to stored information; encryption must not be described as proof that all operator or supplier access is technically impossible. Staff must not use that processing capability as permission for routine browsing.

Verify safeguards using fictional profiles, including ordinary and code-authorised views, files and separate history responses. Changes and rollback must preserve saved privacy choices. New functionality must not be described as implemented until verified. Management must track unresolved actions and restrict affected processing where required; publishing this policy is not evidence that every technical or organisational action is complete.

Partners must receive accurate descriptions of the product and safeguards, and use fictional information for demonstrations. Feedback on About Me and Support has come from parents and carers; it must not be described as direct testing or co-production with autistic young people. Future involvement must be accessible, voluntary and appropriately supported, with relevant consent, assent and safe handling of disclosures.

Review and accountability

MyMedicalSupport UK Ltd owns this policy. The safeguarding lead coordinates its review with management and those responsible for privacy and technical operations. Review at least annually and after a serious incident, relevant legal change, material feature change or significant partner feedback. Record revisions, implementation actions and responsible owners. Do not backdate approval or imply that procedures operated before they were introduced.

This public policy sets organisational requirements and describes the current features expressly identified above. It does not certify the service’s compliance with every applicable law. Internal risk assessments, individual cases, supplier evidence and security-sensitive operational records remain controlled documents.

Read our Privacy policy, Privacy support information and Terms and conditions. The print control on this page allows you to print or save a copy as a PDF.

Back to top

Have a question?

If you’d like help understanding this policy or need to contact our team, we’re here to help.

Contact the Tapiie team