BlkSeal Developer Agreement

Effective Date: 2026-07-02

Company: lyfe.ninja LLC (“we,” “us,” or “our”)
Service: BlkSeal API, SDKs, browser verification tools, signing and verification services, and related developer services (“Service”)
Version: blkseal_v1

This BlkSeal Developer Agreement (“Agreement”) governs your access to and use of the Service. In short: use the Service responsibly, protect your credentials, do not misrepresent what BlkSeal signatures or verification results guarantee, and design your systems with revocable and service-dependent verification in mind.

By registering for a developer account, creating API credentials, accessing developer tools, or using the Service, you agree to this Agreement.

This Agreement supplements our general Terms of Service and Privacy Policy. If there is a conflict between this Agreement and the Terms of Service, this Agreement controls only for developer-specific use of the BlkSeal API, SDKs, browser verification tools, and related developer services.

1. Developer Access and Accounts

To use the Service, you may be required to:

• Register for a developer account.
• Create or manage a workspace.
• Create applications, API credentials, access tokens, leases, or signing authority.
• Provide accurate and current account, workspace, and billing information.
• Comply with applicable plan limits, rate limits, usage limits, and security requirements.

You are responsible for all activity conducted using your account, workspace, applications, API keys, access tokens, client secrets, leases, signing authority, SDK integrations, browser helpers, and other credentials or developer tools associated with your account.

2. Permitted Use

You may use the Service to:

• Generate signatures for supported content, hashes, files, media, application outputs, or workflows.
• Verify signatures, hashes, revocation status, and related verification metadata.
• Integrate BlkSeal into your applications, websites, APIs, browser workflows, internal tools, or systems.
• Use BlkSeal SDKs, documentation, examples, and browser verification tools as permitted by us.

You are responsible for your own applications, systems, integrations, user interfaces, customer claims, operational decisions, security controls, and use of any output from the Service.

3. Prohibited Uses

You agree not to:

• Use the Service for unlawful, harmful, fraudulent, deceptive, abusive, or unauthorized purposes.
• Use the Service to sign, verify, distribute, or promote malware, phishing content, spam, or harmful code.
• Use the Service to misrepresent the origin, authorship, approval, integrity, or trustworthiness of content.
• Impersonate another person, company, application, service, authority, or source of content.
• Attempt to reverse engineer, extract, replicate, copy, or misuse underlying models, systems, APIs, or infrastructure.
• Interfere with, disrupt, overload, scan, probe, or test the Service except as expressly authorized by us in writing.
• Bypass, disable, evade, or interfere with authentication, authorization, rate limits, usage limits, billing controls, or security controls.
• Resell, sublicense, or provide access to the Service in a way that violates this Agreement or our Terms of Service.

4. Credential and Integration Security

You agree to:

• Keep API keys, access tokens, client secrets, and other credentials secure and confidential.
• Use reasonable safeguards to protect credentials from unauthorized access, exposure, or misuse.
• Immediately notify us if you suspect that credentials have been lost, stolen, exposed, or compromised.
• Rotate or revoke credentials when appropriate.
• Implement reasonable security controls in your own applications and integrations.

You must not expose secret API keys, client secrets, private credentials, or server-side tokens in public repositories, client-side code, browser code, mobile apps, frontend JavaScript, logs, support tickets, screenshots, or other locations where unauthorized parties may access them.

We are not responsible for unauthorized access, misuse, data exposure, failed verifications, signing errors, or other issues caused by your failure to secure credentials or properly implement your integration.

5. Service Characteristics and Limitations

BlkSeal has characteristics that may differ from traditional digital signature systems. You are responsible for understanding these characteristics and designing your systems accordingly.

a. Revocability and Expiration

Signatures, signing authority, leases, credentials, applications, models, or verification capabilities may be revoked, expire, rotate, change, or become unavailable. This may occur for reasons including, but not limited to:

• Lease expiration.
• Manual revocation.
• Credential rotation or compromise.
• Workspace or subscription changes.
• Security concerns or suspected misuse.
• Model, service, or infrastructure lifecycle changes.

