Legal

Albion DarkStore Privacy Policy

Effective date: 2026-08-27

This Privacy Policy explains how Albion DarkStore processes data for ADS Launcher, licensed Windows products, Phone Radar and other approved Android sideload products, backend services, and Discord administration tooling.

Data We Process

We process account and entitlement records, including username, email address, password hash, account status, product and license state, activation and expiry times, key verifier and suffix records, redemption history, reset state, and revocation state.

For Phone Radar we process Android P-256 public-key material and its public-key fingerprint, the fixed non-hardware-derived device label, credential creation and revocation timestamps, and the fixed app version and client identifier. The Android private key remains in Android Keystore and is never uploaded.

We process refresh and activation challenges, license sessions, one-time launch sessions, runtime sessions, hashed tokens and proof nonces, proof sequence, expiry and invalidation state, and heartbeat security records.

Backend, Nginx, Docker, and security logs may include IP addresses, request paths, response status, user agent, client version, rate-limit or security result, and timestamp. Restricted Discord administration records contain only the data needed for authorized support and audit; generated keys are not copied into list, status, or audit output.

Gameplay Data Stays Local

Gameplay traffic, raw packets, decoded marker events, positions, map snapshots, target endpoints, and packet diagnostics stay on the device and are not uploaded to Albion DarkStore, ADS backend, Discord, or a relay. Phone Radar does not send Albion traffic, Photon payloads, or local overlay state to the licensing service.

How We Use Data

We use this data to authenticate accounts; issue, validate, extend, revoke, and audit entitlements; bind approved device credentials; authorize downloads and runtime sessions; operate activation, validation, heartbeat, close, reset, and revoke flows; provide support and recovery; and protect the service from misuse.

Sharing

We do not sell personal data. Infrastructure, hosting, domain/TLS, source-hosting, Discord, backup, payment, and support providers may process data only as needed to operate the service or handle a requested transaction, subject to their own obligations.

Retention

Account, entitlement, key-verifier, redemption, reset/revoke, and audit records are retained while needed for access, support, fraud and abuse prevention, accounting, disputes, audit integrity, and legal compliance. Expired session records may be cleaned periodically. Security logs and verified backups are retained and rotated according to operational, security, recovery, and legal need; no fixed schedule is promised where continuing retention is required for those purposes.

Security

Production API traffic uses HTTPS. Passwords and supported tokens are stored as hashes or verifiers where the service contract permits. Phone Radar uses proof-of-possession with an Android Keystore credential; the backend stores public credential material, never the private key. These measures reduce risk but cannot guarantee that client software or infrastructure is impossible to compromise.

Reset, Revocation, Support, and Deletion Choices

You may request account support, device reset, license support, revocation assistance, or deletion where legally and operationally possible. Device reset requires identity verification and revokes the prior credential and affected sessions before the same account may rebind. Some payment, security, abuse-prevention, legal-claim, backup, or audit-integrity records may need to be retained after a request.

Support is available through the official Discord and Telegram channels linked on albiondarkstore.com. Do not send passwords, activation keys, tokens, private keys, raw captures, or other secrets in support messages.

Changes and Contact

Material changes require a corresponding policy version and renewed acceptance where the service requires it. The operational legal text should receive owner and qualified-counsel review before wider paid distribution.

See the canonical End User License Agreement.