POS / Legal & licensing
Legal & licensing
Code licence, trademark use and this site’s privacy practice — kept separate and written plainly.
Last updated: 2026-11-05
Code licence: Apache-2.0
The source code is licensed under Apache License 2.0. You may use, modify and distribute it, including commercially, and sell a derived build without publishing your changes.
When redistributing, keep the licence and copyright notices and include the NOTICE file as required by section 4. The licence also grants patent rights and disclaims warranty: the software is provided “as is”, without warranties of any kind.
Trademark policy
The open-source licence does not include the right to use the project name, logo or icons. The only reason is to keep users from mistaking a modified build for an official release.
- Allowed: factually naming the project in articles, reviews and tutorials, including “based on this project”.
- Allowed: keeping a “Powered by” attribution in a derived build, provided your own build name is equally prominent.
- Not allowed: using the project name or logo as your product, domain or app-store name, or implying official endorsement.
- Not allowed: stripping or replacing official security notices and still distributing under the official name.
For commercial licensing or co-branding, contact us separately.
Privacy (this site)
This site is static: no accounts, no forms, no store data. There is no third-party analytics SDK and no cross-site tracking.
- Access logs: written by your own nginx for troubleshooting and abuse prevention, kept 7 days by default, never used for profiling.
- Language preference: stored in your browser’s localStorage, never uploaded.
- External links: once you follow a GitHub or Gitee link, their privacy policy applies.
- Download counts: if shown, only aggregate release-asset counts, with no personal identifiers.
The client never relays store data through our servers. Cloud features exchange data only after you subscribe and enable them, under separate cloud terms.
Contact
For licensing and trademark matters see the repository README. For security, use the private disclosure channel — not a public issue.