Open-Source Licenses & Notices
Third-party components, license attributions, and source code offers
Owner/Operator & Contact
Owner/Operator
Spyface Tech Company, LLC (d/b/a "ClinicBooking")
30 N Gould St Ste N, Sheridan, WY 82801, USA
Contact
Corporate: hello@spyface.com
Support: care@clinicbooking.com
On This Page
Purpose & Scope
This page explains how ClinicBooking honors the licenses of open-source software ("OSS") we use in our websites, mobile apps, APIs, and back-end services. It also tells you where to find license texts and how to request source code when a copyleft license requires it.
Plain-English summary only. The actual license texts govern your rights and obligations for each component. If anything here conflicts with a license, the license controls.
License Families & Obligations (Summary)
Below is a high-level overview of common OSS licenses. Always consult the full license text.
Family / Examples
Permissive
MIT, BSD-2/3-Clause, ISC, Apache-2.0
Key Duties (Typical)
Keep copyright & license notices; include NOTICE if present (Apache-2.0).
Redistribution
Allowed in proprietary works; source disclosure not required.
Patent Terms
Apache-2.0 includes express patent license & termination on patent suits.
Notes
Common in web/libs; low friction.
Family / Examples
Weak Copyleft
LGPL-2.1/3.0, MPL-2.0
Key Duties (Typical)
Publish modifications to the library (LGPL/MPL); allow relinking; provide notices.
Redistribution
Linking allowed if you allow user relink/replace (LGPL); MPL files remain MPL.
Patent Terms
No special patent grant in LGPL-2.1; MPL-2.0 provides patent grant.
Notes
We honor relinking obligations when distributing object code that links LGPL code.
Family / Examples
Strong Copyleft
GPL-2.0/3.0
Key Duties (Typical)
If you distribute binaries, you must provide corresponding source code (or a written offer).
Redistribution
Derivative works must be GPL when distributed.
Patent Terms
GPL-3.0 adds explicit anti-tivoization & patent terms.
Notes
We provide GPL source on request per Section 3 below.
Family / Examples
Network Copyleft
AGPL-3.0
Key Duties (Typical)
Provide source to users who interact with the program over a network.
Redistribution
Service interaction triggers source availability obligations.
Patent Terms
As in GPL-3.0.
Notes
We make available AGPL source to network users if/when applicable.
Family / Examples
Content
CC BY, CC BY-SA
Key Duties (Typical)
Credit the author; share-alike if BY-SA.
Redistribution
Reuse allowed if attribution (& SA where applicable).
Patent Terms
Patents not typically addressed.
Notes
Used for some docs, images, icons; we preserve attribution.
| Family / Examples | Key Duties (Typical) | Redistribution | Patent Terms | Notes |
|---|---|---|---|---|
Permissive MIT, BSD-2/3-Clause, ISC, Apache-2.0 | Keep copyright & license notices; include NOTICE if present (Apache-2.0). | Allowed in proprietary works; source disclosure not required. | Apache-2.0 includes express patent license & termination on patent suits. | Common in web/libs; low friction. |
Weak Copyleft LGPL-2.1/3.0, MPL-2.0 | Publish modifications to the library (LGPL/MPL); allow relinking; provide notices. | Linking allowed if you allow user relink/replace (LGPL); MPL files remain MPL. | No special patent grant in LGPL-2.1; MPL-2.0 provides patent grant. | We honor relinking obligations when distributing object code that links LGPL code. |
Strong Copyleft GPL-2.0/3.0 | If you distribute binaries, you must provide corresponding source code (or a written offer). | Derivative works must be GPL when distributed. | GPL-3.0 adds explicit anti-tivoization & patent terms. | We provide GPL source on request per Section 3 below. |
Network Copyleft AGPL-3.0 | Provide source to users who interact with the program over a network. | Service interaction triggers source availability obligations. | As in GPL-3.0. | We make available AGPL source to network users if/when applicable. |
Content CC BY, CC BY-SA | Credit the author; share-alike if BY-SA. | Reuse allowed if attribution (& SA where applicable). | Patents not typically addressed. | Used for some docs, images, icons; we preserve attribution. |
GPL/LGPL/AGPL: Source Code Offer
If we distribute any binaries that are subject to GPL, LGPL, or AGPL obligations, we will provide the Corresponding Source by one or more of the following:
- A download link in the app or in a companion NOTICE / LICENSES bundle; or
- A written offer available for at least three (3) years from the last distribution, obtainable by emailing hello@spyface.com or writing to our mailing address (see Contact).
For LGPL components linked into our binaries, we will (as applicable): (a) provide object files to enable relinking with a modified LGPL library, or (b) use dynamic linking that permits end-user replacement of the library, and (c) include the relevant notices and license texts.
Attribution, Notices & Where We Publish Them
- Web: Attributions and license texts are published on this page and/or bundled as downloadable archives.
- Mobile Apps: See "Open-Source Notices" under Settings → Legal (or similar).
- Backend/CLI/Containers: License files are included at /licenses or referenced in image labels and release notes.
- Apache-2.0 NOTICE: We include required NOTICE files and preserve third-party attributions.
- Fonts/Icons/Media: Where third-party licenses require attribution (e.g., CC BY), we include credit in app "About" screens or footer.
Modifications, Contributions & Patch Marking
Where we modify third-party OSS, we mark material changes in commit history and/or change logs and maintain original copyright notices. Upstream contributions are submitted under the project's license (or a contributor agreement, if required).
If a license requires that we make our changes available (e.g., GPL/LGPL/MPL), we will provide the modified source as described in Section 3.
Security, Vulnerabilities & Supply Chain
We curate and update OSS dependencies using industry practices (pinning, checksums, SBOMs, and vulnerability scanning). To report a security issue (including third-party component issues), please see our Security & Vulnerability Disclosure page.
Export Controls & Sanctions
Some OSS components (e.g., cryptography) may be subject to U.S. export laws and applicable sanctions (e.g., EAR/OFAC). By using our software, you agree to comply with all applicable export and sanctions regulations and confirm you are not a prohibited party.
Third-Party SDKs, Analytics & Privacy
SDKs and analytics libraries included in our apps are licensed by their owners and governed by their own terms. See our Privacy Policy and Cookies Policy for tracking disclosures and controls.
Third-Party Components & License Inventory
We maintain an inventory of third-party OSS used in our products. The table below is a template view. The authoritative, current inventory (including full license texts and, where applicable, source bundles) is available on request (hello@spyface.com).
Illustrative Inventory (populate via SBOM)
Component inventory displayed as cards for mobile viewing
Component
(populate)
Version
(x.y.z)
License
(MIT / Apache-2.0 / GPL-3.0 etc.)
Homepage/Repo
link
Source / NOTICE
Included in bundle or on request
Modified?
Yes / No
Used In
Web / iOS / Android / Backend
Component
(populate)
Version
(x.y.z)
License
(LGPL-2.1/3.0)
Homepage/Repo
link
Source / NOTICE
Object files or dynamic linking; notices included
Modified?
Yes / No
Used In
Web / iOS / Android / Backend
Component
(populate)
Version
(x.y.z)
License
(AGPL-3.0)
Homepage/Repo
link
Source / NOTICE
Network source available to users
Modified?
Yes / No
Used In
Service
| Component | Version | License | Homepage/Repo | Source / NOTICE | Modified? | Used In |
|---|---|---|---|---|---|---|
| (populate) | (x.y.z) | (MIT / Apache-2.0 / GPL-3.0 etc.) | link | Included in bundle or on request | Yes / No | Web / iOS / Android / Backend |
| (populate) | (x.y.z) | (LGPL-2.1/3.0) | link | Object files or dynamic linking; notices included | Yes / No | Web / iOS / Android / Backend |
| (populate) | (x.y.z) | (AGPL-3.0) | link | Network source available to users | Yes / No | Service |
Changes, Versioning & Archives
We update this page when we add or remove OSS, change versions, or adjust how notices are delivered. Prior versions of this page and corresponding license bundles are available on request for compliance verification.
How to Contact Us & Request Materials
Email (OSS & notices): hello@spyface.com
Support: care@clinicbooking.com
Mail:
Spyface Tech Company, LLC (d/b/a "ClinicBooking")
30 N Gould St Ste N
Sheridan, WY 82801, USA
Please include: (a) the product/app and version, (b) where you obtained it, and (c) the component(s) you're inquiring about. For GPL/LGPL/AGPL source offers, we aim to respond within 30 days.
Important Disclaimer
Open-source components are provided by their authors on an "AS IS" basis without warranties or conditions of any kind, express or implied, including but not limited to warranties or conditions of title, non-infringement, merchantability, or fitness for a particular purpose. To the maximum extent permitted by law, ClinicBooking disclaims liability arising from third-party OSS included in or used with our products. This page is for transparency and convenience; it is not legal advice.
Looking for privacy or cookies information? See our Privacy Policy and Cookies Policy. To exercise "Do Not Sell or Share" choices, visit our Terms of Service.
