Privacy Policy
Last Revised: November 2026 | Built to Protect - MeridianAuth
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.
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.
Hardware Identification (HWID) Hashing
To enforce device-locked software licenses, client machines generate composite entropy vectors based on non-sensitive hardware attributes.
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.
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.