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.

Information you provide

Depending on the interaction, you may provide a name, business contact, organization details, workflow requirements, support request, or information needed to configure a product. Do not submit passwords, seed phrases, private keys, or other secrets through public forms.

Technical and usage information

The site and services may process device, browser, network, request, diagnostic, and usage information needed to deliver, secure, measure, and troubleshoot a requested interaction. Retention and logging depend on the relevant service and deployment.

Agent Exchange and MCP/API interactions

When an agent or MCP client uses the Agent Exchange, the service may process request inputs, tool name, authentication context, service status, payment reference, result, receipt, and operational logs needed to execute and verify the request. Do not send data beyond the requested purpose.

GitHub App and repository data

If you install or authorize a PrivateDAO GitHub App, the service may receive the repository, installation, account, webhook, and read-only repository context needed for the requested integration. PrivateDAO does not require repository access for the public website or free MCP discovery.

Authentication, payments, and public ledgers

Authentication data is handled by the relevant product or integration. Payment and transaction references may be retained for reconciliation and support. Blockchain records are public and may be permanent; PrivateDAO cannot delete data already committed to a public ledger.

External providers

Wallets, networks, hosting providers, analytics, AI providers, repositories, and other integrations process information under their own policies. PrivateDAO only presents an integration as available where the relevant product path supports it; review the provider terms before use.

Cookies, local storage, and browser processing

Some product interfaces may use cookies, session storage, local storage, or browser-side encryption and proof generation to preserve a workflow or reduce data exposure. Clear local browser data when you no longer want that local state.

Security and retention

PrivateDAO uses access controls, scoped processing, encrypted channels, operational monitoring, and bounded public verification surfaces where applicable. Information is retained only for the operational, security, accounting, dispute, or legal purpose applicable to the service, subject to technical and public-ledger limits.

Your choices and international services

You may contact PrivateDAO to request support, correction, clarification, or deletion where the applicable service and law allow it. PrivateDAO services may be operated across providers and locations; use the contact below for a request about a specific interaction.

Policy updates

This policy may change as products, integrations, and legal requirements develop. The current version is published at this route and applies from its stated publication date.

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 or data requests, contact legal@privatedao.org. For security disclosures, use security@privatedao.org. Include the relevant public reference and never email private keys or seed phrases.