Rights and licences
This site does not own contributed work and does not ask to. It needs permission to publish and archive, and nothing more.
Who holds what
| Element | Held by | Licence |
|---|---|---|
| The finding, the interpretation, the written discussion | the researcher | CC BY 4.0 |
| Pipeline and dashboard code | Taufik Adi Nugraha | MIT |
| Upstream data | the original provider | stated per source, on every case |
| This website | openstudy.id | site code and design only |
What the site takes is a non-exclusive, perpetual licence to publish and archive. You can republish the same work anywhere, put it on your own site, submit it to a journal, or fold it into a thesis — without asking.
Journals routinely require an exclusive copyright transfer. Asking for nothing costs this site nothing, and it is one of the few concrete advantages it can offer before it has any audience to trade on.
Nothing here redistributes somebody else's dataset
Pipelines fetch from the origin every time, and each source's licence is named on the case that uses it. What gets published is the derived result — counts, model outputs, figures — not a copy of the input.
That is partly principle and partly self-protection: a site that redistributes data takes on every upstream licence question, and a small operation cannot carry that. It also means a source withdrawing its data breaks the pipeline honestly rather than leaving a stale copy circulating.
Copyright constrains you, not the venue
If you signed an exclusive transfer to a publisher, that binds you wherever you publish next — a figure you cannot reuse here is one you cannot reuse on your own site either. It is not a reason to publish elsewhere; it travels with you.
In practice it rarely bites here, because instruments are built from the data and the code, never from a publisher's typeset PDF. Figures are re-rendered from source. Nothing reproduces the article. Where a paper is open access under CC BY, reuse is explicit anyway.
What you confirm
"I hold the rights to the data and code published here, and this artifact is compatible with my publisher's or target journal's policy."
That is the whole declaration. This site does not interpret publisher contracts — it cannot, and guessing wrong would be your problem rather than its. The judgement stays with the only person who has read the agreement.
No personal data, ever
Aggregate only. No names, identity numbers, addresses, contact details or anything else that identifies a person — in any published file, not just in the visible page. It is checked mechanically on every case before publication.
This is a scope limit rather than a capability claim. Handling personal data properly means obligations a volunteer-run site should not be taking on, so the answer is to not hold any.