On this page12 sections
- Plain-language summary
- 1.Who we are
- 2.What we collect and why
- 3.Reasons permitted by law
- 4.Who may receive information
- 5.Audio, video and AI assistance
- 6.Cookies and information on your device
- 7.How long information is kept
- 8.Your rights and how to make a request
- 9.Storage and transfers outside Nigeria
- 10.Security
- 11.Changes to this policy
Plain-language summary
Oncominder provides software for healthcare organisations, their staff and patients. This policy covers our website and platform. Health information is sensitive personal data. The information handled depends on the services you and your healthcare organisation use.
Your hospital or research organisation also has responsibilities for the records it collects and the care or study it provides. Read its privacy notice and any study or consultation information alongside this policy. Agreeing to this policy does not give blanket consent to optional processing.
1. Who we are
Oncominder is located in Lagos, Nigeria. For privacy questions or requests about our website or platform, email privacy@oncominder.com. Please describe your request without sending passwords, payment-card details or medical documents in your first email. Draft: to be confirmed with counsel
The organisation providing your care or conducting your study generally decides why and how its clinical or research records are used: it is the data controller for those purposes. We process those records on its instructions as a service provider. We act as a data controller for the purposes we determine ourselves, such as handling business enquiries and operating platform accounts and security.
2. What we collect and why
- Identity and contact information: names, date of birth or stated age, contact details, addresses, patient identifiers, identity or insurance information and emergency contacts, where supplied. These help identify the right person, manage accounts and support care.
- Health and care records: symptoms, diagnoses, allergies, medicines, appointments, clinical notes, test results, scans, uploaded documents, care plans and connected-device readings, where used. These support treatment, follow-up and communication with the care team.
- Research information: study participation, eligibility, consent, questionnaires and study records where a research organisation uses these services. The study information explains its particular purpose and requirements.
- Staff and organisation information: work contact details, roles, professional details, organisation documents and account activity for access management and service administration.
- Billing and transaction information: invoices, insurance or payer details, amounts, payment references and statuses for billing and reconciliation. Where online checkout is used, payment details are handled by the selected payment provider.
- Messages, consultations and AI inputs: messages, dictated audio, consultation audio segments, transcripts and information selected for enabled AI features. Section 5 explains how these features can involve outside providers.
- Website enquiries: your name, work email, organisation, role, organisation size, requested service and optional notes when you request a demo. The request is stored and sent to our team by email so we can respond.
- Technical and activity information: session and device information, IP addresses, browser details, access records, usage events and error reports for security, troubleshooting and understanding service use.
Information can come from you, your healthcare or research organisation, its authorised staff, records it imports, and services or devices connected to the platform. Not every service collects every category. Please avoid putting medical information in a public demo request.
3. Reasons permitted by law
The Nigeria Data Protection Act 2023 applies to our handling of personal data in Nigeria. The lawful basis depends on the particular purpose:
- Contract or requested steps before a contract: where needed to provide a service you have contracted for or respond to your request to arrange it.
- Legitimate interests: responding to business enquiries, administering business relationships, protecting accounts and investigating misuse, subject to your rights and interests.
- Legal obligations: keeping or disclosing records where an applicable law requires it.
- Consent: for a specific activity that relies on your agreement, such as an optional consultation transcription. You can withdraw that consent.
The healthcare or research organisation must identify the lawful basis and the additional condition for processing sensitive information for its activities. For example, medical care under a professional duty of confidentiality may qualify under section 30 of the Act. A software contract alone does not authorise every use of health information or research data.
4. Who may receive information
Information is available to authorised users involved in the relevant service, such as your care team, hospital administrators or research staff. Sharing with another organisation depends on the applicable access arrangements, permissions and lawful basis.
Outside providers can receive information needed for hosting, database and file storage, email or SMS delivery, video consultations, payments, analytics, error reporting or AI processing. Depending on the deployment and enabled features, these can include Vercel, Render, Cloudflare storage, Resend or an email provider, Termii or Twilio, LiveKit, the selected payment provider, Sentry and the AI providers described below. This describes available service arrangements; it does not mean every provider receives every user's information.
Ask our privacy contact or your healthcare organisation which providers actually handle your information, what they receive and where they process it. Information may also need to be disclosed to a competent authority where lawfully required.
5. Audio, video and AI assistance
Video consultations use the configured video service. Where transcription is enabled and the patient's transcription consent is recorded, consultation audio is captured for conversion to text. Dictation also sends audio for transcription. Cloud transcription can use OpenAI or Google Gemini; cloud text or image assistance can use Google Gemini or Anthropic. Those services receive the audio, text or images submitted to the feature.
Text assistance can instead use an organisation's configured local model. Using a local text model does not make a separate cloud transcription service local. Ask your care team which arrangement applies before using an optional feature.
AI-generated clinical summaries and advice are drafts for clinician review. AI assistance can affect the draft information presented to your care team and can make mistakes. You can ask for human review and challenge information affecting your care. Agreeing to this privacy policy does not authorise an outside provider to train models on your medical records; provider data-use terms and the organisation's authorisation need to be assessed separately.
6. Cookies and information on your device
The platform uses several cookies for sign-in, session renewal, account routing and preferences such as language. It also uses browser storage for preferences and, where offline working is used, queued work awaiting synchronisation. Information can therefore remain on the device as well as on the server. Use the sign-out controls and check for unsent work before clearing site data.
On Vercel-hosted production deployments, the website can send page-view events to Vercel Web Analytics. Where configured, Sentry receives technical error reports; the application's reporting filters remove user and request details and do not enable session replay. Analytics and error reporting are separate from the cookies needed to sign in.
7. How long information is kept
Retention depends on the type of information and its purpose. Care and research records can remain after an account closes because of the organisation's medical, study, legal or record-keeping requirements. Ask that organisation for the retention schedule applying to your records.
For enquiries, accounts, billing and operational records, the relevant considerations include whether an enquiry or service is ongoing, the need to resolve a dispute or security incident, and applicable legal duties. There is no single retention period covering every category. Request the period or criteria for the particular information from our privacy contact.
Dictation audio is scheduled for deletion after a seven-day waiting period: from the last update of a completed session, or from creation of a failed session. Consultation audio segments are submitted for deletion after processing or when transcription consent is withdrawn. Deletion failures are retried, so those schedules are not guarantees of immediate removal. Transcripts and accepted notes have their own clinical-record retention requirements.
Backups, provider copies and exported files also need to be considered when handling a deletion request. Removing information from the live application does not by itself confirm removal of every copy. Ask for the backup retention and deletion arrangements that apply to your service.
8. Your rights and how to make a request
Subject to applicable law and any relevant exceptions, you can ask to access or correct your information, obtain a copy or request portability, request deletion or restriction, object to processing and withdraw consent where it is the basis for processing. Withdrawal does not make earlier lawful processing unlawful. You can also challenge a decision based solely on automated processing that has legal or similarly significant effects and request human intervention.
- Download available patient data: sign in and open Settings, then choose "Download my data". The file contains supported categories; contact your hospital for records not included in it.
- Review agreements or ask for deletion: open What I agreed to in the patient portal. A deletion request is recorded for review; it does not immediately erase medical records. Taking back an agreement does not by itself remove every hospital access permission.
- Other requests or help signing in: contact your healthcare organisation for its care or study records, or email privacy@oncominder.com for information we handle for our own purposes.
We may need to verify your identity or clarify your request before disclosing or changing information. Requests must be handled without undue delay and within any applicable legal deadline. Retention duties or another person's rights may limit what can be provided or deleted; you can ask for an explanation of the decision.
You have the right to complain to the Nigeria Data Protection Commission. You do not have to complete our internal process before approaching the Commission. Where another jurisdiction's data-protection law applies, its rights may apply in addition.
9. Storage and transfers outside Nigeria
Our location in Lagos does not mean all information stays in Nigeria. Hosting, storage, communications, video and AI providers may process information in other countries. The applicable locations and safeguards depend on the providers and service arrangement in use.
Transfers from Nigeria must meet the conditions in sections 41-43 of the Nigeria Data Protection Act, including documenting the applicable basis and assessing protection where required. This policy does not itself establish that a particular transfer has been approved. Ask our privacy contact for the locations, recipients and transfer safeguards applying to your information.
10. Security
The platform includes access controls, encryption for selected sensitive fields, private file access and records of access to patient information. These controls reduce risk; they do not guarantee that every field is encrypted or that a security incident cannot happen. We have not yet had an independent security audit. See the security page for more detail.
11. Changes to this policy
The date and version above identify this policy. Updates will be published on this page. Where a change requires additional notice or a fresh consent, those requirements apply; publishing a policy does not replace them.
