Simple terms for an open project.

Welcome

These terms cover the public Peekling website.

These terms apply when you access or use peekling.com, including its documentation, demonstrations, playground, downloads, and links to public project repositories. The site is operated by Prajwal S. Venkateshmurthy, Peekling's creator, author and maintainer.

By using the site, you agree to these terms. If you do not agree, stop using the site. Repository license files remain the controlling terms for the source code and assets they cover.

What Peekling provides

A public site, open-source code, and working demonstrations.

Peekling provides documentation and interactive examples for a browser character engine and its character packs. The website does not currently provide user accounts, paid plans, hosted AI services, or a promise of continuous availability.

Know what each license covers

Source code, brand identity, and character art have distinct roles.

• The website source, documentation, and build tooling are available under the Apache License 2.0, subject to the accompanying NOTICE and repository files.
• Engine packages and other repositories are governed by the license files published with those repositories.
• Character packs, illustrations, fonts, and third-party materials may carry separate licenses or notices next to the relevant files.

The Peekling name, logo, official character identity, and other brand assets are not automatically licensed for trademark or endorsement use by the Apache License 2.0. Keep copyright, attribution, license, and notice information intact when a license requires it.

Use the project responsibly

Explore, learn, build, and contribute without harming others.

You may not use the site to:

• Break applicable law or infringe another person's rights.
• Attack, overload, probe, or disrupt the site or its providers.
• Bypass security controls or gain access you are not authorized to use.
• Distribute malware or use demonstrations to mislead or harm people.
• Suggest official endorsement or ownership of the Peekling brand without permission.

Build with care

Examples show possibilities, not production guarantees.

The playground, code samples, character interactions, and other demos are educational examples. You are responsible for reviewing an integration, choosing suitable character and content licenses, securing your site, testing accessibility, and complying with laws that apply to your product.

Runtime and package behavior is defined by the versioned contracts and release files published with the relevant repository. Marketing examples do not replace those technical contracts.

Other services

External platforms apply their own terms.

The site may link to or rely on services such as GitHub, npm, jsDelivr, Cloudflare, Discord, and X. Their terms, availability, and content are controlled by those providers. A link does not mean Peekling endorses every statement, product, or policy on the destination site.

An evolving project

Features and terms may change as Peekling grows.

The site, examples, and project releases may be changed, paused, or removed. These terms may also be updated. A revised effective date will appear at the top, and continued use after an update means the revised terms apply.

Reasonable boundaries

The site is provided as available.

To the fullest extent allowed by law, peekling.com and its content are provided without warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability, or error-free operation. Open-source components remain subject to the warranty terms in their applicable licenses.

To the fullest extent allowed by law, the operator will not be liable for indirect, incidental, special, consequential, or punitive damages arising from use of the site. Nothing in these terms excludes a right or liability that applicable law does not allow to be excluded.

Questions

Repository terms and applicable law remain in force.

If one part of these terms cannot be enforced, the remaining parts continue to apply. A failure to enforce one provision does not waive it. Specific repository licenses, contribution terms, and notices continue to govern the materials they cover.