Source or repository review
Source review may require confidentiality terms, scope limits, and clear expectations about copying, reuse, benchmarking, or derivative work.
Access terms
Some diligence requests require confidentiality terms before sensitive materials are discussed. This page explains when terms may apply, what reviewers should expect, and why access is scoped manually instead of treated as an automatic data-room gateway.
If access terms are appropriate, follow-up happens after a request is reviewed for app fit, intended use, mission alignment, safety risk, and app-specific readiness.
Current access model
Access terms may be required before sensitive materials are shared.
This page is informational and is not a live e-signature status tracker.
NDA or access-term steps are handled through the controlled review process.
Access terms do not guarantee data-room access, source review, or transfer materials.
When terms may apply
Terms are scoped to the review purpose, material sensitivity, and implementation context so buyers can evaluate responsibly without turning controlled artifacts into public collateral.
Source review may require confidentiality terms, scope limits, and clear expectations about copying, reuse, benchmarking, or derivative work.
Apps connected to survivor safety, crisis training, legal support, or sensitive service delivery may require additional context before walkthroughs or internal materials are shared.
Commercial conversations may involve technical, roadmap, brand, or transfer information that should not be treated as public.
Pilot or deployment conversations may involve organizational workflows, security assumptions, access models, or staffing considerations that should be reviewed carefully.
Reviewer expectations
These expectations help protect the people and communities connected to the work while preserving a useful buyer review process.
Start with the diligence request form. If terms or an NDA are appropriate, the next step will be handled manually after review.