Effective Date: April 1, 2026
Approved By: Legal
Owner: Software and AI Teams

1. Purpose

To enable the safe and lawful use of open source software and protect Ambiq’s intellectual property
rights, while managing legal, operational, reputational, and business risks associated with third-party
code.

2. Scope

Open source software (OSS) is software made available under a license that permits use, modification,
and redistribution of its source code, subject to specific license terms and conditions. Ambiq encourages
the appropriate use of OSS and supports contributions to relevant OSS projects.
This policy applies to:

All Ambiq employees and contractors.
All software and AI software development, including firmware, embedded systems, drivers,
SDKs, tools, models, simulations, and internal tooling.
All OSS usage, modification, distribution, contribution, and release decisions.

This policy applies to code developed in the course of your work for Ambiq. It does not apply to code
that you develop without the use of any Ambiq intellectual property on your own time with your own
equipment that is unrelated to and does not compete with Ambiq’s present or future business activities.
This policy should also be considered in light of our other policies, including the Generative AI Chatbot
Usage Policy and our Code of Business Conduct and Ethics. Violations of this policy may lead to
disciplinary action, up to and including termination.

3. Using OSS

OSS use is permitted if the license is deemed compatible with Ambiq’s business model and license
obligations. See Exhibit A (OSS License Approval Matrix).

If your intended use or the OSS license does not appear on Exhibit A, then contact
Legal@Ambiq.com to request review using the format provided in Exhibit B (OSS Review Request
Form). NOTE: Make sure to allow sufficient time for discussion and review – if the OSS license is not
approved for use, then your schedule needs to permit time to find alternatives.
Software and AI engineers are responsible for the source code deliverables provided by independent contractors to ensure they comply with this policy and are documented appropriately.

Automated scanning (e.g. Blackduck or equivalent) should be used to validate compliance with this
policy during preparation for release. Confirm with your department lead to confirm when this step
should be executed in your workflow and which tool to use.

Software Bill of Materials should be generated for each release.
Any issues flagged during a scan should be resolved by developers – with support from Legal as
needed – before release.

Modifications should be documented and license obligations reassessed, if needed. Changes should be
tracked and maintained by the Software and AI teams.

Legal will provide information regarding compliance obligations such as attribution and distribution of
notices. Software and AI engineering is responsible for implementation and compliance.

4. Contributions to OSS Projects

In certain circumstances, we may determine that we want to voluntarily publish software we have
developed under an open source license or contribute to an external OSS project (e.g. Zephyr Project).
This may include creating a public GitHub repository or publishing internal tooling.

Any proposed contributions must be reviewed and approved by Legal and VP, Software & Solutions or
Head of AI as appropriate. See Exhibit C for the review request template.

Contributors are responsible to ensure that contributions do not expose
confidential/proprietary information.
Proper Ambiq copyrights (and trademarks, where appropriate) must be included.
Certain contribution types/projects may be pre-approved, with individual review reserved for
exceptions or non-standard cases. Consult your team lead.

5. General Copyright Compliance

5.1 Software

All software incorporated into Ambiq products or development environments must comply with
applicable copyright law. Developers must not attempt to avoid license obligations by rewriting or
reformatting third-party code while retaining its underlying structure or logic; derivative works may still
be protected. Ambiq software shall be marked with our Company’s Copyright Notice and any applicable
third-party notices.

5.2 Non-Software Content

This section applies to all non-code copyrighted materials, including:

Technical documentation
SDK documentation
Diagrams and schematics
White papers
Marketing materials
Images, graphics, and design assets
Training materials
Website content
Benchmark data

Any third-party copyrighted material may only be used if licensed for the intended use, or written
permission has been obtained (including through a contractual assignment or work for hire). Only Legal
can determine whether a license exception (e.g. fair use) applies.

Exhibit A: OSS License Approval Matrix

GO

Pre-approved to use code licensed under these licenses for all use cases.
Include original copyright notice and license text in all distributions.

Public Domain
BSD (2- or 3-Clause)
MIT
Apache 1.1 or 2.0 (not
1.0)
Artistic License
PHP License
Python Software
Foundation License
zlib/libpng License
Boost Software License
OpenSSL/SSLeay
License
WTFPL
CC0 (public domain
dedication)
Creative Commons
Attribution-Only (“CC
BY”)
ISC License
Unlicensed
Any software licensed
under a choice of
multiple licenses that
include any of the
above.

CAUTION

Pre-approved to use code licensed under these licenses internally only.¹
Legal approval is required to distribute code. See Exhibit B.
If approved, Legal will provide compliance requirements.

GPL 2.0 (only when a
standalone process)
LGPL (v2.1, v3) (only
when dynamically
linked)
Mozilla Public License
1.1 or 2.0 (“MPL”)
CDDL
CPL or IBM
Eclipse Public License
GPL 2.0 + plus exception
(such as linking,
Classpath, or FOSS
exception)
Apache 1.0

¹ Code libraries in a development tool that must be used in a distributed product at run-time (such as those included in SDKs or APIs) must be analyzed as distribution.

STOP

Consult Legal to use any code licensed under these licenses.
Recommend researching alternatives.

GPL 3.0/3.0+
Affero GPL
Sleepycat
GNU Documentation
License
Creative Commons
ShareAlike (“CC BY-SA”)
SSPL
Open Software License
Academic Free License
Any license requiring
public disclosure of
proprietary source code
Any license imposing
field-of-use restrictions
conflicting with Ambiq’s
business mode

Exhibit B: OSS Review Request Form

Include the following information in your request to Legal and VP, Software & Solutions or Head of AI:

Date:
Requestor Name:
Component Name:
Version:
License (include link or attach copy):
Intended Use (internal tool, embedded firmware, SDK, other (describe)):
Intended Product:
Intended Customer(s):
Will Ambiq modify the code? (Yes/No)
Will Ambiq distribute externally? (Yes/No)
How will Ambiq link the code? (Static/Dynamic)
Business justification:

VP, Software or Head of AI Approval:
Legal Review:

Exhibit C: OSS Contribution Request Form

Contributor Name:
Project Name:
Repository URL:
Description of contribution:
Does this expose Ambiq proprietary techniques or trade secrets?
Is there a particular OSS license required for the contribution? (Provide terms)
Contributor License Agreement required? (Attach if applicable)
Business rationale:

VP, Software or Head of AI Approval:
Legal Approval:

Сopyright and Open Source Software Policy