AppGrout Use limited to your engagement.
Confidential information is used to evaluate, review, or repair your app within the agreed purpose. Your code and project materials remain yours.
Confidentiality & NDA
Your source code, business logic, customer information, and unpublished plans deserve clear boundaries. We agree on confidentiality before you share private project materials.
An NDA before private project access.
Start with a high-level description of the issue, without credentials or confidential code. Before private materials are exchanged, both parties agree on and sign a non-disclosure agreement. You can propose your own NDA for review.
This page explains the intended working process. It is not a signed agreement and does not itself create an NDA; the agreement signed by both parties sets the terms.
No publicity without permission.
We do not publish your private code, screenshots, findings, or project details in portfolios, case studies, or marketing without your written permission.
Know who has access.
Personnel, contractors, and additional reviewers must be bound by confidentiality obligations. Access is limited to what they need, and any disclosure or approval required by the accepted agreement or data-protection law still applies.
Agree on tools and data handling.
Privacy-vetted AI tools may assist delivery, but Client material is not used to train shared models and results remain subject to human review. Stricter confidentiality or data-processing terms are agreed when a project needs them.
Keep access narrow and revocable.
- Prefer staging environments and synthetic or redacted data.
- Use named repository invitations and project-specific permissions.
- Never paste passwords, API keys, or private keys into an inquiry form.
- Revoke access at handover and follow the agreed return or deletion procedure.
Confidentiality is separate from permission to test your systems. The engagement scope also needs to identify the systems, environments, and activities you authorize.