Loading target date…

Participation guidelines

Your personal profile, shared team project, optional discovery preferences and final submission.

Current personal profile agreement

student-profile-2026-09-27-v2

  • I have read the participation guidelines and my track's data and scope rules.
  • I agree that authorized programme staff may use my personal profile to manage my participation, verification and team formation. This does not opt me into discovery, messages or external AI processing. Sensitive identity details remain restricted to authorized staff.
  • I commit to the declared weekly availability, coordination with my team, any later programme-coordinated Libya–US team partnership, and the final pitch on 20 October 2026.

These three acknowledgments apply to the new personal-profile flow. Previously recorded agreement versions stay unchanged. Optional sharing permissions are separate.

Team formation

  • The current team-size limits will appear here once the platform settings are available.
  • Eligible participants from Libyan International University (LIU), Roya Academy, Clarkson University and University of Benghazi — Business Incubator may form mixed-institution teams within the same event. Each participant retains their real institution on their profile.
  • One active team and one shared team project are used for your event participation. Older personal ideas remain saved as drafts and do not become extra judging submissions automatically.
  • Invited students complete only a personal profile and explicitly accept the invitation. If verification is pending, the claim is saved without private team access; resume after verification to recheck eligibility, invitation validity and available places.
  • Programme administrators manage verification and operational reviews. Project management controls sensitive team actions; team membership does not grant administration or judging permissions.
  • Keep invitation links private. Opening a link does not join a team. Before a claim is saved to an authenticated account, the invitation is remembered only in its browser tab for up to 24 hours; another tab or device may need the original link again.

Personal profiles, privacy and discovery

  • Each participant completes a personal profile. You can seek a team without an idea. A team registers its shared project once; new content is written in English while the interface remains available in Arabic and English. Unchanged older content is preserved.
  • Completing registration does not publish your profile, allow messages or authorize external AI processing. After verification, Discover → Participants provides separate visibility and chat-request preferences. Existing preferences are not reset when you update your personal profile.
  • Review the fields and attachment visibility described by the discovery preferences before enabling them. Phone numbers, email addresses and institutional identifiers are not directory fields. Chat starts through a request that the recipient can accept or decline, with blocking controls.
  • Smart suggestions are advisory. Local rules work without external AI; external processing requires its own explicit consent. Suggestions do not assign membership or decide judging results. You can change optional preferences later without rewriting historical agreement records.

Final open-source delivery

  • By 25 September, each group submits its working prototype, code repository, documentation and final slide deck.
  • The latest successful upload becomes active while previous versions and integrity metadata remain retained and access-controlled.
  • Readiness evidence tracks completion and is separate from the final pitch decision. Five winning teams are recognized on 20 October.

Track data and scope rules

Smart Agriculture & IoT

  • Prototypes must run on low-cost, locally available components.
  • Document the sensing, power, water-flow and field assumptions behind every irrigation decision.

Data Literacy: Privacy Analytics

  • No personally identifiable or sensitive real-world data at any stage.
  • Every dataset must be classified, its source documented and its privacy or ethics basis stated.

Entrepreneurship: Sandbox FinTech / APIs

  • No live payments, wallets, bank accounts or real financial data.
  • All transaction flows must be clearly labelled as simulated.