Who owns your work?

The short answer: you do.

Everything you submit through an Ewance challenge — the scoping document, the pitch, the final deliverable, the code, the design — remains your intellectual property. You retain ownership, copyright (where it applies), and the right to do anything you like with it.

We need a few practical rights to make the platform work — covered below — but you are the owner.

What you can do with your submissions

Without asking anyone:

• Put it in your portfolio. Personal website, online portfolio, behance, github, anywhere.
• Use it in interviews. Walk a recruiter through your slide deck. Open your codebase live. Show your design files.
• Submit it as coursework (if your programme allows credit for outside work — that's between you and your institution).
• Adapt it into other formats — turn a market analysis into a blog post, turn a research deliverable into a conference poster.
• Sell it, license it, or commercialise it — though see "edge cases" below for things to check first.
• Decline to share it publicly at all. Ewance never publishes your submission. The credential is public; the submission stays private unless you choose otherwise.

What we ask of you

A few narrow rights, all about making the platform itself work:

• We can reference the title and discipline of challenges you completed when you make your profile public. This is how a recruiter discovers you. You can opt out and keep your profile private.
• We retain the right to verify the cryptographic anchor of your credential — i.e. we can confirm "yes, this is the credential we issued." This is what makes the credential trustworthy in the first place.
• We store a hash of your submission (not the submission itself, just a cryptographic fingerprint) so the credential is tamper-evident. Your actual work stays in your storage.
• If reviewer feedback is included in your record, we retain the right to keep the feedback record alongside the credential. You can request access to it any time.

That's it. We don't claim a licence to your work. We don't get a cut if you commercialise it. We don't republish it.

Submissions stay private by default

Your final submissions are not published by Ewance. They are not added to a public catalogue. They are not shared with recruiters automatically.

What is public is the credential — the fact that you completed challenge X, with the issuance date and your name. The submission itself stays in your account, visible to you and to the reviewer who evaluated it.

If you want to share a submission with a specific recruiter, you do that directly. We facilitate the conversation; we don't broker the artefact.

Team submissions

If you worked on a challenge as part of a team, each team member co-owns the deliverable in proportion to their contribution. The default assumption is equal contribution; reviewers can weight this if there's a documented imbalance.

Practically:

• Each team member can use the deliverable in their own portfolio.
• No team member can stop another from doing so.
• Commercial use of the deliverable (e.g. building a startup on the idea) typically requires agreement from all team members — but that's general copyright law, not an Ewance rule.

We recommend teams discuss commercial intent before they start the challenge if there's any chance of it. After the fact is harder.

Edge cases worth checking

A few situations where ownership has a wrinkle you should be aware of:

You used a real organisation as your case study

Some challenges suggest a fictional company. Some let you pick a real one for context. If you publicly publish work that's framed around a real, named company, normal defamation and brand-use rules apply — that's between you and the company, not Ewance.

Your work used open-source code, data, or assets

Standard rules: respect the licences of anything you incorporated. MIT-licensed code is fine to ship; GPL code has copyleft implications; some datasets have non-commercial clauses. If your final submission incorporates third-party work, you're responsible for the licence compatibility. Ewance doesn't do this audit for you.

You're enrolled in a programme that claims student IP

Some universities, fellowships, or sponsored programmes assert rights over student work. This is between you and them. Ewance doesn't override your institution's policies — if your programme claims your work, that claim still applies. Check your handbook before submitting work you might want to commercialise.

The challenge brief explicitly says "Ewance-shared"

A small subset of challenges may be marked as Ewance-shared — meaning Ewance retains a non-exclusive licence to publish anonymised highlights for marketing or research. This is always stated up front on the challenge page before you accept it. If you don't see that label, you keep everything.

In one line

Your work is yours. We take only what we need to make the credential trustworthy. Everything else stays with you.

---

You've reached the end of the Learning track. Recruiter view: Recruiting track. Reference and pricing: Reference.