Blog
In Practice 6 min read13 January 2026

Data protection in the hackathon: how to prepare real data

Working with real data is the core of the format, and that is exactly why the framework is clarified beforehand, not during the sprint.

Before the sprint

Two to three weeks beforehand is enough, if the right people are at the table early.

  • Set data classes: what may go into which tool
  • Provide test data spaces and access
  • Check data processing agreements and tool approvals
  • Name a contact person from IT/compliance for the sprint day

During the sprint

Teams work in approved spaces, critical data is pseudonymised. Every exception is documented.

Afterwards

Prototypes go into the IT handoff with a clear description of data flows, which makes the decision on production use considerably easier.

Meet the AI training obligation and build something

Book a Discovery Call

Discovery Call

Book a discovery call

In about 30 minutes we clarify which roles are affected by Art. 4 EU AI Act, where your AI literacy stands today and which real task works as a hackathon challenge.

Participants at a Corporathon AI hackathon

Tim Jamboula

Founder, Corporathon

cal.com/jamboula

Pick a slot

Pick a free slot — 30 minutes, no strings attached.

The calendar is embedded via Cal.com. That loads an external script which only starts after your consent.

FAQ

Frequently asked questions

What decision-makers want to know before the first hackathon, kept short and to the point.

Book a Demo