How we keep accounts and data secure
In short
Every account enrols a second factor, administrators sign in with phishing-resistant keys, and privilege changes leave a tamper-evident record. This page describes the controls we rely on. It is not a warranty: any specific commitments sit in your Order, data processing agreement or SLA.
This summary helps you find your way. The full text below is what applies.
Section 1. What this page covers
Fastclinic Limited (“Fastclinic”) runs a security programme designed for healthcare workloads, aligned with recognised frameworks and with our obligations under the Nigeria Data Protection Act 2023 (“NDPA 2023”). This page summarises the controls we rely on. It is a description, not a warranty. Specific commitments may appear in your Order, data processing agreement or SLA.
Detailed control matrices, current penetration test summaries and subprocessor inventories are available to enterprise customers, under appropriate confidentiality, during procurement and renewal.
Section 2. How every account is protected
Fastclinic Account is our single identity platform. It enforces these controls on every account:
- Breached password checks
- When you register or change your password, we check it against a large collection of passwords exposed in data breaches. Known breached passwords are refused at the point of entry.
- Multi-factor authentication
- Every account enrols a second factor at registration: an authenticator app (TOTP) or a phishing-resistant credential (WebAuthn or passkey). Backup recovery codes are created as a fallback.
- Phishing-resistant factors where the reach is greater
- Administrator accounts must hold at least two WebAuthn credentials (a main one and a backup) from approved authenticator categories, with user verification every time they are used. Healthcare professionals whose accounts can reach patient data are prompted to enrol a phishing-resistant factor before clinical scopes are switched on.
- SMS only for identity checks and recovery
- One-time SMS codes confirm that you own a phone number when you register, and support account recovery. They are not a primary sign-in factor, so a SIM swap cannot be used to get past your password or your phishing-resistant credentials.
- Step-up authentication for sensitive actions
- Privilege changes, access to clinical data and other sensitive operations need a freshly completed strong authentication, however recently your session began.
Section 3. How administrator access is locked down
Administrator access to production systems is kept apart from normal user traffic. The administrator console is served on a separate subdomain, behind a network allowlist, using a short-lived server-side session whose access tokens never reach the browser. Administrators cannot reach production data without completing phishing-resistant authentication. If an administrator’s credentials are lost or compromised, a dual-approval reset applies, and a second administrator must agree before the account is restored.
Administrative permissions are fine-grained and follow least privilege. Viewing records, changing records, approving clinical verifications, managing OAuth2 clients and reading the audit trail are all separate privileges that must be granted one by one. Granting or revoking any privilege writes an entry to the tamper-evident audit log and sends an operational alert.
Section 4. Encryption
Data travelling between your device and our services is protected with modern transport layer security, and we review our configurations to retire weak ciphers. Data at rest is encrypted with AES-256 or a stronger equivalent on the storage layers we control, including databases, object storage and backups.
Sensitive fields, including provider verification records, are also wrapped with envelope encryption, so access to the database alone does not reveal their readable contents. Cryptographic keys are managed through cloud provider key management services, with separation of duties for administrative access and a documented rotation procedure.
Section 5. Who at Fastclinic can reach customer data
Fastclinic staff access to production systems and customer data follows least privilege and need-to-know principles. We enforce multi-factor authentication for every staff role with production access, single sign-on where integrated, and role-based access control inside applications. Privileged access is time-bound, scoped, logged and reviewed periodically.
Customers set up their own user roles and permissions in the platform. We provide templates that follow common patterns for separating clinical and administrative duties.
Section 6. Audit logs that show any tampering
We create security-relevant logs for authentication events, privilege changes, verification decisions, data exports and OAuth2 client management. Audit entries are hash-chained. Each row commits the cryptographic hash of the row before it, so any later change to, or deletion of, a historical row breaks the chain and can be detected at verification time. A daily root hash is published to write-once storage for long-term integrity.
The audit writer refuses secret material (tokens, passwords, cryptographic keys, session identifiers), and any attempt to log such fields is rejected when the entry is written. Routine administrative roles have read-only access to the audit log, and the database schema stops the application itself from modifying it.
Enterprise customers can access audit trails through product interfaces or API exports, depending on their subscription tier, to support their own compliance programmes.
Section 7. Infrastructure and availability
Production workloads run on reputable cloud infrastructure, with redundancy across availability zones, automated scaling and documented disaster recovery procedures. Backups are encrypted, tested on a set schedule and stored separately from primary systems, to reduce the risk from ransomware and accidental deletion.
Network segmentation limits how far an intruder could move. Firewalls and web application protections run at the perimeter and application layers. Administrator interfaces are also isolated on a separate hostname with restricted network access.
Section 8. Stopping fraud and abuse
For accounts that can reach clinical information, we apply rule-based risk signals at sign-in: recognising devices used before, changes in the country of access, sign-ins outside a user’s usual pattern, and long periods of inactivity. A combination that looks unusual enough triggers a step-up challenge using your enrolled strong factor. These signals do not deny service silently. The user is always told what extra verification is needed.
Signals are kept for thirty (30) days in an append-only forensic store and then deleted automatically. Rate limits apply to authentication endpoints and sensitive API routes. Suspected abuse is escalated for review by a person, and any administrative suspension of an account is recorded in the audit log.
Section 9. When something goes wrong
We keep a written incident response runbook covering detection, containment, assessment, notification and post-incident review. Security incidents involving personal data are assessed against the NDPA 2023 notification criteria. Where we are the controller, we notify affected data subjects and the NDPC within the statutory seventy-two (72) hour window where required. Where we act as processor, we notify the affected controller without undue delay, and in any event within the window agreed in our data processing agreement.
Report suspected incidents to contact@getfastclinic.com with the subject “Security Incident”, and include any timestamps, identifiers and indicators of compromise you have. We run a tabletop exercise against the runbook every quarter, and fold the lessons from each one into the runbook and our threat model.
Section 10. Finding and fixing weaknesses
We carry out regular vulnerability scanning, dependency review and patch management. Critical security patches are prioritised by severity, exploitability and exposure. We run a coordinated disclosure process for external researchers and customers who find vulnerabilities in our products (see section 14).
Our application security practices include secure development training, code review, static analysis and independent penetration testing. Our programme provides for a scoped external penetration test of our identity and administrator surfaces, with remediation service levels set by the severity of each finding:
| Finding severity | Remediation service level |
|---|---|
| Critical | 7 days |
| High | 30 days |
| Medium | 90 days |
Section 11. Checking the companies we rely on
Subprocessors with access to personal data or to material security functions go through security and privacy due diligence, including review of SOC 2 reports, ISO certifications or equivalent evidence where available. Contracts impose confidentiality, breach notification and assistance obligations consistent with the NDPA 2023 and our data processing agreement template. Our Privacy Policy names our principal subprocessors. Enterprise customers receive the full list and thirty (30) days’ notice of material changes.
Section 12. Frameworks, certification and corporate duties
We align our programme with the NDPA 2023 and track established external assurance frameworks. Mentioning a framework does not imply certification in all domains until we expressly state it here in writing.
As a Nigerian company incorporated under CAMA 2020, we keep the corporate records and governance practices needed for regulatory and contractual transparency. Our accounting, auditor and director filings are lodged with the Corporate Affairs Commission as required.
Section 13. Your part in keeping things secure
Security is shared. You are responsible for adding and removing users, rotating shared secrets, securing the devices used to reach the Services, storing API keys securely and configuring integrations. Misconfiguration and compromised customer credentials remain leading causes of unauthorised access. We strongly recommend enrolling a phishing-resistant factor on every administrative account and requiring one for clinical tools.
Section 14. Reporting a vulnerability to us
We welcome coordinated disclosure of security vulnerabilities. Report issues to contact@getfastclinic.com with the subject “Security Vulnerability”. Please give us a reasonable chance to investigate and fix the issue before any public disclosure, and avoid actions that would degrade the service, access data without authorisation or break the law. We will acknowledge your report, give you an initial assessment and, where it helps your work, credit you on request.