Resources
NDAs and Confidentiality

Some website work involves private business information: unreleased offers, internal processes, credentials, patient or customer context, campaign plans, pricing, code, and operational details. I handle that information with practical restraint.
When an NDA makes sense
I 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 me to provide one, tell me during intake.
An NDA does not replace good access practices. It supports them.
How private information is handled
I 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. I do not reuse private client materials in another project.
If a case study, testimonial, screenshot, or public portfolio mention needs approval, I keep that separate from private working access.
Access and offboarding
Access should be role-based where possible. I 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 I will not claim publicly
I do not publish confidential metrics, private technical details, client quotes, screenshots, or project specifics without permission.
For portfolio work, I 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.
More Working with LER Docs

Your LER Client Portal
How clients use myaccount.lerws.com for support, billing visibility, site requests, and account access.

How We Communicate During a Project
How LER keeps website projects clear through email, WhatsApp, Asana, shared boards, and direct founder-led updates.
Related topics