No fake proof
No fabricated customers, testimonials, reviews, case studies, partner badges, offices or performance numbers.
No unnecessary custom build
If a proven existing product solves the requirement well, NEXAL should recommend using it instead of rebuilding it.
Scope before surprises
Deliverables, exclusions and important dependencies should be defined before implementation. Material changes require discussion and approval.
Acceptance criteria
Projects should have a clear basis for determining whether the agreed work is complete rather than relying on vague “done” claims.
No unsupported security or compliance claims
Security, privacy and regulatory requirements are treated as requirements. NEXAL does not claim legal certification or guaranteed compliance without an appropriate basis.
Customer data and handover
Customer-supplied business data and content remain the customer’s. Agreed access, credentials and documentation are handed over according to the project scope.
AI does not remove accountability
AI may speed up research, drafting, testing or implementation, but production decisions and delivered work remain subject to human review and project responsibility.
Support is defined, not assumed
Maintenance, hosting, monitoring and post-launch support are clarified before launch so neither side relies on unstated expectations.
Trust should be inspectable
Use the company and verification pages to check NEXAL’s official identity and contact routes.