License and Activation Security

• Installation does not create a License — Downloading or installing Vietnam Office does not create Product Entitlement, Version Entitlement, or Platform Entitlement. Rights must originate from a valid transaction, Order, contract, Store, or other official mechanism.
• Backend-authoritative licensing — The Vietnam Office backend is authoritative for Product Entitlement, Version Entitlement, Platform Entitlement, License status, Quantity, Device Binding, Update/Upgrade, and Revocation.
• Multi-factor entitlement verification — Usage rights are not determined by a single data field. The system checks Product + Version + Platform + License/Entitlement + Quantity + Device/Store condition before confirming entitlement.
• Desktop Device Binding — Windows/macOS use Device-Bound Licensing. Initial Activation associates the entitlement with an eligible device through Device Binding.
• No Product Key entry in the standard flow — Vietnam Office Desktop does not rely on users entering a copyable Product Key string to establish rights. Activation is performed electronically using License/Entitlement and Device Trust.
• Mobile Store Entitlement — Android uses Google Play Store Entitlement; iOS/iPadOS uses Apple App Store Entitlement. Vietnam Office combines verified Store information with system Entitlement to determine rights.
• Signed entitlement information — Where applicable, information supporting usage rights may be signed or protected through verification mechanisms to reduce the risk of License data modification or impersonation.
• Activation Verification — During Activation, the backend checks the current entitlement state before establishing a valid usage state.
• Quantity Enforcement — The system may reject Activation or Allocation if granted Quantity has been exhausted or the request exceeds the permitted scope.
• Platform Enforcement — A Windows License cannot be activated as a macOS License; an Android Store Entitlement does not automatically become an iOS/iPadOS entitlement.
• Version Enforcement — A Version outside the Version Entitlement may be rejected during Activation or require Upgrade Entitlement before use.
• Replay/Duplicate protection — Repeating a request or performing Activation multiple times does not create additional Licenses/Entitlements or increase Quantity.
• Reinstall/Restore protection — Restore only recovers existing rights after Product, Version, Platform, License, and Device/Store are verified; it does not create new rights.
• Device Replacement protection — On Desktop, moving rights to a new device must follow Device Replacement/Device Transfer. Installing on a new device does not automatically transfer Device Binding.
• Tamper Detection — Modifying License data, emulating Device Identity, changing Entitlement data, or interfering with verification may cause the request to be rejected or the License to be handled under applicable policy.
• Suspend/Revoke control — The backend may apply Suspend, Revoke, or Invalid status when the entitlement is no longer valid, a transaction is cancelled, or licensing conditions are violated.
• Offline protection — Offline rights are not independent of the official License. When the device reconnects, the authoritative backend state is used to synchronize and verify entitlement.
• Entitlement impersonation is prohibited — Users may not copy License data, impersonate Store transactions, emulate Device Binding, manipulate time, or use tools intended to create or extend unauthorized rights.
• Privacy by purpose — Data required for License/Activation is processed for entitlement verification, rights management, fraud prevention, support, and other purposes disclosed in the applicable policies.

License & Activation Security principle: entitlement must exist first → backend verifies Product + Version + Platform + Quantity → verifies Device Binding or Store Entitlement → establishes valid Activation → continues to control Restore, Update, Upgrade, Suspend, and Revoke according to the authoritative entitlement state.