1. Overview
This page describes how Zyora Global approaches software licensing, intellectual property, open-source use, and compliance practices across client engagements. It supplements—but does not replace—project-specific contracts, statements of work, and license schedules.
2. Client Deliverables and Ownership
Unless otherwise agreed in writing, ownership of custom software, designs, and documentation created specifically for a client is typically transferred to the client upon full payment for the applicable deliverables, subject to any retained background IP described below.
Project agreements generally specify:
- Which artifacts are considered deliverables (source code, designs, documentation, deployment scripts, etc.)
- Milestones or acceptance criteria tied to license grants or ownership transfer
- Whether Zyora retains rights to pre-existing tools, frameworks, libraries, or know-how used across multiple clients
- License terms for staging, production, and third-party hosting environments
3. Background IP and Reusable Components
Zyora Global may use and retain rights to general methodologies, non-client-specific code utilities, development templates, and technical know-how developed before or during an engagement ("Background IP"). Clients typically receive a perpetual, non-exclusive license to Background IP embedded in deliverables, solely as necessary to use the deliverables for their intended purpose.
4. Open-Source Software
We frequently use open-source libraries and frameworks to deliver secure, maintainable solutions efficiently. Open-source components remain subject to their respective licenses (for example MIT, Apache 2.0, BSD, or GPL where applicable).
For client projects we:
- Prefer permissive licenses where practical for client-facing products
- Document material open-source dependencies in project repositories or handover documentation when requested
- Flag copyleft or restrictive licenses that may affect distribution models before incorporation
- Comply with attribution and notice requirements of applicable open-source licenses
5. Third-Party and Commercial Licenses
Some solutions require paid third-party APIs, SDKs, fonts, stock assets, cloud services, or SaaS subscriptions. Unless the agreement states otherwise, the client is responsible for procuring and maintaining licenses for third-party services used in production.
We will identify commercially licensed components during discovery when they materially affect project cost or architecture.
6. Website and Marketing Content
Content published on https://zyoraglobal.net—including text, branding, illustrations, blog articles, and layout—is owned by Zyora Global or its licensors and is protected by applicable intellectual property laws. You may not reproduce or redistribute Site content without permission, except for personal reference or as allowed by law.
7. Compliance and Security Practices
We design solutions with security, privacy, and regulatory context in mind. Specific compliance obligations depend on the client's industry, geography, and data types processed. Common frameworks and standards we align with when relevant to a project include:
- GDPR and CCPA principles for privacy-conscious data handling
- HIPAA-aligned engineering practices for health technology projects
- SOC 2–oriented controls for SaaS and cloud deployments where required
- PCI DSS awareness for payment-adjacent systems
- ISO/IEC 27001 and secure SDLC practices for enterprise engagements
- Industry-specific requirements discussed during discovery (for example pharma, fintech, or education)
7.1 Important note
Reference to a standard or framework does not mean Zyora Global or a specific deliverable is certified under that standard unless explicitly stated in a signed agreement or official attestation. Compliance is a shared responsibility between Zyora and the client, including configuration, policies, hosting choices, and ongoing operations after delivery.
8. Confidentiality
We treat client business information, credentials, and project materials as confidential unless they are publicly available or disclosure is required by law. Mutual non-disclosure terms are typically included in client agreements or may be executed separately upon request.
9. Warranties and Support
Warranty periods, defect remediation, and post-launch support are defined in project contracts. Unless otherwise stated, deliverables are provided with a limited warranty covering material conformance to agreed specifications for a defined period after acceptance.
Ongoing maintenance, security patching, and compliance monitoring may be offered under separate support or retainer agreements.
10. Audits and Documentation
Upon reasonable request and subject to confidentiality obligations, we can provide documentation supporting license compliance, dependency inventories, and security practices relevant to a delivered project. Formal audit rights, if any, are governed by the applicable client contract.
11. Questions
For licensing, compliance, or intellectual property questions related to a current or prospective engagement, contact:
- Zyora Global
- Email: info@zyoraglobal.net
- https://zyoraglobal.net/contact
- Ahmedabad, Gujarat, India and Houston, Texas, USA