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

Privacy Outline

1. Core Principles 2. Data Collection 3. HWID Hashing 4. Telemetry Usage 5. Data Deletion 6. Third-Party Sharing
Data Protection

We strictly believe in zero-knowledge licensing. Raw hardware data never touches our storage.

Review Security
Home / Legal / Privacy Policy
Privacy Commitment

Privacy Policy

Last Revised: November 2026 | Built to Protect - MeridianAuth

01

Core Privacy Principles

MeridianAuth operates under an uncompromising principle: we collect only what is strictly necessary to authenticate legitimate users and protect developer software from unauthorized duplication.

Zero Commercial Telemetry
MeridianAuth never monetizes user data, sells analytics to brokers, or embeds advertising trackers into client verification SDKs.
02

Information We Collect

Data points processed through our licensing nodes are limited to authentication primitives:

  • Developer Account Profiles: Verified email address, hashed administrative passwords, and account tier identifiers.
  • Session Audit Entries: Originating IP address, verification status codes, and request timestamps used for real-time security alerting.
  • Application Configuration: Application IDs, custom variable dictionaries, and generated license key records.
03

Hardware Identification (HWID) Hashing

To enforce device-locked software licenses, client machines generate composite entropy vectors based on non-sensitive hardware attributes.

Cryptographic One-Way Hashing
These system attributes are salted and hashed on the client's local system using SHA-256 prior to network transmission. Raw serial numbers, drive models, or personally identifiable hardware signatures are never transmitted or stored.
04

How Data Is Utilized

Telemetry received by our verification cluster is used solely to:

  • Confirm that an inbound license check matches the assigned hardware digest.
  • Prevent simultaneous session hijacking across disparate geographical locations.
  • Deliver real-time security alerts to developers via Discord or custom HTTP webhooks.
05

Data Retention & Deletion Rights

Developers possess absolute authority over their application data. Resetting a user's HWID, deleting a license, or decommissioning an application triggers immediate removal of the associated hardware hashes and credentials from active databases.

06

Third-Party Disclosures

We do not share, lease, or distribute data with external parties, except as required by lawful court subpoenas or to defend our systems against active cyber-attacks.

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