1. Scope
This policy applies to personal information processed when you visit remotemini.com, register for or sign in to the RemoteMini console, rent a dedicated Mac mini, or contact us by email or through a console support ticket. Website visits, account management and node use are separate activities; this policy explains the purposes for each.
RemoteMini provides remote access to a dedicated physical machine, not a shared virtual desktop. Each node is assigned to one customer, but we still need to process certain information for accounts, orders, payments and support. “Dedicated” does not mean there are no account records or service logs.
Software you install and third-party services you connect to may process information you submit under their own policies. This policy covers RemoteMini’s own processing. Before uploading code, materials or personal information to another service, check its permissions and how it uses data.
2. Information We Collect
Account information: This includes your email address and information needed for registration, verification, sign-in and account security. We use it to identify your account, send essential service notices, verify sensitive actions and help restore account access. Use an address where you can continue to receive email, and never share passwords or verification codes in public enquiries.
Order and payment records: These include the selected model, node, billing period, add-ons, order number, amount, payment status and related transaction identifiers. We use them to provision the service, process renewals, reconcile payments and resolve payment disputes. Support ticket content: This includes your issue description, instance ID, relevant time period, screenshots and troubleshooting correspondence. We use it to understand the issue and keep a record of how it was handled.
Essential technical logs: These may include your IP address, request time, browser or client details, error records and account security events. We use them to protect sign-ins, troubleshoot connection issues and keep the service running. These logs are not the contents of files on your node; keeping technical logs does not mean we browse your project directories.
3. Payment Information
Services are billed in US dollars (USD). We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available payment gateways are determined by the options returned at checkout. Stripe processes card payments, and RemoteMini does not store full card numbers. We use order and payment results to confirm receipt of funds.
For USDT-TRC20 payments, we use the transaction ID, amount and related on-chain records to verify the order. On-chain records are publicly viewable, and deleting account information cannot remove records already written to the blockchain. To request payment reconciliation, provide the order number and transaction ID only. Never send wallet private keys or seed phrases.
We may retain necessary payment records after an order ends to meet settlement, accounting and dispute-handling obligations. We use this information only as needed to process payments, reconcile accounts or meet related obligations; payment credentials are not routinely used for technical troubleshooting.
4. Data on Your Node
You control the code, documents, assets and outputs you create, upload or store on your dedicated Mac mini. RemoteMini does not proactively access files on your node or use your project content for website analytics. During your rental term, you can manage your files, software and access permissions, and export anything you want to keep to your own storage.
We access relevant content only when you authorize troubleshooting through a support ticket, and only to the extent needed to resolve the issue. Specify the instance ID, issue, directories or logs we may inspect, and whether we may take any related actions. If the work needs to go beyond what you authorized, we will check with you first. Authorization for one troubleshooting request is not ongoing permission to access your node.
Before sharing screenshots or logs, remove personal information, access tokens and keys that are unrelated to the issue. A dedicated node does not replace your own backup plan. Keep separate copies of work and assets that cannot be recreated; do not rely on a remote machine as the only place they are stored.
5. Retention and End-of-Term Processing
We set retention periods according to the purpose of each type of information rather than applying one period to everything. Account details support account access and security checks; order and payment records support provisioning, reconciliation and necessary recordkeeping; support tickets and technical logs help resolve issues, investigate security events and operate the service. When information is no longer needed for its purpose, we delete it or de-identify it.
After your rental term ends and the service is terminated, data on the node goes through a clearing process before it is reassigned. This process removes the previous tenant’s files, credentials and environment. The node is prepared for a new customer only after cleanup is complete. Do not treat an expired node as storage you can continue to access, or assume files can be recovered after the term ends.
Before your term ends, check your renewal status or export your code, assets, model weights and outputs. Check the console for the end time and status of your specific order. If you have questions about exporting data or what will be cleared, submit a support ticket before the term ends. Deleting account details and clearing node files are separate actions, so specify each one in your request.
6. Cookies and Analytics
The website and console may use cookies or similar local storage to maintain sign-in sessions, perform security checks and remember essential interface settings. These mechanisms let pages recognize the same visit and verified actions. If you disable this storage, sign-in or checkout may not work properly.
The website uses same-domain Matomo analytics to understand page visits and key actions, such as whether visitors view a plan or start an order. Analytics measures website usage; it does not give us access to project files on dedicated nodes. Do not enter passwords, verification codes or payment credentials in URLs, search terms or other fields that may be recorded.
You can view, clear or restrict cookies and local storage in your browser settings. Clearing sign-in data will usually end your current session. Restricting analytics and disabling essential session storage have different effects. To learn what information about your account we process, you can submit an access request under Section 7.
7. Your Rights
You can ask to access personal information we process about you, correct inaccurate details, delete information that is no longer needed, or export account information where applicable. Submit a request through a support ticket in the console or email us at support@remotemini.com. Specify the action you want and the account involved. Avoid including unrelated sensitive information in your request.
To prevent others from claiming your information or deleting your account, we may need to verify that you control the account and confirm the scope of your request. Please contact us from your registered email address or submit a request while signed in to the console. Do not send identity documents, passwords or verification codes. If we need more information, we will explain why and what is required.
We may need to retain some order, payment or security records to meet applicable obligations, resolve outstanding matters or handle disputes. If so, we will explain which records cannot be deleted immediately and why. Exporting personal information is not the same as backing up a node’s disk. Export files from your node while the service is active, or contact support for help with the process.
8. Contact and Policy Updates
For questions about this policy, your personal information rights or the scope of troubleshooting authorization, contact us at support@remotemini.com, or submit a support ticket in the console. If you have placed an order, include the order or instance ID. For access issues, you may also include when they occurred and any error message. Do not include your sign-in password.
We will update this policy when our service processes or information-handling practices change, and note updates with the version label on this page. If a significant change affects your rights, we will notify you through an appropriate channel, such as the website, console or account email. For requests related to past processing, we will explain how information was handled during the relevant period.
This policy is governed by the laws of the jurisdiction where the platform operator is based. Disputes will be handled by the courts with jurisdiction in that jurisdiction. If you have questions about how we process information, please contact us using the email address or console support ticket above so we can review the facts and scope of your request.