A verification result may change over time. Content that verifies successfully at one time may fail verification later if the relevant signing authority, lease, model, credential, application, workspace, or service capability is revoked, expired, changed, or unavailable.

b. Service and Model Dependency

Verification may depend on access to the Service, associated models, artifacts, metadata, revocation status, infrastructure, or other service components. We do not guarantee perpetual availability of any specific model, artifact, endpoint, SDK, browser helper, signature type, verification method, or verification capability.

c. Model-Based Encoding and Error Handling

BlkSeal and related BlkBolt technology use model-based signing, encoding, decoding, and verification techniques that differ from traditional cryptographic digital signature systems. Although the Service is designed to produce consistent results for supported workflows, signing, encoding, decoding, or verification operations may occasionally fail, return an error, or produce an invalid or non-verifying result.

You are responsible for designing your applications and integrations to handle error states, failed signing attempts, failed verification attempts, timeout events, retry behavior, revocation checks, and other unexpected results in a safe and reasonable manner.

You should not represent BlkSeal or BlkBolt as error-free, perfectly deterministic, permanent, unbreakable, or equivalent to traditional cryptographic signature infrastructure unless the statement is accurate, qualified, and not misleading.

d. No Guarantee of Truth, Legality, or Quality

BlkSeal provides tools for signing and verification. A successful verification does not by itself prove that content is true, lawful, safe, complete, accurate, current, endorsed by a third party, or suitable for a specific purpose.

e. No Compliance Guarantee

We do not guarantee that use of the Service will satisfy any law, regulation, evidentiary requirement, audit requirement, industry standard, contractual obligation, platform policy, or compliance framework. You are responsible for determining whether the Service is appropriate for your specific use case.

6. Acceptable Representation of BlkSeal

You agree not to:

• Misrepresent the capabilities, limitations, purpose, or verification meaning of the Service.
• Claim that BlkSeal signatures are “unbreakable,” “permanent,” “guaranteed,” “tamper-proof,” or equivalent.
• Represent BlkSeal as traditional public/private key cryptographic infrastructure unless the statement is accurate and not misleading.
• Represent a verification result as proof that content is true, lawful, safe, approved, endorsed, or trustworthy beyond what the verification result actually supports.
• Display badges, labels, verification messages, or trust indicators in a misleading or confusing way.

Any public, customer-facing, or user-facing claims about BlkSeal, signatures, verification results, badges, revocation, provenance, authenticity, or integrity must be accurate, reasonable, and not misleading.

7. Developer Data and Content Responsibilities

You are responsible for any content, data, files, media, hashes, URLs, metadata, signatures, user data, application data, or other material that you submit to, process through, or generate using the Service.

You represent that you have all rights, permissions, notices, consents, and legal bases necessary to submit such material to the Service and to use the Service in connection with your applications, customers, users, systems, and workflows.

Unless we separately agree in writing, you must not submit, upload, sign, verify, or otherwise process highly sensitive or regulated information through the Service. This includes, but is not limited to, protected health information, payment card data, financial account credentials, government identification numbers, Social Security numbers, biometric identifiers, precise geolocation data, children’s data, or other information subject to heightened legal, regulatory, or contractual protection.

If your application or integration may involve sensitive or regulated information, you are responsible for contacting us before using the Service for that purpose and for ensuring that appropriate contractual, security, privacy, compliance, and data processing terms are in place.

You are responsible for providing any required notices, disclosures, terms, consents, privacy policies, support, and user-facing explanations for your own applications and integrations.

8. API Usage, Rate Limits, and Fair Use

Use of the Service may be subject to rate limits, usage quotas, verification limits, signing limits, workspace limits, application limits, lease limits, subscription limits, storage limits, or other technical and operational restrictions.

We may monitor usage and enforce limits to protect the Service, prevent abuse, maintain reliability, manage capacity, enforce plan terms, or protect other users.

We may throttle, reject, delay, suspend, or limit requests that exceed applicable limits or appear to create security, operational, legal, or abuse concerns.

