1. About these notices
Most of these licenses are permissive — MIT, BSD and Apache 2.0 — and ask little of us beyond reproducing the copyright notice and the license text in anything we distribute. That is what this page and the per-app acknowledgments are for. We would rather over-attribute than under-attribute.
No component listed here receives your personal information merely by being present in an app. Which ones actually handle data, and what they get, is set out in the Privacy Policy — that is the document to read if your question is about privacy rather than licensing.
2. Components we commonly use
Grouped by platform. Versions differ between apps and over time, and no single app uses all of these — several use none beyond the platform’s own frameworks.
Apple platforms (iOS, iPadOS, watchOS, macOS)
| Component | License |
|---|---|
| Firebase Apple SDK | Apache-2.0 |
| Google Utilities, Promises, GTMSessionFetcher | Apache-2.0 |
| leveldb | BSD-3-Clause |
| nanopb | Zlib |
| AFNetworking | MIT |
| Google Mobile Ads SDK (AdMob) | Google APIs Terms of Service |
| Google Maps SDK for iOS | Google Maps Platform Terms |
| Google User Messaging Platform | Google APIs Terms of Service |
| Interface components — progress, toast and dialog views | MIT |
Android
| Component | License |
|---|---|
| AndroidX / Jetpack — AppCompat, Compose, Lifecycle, Navigation, Room, DataStore, WorkManager, Security-Crypto | Apache-2.0 |
| Material Components for Android | Apache-2.0 |
| Kotlin standard library and coroutines | Apache-2.0 |
| Glide | BSD-2-Clause, with Apache-2.0 and MIT parts |
| Gson | Apache-2.0 |
| Firebase Android SDK | Apache-2.0, with components under Google terms |
| Google Play services — Location, Maps | Google APIs Terms of Service |
| Google Play Billing Library | Google Play Developer Distribution Agreement |
In specific apps only
| Component | License |
|---|---|
| OneSignal SDK | MIT |
| Meta (Facebook) SDK | Facebook Platform License |
| AppsFlyer SDK | AppsFlyer Services Agreement |
| Parse SDK | BSD-3-Clause |
| Third-party advertising SDKs | Each provider’s own terms |
| React Native and its modules | MIT |
Apple’s and Google’s own operating-system frameworks are used under their respective developer agreements and are not listed individually.
3. The exact list for one app
This page is the common set, not a manifest for a particular binary — each app ships its own subset at its own versions. For the authoritative list for a specific app and version:
- where an app has an acknowledgments or licenses screen, it is under Settings → About, and it is generated from what that build actually contains;
- otherwise, email support@wrightscsapps.com with the app name and version from its About screen, and we will send you the complete list with license texts.
4. Full license texts
We will provide the complete, unmodified text of any license covering a component in one of our apps, free of charge, on request to support@wrightscsapps.com.
Copyleft components. Where an app includes a component under a license that entitles you to its source — LGPL, MPL or similar — we will supply the corresponding source for that component, or a written offer for it, on the same request. We avoid such components in shipped apps precisely so this stays a straightforward undertaking rather than a complicated one.
5. Our own code
Everything in our apps that is not a third-party component is © 2008–2026 Wrights Creative Services, L.L.C., all rights reserved, and is licensed to you under §3 of the Terms of Use rather than under an open-source license. The presence of open-source components in an app does not place our own code under their licenses.
6. Corrections
If you are the author of something we use and we have attributed it incorrectly, named the wrong license, or missed you entirely, please tell us at hello@wrightscsapps.com. We will correct it promptly and ship the fix with the next release of the affected app. We regard an attribution error as a defect on our side, not a dispute.