Shipping Policy

banner
banner
banner

Last updated: April 7, 2026

ByteForge Global FZCO ("ByteForge", "we", "our", or "us") is a technology consultancy firm. As a provider of digital and professional services, we do not ship physical goods. This Shipping Policy outlines how we deliver our digital deliverables, services, and outputs to our clients.

1. Nature of Deliverables

All deliverables provided by ByteForge are digital in nature. These include, but are not limited to, software applications, source code, design files, reports, documentation, data models, automation workflows, and strategic recommendations. No physical products are produced or shipped as part of our services.

2. Delivery Method

Digital deliverables are shared with clients through secure, agreed-upon channels including:

Email: Documentation, reports, and smaller files are delivered directly to the Client's designated email address.

Cloud Storage: Larger files, design assets, and project folders are shared via secure cloud storage links (e.g., Google Drive, Dropbox, or similar platforms), as agreed with the Client.

Version Control Repositories: Source code is delivered via private repositories (e.g., GitHub, GitLab, or Bitbucket), with access granted to the Client upon project handover.

Staging / Production Deployment: For web and mobile applications, final deliverables may be deployed to a staging or production environment as specified in the Statement of Work.

Project Management Tools: Updates, milestones, and interim deliverables may be communicated through project management platforms (e.g., Notion, Jira, Trello), as agreed.

3. Delivery Timeline

Delivery timelines are established in the Statement of Work (SOW) or project agreement specific to each engagement. Timelines are estimates based on information available at the time of agreement and are subject to change if the project scope is modified or if the Client delays in providing required materials or approvals. ByteForge will communicate any anticipated delays in writing as soon as reasonably practicable.

4. Milestone-Based Delivery

Most projects are structured around milestones. Each milestone represents a defined set of deliverables agreed upon at project inception. Upon completion of each milestone, ByteForge will notify the Client and share the relevant deliverables for review and approval. The Client is expected to review and provide feedback within the timeframe specified in the SOW.

5. Client Acceptance

Upon delivery of each milestone or final project, the Client is required to review the deliverables and provide written acceptance or detailed feedback within the agreed review period (typically five to ten business days). If no feedback is received within this period, the deliverable will be considered accepted. Acceptance marks the transfer of ownership rights as described in our Terms and Conditions.

6. Revisions and Corrections

Any revisions or corrections requested after delivery will be assessed against the agreed scope. Revisions that fall within the original scope will be addressed at no additional cost during the warranty period. Out-of-scope changes or requests received after the warranty period may be subject to additional fees and will be quoted separately.

7. Third-Party Dependencies

Delivery timelines may be impacted by third-party services, API providers, or platform constraints outside ByteForge's control. ByteForge will proactively communicate any such dependencies and work with the Client to find suitable solutions.

8. Contact Us

If you have any questions about delivery timelines, formats, or this Shipping Policy, please reach out to us:

ByteForge Global FZCO
A1, Dubai Digital Park, Dubai Silicon Oasis, Dubai, UAE
Email: hello@byteforge.com
WhatsApp: +971 508 945 608