Shipping and Delivery Policy

Brihat does not generally ship physical goods as part of core service delivery. Project outputs are delivered digitally through repositories, secure links, cloud environments, documentation systems, or approved collaboration channels.

Depending on engagement scope, deliverables may include architecture documents, source code, design assets, deployment scripts, test records, runbooks, training materials, and support handover documents.

Timelines are defined in statements of work, project plans, sprint cycles, or milestone schedules approved with the client.

Actual timelines can change due to scope evolution, dependency delays, client-side approvals, compliance requirements, or force majeure events.

Delivery acceptance criteria are documented in project agreements. Formal handover occurs after agreed checkpoints, including validation, sign-off, and knowledge transfer where applicable.

Certain deliveries depend on third-party services such as cloud platforms, app stores, payment partners, and client-managed environments. Brihat is not responsible for delays solely caused by third-party or client-controlled systems.

Post-delivery support, stabilization, and enhancement windows are defined by contract. Unless explicitly included, ongoing support is handled as a separate managed services scope.

If any engagement requires physical shipment of media, hardware, or printed documentation, shipping terms, ownership transfer points, and risk treatment will be defined separately in writing.