Terms of Service
Review the operational guidelines that govern our diagnostic scoping, code ownership transfer, and technical system liability.
Operational Agreements & Engagement
By interacting with this website, submitting a project brief, or requesting a diagnostic assessment, you agree to coordinate under these terms. All project milestones, deliverables, and financial compensation protocols will be strictly governed by a separate, bilateral Master Services Agreement (MSA) or Statement of Work (SOW). No engineering work will commence prior to signature of these documents.
Bilateral Code Ownership
Unless specified otherwise in a custom Statement of Work, all original source code, API pipelines, custom database schemas, configurations, and interface layouts engineered by NERQIVA will be fully transferred to the client upon receipt of final project payments. NERQIVA retains no licensing hooks, proprietary locks, or runtime restrictions on your shipped systems.
Infrastructure Liability Limits
NERQIVA builds systems to highly rigorous, type-safe production standards. However, we do not claim liability for runtime outages caused by external infrastructure APIs or third-party hosting partners (such as Vercel, Supabase, AWS, or Stripe). Risk mitigation is achieved through automated fallback pipelines and operational error tracking.
These terms govern scoping interactions. Production systems and project deployments executed for clients are bound exclusively by independent Master Services Agreements (MSAs).
Tell us the problem.
We'll figure out exactly what should be built — and what shouldn't.