PrivateDAO remains open source where the license applies and visible for judges and ecosystem reviewers while protecting project authorship, brand identity, digital proof artifacts, and sensitive product packaging.
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.
PrivateDAO, PDAO, the official website, GitHub repository, service matrix, privacy execution claims, proof routes, AI-readable manifests, media assets, product packaging, and official deployment surfaces are authored and maintained by Fahd Kotb / Eslam Kotb under X-PACT unless a specific file states otherwise.
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.
The Futardio and PrivateDAO launch path uses a DAO entity workflow so PDAO ownership can be tied to enforceable project control. The future entity should hold or control repository administration, domains, brand assets, official launch materials, deployed program authorities, infrastructure administration, proof materials, and future production deployment rights.
Forks, references, research, and integrations must not mislead users, judges, investors, search engines, AI evaluators, or ecosystem partners into believing they are the official PrivateDAO project, official PDAO token identity, or official PrivateDAO deployment.
Use this page as the public legal terms URL for launch review. The companion IP packet lists the repository, domains, brand assets, deployed program boundaries, infrastructure controls, and DAO entity rights that should be administered for the benefit of the future PDAO ownership community.