XchangeEXPERIMENTAL XRD

XCHANGE / DOCUMENTATION

Community and data policy

Understand shared content, account information and corrections.

2026-10-13 · Xchange

01

Sharing and visibility

This site supports scientific data exchange. Metadata, contributor names, institutions, patterns, structures and review notes are publicly browsable, including pending and not-approved records. Download approval controls files and ZIP archives, not preview confidentiality.

Submit only material you have permission to share. Do not upload confidential projects, sensitive personal information, credentials or data that cannot be redistributed.

02

Quality and review

Contributors should describe experiments, sources and uncertainty accurately. Human review, XMatcher candidates and calculated peaks support assessment but do not replace independent scientific validation. Feedback should address the data and offer actionable corrections.

03

Licensing and attribution

State the applicable license and source when submitting. This policy does not assign one universal license to all records. Before reuse, check record and upstream terms, preserve contributor and publication attribution, and contact the project lead when permissions are unclear.

04

Accounts and privacy

Accounts store username, email, optional organization, password hash, role, download approval and registration time. Legal names are not requested. Administrators can inspect account information needed for approvals. A session cookie supports sign-in; browser local storage remembers the interface language. Pages require no third-party tracking or remote fonts.

Passwords are not stored in plaintext. Backups are not additionally encrypted by this application. Data resides on the operator’s machine and in its configured backups. Uploading sends the selected files to the server you are visiting.

05

Correction, removal and retention

Uploaders can correct their records as permitted by review status. Disabling an account preserves contribution identity. Deleted experiments move into private recovery storage, and history and backups may retain copies. There is no automatic retention deadline.

For identity corrections, inappropriate public content or permanent removal requests, contact the project lead with the record ID and reason. Handling must consider active records, history, recovery storage and backups; a web deletion does not immediately erase every copy.

06

Contact and feedback

For data questions, account help, download approval, licensing or security reports, use the contact address below. Include record IDs, the issue and reproducible steps; do not send passwords or sensitive raw data.