PrivateDAO remains open source where the license applies and visible for judges and ecosystem reviewers while protecting founder authorship, brand identity, digital proof artifacts, and sensitive product packaging.
After the active judging window, PrivateDAO will move the commercial service flow into a fully encrypted client lane: intake, package selection, provider routing, on-chain payment reference, time-limited access, delivery, renewal, and upgrade decisions will be bound to the customer's selected privacy and intelligence requirements.
The defensive license layer is designed to revoke access, erase locally sealed service material, and stop execution when tampering is detected. It is not designed to damage user devices or third-party systems.
After Phase 2, the roadmap moves into Mainnet deployment preparation and external security review. Phase 3 opens the same protected infrastructure cross-chain so sensitive institutions can use broader blockchain rails while Solana remains the guardian chain, first proof home, and decision layer that anchors the system.
The payment transaction hash can become the customer's activation reference after settlement confirmation.
QVAC handles local emergency and private briefs; external rails add wallet, market, identity, and simulation context.
Sensitive source, policy matrices, and anti-tamper logic move behind auditor and partner review after the public judging phase.
This notice is intended to protect the public-good review posture of PrivateDAO while keeping the path open for judges, auditors, Solana ecosystem contributors, partners, and serious institutional collaborators. It is not a substitute for formal legal counsel or a signed commercial agreement.
The repository remains open source where the repository license applies, and the website remains available so judges, auditors, partners, and ecosystem reviewers can inspect the work. Review access does not grant permission to impersonate PrivateDAO, redeploy official surfaces, reuse brand identity, or commercialize official service packages without written coordination.
Source files that explicitly remain under AGPL-3.0-or-later keep the rights and duties of that license. PrivateDAO brand, product design, documents, evidence packets, roadmap material, media assets, service packaging, and official deployments are reserved unless separately licensed.
On-chain transaction hashes, Supabase receipt traces, runtime proof packets, screenshots, and submission evidence are preserved as PrivateDAO review artifacts. They may be cited for evaluation, security reporting, and ecosystem coordination, but not copied into misleading or competing official claims.
PrivateDAO is open to ecosystem collaboration, audits, pilots, and official integration work. Open-source forks must respect the repository license; brand use, official-looking derivative deployments, commercial packaging, or government/institutional reuse should be coordinated through official PrivateDAO channels first.