9. SDKs, Browser Tools, and Documentation

We may provide SDKs, browser verification tools, sample code, documentation, examples, or other developer resources. These materials are provided to help you integrate with the Service, but you are responsible for testing, validating, securing, and maintaining your own implementation.

Documentation, examples, helper scripts, SDKs, endpoints, parameters, features, and supported content types may change over time. You are responsible for monitoring updates and ensuring your integration remains compatible with the Service.

10. Data Handling

We aim to minimize data retention. However, API usage data and service metadata may be logged and processed as needed to provide, secure, troubleshoot, support, improve, and enforce the Service.

This may include, but is not limited to:

• Request metadata.
• IP addresses.
• Authentication and authorization events.
• Workspace, application, lease, and signing authority identifiers.
• Signature and verification metadata.
• Usage counters and quota records.
• Error logs and security events.

Unless a feature specifically requires storage, BlkSeal is designed to verify integrity rather than host or publish customer content. We do not retain submitted content longer than necessary to process the request, operate the Service, maintain security, troubleshoot issues, comply with legal obligations, or enforce usage limits.

11. Beta, Preview, or Experimental Features

Some features may be provided as beta, preview, experimental, limited-release, or early-access features. Such features may change, break, be unavailable, produce unexpected results, or be discontinued at any time.

Beta, preview, experimental, limited-release, and early-access features are provided for evaluation and testing and should not be used in production or mission-critical systems unless you accept the associated risks.

12. Suspension and Termination

We reserve the right to restrict, suspend, revoke, throttle, disable, or terminate access to the Service at any time, with or without notice, including but not limited to cases involving:

• Security concerns.
• Credential compromise.
• Suspected abuse or misuse.
• Violation of this Agreement or our Terms of Service.
• Failure to pay applicable fees.
• Exceeding plan limits or usage limits.
• Protection of the Service, our infrastructure, our business, or other users.

We may also revoke API credentials, disable applications, revoke signing authority, invalidate access tokens, limit endpoints, or disable specific features where needed to protect the Service or address suspected misuse.

13. Disclaimers

The Service is provided on an “as is” and “as available” basis. We do not warrant that the Service will be uninterrupted, error-free, secure, free of vulnerabilities, or available at all times.

We do not guarantee absolute security, prevention of all tampering or misuse, error-free signing, encoding, decoding, or verification, fitness for a particular purpose, accuracy of all verification outcomes, continued availability of any specific feature, or compatibility with every application, browser, platform, system, or workflow.

You are responsible for independently evaluating and validating whether the Service and any verification result are appropriate for your intended use.

14. Limitation of Liability

To the maximum extent permitted by law, lyfe.ninja LLC and its owners, employees, contractors, service providers, and affiliates will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, data, goodwill, business opportunity, or business interruption arising from or related to your use of, or inability to use, the Service.

To the maximum extent permitted by law, our total liability for any claim arising from or related to the Service or this Agreement will not exceed the amount you paid to us for the Service during the three months before the event giving rise to the claim, or one hundred dollars ($100), whichever is greater.

15. Indemnification

You agree to defend, indemnify, and hold harmless lyfe.ninja LLC and its owners, employees, contractors, service providers, and affiliates from and against any claims, damages, liabilities, losses, costs, and expenses, including reasonable attorneys’ fees, arising from or related to:

• Your use of the Service.
• Your application, website, API, system, workflow, integration, or customer-facing implementation.
• Your content, data, files, media, hashes, URLs, signatures, metadata, or other materials.
• Your violation of this Agreement, our Terms of Service, or applicable law.
• Your infringement, misuse, or violation of another party’s rights.
• Your public or customer-facing claims about BlkSeal or verification results.

16. Changes to This Agreement

We may update this Agreement from time to time. Any changes will be posted on this page with an updated effective date. Your continued use of the Service after the updated Agreement is posted means you accept the updated Agreement.

17. Contact

If you have questions or concerns about this Agreement, you may contact us at: support@lyfe.ninja.