We Built an App in 36 Hours. Who Actually Owns It?
Built something at a hackathon or in class? A student's plain look at copyright, team ownership, event rules, and school IP policies before launch.
“Nearly re-enrolled in English class while reading a lease.”

Theology · Scripture Cards
Open a scripture card
Already read and shared by 315 people.
The New Covenant in My Blood
Luke 22:19-20
He took bread, and when he had given thanks, he broke and gave it to them, saying, “This is my body which is given for you. Do this in…
Read this card
The Jar Was Not Empty
1 Kings 17:14, 16
For Yahweh, the God of Israel, says, ‘The jar of meal will not run out, and the jar of oil will not fail, until the day that Yahweh sends…
Read this card
Unto Us a Child Is Born
Isaiah 9:6
For a child is born to us. A son is given to us; and the government will be on his shoulders. His name will be called Wonderful Counselor…
Read this card
Your God, My God
Ruth 1:16
Ruth said, “Don’t urge me to leave you, and to return from following you, for where you go, I will go; and where you stay, I will stay.…
Read this card
Take Heart, It Is I
Matthew 14:27, 31
But immediately Jesus spoke to them, saying, “Cheer up! It is I! Don’t be afraid.” … Immediately Jesus stretched out his hand, took hold of…
Read this card
The Lord Will Fight for You
Exodus 14:13-14
Moses said to the people, “Don’t be afraid. Stand still, and see the salvation of Yahweh, which he will work for you today; for you will…
Read this card
Bread from Heaven
Exodus 16:4
Then Yahweh said to Moses, “Behold, I will rain bread from the sky for you, and the people shall go out and gather a day’s portion every…
Read this card
My Heart Rejoices in the Lord
1 Samuel 2:1-2
Hannah prayed, and said, “My heart exults in Yahweh! My horn is exalted in Yahweh. My mouth is enlarged over my enemies, because I rejoice…
Read this card
Key Takeaways
- Copyright usually starts automatically.
- Read hackathon IP rules before you build.
- Get team ownership in writing.
General information, not legal advice. Rules vary by state and can change; check the official sources linked in this guide.
Thirty-six hours, four energy drinks, one sketchy pizza, and an app that actually works. Then someone on the team said, "We should launch this for real," and another person said, "Wait, can we?" That's how I ended up searching who owns the code i wrote at a college hackathon.
Quick reality check: I code; I don't practice law. Intellectual property questions depend on the event rules, your school's policies, and what your team agreed to.
Copyright starts automatically
In the U.S., original code is generally protected by copyright as soon as it's written down. The wiki on copyright basics gives a solid overview, and the Copyright Office has a plain page on what copyright protects. Ideas themselves usually aren't covered; the specific expression, like your code and design files, often is.
Team projects get complicated
When several people write parts of the same project, ownership can be shared. That can mean everybody needs to agree on big decisions like licensing or selling. Questions I'd sort out with the team, ideally in writing:
- Who owns what percent, if anyone plans to make money?
- Which open-source license, if any, are we using?
- What happens if someone leaves?
- Who controls the GitHub repo and domain?

Read the event rules
Many hackathons have rules about intellectual property. Some say teams keep everything. Some give partner companies certain rights to submissions. Search the rules page for "intellectual property," "license," or "ownership." If you signed up through a form, that checkbox counted.
School policies can matter
Some universities have IP policies, especially when school money, labs, or staff are involved, or when work happens for a class. Ask your tech transfer office or check the student handbook.
Using libraries and code snippets? Watch the licenses. The wiki on fair use explains why copying someone else's work isn't automatically okay just because it's for a project.
What about patents?
Most hackathon apps don't go there, but if you think you invented something truly new, the wiki on patentability requirements explains the general bar. Talking publicly about an invention can affect patent options in some cases, so ask your school's IP office before a big demo if that's on your mind.
Most of the time, the real answer is: get your team on the same page early. Then launch the thing, and maybe use your first user signup to impress someone in your CS lab.
Know someone stuck with a landlord or billing problem? Pass this along.
Pick an app — it just sends the link, nothing else.
Frequently Asked Questions
Do I own code I write at a hackathon?
Often you have copyright in what you write, but event rules, team agreements, and school policies can change that.
Can hackathon partner companies claim my project?
Some events give partner companies rights. Read the official rules.
What if my teammates want different things?
Put an agreement in writing about ownership and licenses.
Can my university own my project?
Sometimes, depending on its IP policy and resources used. Ask your school.