Freelance Confidentiality Clauses: What Should You Look Out For?

Confidentiality clauses are common in freelance contracts.

They can be perfectly reasonable: clients often need to protect commercially sensitive information, customer data, unreleased products, internal processes or other material that should not be shared.

The difficulty comes when the wording is so broad that it becomes hard to tell what you are actually allowed to say, keep, reuse or show later.

The important question is not simply:

“Do I have to keep things confidential?”

It is:

“Exactly what information is protected, how long does the obligation last, and what am I still allowed to do?”

What is a confidentiality clause?

A confidentiality clause requires one or both parties to protect certain information and restrict how it is used or disclosed.

It may cover things such as:

• business plans;
• financial information;
• customer information;
• pricing;
• technical information;
• source code;
• designs;
• product plans;
• internal processes;
• trade secrets;
• passwords;
• unpublished work.

The clause may also explain:

• who you can share information with;
• how the information can be used;
• how long the obligation lasts;
• what happens after the project ends.

Why do confidentiality clauses matter to freelancers?

Freelancers often work across multiple clients in the same field.

That means you may need to distinguish between:

• genuinely confidential client information;
• your own pre-existing knowledge;
• general professional skills;
• information already public;
• ideas or techniques you independently develop.

A clause that fails to make those distinctions can create uncertainty about what you are allowed to use in future work.

Confidentiality red flags worth checking

These features do not automatically make a clause unreasonable.

They are simply areas worth understanding before signing.

Everything is treated as confidential

Some clauses define confidential information extremely broadly.

For example:

all information relating directly or indirectly to the Client or its business.

That could potentially cover far more than genuinely sensitive material.

Check whether the definition distinguishes confidential information from information that is already public or commonly known.

There are no exclusions

Many confidentiality clauses exclude information that:

• was already known to you;
• becomes public through no fault of yours;
• is received lawfully from somebody else;
• is independently developed without using the client's confidential information.

If none of these exclusions appears, ask what happens in those situations.

The obligation lasts forever

Some information, such as trade secrets, may need long-term protection.

Other information may lose its sensitivity quickly.

A clause applying indefinitely to every piece of information may deserve closer attention.

Ask whether the duration matches the type of information being protected.

You cannot mention the client at all

Confidentiality wording may effectively prevent you from:

• listing the client on your website;
• showing the work in a portfolio;
• publishing a case study;
• discussing the project publicly.

For freelancers who rely on previous work to attract new clients, this can matter commercially.

The clause covers your own knowledge and skills

Be cautious if the wording appears to prevent you using:

• general experience;
• industry knowledge;
• techniques;
• methods;
• ideas developed independently.

The client may reasonably protect its own confidential information without owning your general professional knowledge.

You are responsible for people you cannot control

A clause may make you responsible for disclosure by:

• subcontractors;
• advisers;
• employees;
• collaborators.

That may be appropriate if you choose to share confidential information with them, but check whether the obligation reflects people you can actually control.

The client can label anything confidential after the fact

Some agreements let the client designate information as confidential at any time.

That can make it difficult to know your obligations when information is first received.

Ask whether there is a clear process for identifying protected information.

Questions to ask before signing

A good confidentiality clause should let you understand what information is protected and how you may use it.

What counts as confidential information?

Is there a clear definition?

Does it cover specific categories of information?

Or almost anything connected with the client?

What information is excluded?

Check whether the clause excludes information that:

• is already public;
• was already known to you;
• is independently developed;
• is lawfully received from another source.

How long does confidentiality last?

Does the obligation end:

• when the project ends;
• after one year;
• after five years;
• never?

Does the duration make sense for the type of information involved?

Can I share information with people helping me?

If you work with:

• subcontractors;
• accountants;
• lawyers;
• insurers;

can you disclose information where reasonably necessary?

If so, what protections must those people follow?

Can I use the work in my portfolio?

If portfolio rights matter, check whether you may:

• name the client;
• describe the project;
• show screenshots;
• display final work;
• discuss results.

You may need explicit permission.

What happens if disclosure is required by law?

Some clauses allow disclosure where required by:

• law;
• court order;
• regulator;
• tax authority.

Check whether the contract explains how this is handled.

Example: a broad confidentiality clause

Consider this fictional clause:

The Contractor shall keep strictly confidential all information relating directly or indirectly to the Client, its business, customers, suppliers, operations and affairs, whether or not marked confidential, and shall not use or disclose such information at any time for any purpose other than the Services.

A freelancer might reasonably ask several questions.

Does “all information” include public information?

The wording does not say otherwise.

