You can usually describe your genuine skills and responsibilities on a resume without reproducing a client’s name, restricted screenshots, customer records, or unpublished figures. Start by checking your agreements and workplace policies: permission determines what may be disclosed, not whether the detail would impress a recruiter. If a particular project cannot be discussed, use an accurate, general task description only to the extent allowed. Never assume a password-protected portfolio or a percentage instead of an absolute number makes restricted information safe.
Sort the evidence into public, approved, and restricted
Before drafting, make a private inventory of what you worked on. Identify public facts, material explicitly approved for external use, and restricted material. Public examples may include a published job title or a named product that your employer openly credits to a team. Approved material may be a sanitized summary cleared by a manager or communications team. Restricted items may include client identities, proprietary designs, system architecture, patient records, employee data, contract amounts, internal financial results, and unpublished launch plans.
This is not a generic rule that all nondisclosure agreements are identical. The exact agreement and organizational policies matter, and sensitive sectors may have additional restrictions. UC Berkeley’s employer-interaction guidance specifically cautions job seekers to protect proprietary information belonging to current and former employers. USAJOBS likewise instructs federal applicants to exclude classified or government sensitive information from resumes. When in doubt, withhold the detail and seek the right approval rather than guessing.
Write the job first and the protected project second
Keep the employer and legitimate job title when they are public and not restricted. In the bullet, focus on what you actually did: prepared user instructions, tested a workflow under supervision, coordinated review cycles, tracked approved work items, or documented handoffs. If even the project identity is restricted, use a broad label only when the context cannot identify the client indirectly. The phrase “confidential client” explains less than a clear, permitted description of a task.
A fictional example: before, “Redesigned Project Orion’s secret checkout for Client Nova and increased sales 27%.” That leaks invented project and client identifiers and implies an unverified result. A safer draft, subject to approval, is “Revised customer-facing form instructions and documented usability issues for the product team.” The point is not that the second sentence is universally permissible; it demonstrates a lower-detail form to check against actual restrictions.

Find evidence that does not reveal protected results
An accomplishment need not include a number to be useful. You might describe the audience, general method, decision, handoff, quality check, or approved deliverable. “Created step-by-step instructions for service agents and incorporated reviewer feedback” is meaningful when it reflects real work and the topic is permitted. Do not invent an improvement rate because numbers look stronger. Do not use figures derived from confidential dashboards, even after rounding, without permission.
Use this practical filter: Could the sentence reveal a person, customer, supplier, unreleased feature, security practice, internal financial result, or an identifiable combination of otherwise innocuous clues? A narrow industry plus geographic hint plus launch date may identify a client even without its name. If so, generalize further or leave it out. Some material is not safe to summarize at all. The employer’s confidentiality terms and your role’s obligations control the boundary.
Separate a public resume from a portfolio or interview
Your resume is a public or semi-public application document. A portfolio link may be shared more widely than expected. Do not upload work screenshots, internal reports, client emails, designs, source code, or customer data just because a recruiter asks for samples. Seek explicit permission for a case study or create a new, wholly fictional demonstration of a similar skill from scratch. Label the demonstration as a sample, not actual client work, and make sure it does not reproduce hidden intellectual property.
For interview stories, prepare an approved example that explains your role, the generic problem, the approach, and what you learned. A useful statement is: “I can discuss my method and my responsibilities, but I cannot share the client’s identity or internal results.” If interviewers require details that are restricted, decline that part and offer a different project. Confidentiality is an ongoing obligation, not an obstacle you should work around by euphemism.

Avoid misrepresenting scope when anonymizing
Anonymization is not permission to inflate your contribution. A contractor who built documentation for a team’s migration should not write “architected the company platform” because technical names have been removed. Likewise, an employee who participated in a review under direction should not claim final approval authority. Identify your actual role and, where relevant, note review or oversight. This helps a hiring reader distinguish transferable ability from leadership claims that are unsupported.
Consider a second hypothetical rewrite. Unsafe: “Reduced a named client’s complaint backlog from 3,200 cases to 600 using confidential queue data.” Potentially usable only if authorized: “Categorized incoming service requests and prepared a weekly exception summary for supervisor review.” If even service categories or methods are restricted, choose an unrelated, permitted example. A weak but truthful bullet is better than a vivid disclosure you cannot undo.
Use a clearance process before you send samples
Ask the appropriate manager, legal team, communications contact, or client for a permitted summary when this is available and appropriate. Keep the approval’s scope: permission to share a sentence in a resume does not necessarily grant permission to show screenshots in a public portfolio. Check every attachment and hyperlink in the final PDF or DOCX. Metadata, comments, tracked changes, file titles, and shared-drive links can also disclose restricted material even when the visible text seems safe.
Before uploading, review each sensitive bullet with a simple decision path: Is it publicly known? If not, do you have appropriate authorization? If the answer is unclear, remove or rewrite it at an approved level. Is your own contribution still accurately represented? Finally, can the resume reader understand the skill without the hidden detail? If not, choose another example rather than forcing a confidential accomplishment into the page.

How We Research Confidential Resume Projects
We relied on UC Berkeley’s explicit conduct guidance about honesty and proprietary information, current USAJOBS resume restrictions on government-sensitive data, and Harvard’s fact-based writing recommendations. These sources support an accuracy-and-permission approach; they are not individual legal interpretations of an NDA, privacy law, or security classification. See Berkeley applicant conduct, USAJOBS resume guidance, and Harvard resume writing. All project examples are invented. See our affiliate disclosure.
More Resume and Cover Letter Guides
Only if the statement is itself permitted and useful. A short note cannot replace checking your agreement and employer policies.
No. A percentage derived from restricted data may still be confidential, and a combination of clues can identify a client.
Access control is not permission. Share a sample only if the content and the method of sharing are explicitly allowed.
Explain that you cannot share restricted material and offer an approved sample or a new fictional demonstration of the skill instead.
Describe permitted tasks, methods, review steps, audiences, and your specific contribution. Do not invent a numerical improvement to make a bullet sound stronger.
