1. Scope and processing principles
This policy covers the LoopVM client, website, accounts, plans, installation rules, templates and support. Services independently provided by apps inside a virtual device and payment-provider pages you visit have their own policies. LoopVM remains responsible for information it provides or receives.
Processing should have a specified purpose, use the minimum necessary information and have a limited duration. Depending on the activity, the basis may be contractual necessity, valid consent, a legal obligation or another applicable lawful basis. A general agreement does not replace separately required notices and choices.
2. Accounts, email and sign-in security
Registration, sign-in, recovery and security verification involve the email, login name or nickname you provide, password verification information, code verification records, account status and relevant times. Email supports account verification and necessary messages. Passwords should be stored in a secure verification form, not ordinary plaintext business fields or logs.
Session, client-connection and security records, request IP, sign-in times and necessary failure reasons help maintain sessions and identify abuse. Without essential authentication information, the corresponding account service cannot operate. An optional nickname should not be a condition of signing in.
3. Plans, orders and payment records
Trials, redemptions, purchases and allocations involve plan versions, features, quantities, duration, entitlement sources and changes. Orders and refunds also involve references, amounts, currencies, channels, payment status, provider transaction identifiers, times and necessary evidence, for fulfilment, reconciliation, duplicate prevention and disputes.
Your chosen provider handles payment. LoopVM does not require payment passwords, wallet private keys or recovery phrases. Cryptocurrency transactions may display addresses and amounts on a public blockchain. Do not paste unnecessary financial details into support messages.
4. Virtual-device configuration and records
Creating or changing a virtual device involves its name, owner, Android and image versions, model, template references, feature configuration, resource usage, request times and client-reported status or errors. These support eligibility checks, configuration delivery, result records and troubleshooting; they do not mean the server remotely runs your device.
Files and app data inside a virtual device are primarily stored on the terminal. Business status records are not continuous collection of the whole Android desktop or internal files, and are not a cloud backup. Additional service processing requires an upload you choose, selected diagnostics or a clearly notified lawful functional purpose.
5. Installation checks and events
Installation, update, overwrite, reinstallation and split-package requests involve the source, session, device ownership, package name, version, signer identity, file manifest and digests. Decisions, rule versions and client results are recorded to check support and detect inconsistencies.
Troubleshooting may include failure stages, explanations and client or kernel versions. These installation details are not continuous access to chats, photos or account content inside installed apps. If support needs additional material, its necessity should be explained and you choose what to submit.
6. Official and personal templates
Template uploads include the model, manufacturer, Android version, collection time, WebView version, patch date, unlock status, template version, description, archive and necessary extraction password you submit. Files may include device, network or proxy parameters you put into them. Check for sensitive content before uploading.
Personal templates are provided according to account ownership, without access for other ordinary users. Official templates follow their publication scope. Publication or conversion into official content requires an appropriate lawful basis and express authority; uploading does not imply it. Necessary operational and support access remains subject to least-privilege controls.
7. Optional collection, diagnostics and support
When you submit a ticket, appeal, ownership claim or diagnostic file, we process the explanation, contact details, linked order or virtual device, replies and selected attachments to handle that request. Requested device reports and personal templates have different purposes. Sending diagnostics does not automatically authorise publication or unrelated reuse.
Screenshots, logs, templates and archives may contain third-party data, locations, network credentials or other sensitive content. Submit only what is needed. If sensitive personal information is necessary, its purpose, impact and safeguards should first be explained, with separate consent where required.
8. Terminal permissions and simulated values
Selecting an installation package, importing a template or saving a download may require access to selected files. The client should explain permissions when the feature is invoked and request them through the system. Refusing an optional permission should affect only features that depend on it.
Virtual location, simulated network or SIM, sensors, display and clipboard settings do not by themselves imply collection of your real location, messages, contacts or all host files. Real-device data collection depends on the actual feature, permission prompt and notice. A plan feature name is not a substitute for a permission notice.
9. Website access and advertising
Website and API requests may produce IP addresses, times, paths, response statuses and browser or client information for delivery, security and troubleshooting. Session storage supports necessary sign-in functions. Non-essential tracking or marketing requires applicable notice and choice.
Advertising is separate from plans and virtual-device services. Before enabling a provider, its identity, information processing, purposes and necessary choices should be disclosed. A reserved advertising configuration is not consent to tracking. Processing must remain within the notified purposes.
10. Providers, sharing and publication
Relevant backend providers include Zoho for email, Cloudflare for network and security services, and NOWPayments when selected for payment. Recipient addresses and message content, network request data and relevant payment information enter these services for their respective purposes. See Third-Party Services and Payments.
Processors should have limited purposes and security obligations. Transfers to independent recipients require the notices, consent or other lawful conditions that apply. Personal templates should not be published or information supplied to unrelated parties without express authority, legal requirements or another necessary lawful basis. Enterprise membership does not automatically widen access to private data.
11. Storage regions and international processing
Serving users globally does not mean local storage is available in every user’s region. The current business server is deployed in Hong Kong, China. Email, network and payment providers may also process relevant information in other regions within their service networks.
International processing requires applicable notices, lawful conditions and safeguards, taking account of differences in protection. You may contact admin@loopvm.com about storage and recipients and exercise applicable rights.
12. Retention and deletion
Account and configuration information is kept as necessary for the service and security. Transaction, refund, dispute and necessary audit records follow applicable obligations and actual handling needs. Templates and support attachments follow their purpose and valid requests. Information should not be kept indefinitely for unspecified future uses; detailed schedules must match system settings.
When an account closes, a valid deletion request is accepted or a purpose ends, unnecessary information should be deleted or made irreversibly non-identifiable. Records that must legally remain, are disputed or await backup expiry should have restricted use and appropriate isolation, rather than indefinite unrelated reuse.
13. Security and incident response
Authentication, account and file ownership checks, least privilege, transmission protection and necessary auditing help prevent unauthorised access. Archive passwords alone do not protect uploads. Protect your email and terminal and avoid sending unrelated keys or credentials.
No system is absolutely secure. On discovering an information-security incident, we should contain, investigate and remedy it and provide legally required notices to affected users and authorities. Describing safeguards does not remove applicable responsibilities.
14. Access, correction, deletion and other rights
Contact admin@loopvm.com to request access, a copy, correction, deletion, account closure or withdrawal of optional consent-based processing. Where applicable, you may also request restriction, objection or portability. Describe the account and scope; identity checks should be proportionate to the risk.
Withdrawal does not invalidate prior lawful processing. Without essential information, the related feature may no longer operate, but unrelated features should not be affected. If a request cannot immediately be fulfilled, reasons and workable alternatives should be explained. Required order or dispute records are handled separately from deletable data, and account closure should not hide an unresolved payment issue.
15. Information about minors
Users below the applicable age for independent consent should have a guardian determine use under local requirements. Information about minors requires protection appropriate to age and risk. Paid services and third-party providers may impose separate age requirements.
Guardians who believe information has been processed without necessary consent can contact admin@loopvm.com. Following necessary verification, requests for restriction, deletion or other protection should be handled under applicable law.
16. Changes and contact
Material changes should explain the version, changes and effective arrangements on the website or in the client. New purposes, sensitive information or other processing requiring renewed consent must follow the applicable procedure; continued use alone is not consent.
Contact admin@loopvm.com for questions about personal information, providers, account closure or security.