Privacy
How MetaProc handles your data. Short version: analyses run in throwaway, EU-hosted containers, and you should never upload identifiable patient-level data.
No identifiable patient-level data
MetaProc is a tool for aggregate, study-level meta-analysis: the summary statistics already published in papers (event counts, means, SDs, effect sizes). It is not designed for and you should not upload individual patient data or any directly identifiable personal information. Please remove identifiers before importing anything.
Ephemeral by design
Your analysis runs inside an isolated, RAM-backed container that is destroyed at the end of your session. Data you upload lives in that container's memory for the duration of your work and is not written to long-term storage by the analysis runtime. When your session ends, the container (and the data in it) is torn down.
Hosting & sub-processors
MetaProc is hosted in the EU. The following sub-processors may handle data in the course of running the service:
| Sub-processor | Purpose | Location |
|---|---|---|
| Hetzner | Application hosting & compute | Germany / Finland (EU) |
| Cloudflare | CDN, DNS, and edge delivery | Global edge (config in EU) |
| Auth0 / Okta | Authentication / login | EU region |
| Backblaze | Build artifact storage | EU region |
Erasure & contact
Because analyses are ephemeral, there is normally nothing persistent to erase once your session ends. For any privacy question, data-erasure request, or concern, contact myron.moskalyk@gmail.com.