NDAs and Confidentiality

Privacy dashboard showing sensitive website information, access controls, and compliance-aware decisions

Some website work involves private business information: unreleased offers, internal processes, credentials, patient or customer context, campaign plans, pricing, code, and operational details. We handle that information with practical restraint.

When an NDA makes sense

We can sign an NDA before reviewing private materials or beginning work. This is common for unreleased products, competitive strategy, sensitive internal systems, regulated industries, and work involving private client information.

If your company has a standard NDA, send it before discovery. If you need us to provide one, tell us during intake.

An NDA does not replace good access practices. It supports them.

How private information is handled

We ask only for the access and context needed to do the work. Credentials, account invites, admin access, and code repositories should be shared through appropriate secure methods, not pasted into casual messages.

Your code, content, data, account information, and business materials remain yours. We do not reuse private client materials in another project.

If a case study, testimonial, screenshot, or public portfolio mention needs approval, we keep that separate from private working access.

Access and offboarding

Access should be role-based where possible. We prefer named accounts, temporary access, collaborator roles, or agency permissions over shared passwords.

When work ends, access can be removed, rotated, or reduced based on the support relationship. For ongoing plans, the right access stays in place so support is fast.

If a credential was shared in a less-than-ideal way, rotate it after the work is complete.

What we will not claim publicly

We do not publish confidential metrics, private technical details, client quotes, screenshots, or project specifics without permission.

For portfolio work, we use approved public context and avoid signed-NDA specifics unless the client explicitly clears them.

That is why some proof points stay private until the client approves the exact language.

Working together

Keep the project easy to manage.

If an NDA, approved quote, or restricted screenshot is required, tell us early so the project and case study stay clean.

Contact LER