Docs & Transparency

Documentation & radical transparency

Privacy tools only earn trust through honesty. Here's what INCOGNITO is, how data is handled, and the risks you should understand.

Technical documentation

Architecture overview, module boundaries, and intended integration points.

Security architecture

No client-side key storage, server-side secrets, and explicit approval for sensitive actions.

What is collected, what is local, and what controls you have — written plainly.

Dependencies

Next.js, React, TypeScript, Tailwind, shadcn/ui, and Lucide icons power the interface.

Data handling

Where your information goes

A plain-language map of what stays on your device, what would be sent out, and what is kept server-side.

Processed locally

Wallet-connection UI state (demo)
Privacy preference toggles
Draft agent configurations
Theme and interface settings

Sent to external services

Nothing today — the prototype has no live backend
Future: AI model requests, if you enable them
Future: RPC/network reads, if connected

Kept server-side (by design)

API keys and privileged credentials
Any future secret or signing operation
Rate-limiting and abuse protection

FAQ

Straight answers

Risk disclosure

Interacting with Web3, AI, and experimental software carries risk, including loss of funds, data exposure, and software defects. INCOGNITO is provided as-is for exploration. Nothing here is financial, legal, or security advice. Never share private keys or seed phrases with anyone, including anyone claiming to represent INCOGNITO.

Documentation & radical transparency

Where your information goes

Processed locally

Sent to external services

Kept server-side (by design)

Straight answers

Is INCOGNITO a working, live product?

Are my conversations or data encrypted or anonymous?

Does connecting a wallet do anything real?

Is there a token I can buy?

Has the project been audited?