Scope
This policy applies to the minidebug.com website, MiniDebug Console, Cloud Mac order fulfillment, and communications through support email or console tickets. It covers information generated when visitors browse pages, create or use accounts, choose rental terms and nodes, manage orders, connect to dedicated physical machines, submit troubleshooting materials, or exercise data rights.
The console supports account verification, order configuration, payment status, instance information, subscription management, billing, and ticket handling. Public website pages mainly provide configuration, pricing, node, usage, and policy information. Support workflows cover pre-sales questions, order verification, connection troubleshooting, build-environment troubleshooting, security reports, and privacy requests.
Source code, build artifacts, assets, models, and project configurations that users create, upload, or process on a rented dedicated physical machine do not automatically become website operation data simply because they reside on the host. When access is necessary to deliver the host, respond to a ticket, protect security, or fulfill an explicit user request, we process the materials only to the extent required for that purpose.
This policy does not change the user’s responsibility for managing their code, certificates, assets, models, or build artifacts. Before submitting support materials, remove secrets and personal information unrelated to troubleshooting.
Information We Collect
We collect information necessary for the actions users take rather than requiring every visitor to provide the same data. Visitors who neither create an account nor place an order typically generate only basic website access data. Account, order, and support records are generated when users access the console, purchase services, or submit tickets.
Account and Verification Data
This may include email address, account identifier, verification status, login times, session status, password-reset records, and necessary security-event records. Passwords are processed in a secure form required for verification and are not displayed in support responses.
Order and Billing Records
This may include order ID, MiniDebug M4 configuration, rental period, selected node, storage add-ons, number of Thunderbolt 5 links, USD amount, payment method type, payment result, and renewal or release status.
Device and Connection Metadata
This may include assigned node, host status, connection status, server-side timestamps, source network address, browser or client type, session identifier, and technical information needed to detect unusual access and troubleshoot connection issues.
Support Communications
This may include email or ticket content, order ID, time of occurrence, reproduction steps, expected result, actual result, node information, and screenshots or redacted logs voluntarily submitted by the user.
Operational and Security Logs
This may include login results, permission changes, instance actions, API errors, unusual requests, ticket actions, and security alerts. Logs are used to confirm activity chains, diagnose failures, and prevent unauthorized access.
Website Access Data
This may include pages visited, referring pages, interaction events, device category, browser information, and approximate access time. This data helps us confirm page availability, content discoverability, and errors in key workflows.
Do not submit login passwords, private keys, complete payment credentials, signing-certificate passwords, repository tokens, upload keys, or unredacted project source code in emails, tickets, or log attachments. If troubleshooting requires a specific configuration fragment, provide only the smallest portion needed to reproduce the issue and replace its secrets.
How We Use Information
We use information for service workflows users can reasonably expect and limit access according to the specific purpose. Data does not become available for unlimited secondary uses merely because it is associated with the same account.
-
Account Management
Verify accounts, maintain login sessions, process credential updates, detect unusual access, and provide users with records of account activity.
-
Order Fulfillment
Verify the model, rental period, node, and add-ons; record payment results; and complete host allocation, connection-information delivery, renewal, and release workflows.
-
Node Delivery
Associate orders with the selected node, physical host, and connection status; confirm host availability; and return the relevant management information to the console.
-
Troubleshooting
Use order IDs, nodes, timestamps, operating steps, and redacted logs to distinguish infrastructure, connection, macOS environment, and project-configuration issues.
-
Security Protection
Detect unusual logins, abuse, unauthorized requests, and activity that may affect node operation, and retain necessary response records.
-
Service Improvements and Necessary Notices
Analyze workflow errors, improve documentation, and send notices required for order status, security changes, material policy updates, or service delivery.
Access data used for page improvements is intended to identify overall usability issues, not to fabricate reviews, ratings, or user numbers. If a new use materially differs from the original collection purpose, we will provide the necessary explanation first and obtain authorization when required.
Payment Information
MiniDebug supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All orders are settled in USD. Available payment options are determined by the result returned by the console.
| Payment method | Information processed during payment | Order information retained by MiniDebug |
|---|---|---|
| USDT-TRC20 | Payment address, on-chain transaction ID, amount, confirmation status, completion time, and other information needed for verification. | Order ID, USD order amount, payment method type, verification result, and order status. |
| Visa / Mastercard / Amex (via Stripe) | Card payment details are processed by Stripe through its payment workflow. | Order ID, USD amount, payment method type, payment result, and necessary transaction references; complete card numbers or security codes are generally not received. |
The website presents service information, the console creates and manages orders, and the payment-processing workflow verifies the selected payment method. We will not ask users to send complete card details, wallet private keys, seed phrases, or other credentials that could directly control funds by support email.
Refunds, payment reconciliation, or unusual-transaction investigations may require linking an order ID, payment result, and transaction ID. When submitting related materials, users should cover account balances, other transaction records, and personal data unrelated to verifying the order.
Retention and Deletion
Retention periods are determined by service delivery, billing reconciliation, security, dispute handling, and applicable obligations—not by a default goal of keeping information indefinitely. Because records serve different purposes, deleting an account may not remove records still needed for order reconciliation or legal obligations.
| Record category | Primary retention grounds | Deletion or correction process |
|---|---|---|
| Account data | Account access, identity verification, security controls, and user-request handling. | Users may request correction or deletion. We will first address any active orders, incomplete billing, or security disputes. |
| Order and billing records | Order fulfillment, payment reconciliation, financial records, refunds, or dispute handling. | Users may request correction of inaccurate information. Information that must be retained by law or to handle a valid dispute will be deleted or de-identified after the basis for retention ends. |
| Support records | Tracking issue handling, reproducing failures, avoiding duplicate submissions, and confirming resolution. | Users may request deletion of attachments or content unrelated to the ticket’s purpose. Necessary issue records may be retained until handling and a reasonable review period are complete. |
| Security and operational logs | Anomaly detection, access audits, fault diagnosis, and abuse prevention. | Access is restricted as needed for security and records are regularly cleared. Records concerning an ongoing investigation may be retained until the investigation and follow-up actions are complete. |
Users should back up any source code, certificates, assets, models, caches, and build artifacts they need before the rental ends or the host is released. After release, console order records and user data on the host are handled separately; order records may remain stored under the grounds described above.
To request deletion or correction, log in to the console and submit a ticket, or email support@minidebug.com. Include the account email, relevant order ID, information category to be handled, and specific reason, but do not attach passwords, private keys, or complete payment credentials.
Cross-Region Processing
MiniDebug offers five nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the U.S. East Coast. When users choose different nodes or access the website, console, or host from different regions, order information, connection metadata, support materials, and necessary operational records may be transferred to or processed in regions required to provide the service.
Node selection determines where the dedicated physical machine is delivered, but does not mean account, payment-processing, support, and website-access data are stored only at that node. Information enters the relevant workflows based on the actual needs of account management, payment verification, node operations, security, and support.
Cross-region processing follows the principle of necessity: we transfer only information needed to deliver orders, maintain connections, respond to security events, or fulfill user requests, and reduce unnecessary access through access controls, separation of privileges, and logging.
User Rights and Contact
To the extent permitted by applicable rules, users may ask how information related to their account is processed, access identifiable account data, correct inaccurate information, delete information no longer needed, or ask questions about specific processing activities.
Review your data
Request information about the categories, sources, purposes, and processing scope of account, order, or support records.
Correct inaccurate data
Identify the fields to change, their current values, and the correct values so we can verify and update them.
Request data cleanup
Specify the account data, attachments, support content, or other categories to delete, along with the relevant order or ticket ID.
Ask a privacy question
Ask about information use, sharing scope, retention grounds, cross-region processing, or specific provisions of this policy.
To prevent impersonation and unauthorized access to or deletion of account data, we may require necessary account verification and information that helps locate the relevant records. Verification materials are used only to confirm the requester’s connection to the account or order and must not include passwords, private keys, or complete payment credentials.
There are two ways to submit a request: log in to the console to create a ticket, which is best for issues linked to an existing account, order, or instance; or email support@minidebug.com, which is best if you cannot log in or have a general privacy question. For existing orders, console tickets are preferred to reduce back-and-forth verification.
Policy Updates
We may update this policy when service workflows, information types, payment processing, security measures, or applicable rules change. Material changes involving information use, sharing scope, user rights, or retention will be announced prominently on the website, through console notifications, or by account email.
Updated policies will show a new effective date. Minor wording corrections, layout changes, or clarifications that do not materially affect user rights will also appear in the current version. To request a historical version, submit a console ticket or email support@minidebug.com and specify the version range you want to review.
This policy and related disputes are governed by the laws of the jurisdiction where the platform operator is based. Disputes that cannot be resolved through support will be handled by a court with jurisdiction in that jurisdiction. Rights that applicable rules make non-waivable are not affected by this section.