Pablo Nieto • about 1 month ago
The XPRIZE Transparency Paradox: Broken Infrastructure, Zero Confidentiality, and the IP Liability Trap
Hi everyone,
Like many of you, I joined this competition inspired by the massive societal impact of building agentic AI ecosystems. However, after carefully auditing the official rules, looking at the dead-on observations from other participants like Nishtha and Marcos, and hitting the infrastructure brick wall, we need to talk about the massive structural tension in this hackathon.
Right now, the organizers are asking us to build real, revenue-generating entities while simultaneously forcing us into a severe legal and technical liability trap.
Here is the cold, hard reality of what we are facing:
1. The Legal Nightmare: Section 9 vs. Proprietary Codebases
The criteria demand that we submit a full, working source code repository. Yet, Section 9 (Entry Conditions and Release) explicitly states: “The relationship between you, the Entrant, and the Sponsor and Administrator, is not a confidential, fiduciary, or other special relationship.”
There is formally zero duty of secrecy or non-disclosure on their end once we hand over our code.
To make it worse, according to Section 6, the judges are completely anonymous by design and can change at any time.
We are being asked to expose proprietary business logic and backend architectures to legally unbound, anonymous third parties. No serious founder or technical engineer can accept this without basic NDA protections.
2. Handing Over Customer PII and Core Business Intelligence
Per Section 4 (Submission Requirements), the organizers can request actual “customer contact information (name, email, phone)”.
This isn't just a compliance issue; it’s a massive liability under global data protection laws (like GDPR/CCPA) to hand over real customer PII to an administrator that has disclaimed all confidentiality obligations.
We are also required to hand over exhaustive financial records, month-by-month revenue breakdowns, and corporate IDs before even knowing if our IP is legally safe.
3. Broken Infrastructure and Zero Technical Support
The platform-wide failure of the $100 Google AI Ultra/Antigravity bonus overage mechanism has left teams completely dead in the water.
The redemption deadline passed with participants hitting rigid baseline quotas and getting locked out of their workspaces.
The official response telling us to simply look at the generic "free tier" links is an absolute brush-off.
We are being heavily judged on our ability to "Sell, Market, and Grow" a business, yet the promised building resources are non-existent, and zero support has been allocated for user acquisition. Expecting developers to fund out-of-pocket marketing budgets just to compete fairly creates a massively uneven playing field.
A Call for Action from the Organizers
We are putting in the hours, the sweat, and the engineering to build production-grade solutions. But we cannot build with confidence when the platform is technically broken and legally predatory.
We urgently need the XPRIZE team to address three things immediately:
An explicit, binding confidentiality amendment or NDA framework for all judges accessing private repositories.
An immediate extension and fix for the workspace infrastructure credits.
Clear guidelines on how we can shield sensitive business intelligence and customer data during the submission process.
If we don't demand clarity now, we are just giving away our hard-earned innovations for free to an unaccountable system. What is everyone else's strategy to protect their IP under these conditions?
Log in or sign up for Devpost to join the conversation.

3 comments
santiago nery figueredo pombo • about 1 month ago
ya dieron alguna respuesta?
Brandon Rodríguez • about 1 month ago
Any answers yet?
Justin Brezhnev Manager • about 1 month ago
Greetings Pablo! Thank you for your question. Judges adhere to confidentiality and nondisclosure of project submissions. Private repos should be shared with testing@devpost.com and judging@hacker.fund to ensure sufficient protections during the judging process. The hackathon contest is designed to compliantly handle PII. As for any names you are not able to share, feel free to cross them out or similarly anonymize. Hope this helps!