Skip to content

Privacy and data handling

Privacy Notice

What information the Signal service may process, why it is used, where public blockchain data appears, and what is deliberately excluded.

Important

This MVP privacy notice describes the current operating design and should receive jurisdiction-specific review before broader commercial processing or marketing.

01

Scope

This notice describes how Keelbase Signal handles information associated with visits to the public site, free API requests, x402-paid requests, operational security, analytics, corrections, and direct communications.

Signal is a Parent-owned public intelligence surface. It is not designed to collect or expose private Keelbase Child Vessel records.

02

Information processed

  • Technical request data, such as IP address, request time, requested route, response status, user agent, referral information, and diagnostic or security events that may be processed by hosting infrastructure.
  • Public x402 payment metadata, including payer and recipient wallet addresses, network, asset, amount, transaction hash, block number, resource, and settlement result.
  • Usage and operational measurements such as endpoint, classification, latency, payload freshness, filters, failures, corrections, and support events where those measurements are available.
  • Information voluntarily supplied through a support, correction, business, or other direct communication.

03

Information not intentionally requested

  • Private keys, seed phrases, wallet recovery material, or reusable payment signatures.
  • CDP API credentials, authorization nonces, or wallet-session secrets.
  • Private Vessel or founder information, private agreements, internal identifiers, confidential architecture, private financial data, credentials, signing material, or other non-public operational records.
  • Sensitive personal information that is not necessary to answer a legitimate support, correction, or business request.

04

Purposes

  • Deliver free and paid resources and verify that protected responses are released only after valid settlement.
  • Operate, secure, troubleshoot, maintain, and improve the service.
  • Reconcile payments and distinguish Keelbase tests, disclosed external tests, and genuine organic purchases.
  • Measure product usage, reliability, freshness, demand, corrections, and support needs.
  • Respond to communications, correction requests, security reports, and legal obligations.
  • Protect Keelbase, users, buyers, infrastructure providers, and third parties against abuse or fraud.

05

Payment and public blockchain data

x402 payments use public wallet addresses as payment and protocol identifiers. Successful settlements may be permanently visible on a public blockchain.

Keelbase cannot erase or alter public blockchain records. Keelbase may retain a sanitized internal record of public transaction evidence for reconciliation, audit, security, and accounting.

Payment verification and settlement are performed through the configured Coinbase Developer Platform facilitator.

06

Service providers and disclosure

Keelbase may use infrastructure, hosting, security, payment-facilitation, domain, and operational service providers that process information to provide their services.

  • Information may be disclosed where necessary to operate, secure, or support Signal.
  • Information may be disclosed where required by applicable law, lawful process, or a valid governmental request.
  • Information may be disclosed to investigate abuse, security incidents, payment disputes, or violations of the service terms.
  • Keelbase does not sell private Child Vessel information or personal data to advertisers.

07

Cookies and tracking

The current MVP does not intentionally deploy advertising cookies or cross-site behavioural advertising trackers.

Infrastructure providers may process necessary technical identifiers, request metadata, or security information under their own notices and service terms.

08

Retention

Keelbase retains information only for as long as reasonably necessary for the stated operational, security, correction, accounting, audit, dispute, and legal purposes.

Public blockchain records may remain permanently available independently of Keelbase.

Sanitized settlement evidence and correction history may be retained for long-term auditability. Secret payment authorization material must not be retained in the analytics ledger or public repository.

09

Security

Keelbase applies reasonable technical and organizational safeguards appropriate to the MVP, including credential separation, repository exclusions, bounded responses, payment verification, and restrictions on retained payment artifacts.

No internet or blockchain system can be guaranteed completely secure. Users must protect their own wallets, devices, credentials, and signing processes.

10

International processing

Signal, its users, public blockchain infrastructure, and service providers may operate in different jurisdictions. Information may therefore be processed or made publicly available outside a user’s country.

Applicable mandatory privacy rights remain unaffected.

11

Individual rights and requests

Depending on applicable law, an individual may have rights relating to access, correction, objection, restriction, deletion, portability, or complaints concerning personal information processed by Keelbase.

Requests should use the current official Keelbase contact method and identify the Signal service and the relevant request. Keelbase may need to verify the requester’s identity and authority.

Keelbase cannot remove information from a public blockchain and may retain information where required for legal, security, accounting, audit, or dispute purposes.

12

Children

Keelbase Signal is a business and professional intelligence product and is not intentionally directed to children.

Do not submit information about a child unless it is lawful, necessary, and supported by appropriate authority.

13

Notice updates

Keelbase may update this notice as the product, providers, telemetry, legal obligations, or processing practices change.

The effective date shown on this page identifies the current published version.