TreeHacks rules claim no IP; code must be built during hacking hours

The TreeHacks site, the 2026 Ultimate Guide (a Google Doc linked from the event's materials) and the code of conduct (TreeHacks/policies on GitHub) contain no IP, licensing or assignment language. The guide does say 'All building must have taken place during hacking hours' and that ideation and planning beforehand is allowed, so a prior idea is fine but bringing existing code is not. Devpost submission is required for judging and travel reimbursement. Stanford's own IP policy covers Stanford students and inventions made with 'more than incidental use' of non-public university resources per its student best-practices guide. Sponsor prize terms are separate and were not verified.