A client hands over photos, brand assets, customer data, and internal documents over the course of an engagement, and without an explicit clause covering ownership and usage rights, both sides are left assuming things that were never actually agreed. That gap surfaces awkwardly later, when a portfolio use, a retention question, or a data request has no clear answer.
A data ownership clause doesn't need to be complicated. It needs to answer a few specific questions plainly, before they come up as a dispute.
Assumption isn't a clause, and client-supplied data needs a real one
Without an explicit clause, both sides operate on assumptions about what happens to supplied materials, assumptions that often turn out to differ once something specific is actually at stake. Write the terms down rather than relying on shared, unstated understanding.
Name explicitly what stays the client's, not implied by default
State plainly that client-supplied assets, photos, data, brand materials, remain the client's property throughout and after the engagement. This should never be left implied, even though it's usually the obvious intent.
In Stelaah, client-supplied files and assets stay attached to the client record with clear provenance, so what came from the client versus what was produced during the engagement stays distinguishable. See how files works.
Define your own usage rights during and after the engagement
Specify exactly what you're permitted to do with client-supplied materials, use them to produce the deliverable, reference them internally, and separately, what you can do with the resulting work afterward, portfolio use, case studies. These are different rights and deserve separate, explicit terms.
Address deletion and retention directly, not leave it unstated
State what happens to client-supplied data after the engagement ends, deleted after a defined period, retained for a stated reason, rather than leaving retention as an open question a client might reasonably ask about later.
Cover what happens if the client-supplied materials turn out to be flawed
If a client supplies inaccurate data or improperly licensed material that later causes a problem, responsibility for that should sit with the client, not be silently absorbed as your liability. State this explicitly rather than leaving it to assumption.
A simple checklist
If you do nothing else, do these five things:
- State explicitly that supplied assets remain the client's property.
- Define your usage rights during and after the engagement separately.
- Address retention and deletion directly, not as an open question.
- Assign responsibility for flawed or improperly licensed materials to the client.
- Never leave data ownership to unstated, shared assumption.
Do that, and client-supplied data has clear, agreed terms from day one, not a question that only gets answered awkwardly when it actually matters.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
