Privacy Policy & Personal Information Practices

Scope of this policy

This policy applies to website pages, product information, pricing and node details, and help content provided by MiniRent on macminirent.com, as well as inquiry emails generated and sent through the contact team page. It also covers information users provide in the console to create an account, configure an order, manage a device, view bills, or submit a support ticket.

Website content pages and the console serve different purposes. Content pages explain configurations, pricing, five nodes, and usage boundaries for dedicated physical Mac mini devices; the console handles identity verification, order confirmation, device records, and support requests. We process only the information required for the feature being used and do not request order details unrelated to a visit to public content.

Three types of interaction covered

Browse the website:Read public pages and review plans, nodes, security information, and help content.
Contact us:Send pre-sales recommendations, migration assessments, order questions, or technical-support materials by email.
Use the service:Log in to the console, create or manage orders, receive connection details, view bills, and submit support tickets.

Scope boundaries

Information users actively submit to third-party development tools, code repositories, continuous integration systems, or other external services is governed by those services’ rules. This policy only describes the information MiniRent actually receives and processes as needed to deliver the service.

Information we collect

We collect information for specific tasks rather than building user profiles unrelated to the service. The fields processed depend on whether someone only browses the website, submits an inquiry, creates an account, or has an active order.

Contact and account information

This may include a name, work email address, team size, account identifier, language preference, and contact details provided to receive service notifications.

Inquiry and support-ticket content

This may include the target model, expected duration, target node, workload, problem description, reproduction steps, redacted logs, and context the user chooses to provide.

Order-related records

This may include the order number, device identifier, selected model, billing period, node, add-ons, billing status, and service lifecycle events.

Device and browser information

This may include browser type, device category, operating-system version, page path, request time, network address, and basic error information.

Security and audit logs

This includes login attempts, session changes, credential resets, security-sensitive actions, unusual requests, and audit records created by support staff investigating incidents.

Service-operation information

This includes device delivery status, connection-event results, infrastructure alerts, and fault-diagnosis records. We do not routinely monitor user code or work content.

Do not submit unnecessary keys, complete payment credentials, unredacted logs, or other sensitive content unrelated to your issue in ordinary inquiry emails. When support requires logs, remove tokens, private keys, signing materials, personal communications, and business data first.

How we use information

We use collected information to complete tasks users explicitly request, protect account and device security, fulfill orders, and retain necessary business records. Information is not automatically used for unrelated purposes simply because it may support an analysis.

Handle inquiries: Identify the issue the user wants to solve, assess whether MiniRent M4 Core or MiniRent M4 Plus fits the target workload, and reduce repeated questions.
Provide and manage services: Create accounts, associate orders, configure selected nodes and add-ons, deliver connection details, process billing, and maintain device lifecycle records.
Protect account security: Verify identity, manage sessions, detect unusual logins or high-risk actions, respond to credential issues, and record necessary security audit details.
Diagnose issues: Use device identifiers, issue times, reproduction steps, and redacted logs to investigate connection failures, build failures, disk-space issues, or network problems.
Maintain required records: Retain necessary evidence of orders, payment status, billing, security incidents, and rights requests to support operations, audits, and applicable legal requirements.
Improve website experience: Understand whether pages load correctly, navigation works, and where errors occur, then improve content structure and technical performance.

When processing requires a user choice, we provide an appropriate option. Information used for service delivery, security alerts, order status, and ticket replies is managed separately from optional product communications.

Payment data processing

MiniRent orders are settled in USD and support only USDT-TRC20 and Visa, Mastercard, or Amex through Stripe. Available payment gateways are determined by the result returned in the console.

USDT-TRC20

On-chain transaction details

To match payments with orders, we may process the payment amount, transaction hash, confirmation status, associated receiving address, and order number. Transactions on a public ledger are verifiable; avoid adding unnecessary personal information to transaction memos or support materials.

Cards · via Stripe

Payment-result details

Card entry and payment authentication for Visa, Mastercard, and Amex payments are handled through the applicable payment-processing flow. MiniRent receives the payment status, amount, currency, time, and transaction reference needed to complete an order and does not need to store full card numbers itself.

Payment records are associated with orders, bills, and information needed for refunds or disputes. Payment processors may handle necessary data for security, fraud prevention, and legal obligations; MiniRent uses received results only as needed for order fulfillment, accounting, security investigations, and legal obligations.

We do not operate a business model based on selling personal information. Only when necessary to deliver services, protect security, operate essential infrastructure, or meet legal obligations do we allow responsible processors to access the required fields.

