DATA SHARING POLICY

This policy describes how the authors of STORAGE: Jurnal Ilmiah Teknik dan Ilmu Komputer make their data, code, and materials available to other researchers, and how they protect the people and the organizations that took part in the research. It applies to research in architecture, civil engineering, mechanical engineering, and computer science.

Policy at a Glance

Question	Answer
What is the basis of the policy?	Sharing upon reasonable request.
Is a Data Availability Statement required?	Yes, for every research article.
Where does the statement go?	In the acknowledgments, which are subsection 3.7 of the article template.
Must data be deposited in a repository?	No, but deposit is encouraged when it is ethically appropriate.
Can data about participants be shared?	Only when it is ethically appropriate, the participants cannot be identified, and their consent allows it.
Are the data peer reviewed?	No. The authors are responsible for the soundness of their data.

1Policy Basis

Topic	Policy
Sharing on request	When authors submit a manuscript, they agree to make the supporting data, code, and materials available to other researchers on reasonable request.
What is reasonable	The authors decide whether a request is reasonable. They consider the purpose of the request and the protection of the participants.
Access for editors	The editors have independent access. Authors must provide the data when the editors ask for them during the review, or when a concern about integrity is examined after the publication under the Allegations of Misconduct policy.
Retention	Authors should keep their data for a reasonable period after the publication.

2Data Availability Statement

Every research article must include a Data Availability Statement. The statement must say the following.

No.	The statement must say
1	Whether the supporting data, code, and materials are available.
2	Where and how they can be obtained, for example in a repository with a persistent identifier, in supplementary files, or from the corresponding author.
3	When they cannot be shared, the reason, for example the protection of participants, the conditions of consent, a confidentiality agreement, or the restrictions of an institution or a company.

Examples of statements

Available on request
The anonymized data set is available from the corresponding author on reasonable request.

Deposited in a repository
The data set and the research instruments are available in [name of the repository] at [DOI or persistent link].

Code available
The source code and the trained model are available in [name of the repository] at [DOI or persistent link].

Not available
The interview recordings and the transcripts cannot be shared, because the participants did not consent to their release and could be identified. The interview guide is provided as supplementary material.

Included in the article
All the data that support the findings are presented in the article.

3Citing Data and Software

Authors cite the data sets and the software that they used or referred to. This includes their own data, data that they deposited, and data and software from other parties.
Citations of data sets and software are added to the list of references, in the format of the journal that is described in the Manuscript Preparation guidelines. Give a DOI or another persistent link when there is one.
For sources from other parties, such as national statistics, public databases, or online platforms, name the source and describe the conditions of access.

4Ethical Limits and Protection of Participants

Data are shared only when it is ethically appropriate. Sharing is not required when it would break the protection of participants, or when it would raise ethical, legal, privacy, or security concerns. Authors respect the consent that the participants gave. For minors, extra care is needed: the parents or the guardians, and the institution, must approve how the data are used and shared.

Type of data	Handling
Surveys, questionnaires, usability tests, and other user study data	Share the data in an anonymized form. Remove names, email addresses, identification numbers, and device identifiers. Check whether a combination of details, such as age, occupation, and location, could identify a person.
Interviews, focus groups, and recordings	These are usually not shared in full. Share anonymized excerpts, the coding scheme, or the interview guide. Share recordings only with the clear consent of the participants.
Experimental, measurement, sensor, and simulation data	Sharing is encouraged, in open formats and with a description of the units, the instruments, and the conditions. Remove personal data and location details that could identify people or sensitive sites.
Data from social media and other online platforms	Share only as far as the terms of service of the platform and the privacy of the users allow. Where the content cannot be redistributed, share derived data, identifiers, or a description of how the data were collected.
Drawings, designs, and models	Share drawings, CAD models, and building models when the authors hold the rights and the owner or the client agrees. Do not share confidential client or proprietary information.
Source code, trained models, and analysis scripts	Sharing is encouraged, so that others can verify and reproduce the analysis. State the version and the dependencies, and attach a license. Proprietary or third party code is shared only when it is permitted.
Research instruments	Questionnaires, interview guides, and test protocols are encouraged as supplementary material when the authors hold the publication rights. See the section on third party material on the Licensing page.
Data about organizations, projects, and sites	Share only when the organization, the project, or the site cannot be identified, or when the owners agreed to be named, and when sharing creates no security or safety risk.

Security and safety. Data or code that could create a security or a safety risk, for example details of an unpatched vulnerability or of critical infrastructure, should be shared in a responsible way. The Data Availability Statement explains the limits.

Data about participants must stay confidential, as required by the Publication Ethics. Confidential data must not be uploaded to generative AI tools, as stated in the Generative AI Policies.

5Repositories and Licenses

Topic	Policy
Repositories	Authors are encouraged, but not required, to deposit the data that can be shared in a trusted repository that issues persistent identifiers, such as a DOI. Examples are Zenodo, Open Science Framework, Figshare, Mendeley Data, and institutional repositories.
Code	Platforms such as GitHub or GitLab are useful for development. For citation, a fixed release of the code should be archived in a repository that issues a persistent identifier, such as Zenodo.
License for data and code	Authors attach a clear license to the data and the code that they deposit, so that the terms of reuse are known.
License of the journal	The CC BY 4.0 license covers the published article. It does not automatically cover data or code that are held elsewhere. See the Licensing page.

6Information at Submission

Step	What the authors do
1. State	Say at the submission whether a data set or code is associated with the manuscript.
2. Identify	If so, give a DOI, a preregistered DOI, a link, or another persistent identifier. Put it in the comments for the editor in the online submission, and in the Data Availability Statement of the manuscript.
3. Allow access	If the identifier is preregistered, provide a private link for the reviewers when they ask for it.
4. Upload	Upload supplementary files together with the manuscript.

7Review and Responsibility

Data sets and code are not formally peer reviewed. The authors are responsible for their soundness, and errors rest with those who produced the data.
Reviewers may ask for the data or the materials that they need to evaluate the manuscript.

Situation	Handling
A significant error in the data after publication	Handled under the Correction and Retraction policy.
A false statement, or data withheld without a legitimate reason when the editors ask for them	May be handled under the Allegations of Misconduct policy.