1. Scope

This draft describes how k4k3ru may handle information when people or software systems visit the website, use the API, purchase usage credits, or contact the project. k4k3ru is API-first market-data infrastructure with Console for browser-based account access.

2. Information we may handle

• Contact and account information voluntarily provided by a user.
• API requests, timestamps, usage quantities, operational responses, and security logs.
• IP addresses, user-agent information, error events, and abuse-prevention signals.
• Public blockchain transaction details associated with usage-credit purchases.

3. How information may be used

Information may be used to operate and secure the service, authenticate requests, deliver market data, account for usage credits, verify payments, diagnose failures, prevent abuse, provide support, and improve documentation.

4. Providers and public networks

Infrastructure, communications, security, blockchain, payment, or market-data providers may process information where required to deliver the service. Blockchain transactions are public and may remain observable. Production providers must be identified or categorized in the effective policy.

5. Retention and security

Information should be retained only as required for operational, security, accounting, dispute-resolution, and legal purposes. Exact periods require approval. Reasonable safeguards should be used, but no internet or blockchain service can guarantee absolute security.

6. Rights and choices

Depending on applicable law, individuals may have rights to request access, correction, deletion, restriction, objection, or portability. The effective policy must provide a verified privacy contact and request procedure.

7. External services

Documentation, GitHub, and X operate under their own privacy terms and may collect information independently when visited.

8. Changes and contact

Material changes should update the date shown above and include additional notice where appropriate.