Open Source Compliance
1. Overview
Mobile-ID is committed to complying with all regulations related to Open Source Software (OSS) used in its products and services.
This page provides transparent information about the use of Open Source Software (OSS), applicable licenses, and necessary compliance requirements for Mobile-ID and related parties.
2. Transparency Commitment
Mobile-ID is committed to transparency in the use and compliance with open-source software licenses applied in its products and services.
We maintain a public open-source repository to:
- Fully fulfill our obligations under the OSS license.
- Facilitate customer, partner, and stakeholder verification and evaluation of compliance.
- Demonstrate our long-term commitment to the open-source community.
Mobile-ID respects the copyright and licensing terms of all open-source projects used.
We sincerely acknowledge and thank the global open-source community for their contributions and development of the many software projects we use in each of our products and services!
Contact:
support@mobile-id.vn
for further inquiries.
3. List of Applicable Licenses
Mobile-ID uses open-source software components under the following licenses:
- MIT License.
- BSD License (2-Clause, 3-Clause).
- Apache License 2.0.
- ISC License.
- Zlib License.
- LGPL (GNU Lesser General Public License, v2.1, v3).
- MPL (Mozilla Public License 2.0).
- EPL (Eclipse Public License 2.0).
- CDDL (Common Development and Distribution License).
- GPL (GNU General Public License, v2, v3).
- AGPL (GNU Affero General Public License).
4. Open Source Code Repository
This repository is intended to support compliance review, assessment, and fulfillment of source code disclosure obligations under applicable OSS licenses.
5. AGPL Compliance Notice
- Mobile-ID is committed to transparency in the use of Open Source Software (OSS).
- Certain components within the Mobile-ID product/service ecosystem are licensed under the GNU Affero General Public License v3 (AGPL-3.0).
- AGPL is a license with specific obligations for systems that provide services over a network.
5.1 Scope of AGPL applicability
AGPL compliance obligations may arise when:
- A partner integrates AGPL components of Mobile-ID into its own system.
- A partner modifies, customizes, or extends AGPL components.
- A partner deploys, operates, or provides services (SaaS / hosted services) based on AGPL components.
- A partner redistributes software or services containing AGPL components.
5.2 Partner compliance responsibilities
Partners are responsible for proactively assessing and fully complying with AGPL-3.0 obligations, including but not limited to:
- Providing Corresponding Source Code to users who interact with the software over a network.
- Preserving copyright notices, license terms, and author attributions.
- Not imposing additional restrictions or conditions contrary to AGPL.
- Ensuring compliance with the AGPL Network Use clause.
5.3 Disclaimer
- Mobile-ID provides this information for open-source license transparency purposes only.
- Mobile-ID does not provide legal advice regarding compliance with AGPL or other OSS licenses.
- Partners bear full responsibility for assessing legal risks, determining source code disclosure obligations, and ensuring OSS license compliance within their systems.
5.4 Relationship between Mobile-ID and partners
- Mobile-ID does not represent partners in AGPL compliance matters.
- The provision of APIs, SDKs, software, or services by Mobile-ID does not imply that Mobile-ID assumes AGPL compliance responsibilities on behalf of partners.
- Any obligations arising on the partner side are the sole and independent responsibility of the partner.
6. Legal Notice
The content on this page is provided for informational purposes only and does not constitute legal advice, contractual commitments, or legal compliance guarantees for any third party.
7. OSS & Compliance Contact
If you have questions regarding:
- The list of OSS used.
- Open-source licenses.
- Source code provision requirements under licenses.
Please contact:
8. Update History
- 20/10/2016 – Open-source repository published.
- 07/09/2022 – Customer support email added.
- 10/02/2025 – Updated transparency policy & bilingual open-source license information.