Scope
This policy applies to the processing of personal information generated when you visit minirents.com, use the MiniRents console, order or manage cloud Mac services, or contact our support team by email or console ticket.
This policy covers website visitors, account holders, order payment contacts, team deployment contacts, technical support requesters, and security reporters. If a team administrator creates or manages access for other members, the administrator must ensure they are authorized to provide MiniRents with the necessary information about those members.
Code, build artifacts, repository tokens, signing materials, and environment variables on dedicated physical machines are controlled by you. MiniRents does not use this content as website analytics data. To handle support requests you submit, support personnel may access the redacted logs or issue materials you provide after receiving the necessary authorization; access is limited to what is needed to resolve the request.
Information we collect
We collect different categories of information depending on the features you use. Not every user will generate all of the data listed below.
Account and contact information
This may include your name or display name, work email address, login verification records, account status, team role, and contact details you voluntarily provide during support communications.
Order and billing records
This may include the order ID, selected model, node, rental period, add-ons, amount due and paid, settlement currency, payment status, transaction reference, and billing correspondence.
Device and browser information
This may include browser type, operating system, interface language, access time, IP address, session ID, request result, and necessary troubleshooting information.
Support requests and security logs
This may include ticket subject, issue description, device identifier, node, time range, redacted logs, attachments, handling records, and security event records such as failed logins, permission changes, and unusual access.
Do not submit passwords, private keys, complete payment card details, or unredacted long-lived credentials by email, ticket, or attachment. When troubleshooting build issues, provide only log excerpts relevant to the error, after removing tokens, keys, signing materials, and personal data.
How we use information
MiniRents uses the information it collects for the specific purposes below and processes it only to the extent appropriate for each purpose.
- Provide and manage services Create accounts, record orders, provision dedicated physical machines, display device status, manage rental periods, and process configuration or node migration requests.
- Verify access Complete login verification, identify sessions, verify high-risk actions, manage team permissions, and detect unauthorized access attempts.
- Process orders and billing Confirm settlement results, match transactions with orders, create billing records, handle payment issues, and respond to billing questions.
- Respond to support requests Diagnose connection, disk space, build, automation, or billing issues, document communications, and verify whether the issue has been resolved.
- Protect security Analyze unusual logins, abuse, and service risks; limit the impact; preserve necessary evidence; and restore affected accounts or services.
- Meet legal obligations Retain transaction or compliance records that must be kept by law, respond to requests from authorized parties, and maintain necessary audit trails.
- Improve the experience Analyze feature usage and error outcomes, fix interface issues, and improve documentation and support workflows. Data used for improvement is, where possible, aggregated or de-identified.
If a later processing purpose materially differs from the original collection purpose, we will provide additional information where appropriate and obtain any authorization required by applicable rules.
Payment data
MiniRents supports USDT-TRC20, as well as Visa, Mastercard, and Amex card payments processed by Stripe. All orders are settled in US dollars (USD); the gateway actually available is determined by the console.
| Payment method | Information received by MiniRents | Information accessed during payment processing |
|---|---|---|
| USDT-TRC20 | Order ID, USD amount due, on-chain transaction reference, receipt status, confirmation result, and necessary reconciliation records. | Blockchain networks publicly record transaction addresses, amounts, transaction hashes, and confirmation status. Do not include sensitive personal information in transaction memos. |
| Visa / Mastercard / Amex (via Stripe) | Order ID, USD amount, payment status, payment method type, transaction reference, and risk or failure result. MiniRents does not receive the full card number or security code. | The payment processor accesses the card and transaction information needed for authorization, risk assessment, settlement, and dispute handling. |
Billing records are used to fulfill orders, reconcile payments, handle disputes, conduct security audits, and meet legal obligations. If a payment fails, we may receive a failure category or risk result to prompt you to check your information or choose a currently available payment gateway.
Retention and security
Retention periods are determined by the purpose of the data, account or order status, security risks, dispute-handling needs, and applicable obligations. Once the purpose is fulfilled, information enters a deletion, anonymization, or restricted-archiving process; records that must be retained by law have restricted access and use.
| Record category | Primary purpose | Retention criteria | End-of-retention handling |
|---|---|---|---|
| Account records | Login verification, permission management, account recovery, and service communications. | Normally retained until the account is closed and the necessary security and dispute-handling periods have ended. | Delete identifying fields or move necessary records to restricted archives. |
| Order and billing records | Order fulfillment, reconciliation, refunds or dispute handling, and legal obligations. | Determined by the transaction relationship, dispute period, and applicable recordkeeping obligations. | Delete nonessential details while retaining the minimum records required by law. |
| Support records | Resolve issues, review outcomes, identify recurring failures, and improve guidance. | Determined by issue complexity, follow-up review needs, and whether a dispute is involved. | Delete attachments and logs no longer needed; retain de-identified summaries when necessary. |
| Security records | Detect unusual access, investigate incidents, limit impact, and prevent repeat attacks. | Determined by incident risk, investigation status, and security audit needs. | Delete details, aggregate statistics, or retain them on a restricted basis where necessary. |
Our security measures
- Limit access to account, order, support, and security records according to job responsibilities.
- Retain necessary logs for key login, permission-change, ticket-handling, and security-response actions.
- Use transmission protection, session controls, and risk checks to reduce the likelihood of interception or misuse.
- Minimize and redact support materials, avoiding credentials and code content that are not needed to resolve the issue.
- Regularly review data purposes and access scope, and delete or de-identify information once its retention purpose has been fulfilled.
- After detecting a security incident, respond by identifying it, limiting its impact, preserving necessary evidence, remediating it, and verifying the result.
No system can eliminate risk entirely. You should also protect your login credentials, use separate and sufficiently strong authentication information, promptly revoke access for departing team members, and avoid sending secret materials in support communications.
Your rights and contact
Subject to applicable rules and the specific circumstances of the processing, you may request access to, correction of, deletion of, or restriction of the processing of your personal information. You may also ask about its source, processing purposes, retention basis, and sharing scope.
Access
Request confirmation of whether MiniRents processes information about you, and obtain applicable records or explanations within the permitted scope.
Correction
Request correction of inaccurate or incomplete account and contact information. For fields you can update yourself, the console will be the preferred option.
Deletion
Request deletion of information that no longer needs to be processed. Minimum records required by law, for dispute handling, or to protect security may not be deleted immediately.
Restriction of processing
Request limits on the use of specific information while its accuracy is verified, an objection is handled, or a dispute is investigated.
How to submit a request
-
1
Choose a contact path
After signing in, submit a ticket through theconsole; if you cannot sign in or have a general privacy question, email support@minirents.com.
-
2
Describe the scope of your request
Provide your account email address, the relevant order or ticket ID, the right you want to exercise, and the applicable time period. Do not include passwords, private keys, or complete payment card details.
-
3
Complete necessary verification
To prevent someone else from impersonating you, we may verify your identity through your existing account or email address. Verification collects only the information needed to complete this step.
-
4
Receive the outcome
We will explain what actions were taken, what could not be completed, and why. If a complex request requires more information, we will continue communicating through the original contact path.
Some rights may be limited by legally applicable exceptions, such as fulfilling a contract, retaining transaction records, investigating security incidents, establishing or handling disputes, or protecting the rights of others. We will limit any exception to what is necessary and explain the reason where appropriate.
This policy and related personal information processing activities are governed by the laws of the jurisdiction where the platform operator is based. Disputes arising from this policy that cannot be resolved through communication will be handled by a court with jurisdiction in that jurisdiction.