Software licences and acknowledgements

Effective: 11 October 2026 · Version 1.0.0

Jepify uses open-source software and some third-party assets. This page explains where legally required notices belong, how to report attribution problems, and why a version-specific notice bundle is different from a general list of technologies.

Your rights under open-source licences

Libraries in Jepify can be governed by their own open-source terms. The applicable component licence takes precedence for that component when it grants rights that these Terms of Service do not. Using the app does not cancel your rights under MIT, Apache, BSD, MPL or another applicable licence.

Licence text, copyright notices, attribution requirements and NOTICE files must be reproduced when required by the licence, not replaced by this summary page.

Mobile application

The current application architecture includes packages from ecosystems such as React, React Native, Expo, Firebase and related components. These are examples, not a complete and verified inventory of what a particular mobile release actually includes.

An app-build-specific licence snapshot should identify relevant packages, versions, copyright holders, obligations and required full texts. Some obligations depend on whether a dependency is distributed in the binary or used only to build or run servers. The app is designed to show these notices under More → Settings → About → Open-source licences. Where required, bundled notices should remain available without a network connection.

Website and backend

The website uses Astro and other dependencies. Backend service dependencies and bundled scripts are separately inventoried. Obligations of website, server and client dependencies are evaluated by distribution and use, not indiscriminately copied from the entire development lockfile.

Visual assets and external services

Third-party photographs, icons, flag graphics, fonts and artwork may have licence or attribution conditions that differ from software licences. The visual-asset register should record each asset’s source, author if required, permitted use, modifications and specific credit wording. A stock image described as ‘free’ is not automatically public domain or free of attribution conditions.

External service providers (cloud hosting, authentication, push notifications, crash reporting) may also have terms, data-processing arrangements and trademark requirements. Service contracts are not automatically open-source licences.

Release-specific licence inventory

A dedicated public Licences & Credits page is being prepared in a separate GitHub change, with the eventual release-specific inventory generated from the app and site pipelines. This page alone is not a representation that every production dependency and artwork credit has already been enumerated. The final inventory must reflect the actual distributed version.

If a reciprocal licence requires source availability, installation information or another legal obligation, that requirement is handled for the affected component. Nothing on this page waives it.

Missing credits or licence issues

If you believe required credit, licence text or copyright information is missing, write to support@dynamikus.com with the component/asset name, where it appears and the issue. Do not send unrelated family data.

See also the Legal Centre and Privacy notice.