Privacy without losing confidence.

PrivateDAO is built around a simple boundary: sensitive organizational information should remain limited to the people and systems that need it, while the resulting work can still be checked.

Sensitive inputs stay scoped

PrivateDAO product workflows are designed to limit sensitive information to the people, services, and review scope required for that workflow.

Proof does not mean publication

Verification surfaces may expose a claim, status, or outcome without exposing the original record or private organizational details.

You choose what to share

Where a product supports selective disclosure, the organization decides the verification scope and whether a shared result expires or is revoked.

What we collect

Only what a requested interaction needs.

The public website may receive information you submit through contact or product flows, such as your email address, organization details, workflow description, or technical request. Product runtimes may process workflow data needed to provide the requested operation. The exact data boundary depends on the product and configuration.

Do not submit passwords, seed phrases, private keys, or other credentials through public forms. Wallet and external-provider interactions are controlled by the relevant wallet or service interface.

Verification links and third parties

A public result is not the private source.

A verification link may contain a public status, proof identifier, timestamp, scope, or network reference. It should not be used to publish employee records, private payroll details, confidential bids, or source documents. Integrations such as wallets, networks, hosting providers, and external protocols have their own systems and policies.

Questions or data requests

For privacy questions about a PrivateDAO interaction, contact the project owner at fahd@privatedao.org and include the relevant public reference. Do not email private keys or seed phrases.