Security, at its finest.

Who We Are

nullX is led by a small owner team, which means sensitive security and customer access decisions stay close to the people responsible for the product.

Everything we protect is handled with these promises in mind.

Zero Compromise Security

We do not treat customer license access as a normal dashboard lookup. Protected actions sit behind multiple checks, authentication flows, passcodes, and owner-level approvals before sensitive license details can be viewed or changed.

In practice, viewing or handling sensitive customer license information can require more than five separate gated steps, including internal passcodes, account authentication, permission checks, and explicit approval from authorized owners such askio andAurora.

License Ownership

Licenses are locked to the assigned customer account only. A license is intended for one authorized user or customer workspace, and access is not meant to be shared, transferred, reused, or passed around outside the approved owner.

License flows are designed around binding, verification, and account checks so protected portal access stays attached to the customer it belongs to. If ownership or access needs to change, that change must go through controlled support or security handling.

Minimal Data Handling

We avoid storing more customer license data than the service needs to operate, secure access, and support the customer. Generated secrets, temporary values, and short-lived authorization data are handled as sensitive material and are not kept around for casual review after their purpose is complete.

Our operating principle is to keep sensitive data limited, access controlled, and review paths narrow. We do not use customer data as a product to sell, trade, or expose.

Revocation Controls

License revocation is built to require confirmation from the affected user whenever possible. A normal revocation flow requires the user to approve the action through a direct bot message before the license is removed.

The only intended bypass is a force removal performed by authorized owners such as kio orAurora when there is a security, abuse-prevention, or emergency support reason to act immediately.

Product Protection

Our anti-cheat and obfuscator are designed to protect your games at every layer we can reasonably control. WatchDog focuses on active runtime defense, detection, logging, and response, while the obfuscator is built to make protected code harder to inspect, tamper with, or reuse outside the license it belongs to.

We build these systems with the highest security we can design: locked access, account-bound licenses, protected runtime values, defensive checks, audit visibility, and careful support workflows. The goal is not just to ship tools, but to give your game the strongest protection we can keep improving over time.

Customer Breach Response

If a customer believes their license workspace, account, runtime token, or connected environment has been compromised, we treat that as urgent. We will prioritize the issue, review the affected access, rotate or revoke platform-side credentials where appropriate, and help the customer get back to a secure state.

Our commitment is to drop normal priority work when a real customer security incident needs attention. We do not ignore breach reports, and we do not leave customers alone when platform-side action can reduce damage or restore trust.

Transparency

We are willing to explain and, when appropriate, demonstrate how our security gates work so customers understand that license data is not being handled casually. Some internal details must stay private to preserve security, but the standard we hold ourselves to is direct: protect the customer first.

What We Will Never Do