Engagement scope
Operational software, infrastructure, assessment, integration, or implementation work must be separately scoped and agreed before work begins.
Terms
Website terms and public-form boundaries.
This website explains Epyk Systems' current services, portfolio, assessment offer, and long-term direction. Actual work begins only under an agreed scope.
Website use
The site is informational until a separate scope is agreed.
Nothing on the public site creates a services agreement, compliance certification, security audit, legal opinion, safety certification, or implementation commitment.
Portfolio labels
Portfolio entries use maturity and provenance labels to separate production work, active development, prototypes, architecture, research, and future concepts.
No unsupported claims
Public examples are sanitized and do not imply certifications, client results, savings, partnerships, or deployment claims unless explicitly stated.
Public form limits
Do not use public forms for controlled or sensitive material.
Do not submit passwords, credentials, export-controlled information, CUI, ITAR-controlled technical data, proprietary customer files, or other sensitive material through this public form.
The public contact and assessment forms are intended for initial inquiry and intake only. If a project may involve controlled, restricted, proprietary, safety-critical, cybersecurity, legal, or regulatory material, the appropriate handling method must be discussed before that material is shared.
Next step
Questions about scope or form limits?
Use a general inquiry first and avoid sending sensitive details until the boundary is clear.