binance / binance/binance-public-data
Clarification requested: private research use of historical Spot Kline archives
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 613
- PR merge metrics
- No merged PRs in 30d
Description
## Request
Binance Customer Support directed this request to the official repository for written clarification about historical data available from https://data.binance.vision/.
## Dataset and intended use
- Binance Spot monthly Kline archives, approximately 2020-01 through 2024-12.
- Private, non-public quantitative research only.
- No trading, execution, account data, or redistribution of raw data.
- No public data API, bulk-download service, or publication of source archives.
## Clarifications requested
1. Which Binance legal entity and authoritative policy or terms apply, including the policy link, version, and effective date.
2. Whether the README Licence: MIT statement applies to the downloadable historical data archives themselves, and how it interacts with any separate Binance Terms of Use or data-use terms.
3. Whether private long-term retention of these archive files is permitted.
4. Whether non-public backtesting and machine-learning model training using the archive data are permitted.
5. Whether non-public derived research outputs may be retained or used internally, provided raw data is not shared.
6. Any restrictions concerning territory, account or authentication, attribution, commercial use, redistribution, sublicensing, or publication of derived outputs.
7. For historical archives, whether applicable terms are determined by the archive coverage period, download date, or the current version of the terms.
8. If this public issue tracker cannot provide an authoritative answer, the appropriate official private escalation channel.
No personal, account, or proprietary data is included in this request. A link to the authoritative written policy would be appreciated.
Thank you.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the request in issue #481 and the historical archives referenced at data.binance.vision. Identify the authoritative Binance policy, applicable entity, version, and escalation channel; done means receiving or linking a written answer that addresses the listed data-use and retention questions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100