Skip to content

Latest commit

 

History

History
82 lines (53 loc) · 2.17 KB

File metadata and controls

82 lines (53 loc) · 2.17 KB

LICENSING AND COMMERCIAL USE

The Age Verification Protocol (AVP) is a proprietary protocol authored by R. Payne (GitHub: iamfurydammit).

All rights are reserved unless expressly granted in writing.


1. LICENSING MODEL

AVP is not released under an open-source license.

Use of the protocol, specification, reference implementations, or associated materials beyond inspection or evaluation requires an explicit license granted by the author.

No rights are granted by implication, estoppel, or publication alone.


2. EVALUATION USE (NO FEE)

The following uses are permitted without charge:

• Viewing the source code and documentation
• Reviewing the protocol for evaluation, research, or due diligence

Evaluation use does not include deployment, integration, operational reliance, or use in live or production systems.


3. COMMERCIAL AND PRODUCTION USE (PAID LICENSE REQUIRED)

A paid license agreement is required for any of the following:

• Commercial or revenue-generating use
• Production or operational deployment
• Hosted, SaaS, or service-based implementations
• Regulatory, compliance, or policy-driven use
• Modification, adaptation, or derivative works
• Integration into products, platforms, or services
• Redistribution or sublicensing

Licenses may be offered on a per-deployment, per-organization, or enterprise basis, at the discretion of the author.


4. SERVICES AND CERTIFICATION

Commercial services may be offered separately, including but not limited to:

• Hosted deployments
• Enterprise integrations
• Support and maintenance agreements
• Advisory or compliance-aligned services
• Certification or conformance programs

No certification, approval, or endorsement is implied by access to this repository.


5. TRADEMARKS AND REPRESENTATION

No rights to trademarks, branding, or certification marks are granted.

You may not represent AVP as open source, freely licensed, certified, approved, or endorsed without explicit written authorization.


6. CONTACT

All commercial licensing inquiries, deployment permissions, or derivative rights must be obtained directly from the author.