Stay in control of your data
Security, privacy, and compliance details in one place, written for the people who review and approve new partners.
The analysis comes to the data
Researchers bring their own container and tools and run the analysis in their own compute. The dataset is accessed in place and never becomes theirs. The custody boundary stays with the data holder. Access controls and monitoring apply for the life of the analysis session. Controls are designed to prevent copying or export. LooporaData never receives a copy.
- Available now: Access requests with your approval · Revocation at any time · Access is logged and monitoring is applied · Immutable audit trail · Compute in the buyer’s cloud
- Coming next: Secure streamed access
Example view of the data holder's side of Platform 1.0. Illustrations are not a technical specification.
You decide who can access your data
- You approve every request.: Each buyer tells you who they are, what they plan to do, and which data they need. You approve or decline every request.
- Revoke access at any time.: Data-holder-controlled revocation, whenever you decide.
- Every event is logged.: Every consent decision and access event is recorded in an immutable audit trail. Monitoring is applied.
Ready for your IRB and donor advisory committee
Each request shows who is asking, what they plan to run and which consent codes it must match. Access is logged and monitoring is applied. Audit records for your datasets are available on request.
Our privacy and compliance commitments
Privacy
You set the de-identification standard.
Your IRB stays in charge, and no one gets access without your approval. We help you document the method in your datasheet. Aggregate results are reviewed before release, and small counts are suppressed.
Compliance
Our Information Security Management System (ISMS) is aligned with ISO/IEC 27001 and the AICPA Trust Services Criteria.
Independent SOC 2 Type II and ISO 27001 audits are on our roadmap. HIPAA safeguards are operational, and we execute a Business Associate Agreement when required. Our security documentation is available under NDA.
Consent
Consent you can read.
Consent terms are tagged with GA4GH Data Use Ontology (DUO) codes in each datasheet.
- General research use
- Health / medical / biomedical
- Disease-specific research
- Not-for-profit use only
Coming next
DUA management
Illustrative codes
Dataset description
Every listing comes with a dataset description.
Each datasheet covers the cohort, modalities, consent scope and known limitations.
Want the full details? Read our White Papers
- Available now Access data without moving it: Technical overview · The shape of every engagement: a catalog, an attestation check and an audit log, with the read going straight from the data holder's storage to verified compute.
- Coming next Attestation: Trust and verification · The check every request passes before a credential exists: is this exactly the pipeline that was approved?
- Coming next Output review: Trust and verification · Two independent checks, one at registration and one on every run: what a pipeline is built to do, and what it actually tries to release.
Request a security packet
Everything your security, privacy and legal reviewers need, in one place.