Private amounts.
Clear boundaries.

This website

This launch site does not connect a wallet, accept funds or create an account. We do not add analytics, tracking cookies or browser storage. Fonts are served with the site.

The pilot brief builder processes your text in this browser and downloads a file only when you request it. It does not send your brief to us. Your browser or download software may retain the downloaded file. The hosting environment may process routine request information such as IP addresses for delivery and security.

The proposed payment product

The intended design separates client project information, agency allocations and each contractor’s own rate and receipt. This is a design target pending cryptographic integration and authorization testing.

Documents should be encrypted before storage, with explicit recipient access and randomized commitments. Anyone who has already decrypted or downloaded information may retain a copy. Revoking future access cannot erase it.

What may remain public

Wallet addresses, transaction timing, contract interaction patterns, fees and ordinary token deposits or withdrawals can remain public. Those details may allow observers to infer relationships or amounts. Small groups and distinctive payment timing can weaken practical privacy.

Inco uses encrypted state and an authorization/attestation system. Its infrastructure and trust model are part of the assessment; encrypted state alone does not prove our escrow safe or production-ready.

Before real funds

We must publish an evidence-backed privacy boundary, test each participant’s access, assess key recovery and custodial responsibilities, and obtain independent contract review. Payments stay disabled until those gates are addressed.