How we look after your personal data
In short
This policy covers the personal data we handle when you visit our website, use a Fastclinic Account or use our software. Sometimes we decide how that data is used, and sometimes a hospital or clinic decides and we act on its instructions. Either way, the Nigeria Data Protection Act 2023 gives you rights, and section 19 shows you how to use them.
This summary helps you find your way. The full text below is what applies.
Section 1. What this policy covers
This policy describes how Fastclinic Limited (RC 1919428), which we call “Fastclinic”, “we”, “us” or “our”, processes personal data when you:
- visit getfastclinic.com
- register for a Fastclinic Account at account.getfastclinic.com
- use our enterprise healthcare software, our APIs, or our mobile or web applications
- contact our support channels
- deal with our services in any other way.
Together, we call these the “Services”.
Fastclinic makes software for hospitals, clinics, insurers, laboratories, pharmacies, pharmaceutical companies and other healthcare organisations. We also run Fastclinic Account, one identity platform that lets a person sign in once and reach every Fastclinic product they are allowed to use. Our role under the Nigeria Data Protection Act 2023 (“NDPA 2023”) depends on the context of the processing, as section 2 sets out.
By using the Services or giving us personal data, you acknowledge that you have read this policy. If you do not agree with it, you must not use the Services.
Section 2. When we decide, and when your hospital decides
We handle personal data in two capacities, and the NDPA 2023 gives each one different duties. The capacity matters because it settles who decides why the data is processed, and who you go to when you want to use your rights.
- When Fastclinic is the controller
- We decide the purposes and means of processing when a person (a patient, provider or workforce user, for example) registers a personal Fastclinic Account at account.getfastclinic.com, when someone subscribes to our newsletter, requests a demo, contacts support for themselves, or sends us information through the forms on our website. Fastclinic is the controller of that data.
- When Fastclinic is a processor
- A healthcare organisation that is our enterprise customer may use our platform to manage patient records, clinical work, billing and similar tasks. That customer is the controller of its patient and operational data. We process that data on its documented instructions, under a data processing agreement (see our Data Processing Agreement).
The same person can deal with us in both capacities. Take a clinician with a personal Fastclinic Account: for that account, Fastclinic is the controller. When the clinician uses it to reach a hospital’s deployment that is connected to Fastclinic Account, the hospital is the controller and Fastclinic is its processor for the hospital’s workflow data. When this policy says “we decide” or something similar, it means processing where Fastclinic is the controller.
Section 3. Who we are and how to reach us
For processing where Fastclinic is the controller:
- Fastclinic Limited (RC 1919428) is a company incorporated in Nigeria under the Companies and Allied Matters Act 2020 (“CAMA 2020”), registered on 14 April 2022.
- Our registered address is 16 Zone D, Road 1, Ushafa, Abuja, Nigeria (901101).
- We are registered with the Nigeria Data Protection Commission as a data processor of major importance, registration number NDPC/DCP/15807, which you can verify on the Commission's website.
- For general questions, email contact@getfastclinic.com.
- For privacy and data protection, use the same address with the subject line “Data Protection Inquiry”. Our Data Protection Officer is described in section 21.
Where Fastclinic processes data for a healthcare organisation that is our customer, that organisation is the controller of it. If you contact us about patient or end-user records we hold for one of our customers, we will point you to that organisation.
Section 4. The laws we follow, and our lawful reasons for processing
We process personal data in line with the NDPA 2023, the subsidiary legislation and guidance issued by the Nigeria Data Protection Commission (“NDPC”), and the other Nigerian laws that apply. Where our processing involves companies incorporated under CAMA 2020, we also keep to the corporate record-keeping duties that can affect how long certain business records are kept.
We rely on the lawful bases the NDPA 2023 recognises. They include:
- Performance of a contract
- To keep your Fastclinic Account running, give you the products you subscribe to, process orders and invoices, and support you.
- Compliance with a legal obligation
- To keep tamper-evident audit trails, answer regulators’ inquiries, and meet record-retention duties under the NDPA 2023, CAMA 2020 and healthcare rules for our sector.
- Consent
- For marketing messages, optional product features, and the permissions you grant on our OAuth2 consent screen when you let a Fastclinic product read your data. You can withdraw consent at any time (see section 19).
- Legitimate interests
- To prevent fraud and account takeover, secure our networks, detect abuse of our APIs and make our service more reliable. We weigh these interests against your rights and freedoms.
- Vital interests and the public interest
- In limited situations only, such as an emergency disclosure to protect someone’s life, or cooperating with lawful authorities.
Special categories of personal data, including health data, get stronger protection. We process them only where a specific legal basis under the NDPA 2023 applies, and with suitable technical and organisational safeguards in place.
Section 5. The personal data we may collect
What we collect depends on how you deal with us. It may include:
- Identity and contact data
- Given name, middle name (optional), family name, preferred display name, date of birth, gender, state and city of residence, phone number, email address, postal or office address, and the organisation you belong to, where that applies.
- Account and authentication data
- Set out in detail in section 7.
- Provider verification data
- Where you register as a healthcare professional or facility. See section 8.
- Technical and usage data
- IP address, device type, browser, operating system, approximate location worked out from your IP address (often only to country level, through our network edge), log timestamps, pages viewed, features used, error reports and performance diagnostics.
- Communication data
- Messages you send to our support, sales or security teams, recordings of calls where we lawfully record them and tell you first, and the metadata that goes with these communications.
- Commercial data
- Billing address, purchase history, subscription tier, tax identifiers where required, and payment references. Certified payment processors handle payment card numbers, which do not reach our systems.
- Health and clinical data
- When customers use our platform to manage care, we process on their behalf patient demographics, identifiers, medical record numbers, diagnoses, medications, laboratory results, imaging metadata, appointment details, and other clinical or operational data that the customer or its authorised users submit.
- Marketing and preferences
- Event registrations, newsletter subscriptions, content downloads, and preferences drawn from cookies, where you have consented or another lawful basis applies.
You do not need to fill in fields marked optional to use the Services. Fields marked required support core account or contract operations. If you opt into specific features, we may ask you for more data.
Section 6. What your Fastclinic Account holds
Fastclinic Account is our single identity platform. When you create a Fastclinic Account at account.getfastclinic.com, we collect and store the following as controller:
- Registration details
- Your names, date of birth, gender, state and city, and your main identifier (phone or email), plus a second identifier if you choose to add one.
- Account state
- When the account was created and last updated, its status (active, inactive or scheduled for deletion), your display name preferences, and any optional public metadata you set. One example is the time you dismissed our prompt to add a passkey, so we stop asking you.
- Entitlements
- Which Fastclinic products you can use, how you got that access (a personal subscription, an organisation membership or a promotion), when it expires, and any administrative status flags.
- Organisation memberships
- If you belong to a hospital, clinic, HMO or other organisation on the platform: your membership record, your role and when you joined.
You can see most of this in your dashboard at account.getfastclinic.com/dashboard. You can also export all of it at any time as a machine-readable JSON file (see section 19).
Section 7. How we confirm it is really you
Account security rests on credentials we keep in a separate store with restricted access:
- Password hash
- We hash passwords with a modern memory-hard algorithm before storing them. Your actual password never leaves your browser in a form we keep.
- Authenticator app secret (TOTP)
- If you set up an authenticator app for multi-factor authentication, we store the shared secret needed to check the time-based one-time codes you enter.
- Backup recovery codes
- One-time codes created when you set up multi-factor authentication. We store them as hashes. Once a code has been used, it cannot be used again.
- Passkeys and security keys (WebAuthn)
- When you add a passkey or hardware security key, your device creates a public and private key pair. We store only the public key, the credential identifier, and an authenticator attestation identifier (“AAGUID”) that shows the type of device. The private key never leaves your device. Any fingerprint or face scan your device uses for the credential stays on your device too. Fastclinic does not receive or store biometric template data.
- Session records
- A session identifier tied to your browser or app, so we can recognise you from one request to the next without asking for your credentials again, along with the authentication factors you used and when you completed them.
- SMS one-time codes
- Used only to confirm your identity when you register and when you recover your account yourself. They are not used for everyday sign-in. The codes are short-lived and are not kept after verification.
We use authentication data to confirm that a request comes from you, to enforce multi-factor requirements and to detect credential-stuffing attempts. Accounts with higher privileges get extra controls, described in our Security Practices.
Section 8. Checking healthcare professionals and facilities
To register as a healthcare professional or facility, you must be verified. If you send us a verification request, we process:
- Licence details
- Your professional licence number, the authority that issued it, and its expiry date.
- Supporting documents
- Images or PDFs of your licence, government identification, facility registration, or other documents you upload to support the request.
- Review records
- The review status, reviewers’ comments, when decisions were made, and any follow-up information we ask you for.
Licence numbers and document contents are encrypted at rest under keys set aside for verification material. Only authorised reviewers who need to see them can do so, after step-up authentication, and every access is recorded in the audit log. We do not share verification documents outside Fastclinic unless the law requires it or there is a documented regulatory inquiry.
We keep verification records for up to seven (7) years after a request is rejected or suspended, in line with what is expected of professional registration records. If you make a successful erasure request (see section 19), we apply the exception in Section 16(2) of the NDPA 2023 only where a legal obligation requires us to keep the record, and we will tell you if that is the case.
Section 9. The signals we use to stop account takeover
To prevent account takeover, credential stuffing and SIM-swap fraud, especially on accounts that can reach clinical information, we create and store a limited set of security signals:
- Device binding
- On provider accounts, we record an identifier for each browser. It comes from a first-party cookie combined with your User-Agent and Accept-Language headers, all hashed so the raw values are never stored. This lets us tell a device you have used before from a new one, and ask for extra verification on a device we do not recognise. You can see and revoke bound devices in your dashboard.
- Sign-in context
- On provider accounts, we work out signals such as the country of the network you are signing in from (taken from our network edge, not your precise location), whether the device is new or recognised, and whether the sign-in is outside your usual hours. Together they give a risk score that may trigger a step-up authentication prompt.
- How long signals are kept
- Risk signals are held for thirty (30) days in an append-only forensic store, and older records are deleted automatically. Device bindings last while the binding is active and are removed when you revoke them.
Our lawful basis for these signals is legitimate interest: preventing fraud against you and across Fastclinic products. We weigh that interest against your rights. The signals do not drive automated decisions with legal or similarly significant effects. The most they can do is ask you for extra verification. They never deny you service without telling you.
Section 10. What we use personal data for
We use personal data to:
- provide, run, maintain and improve the Services
- create and manage your Fastclinic Account and your access across Fastclinic products
- authenticate users, enforce multi-factor requirements and detect unauthorised activity
- process orders, invoices and payments, and manage enterprise contracts
- provide customer support, professional services, training and documentation
- meet legal, regulatory and audit requirements, including under the NDPA 2023, CAMA 2020 and healthcare rules for our sector
- run security monitoring, fraud detection, incident response, backups and business continuity
- produce aggregated or de-identified analytics that improve our product design, reliability and documentation
- send service notices and administrative messages and, where permitted, marketing messages you can unsubscribe from through the link at the foot of the message or your preferences
- develop and run machine learning or analytical features in line with our Fastclinic Intelligence Policy and our customer agreements, with human oversight where that is clinically or operationally appropriate.
Section 11. How we treat health and patient data
Patient data and other health data processed through the Services is treated as sensitive personal data under the NDPA 2023. Access to it is limited by role, by purpose and by contract. We do not sell patient data. We process it for the purposes the healthcare organisation (the controller) instructs, such as care delivery, billing, quality improvement and regulatory reporting, or where the law requires it.
Our authorised staff can reach this data only when they need to, and they are bound by employment confidentiality, training and technical controls. We keep procedures for data minimisation, for pseudonymisation where appropriate, and for keeping environments separate where a customer’s configuration requires it. Clinical tools require phishing-resistant authentication factors.
Section 12. Your record of who you let in
When you allow a Fastclinic product, or a third-party application connected to us, to access your Fastclinic Account account, we record that consent in an append-only log. The record shows the product or client, the exact scopes you granted, the date and time, and the network address the authorisation came from. You can see your active consents, and the audit trail for each, in your dashboard.
Consents expire automatically twelve (12) months after you grant them, and you will be asked to authorise again the next time they are used. You can revoke any consent at any time, and you can revoke single scopes inside a consent without revoking the whole grant. A revocation takes effect straight away for new requests. Access tokens already issued stay valid until they expire (usually within the hour) or are explicitly invalidated.
Section 13. Why some records outlast your account
We record administrative actions, privilege changes, verification decisions, authentication events and sensitive workflow steps in a tamper-evident audit log. Each entry is hash-chained to the one before it, and each day’s root hashes are published to write-once storage so the log keeps its integrity over the long term.
We keep the audit trail for seven (7) years. Even if you use your right to erasure, audit entries that refer to your account identifier are kept under the exception in Section 16(2) of the NDPA 2023 for compliance with legal obligations, because the chain only holds together if every entry is preserved. Sensitive content such as tokens, cryptographic secrets and raw credentials is never written to the audit log. A redaction check rejects any attempt to write it.
Section 15. When data leaves Nigeria
Our main operations are set up for secure processing within Nigeria and in deployments aligned with Africa. Our primary identity, verification and clinical data stores are hosted in regions aligned with our Nigerian deployment.
When personal data is transferred outside Nigeria, we do it in line with the NDPA 2023 and the regulations that apply. That may mean an adequacy decision, standard contractual clauses approved by the NDPC, binding corporate rules, another legally recognised transfer mechanism, or a narrow derogation such as your explicit consent or the performance of a contract. In particular, transactional email sent through a processor in the United States (Resend) is covered by standard contractual clauses. Limited network metadata that passes through global edge services (Cloudflare, for example) is handled under that processor’s cross-border safeguards.
Enterprise customers can set data residency or processing limits in their order form or data processing agreement, subject to what is technically feasible and the agreed scope of service.
Section 16. How long we keep data
We keep personal data only as long as we need it for the purposes in this policy, unless the law requires or allows a longer period. These periods apply to the data we control:
| Data | How long we keep it |
|---|---|
| Fastclinic Account identity (profile, credentials, entitlements, memberships) | For the life of the account, plus a forty-eight (48) hour cool-off window after an erasure request, during which you can sign in and cancel the request. |
| Consent records | Twelve (12) months from grant if unused, or seven (7) years from revocation or expiry where kept as part of the audit trail. |
| Provider verification records | Up to seven (7) years from rejection or suspension, or for as long as a verification is active. |
| Audit log | Seven (7) years. The exception in Section 16(2) of the NDPA 2023 applies (see section 13). |
| Device binding records | While the binding is active. Removed when you revoke it yourself. |
| Risk signals | Thirty (30) days on a rolling basis, then deleted automatically. |
| Session records | Usually up to twenty-four (24) hours, and sooner if you sign out or a policy change ends the session. |
| Transactional SMS and email content | Kept by the processor under its own retention policy. Fastclinic keeps only delivery metadata, for troubleshooting. |
| Support tickets | Up to three (3) years from resolution. |
| Billing records | As tax and company law require, usually six (6) years. |
Backups are rotated on a set cycle, so personal data in a backup may remain until the end of that rotation window after it has been deleted from live systems. When a contract ends, we delete or return customer data as the agreement says, though we may keep some data for a limited time for disputes, security logs or legal holds.
Section 17. How we protect data, and what happens after a breach
We use administrative, technical and physical safeguards suited to the risk. They include encryption in transit and at rest, role-based access control with phishing-resistant multi-factor authentication for privileged roles, tamper-evident audit logging and a documented incident response process. Our Security Practices give the details.
No way of sending or storing data is completely secure. If there is a personal data breach, we will notify affected parties and regulators where the NDPA 2023 requires it. For data we control, we do so within the statutory 72-hour window. For data we process on behalf of a customer, we do so without undue delay, as our Data Processing Agreement sets out.
Section 19. Your rights, and how to use them
Subject to the NDPA 2023 and the guidance under it, you have the rights below over personal data we control about you. Many of them are self-service controls in your Fastclinic Account dashboard. Others need a written request to our privacy contact.
- Access
- Download a machine-readable JSON file of your profile, authentication metadata, consents, entitlements, organisation memberships and verification request metadata, using the export in your dashboard. We work to answer subject access requests within the statutory timeframe, typically within thirty (30) days.
- Correction
- Correct your profile details in your dashboard. For data you cannot edit in the app (review records, for example), contact our privacy address below.
- Erasure
- Ask for immediate erasure through the self-service “Erase my account” flow. This starts a forty-eight (48) hour cool-off window during which you can sign in and cancel. After the window, we delete your identity details, credentials, session state, device bindings and risk signals, and revoke your active consents. Audit entries, and records we must keep under a legal obligation (such as financial records, and completed verification records still inside their statutory period), stay for the periods in the retention schedule above. We will tell you which of these apply.
- Restriction and objection
- Revoke particular consent scopes from your dashboard, or contact us to object to processing based on legitimate interest. We consider each objection on its merits under the NDPA 2023.
- Withdrawing consent
- Where processing relies on consent, you can withdraw it through your dashboard or your message preferences. Withdrawing consent does not affect the lawfulness of processing that happened before.
- Data portability
- The self-service export comes in a common, machine-readable format (JSON). Sending your export to another controller for you is not automated. Contact us and we will help.
- Complaining to the regulator
- You can lodge a complaint with the NDPC at any time. We ask you to contact us first so we can try to put it right, but you do not have to do so before complaining to the NDPC.
To use your rights against Fastclinic as controller, email contact@getfastclinic.com with the subject line “Data Protection Inquiry”. Where we process data only as a processor for a customer, we will point you to that organisation. It is responsible for answering patient or end-user requests in the first instance, and we help our customers as our contracts and the law require.
Section 20. Significant decisions are never left to automation alone
We do not make decisions about you that have legal or similarly significant effects by automated means alone. The rule-based signals we use to spot unusual sign-in activity (see section 9) may ask you for an extra verification step. They do not deny you service without telling you, and a person is involved in any decision to suspend or restrict an account for suspected abuse.
Section 21. Our Data Protection Officer
We have named an internal role responsible for overseeing compliance with the NDPA 2023, with a direct line of escalation to the company’s executive leadership. You can reach the Data Protection Officer (or whoever is currently designated) at contact@getfastclinic.com with the subject line “Data Protection Inquiry”. We will acknowledge your message and reply within the statutory timeframes.
Section 22. Children’s data
Our Services are meant for healthcare organisations and authorised adults. We do not knowingly collect personal data from children for consumer purposes. Patient records may include data about minors where healthcare providers instruct it, and that processing is governed by the controller’s legal bases and clinical obligations.
Section 23. When this policy changes
We may update this policy to reflect legal, regulatory or operational changes. We will post the new version on this page and change the “last updated” date. Where a change is material and the NDPA 2023 requires us to get your consent or give you notice, we will do so as the law requires. Where the law allows, continuing to use the Services after the effective date means you accept the revised policy.