Key information-sharing and delegated-processing scenarios
Processing scenario	Information that may be involved	Limited purpose	Controls
Infrastructure operations	Account identifiers, order associations, device status, and technical logs	Deliver and maintain cloud Mac services	Access authorized by role and limited by scope
Payment processing	Order number, amount, currency, payment status, and transaction reference	Settle in USD and reconcile accounts	Only transaction-required fields are transferred
Security and incident handling	Login records, request information, redacted logs, and incident timelines	Identify, isolate, investigate, and resolve issues	Permissions assigned by incident with audit records retained
Legal obligations	Necessary records directly related to a lawful request	Respond to binding legal requirements	Verify the request’s basis, scope, and authority

Service providers may process information only for agreed purposes and within the necessary scope. If a reorganization, asset transfer, or change in the service operator involves transferring information, we require the successor to continue meeting applicable data-protection obligations and explain the change to affected users when appropriate.

Retention and deletion

We do not use one fixed retention period. Instead, we assess retention based on the processing purpose, order status, security risk, dispute handling, and legal obligations. When the purpose is fulfilled and no basis for continued retention remains, we delete, de-identify, or restrict access to the information.

Inquiry records

Retained for as long as needed to answer the inquiry, complete recommendations or migration assessments, and handle reasonable follow-up communication. If no service relationship develops and there is no basis for continued processing, the records may enter the deletion process.

Order and billing records

Retained as needed to fulfill orders, process bills, reconcile payments, resolve disputes, and meet applicable recordkeeping obligations. Deleting an account does not necessarily immediately delete billing records that must be retained by law.

Security logs

Retained as needed for risk investigations, anomaly detection, and system protection. Records involving unresolved security incidents, abuse investigations, or disputes may be retained until the matter concludes.

Support materials

Tickets, reproduction steps, and redacted logs are retained as needed to resolve issues, verify fixes, and handle subsequent disputes. Users should not upload complete business data unrelated to the issue.

Deletion request process

1
Submit a request
Send an email from the address associated with the account, or log in to the console and submit a support ticket stating what information you want deleted.
2
Verify identity and scope
We may request an order number or other necessary details, but will not ask for sensitive information unrelated to verification.
3
Assess retention requirements
We distinguish information that can be deleted immediately, information whose processing should be restricted, and records that must remain due to billing, security, or legal obligations.
4
Report the outcome
After processing, we explain the measures taken through the original request channel or explain the specific categories and reasons that cannot yet be deleted.

User rights and choices

To the extent permitted by applicable rules, users may request access to, correction of, deletion of, or restricted processing of information concerning them. We verify identity, locate the relevant data, and avoid incorrectly disclosing information about other users or organizations.

AccessAsk whether we process information concerning you and request a copy or description of categories within a reasonable scope.
CorrectionUpdate inaccurate or incomplete contact details, order-related information, and support-request context.
DeletionRequest deletion of personal information when the processing purpose is complete and no basis for continued retention exists.
Restrict processingRequest temporary limits on certain uses while accuracy, the processing basis, or a dispute is being reviewed.
Withdraw optional communicationsStop receiving optional content that is not required for the service, without affecting orders, security alerts, or support-ticket replies.

When submitting a request, specify the request type, associated email address, relevant order or inquiry scope, and the information needed to locate the records. Do not send device credentials or unredacted logs through public channels. We may limit a request and explain why if we cannot verify the requester, the request would affect another person’s rights, or records must continue to be retained by law.

Submit a request by email Submit a support ticket in the console

Cross-region processing, policy updates, and contact

MiniRent provides five cloud Mac service nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the western United States. Choosing a device node means the rented dedicated physical Mac mini operates in that service region; it does not mean account details, inquiry emails, order records, payment-related information, and security logs are stored exclusively there.

To manage accounts and orders, reconcile payments, protect security, and provide technical support, necessary information may be processed across regions by systems or teams with corresponding responsibilities. We apply access controls, transfer safeguards, log audits, and least-privilege measures based on data type, purpose, and risk. Choosing a node does not expand how information is used.

Policy updates

We update this page when service features, information categories, processing purposes, or applicable requirements materially change, and show the new update date at the top of the page. If a change significantly affects user rights or how information is used, we will highlight it through an appropriate account or service notice.

Applicable law and dispute handling

This policy is interpreted and enforced under the laws of the jurisdiction where the platform operator is based. Any dispute arising from this policy or personal-information processing that cannot be resolved through communication will be handled by a court with jurisdiction in that jurisdiction.

Contact us

Privacy inquiries, security reports, data-rights requests, and compliance-material requests may be sent to support@macminirent.com. For existing-order questions, we recommend logging in to the console, submitting a support ticket, and including the order number so we can verify the matter without collecting unrelated information.

For service usage boundaries, please also read theTerms of Service; to confirm what troubleshooting information to include in a support request, see theHelp Center.