Version 2026-08-11-v1

Third-Party Notices

Last updated: 11 August 2026

This page lists third-party software and assets intentionally used in HisaBooks public builds. It is an operational notice page, not a replacement for the license text included with each dependency or final platform build.

Commercial-use control. AARK reviews third-party software and assets before production release and keeps licence evidence for approved builds.

1. Fonts

HisaBooks uses the Inter typeface in web builds.

File: assets/fonts/Inter-VariableFont_opsz,wght.ttf
License: SIL Open Font License 1.1
Copyright holder: The Inter Project Authors
Source: github.com/rsms/inter

Production packaging allows only approved font files. Unused or unapproved font files must stay out of public release bundles.

2. Web JavaScript libraries

The web application includes selected local vendor scripts so document export and security setup can work without runtime CDN dependencies.

jsPDF - file js/vendor/jspdf.umd.min.js, MIT license based on the vendor file header.
jsPDF AutoTable - file js/vendor/jspdf.plugin.autotable.min.js, MIT license based on the vendor file header.
QR/TOTP helper - file company/js/totp_qr.js; source and license comments must remain preserved in the file.

Vendor headers and license comments must not be stripped from production assets.

3. Mobile and desktop dependencies

The Android mobile applications and desktop application use package-managed dependencies from their respective package lock files. Release-build notices should be generated from the exact package lock files used for the mobile submission or desktop installer and included or made available where the dependency licences require it.

Mobile source: mobile-app/package-lock.json
Desktop source: desktop-app/package-lock.json
Server release assets: files selected by deploy/public_html_allowlist.txt using the same blocked-file rules as the package builder.
Desktop runtime: Electron and Chromium notices must be included with the distributed installer or release materials.

Current notice reports are generated as Markdown and JSON from the exact lock files and public distribution asset list, including SHA-256 hashes for server distributed files. Mobile apps must not include subscription purchase, checkout, or pricing links. Store declarations must match the exact SDKs and permissions in the final build.

4. First-party assets and screenshots

HisaBooks logos, app icons, marketing screenshots, and product imagery are treated as first-party AARK/HisaBooks assets only when they were created by AARK, created for AARK, or otherwise licensed for HisaBooks commercial use.

Logo and icon files must have creator/source, approval date, rights holder, and commercial-use confirmation.
Marketing screenshots must be captured from HisaBooks-owned UI with demo or synthetic data only.
Screenshots must not show real customer data, unapproved third-party logos, competitor UI, stock imagery, or government/bank/payment-provider marks unless permission is recorded.

5. Provider marks and public references

References to providers such as Stripe, Cloudflare Turnstile, Expo, Google Play, hosting, email, DNS/CDN/security edge, or professional advisers are descriptive references to integrations or operating providers. Provider logos, badges, or trade marks should be used only when the applicable brand guidelines permit that use.

6. Questions

If you believe a notice is incomplete or a third-party work is incorrectly attributed, contact AARK NETWORK PTE. LTD. at support@hisabooks.com.