dxAuth legal
Independent platform
Updated 2026-07-13

Legal terms for identity verification, registered applications, and secure auth-code exchange.

dxAuth operates as a dedicated authentication and application-registration platform. These documents set out platform boundaries, operational safeguards, privacy handling, retention, and reporting channels.

Last updated 2026-07-13
Current release

dxAuth Abuse Reporting

Reporting channel and response framework for sign-in, email, application-registration, and security abuse.

Section 01

Reporting channel

  1. 1.1

    Report sign-in abuse, unwanted auth emails, phishing, impersonation, suspicious registered apps, brute force attempts, or security concerns to abuse@doxanh.dev.

  2. 1.2

    General contact: contact@doxanh.dev.

Section 02

Report contents

  1. 2.1

    Include the application name or domain, the email address receiving unwanted sign-in messages if it is yours to provide, approximate time, relevant headers or screenshots if safe, and your contact email.

Section 03

Potential enforcement actions

  1. 3.1

    doxanh may suppress or rate-limit abusive sign-in attempts, block risky domains or recipients, disable an application, revoke sessions, preserve records, or escalate severe abuse to providers or authorities where appropriate.

Section 04

Prohibited uses

  1. 4.1

    dxAuth must not be used for phishing, spam, credential theft, deceptive sender identity, harassment, malware, account enumeration, or attempts to bypass technical, legal, or platform restrictions.

Section 05

Response framework

  1. 5.1

    Final service-level targets should be set before production. Suggested internal targets are to acknowledge high-risk abuse reports within 1 business day, review urgent safety or security reports as soon as practicable, and document action taken in operational records.

Last updated 2026-07-13.Contact contact@doxanh.dev, privacy@doxanh.dev, legal@doxanh.dev, or abuse@doxanh.dev.