Privacy policy

Scope of this notice

This page describes the data that Coinkun's dashboard, API and public pages process today. It will be replaced by a reviewed policy that names the operating entity and its hosting environment.

Data in the application

Account creation stores an account identifier, a digest of the Transfer Key and related key records. The API can also accept an optional merchant profile containing first name, last name, email, country, organization type and a preference for product updates. The dashboard creation form does not request these profile fields. Key preparation and address generation add public derivation and ownership records. Payment monitoring stores transaction IDs, block references, observation times, input references, conflicting transactions, output indexes and amounts. The raw Transfer Key is returned once and must be kept private by its holder.

Invoices and public information

Invoices store amounts, expiry, payment status, callback and return URLs, and merchant-supplied user-data. Anyone who knows an invoice's link or identifier can read its public data, including user-data; an unguessable link is not a private customer-data store. Merchants should not put identity documents, secrets or unnecessary personal details in these fields. Account IDs also give access to public account information such as balances and history. Blockchain addresses and transactions are public and may be linkable to a person.

Payment and notification records

Coinkun stores transfer intents, recipient addresses, amounts and fees, idempotency keys, input reservations and signed transaction bytes for safe retries. Callback records include callback destinations, merchant-supplied data, payment payloads and HTTP attempts with bounded response bodies and headers. These are server-side records, not browser preferences. Their access, backup and retention rules will be set out in the final policy; no automatic deletion policy is promised here.

Data in your browser

The dashboard uses necessary session access. Cookie settings controls optional storage of public Account IDs and the dashboard, documentation and explorer themes. The privacy choice itself is stored to apply your decision. Public widget illustrations have no configuration fields and collect no customer information. Removing browser data does not delete server-side records.

Infrastructure and logs

Coinkun's servers create operational logs. The hosting provider, subprocessors, access controls, backup handling, retention schedule and any international transfers will be documented in the final policy. No blanket promise of anonymous use or zero data collection is made here.

Information still to be published

• The legal operator, registered address and privacy contact.
• Processing purposes and the applicable legal basis for each purpose.
• Retention and deletion rules, including operational backups.
• Actual service providers and any cross-border data arrangements.
• A verified process for privacy requests and complaints.

Questions and requests

A privacy contact will be published with the final policy. Until then, do not send identity documents, secrets or payment credentials to an unverified address.