MeridianAuth Logo MeridianAuth
  • Features
  • Documentation
  • Security
  • Pricing
Discord Sign In Get Started

Terms Outline

1. Acceptance of Terms 2. Developer Responsibilities 3. Acceptable Use Policy 4. Availability & Quotas 5. Limitation of Liability 6. Account Termination
Direct Inquiries

Need custom compliance terms or high-volume enterprise agreements?

Contact Team on Discord
Home / Legal / Terms of Service
Binding Agreement

Terms of Service

Last Revised: November 2026 | Built to Protect - MeridianAuth

01

Acceptance of Terms

By registering an account, interacting with the MeridianAuth API cluster, or linking the client verification libraries with your software, you acknowledge that you have reviewed, understood, and agreed to be bound by this Agreement.

Core Covenant
MeridianAuth provides software licensing infrastructure designed to authenticate authentic users and guard against unauthorized execution. You agree to use these tools in compliance with all relevant computational security and export regulations.
02

Developer Responsibilities & Key Security

Developers assume complete responsibility for safeguarding their account access tokens, master encryption secrets, and application identifiers.

  • Secret Protection: Master application secrets must never be committed to public code hosting repositories or embedded in decompilable plaintext formats.
  • Revocation: In the event that a developer secret token is compromised, you must immediately cycle and regenerate the token via the developer dashboard.
  • Authorized Allocation: All license keys created, dispatched, or validated through your account fall under your administrative jurisdiction.
03

Acceptable Use Policy

MeridianAuth strictly prohibits the use of its authentication infrastructure for illicit, disruptive, or harmful applications. You agree not to:

  • Deploy MeridianAuth licensing for malicious payloads including worms, trojans, ransomware, or spyware.
  • Execute unauthorized load-injection, stress-testing, or distributed denial-of-service (DDoS) campaigns against the authentication endpoints.
  • Interfere with, subvert, or intercept cryptographic packet exchanges of other developers using proxy interception or DNS spoofing.
04

Service Availability & Fair-Use Quotas

MeridianAuth verification services are hosted on multi-region redundant infrastructure. We enforce fair-use rate limits calibrated to prevent individual application anomalies from degrading cluster-wide performance. Applications demanding high-volume burst thresholds must operate under the Enterprise tier.

05

Limitation of Liability

While MeridianAuth enforces state-of-the-art cryptographic hashing, memory validation, and dynamic packet signing, software security is an adversarial and evolving field.

Disclaimer of Client-Side Warranties
MeridianAuth shall not be held liable for revenue losses, operational disruptions, or damages resulting from third-party client reverse-engineering, memory dumping, or modified client executables that operate outside our server-validated boundaries.
06

Termination & Account Suspension

We reserve the right to suspend or permanently deactivate developer accounts found to be in violation of our Acceptable Use Policy or engaging in attacks directed against the platform cluster.

MeridianAuth Logo MeridianAuth

Built to Protect - MeridianAuth. The modern developer authentication and licensing security layer.

Product

  • Features
  • Documentation
  • Security Guard
  • Pricing Plans

Community & Portal

  • Discord Community
  • Sign In
  • Register

Legal & Security

  • Terms of Service
  • Privacy Policy
  • Security Policy
© 2026 MeridianAuth. Built to Protect - MeridianAuth. All rights reserved. Cryptographically Verified Infrastructure