Terms & Conditions

Rules for authorized use of ATLAS MDM

These terms describe the expected customer, reseller, sub reseller, and administrator responsibilities for using the platform. They should be customized for your business entity, payment process, supported regions, and final service model.

Home Legal Hub Privacy Refund FAQ Compliance

Authorized Use

ATLAS MDM may be used only to manage Android devices, APKs, users, clients, and reseller accounts that the user is legally authorized to manage. You must not enroll, monitor, control, or modify a device without permission from the device owner, customer, or authorized administrator.

  • Remote support requires client consent unless a lawful enterprise policy clearly authorizes unattended management.
  • Users must not bypass consent prompts, role limits, activation checks, credit rules, audit logs, or device ownership restrictions.
  • The platform may not be used for harassment, fraud, scams, surveillance abuse, data theft, extortion, credential theft, malware distribution, or unlawful access.

Account and Role Responsibilities

Admin

Admin has full platform access for operations, billing, support, audit, security, reseller management, APK review, device management, and incident response. Admin is responsible for protecting platform-level access and ensuring production backend controls enforce the same role rules shown in the panel.

Reseller

Resellers may manage their assigned sub resellers, reseller-owned APKs, reseller-owned clients, direct devices, credit transfers, tickets, and logs within their hierarchy. Resellers must not access another reseller's accounts, APKs, clients, devices, folders, support sessions, or credit records.

Sub Reseller

Sub resellers may manage their own clients, devices, APKs, tickets, activation codes, folders, and available credits. They must request additional credits from their reseller or the assigned parent account.

APK Uploads and Application Deployment

Uploading an APK means the uploader confirms they have the legal right to distribute that application to the selected customers and devices. ATLAS may scan, quarantine, reject, disable, or remove APKs that appear unsafe, defective, unauthorized, infringing, malicious, or inconsistent with platform policy.

Production deployments should verify package name, version, requested permissions, signing certificate, checksum, manifest integrity, malware scan result, file size, and assignment scope before any APK is made available for device deployment.

Credits, Billing, and Activation

Credits are used to activate clients or devices according to your business rules. Admin credits may be unlimited. Reseller and sub reseller usage is limited by available balances. If a reseller sells 100 credits and transfers 50 credits to a sub reseller, the reseller's own available client activations are reduced accordingly.

All credit transfers, pullbacks, approvals, and activations must be recorded in a backend ledger with actor, target, old balance, new balance, reason, timestamp, and audit ID.

Suspension and Termination

ATLAS may suspend remote access, block panel actions, disable APK availability, pause agents, or restrict accounts when there is suspected abuse, unpaid service, malware upload, unauthorized access, policy violation, legal risk, chargeback, or security incident. Security suspensions should apply only to the offending account unless another account triggers its own separate violation.