Institutional Technical Brief

Data security, architecture, & regulatory compliance.

A detailed account of LongData's on-premise relational architecture, offline encryption protocols, and local data sovereignty protections — designed for institutional review boards, IT security teams, and grants compliance officers.

On-premise by design Zero cloud exposure NDPA · GDPR · HIPAA baseline

01 · Sovereignty

Boundless Collection, Localized Control

In public health surveillance and longitudinal clinical trials, data migration across international borders often violates strict national health privacy mandates. LongData is engineered from the ground up to guarantee absolute, uncompromised Data Sovereignty.

Zero Cloud Exposure

LongData does not utilize or mandate foreign public cloud hosting pools — e.g. commercial AWS, Google Cloud, or Azure environments — where data sits outside domestic jurisdictions.

100% On-Premise Campus Deployment

The entire master server database stack is deployed directly onto physical server hardware located within the host institution's secure network infrastructure.

Regulatory Compliance Alignment

By enforcing full on-premise execution, the platform aligns directly with national legal mandates, including Nigeria's National Data Protection Act (NDPA), the General Data Protection Regulation (GDPR) principles for African research hubs, and international HIPAA health data management baselines.

02 · Architecture

The Zero-DevOps Infrastructure Stack

Traditional open-source health informatics software stacks rely on multi-layered, containerized architectures (Docker, Kubernetes, heavy Java instances, Node.js nodes) that introduce heavy maintenance footprints and break easily during regional grid power fluctuations. LongData eliminates this vulnerability.

FIELD PWA · IndexedDB · Offline Sync Queue

EDGE Apache / Nginx · HTTPS · PHP 8.x

DATA MySQL / MariaDB · InnoDB · UTF-8mb4

BACKUP Nightly mysqldump · Offsite Mirror (Domestic)

Minimal-Dependency Environment

The platform runs natively on standard, highly stable web server components: Apache/Nginx, PHP 8.x, and MySQL/MariaDB.

Native Backend Normalization

Data is ingested directly into a natively normalized relational database layout instead of wide, unstructured flat-file formats or Entity-Attribute-Value (EAV) models. This configuration preserves absolute data integrity at the point of storage and prevents relational corruption or duplicate identity matching across decades of longitudinal monitoring.

Infrastructure Sustainability

Because the environment requires no complex background microservices, it places near-zero computational strain on hosting machines, allowing universities to reuse cost-effective, existing local IT server assets.

03 · Cryptography

End-to-End Cryptographic Security

Field surveillance often occurs in deep rural enumeration environments with completely absent 3G/4G cellular coverage. LongData's device-agnostic Progressive Web App (PWA) handles offline storage and over-the-air synchronization through an encrypted, ring-fenced pipeline.

TLS1.3

In-transit encryption on every sync cycle

AES-256

At-rest encryption for offline device cache

bcrypt

Credential hashing for all authentication paths

SHA-256

Payload integrity verification per sync packet

Device-Side Encrypted Cache

Captured form data is stored in an encrypted IndexedDB cache on the device, isolated from the browser's standard storage. Records remain encrypted until an authenticated sync cycle uploads them.

Atomic Synchronization Handshakes

Sync cycles execute using atomic database transactions. If an internet network cuts out mid-sync on a rural road, the entire transaction automatically rolls back to prevent half-synced or duplicated database states, completing only when an uncorrupted, end-to-end data packet transmission is verified.

Replay-Resistant Payloads

Each sync packet carries a per-session nonce and SHA-256 payload digest, preventing replay or tampering even if the underlying cellular network is hostile.

04 · Access Control

Granular System Access Control

Administrative dashboards enforce strict privilege isolation across every operational role touching the platform — from field enumerator to principal investigator.

Role-Based Access Control (RBAC)

Field collectors can only access their designated project forms; site supervisors can audit cluster inputs; data analysts can extract scrubbed relational files; and system administrators manage server settings. No single user possesses global unvetted access to row-level clinical records.

Cryptographic Hashing

User authentication credentials, collector sync passwords, and administrative access points are processed natively via standard secure hashing algorithms (such as bcrypt/SHA-256), mitigating threat vectors from local database intrusion.

Atomic Synchronization Handshakes

RBAC role matrix. Every role is reviewed and provisioned by the host institution's designated System Administrator — LongData engineers hold no persistent production access after deployment handoff is complete.

Ready for institutional review?

Share this brief with your IRB & IT security team.

Whether you are preparing for an SDMP intake audit or embedding LongData into a grant proposal, our team can provide a tailored compliance annex on request.

Apply to the SDMP Cohort Request Compliance Annex