What about information I already knew?

There is no obvious exclusion.

How long does the obligation last?

The phrase “at any time” suggests there may be no end date.

Can I mention the project in my portfolio?

The clause appears to prohibit use for any purpose other than providing the services.

Can I use general knowledge gained during the project?

That is unclear.

Those questions do not determine the legal effect of the clause.

They do show why the boundaries deserve attention.

Portfolio use and confidentiality

Portfolio restrictions can matter significantly to freelancers.

Imagine you design a website for a client.

You may reasonably want to show:

• the finished design;
• a screenshot;
• the client's name;
• a short description of your role.

But a broad confidentiality clause may appear to prohibit any disclosure about the project.

If portfolio use matters to you, do not assume it is automatically allowed.

Check whether the contract:

• expressly permits it;
• requires prior written consent;
• prohibits it.

Confidentiality and intellectual property are different

A client owning intellectual property does not automatically answer whether you may talk about the work.

Likewise, retaining ownership of material does not necessarily mean you may disclose confidential information contained within it.

For example:

• the client may own the final design;
• you may retain ownership of your general tools;
• the project itself may still be confidential.

Read the two clauses together.

Confidentiality and non-compete clauses can overlap

Sometimes a client may use both:

• a confidentiality clause; and
• a non-compete clause.

The confidentiality clause protects information.

The non-compete restricts future work.

Ask whether the non-compete is genuinely necessary if the client's main concern is simply preventing misuse of confidential information.

The two obligations serve different purposes.

Client-supplied information

A freelancer may receive large amounts of client information during a project.

Check whether the contract requires you to:

• store it securely;
• limit access;
• delete it after the project;
• return copies;
• notify the client about security incidents.

These obligations may have practical consequences for how you work.

Data protection and confidentiality are not the same thing

A confidentiality clause may protect business information.

Data protection rules may separately apply where you handle personal information.

For example:

• customer names;
• email addresses;
• employee records;
• analytics data.

A confidentiality clause does not necessarily satisfy every data-protection obligation.

If your work involves significant personal data, specialist advice may be appropriate.

What happens when the contract ends?

Some confidentiality obligations continue after termination.

Check whether the agreement requires you to:

• return documents;
• delete files;
• destroy copies;
• remove access;
• certify deletion.

Also consider whether you are realistically able to comply.

For example, information may exist in:

• backups;
• email archives;
• cloud storage;
• source repositories.

The obligations should ideally be practical as well as clear.

Confidentiality and subcontractors

If you use subcontractors or collaborators, the contract may require you to ensure they keep information confidential too.

Check whether:

• subcontracting is allowed;
• client permission is required;
• subcontractors must sign equivalent terms;
• you remain responsible for their conduct.

Do not assume you can share confidential information with another person simply because they are helping you with the project.

Mutual confidentiality

Some contracts protect only the client's information.

Others protect confidential information belonging to both sides.

A mutual clause may matter where the freelancer also provides sensitive material, such as:

• pricing;
• processes;
• proprietary tools;
• business information.

Mutual wording is not automatically better or worse.

The actual definition, exclusions and obligations still matter.

What might clearer confidentiality terms focus on?

The parties may discuss:

• a clearer definition of confidential information;
• standard exclusions;
• a reasonable duration;
• permission to share with advisers or subcontractors;
• treatment of legally required disclosure;
• portfolio permissions;
• return or deletion procedures;
• protection of each party's confidential information.

The appropriate wording depends on the project and the information involved.

PactRivet does not rewrite confidentiality clauses as legal advice. Its role is to help identify the questions worth asking.

Should you agree to a broad confidentiality clause?

There is no universal answer.

A client may have legitimate reasons to protect highly sensitive information.

But before signing, check:

• what information is covered;
• what information is excluded;
• how long the obligation lasts;
• whether you may use general knowledge and skills;
• whether portfolio use is permitted;
• whether subcontractors may receive information;
• what happens on termination;
• whether deletion obligations are practical;
• how confidentiality interacts with intellectual property and future work.

If the potential consequences are significant or unclear, consider getting advice from an appropriately qualified professional.

Check what your contract actually says

Confidentiality clauses can affect portfolio use, future work, intellectual property and the way you handle client information.

The wording in your own contract is what matters.

PactRivet checks freelance service agreements across ten areas, including confidentiality, intellectual property, work restrictions, scope, payment, revisions, termination, liability and disputes.

It highlights wording that may deserve attention and gives you plain-English questions you can take back to the client.

PactRivet provides general information and questions to consider. It is not legal advice.