Clear boundaries for information handling

This Privacy Policy applies to the deploymini.com website, related forms available on the site, account and order workflows, and communications through the support email or console tickets. Whether you are comparing plans, creating an order, managing a rental period, or submitting a technical issue, this policy explains the boundaries for processing relevant personal information and business records.

If a console feature provides more specific data notices, such as identity verification, billing details, or device activity records, those notices supplement the information shown here. Together, the additional notice and this policy provide the basis for processing in the relevant workflow.

Source code, build artifacts, models, media assets, and configuration files that users create, upload, sync, or generate on a dedicated physical machine are not website form data. Users manage this device data directly, subject to the boundaries described in the “Device and project data” section of this policy.

We process information only to the minimum extent needed to complete a specific workflow. The data categories generated vary depending on the features each user accesses.

Attachments, screenshots, or logs sent by users may contain project names, file paths, internal hostnames, or other context. Before submitting them, remove passwords, private keys, tokens, and complete payment credentials, and include only the excerpts needed to troubleshoot the issue.

We do not process collected information outside reasonable business purposes. Information is primarily used for the following tasks:

• Provide and deliver services Create and manage orders, associate dedicated physical machine configurations, display rental and billing status, and provide account features requested by users.
• Verify orders and requests Confirm order ownership, resolve configuration or billing issues, and verify the requester’s identity when sensitive actions are involved.
• Protect service security Detect unusual access, abuse, credential attacks, and security incidents that could affect a node or other users.
• Respond to support requests Use the order number, node, time of occurrence, and redacted logs to identify connection, device, network, or billing issues.
• Improve the site experience Analyze page errors, feature availability, and navigation paths to reduce repetitive actions and improve explanatory content.
• Meet necessary obligations Retain records needed for legal, billing, security audit, and dispute-resolution purposes, and respond to valid rights requests.

When the purpose of processing materially changes, we assess whether to update this notice, reduce the data scope, or obtain additional authorization rather than automatically extending existing data to unrelated uses.

DplyMini supports USDT-TRC20 and Visa, Mastercard, and Amex through Stripe. All charges are settled in U.S. dollars (USD). Available payment gateways are determined by the checkout interface in real time.

Payment information is handled by the relevant payment provider according to its procedures. We receive only the transaction status, transaction identifier, amount, currency, and other necessary status information needed for order verification, delivery, billing records, and exception handling.

We do not ask users to submit complete card details, complete on-chain credentials, passwords, private keys, or other sensitive information that could directly authorize a payment through email or console tickets. To verify a transaction, provide the order number, transaction identifier, and necessary redacted screenshots.

DplyMini provides dedicated physical cloud Mac machines, not virtual machines. Users decide how to use and manage repositories, signing materials, build caches, models, media assets, test data, environment variables, and build artifacts stored on the device.

Configure access permissions according to project sensitivity, encrypt sensitive files appropriately, and keep important data in a separate backup location. A dedicated machine should not be treated as the only copy of project data, especially for short-term rentals, batch jobs, or collaborative work.

When users request support, we need only the minimum information related to the issue. Unless necessary to investigate a specific problem and explicitly provided by the user, do not send complete projects, unredacted configurations, or usable access credentials in a ticket.

We use relevant service providers only as needed to deliver services, protect security, process payments, meet necessary obligations, or act on user authorization. Their processing is limited by the functions they perform and does not automatically grant access to unrelated data.

Processing roles may include infrastructure and node services, payment processing, email delivery, security protection, error diagnostics, and necessary business support. Information provided to a processor is limited to what is needed for its task. For example, a payment provider processing a transaction does not need access to project content on a user’s dedicated device.

We may provide relevant records when necessary for legal proceedings, security incidents, or the protection of rights, based on a valid request. We review the request basis, data scope, and necessity, and limit disclosure where permitted.

If users authorize team members, contractors, or others to access an account, order, or device, their actions fall within the user’s authorization. Users should review authorization relationships regularly and revoke access promptly when roles change.

Retention periods are determined separately based on service delivery, billing verification, security investigations, rights requests, and applicable legal obligations. We do not apply one fixed period to all data. We consider the data type, processing purpose, sensitivity, and need for continued retention.

Account and order records

Retained for as long as needed for account and order management, billing verification, dispute resolution, and necessary audits.

Access and security logs

Retained for as long as needed to investigate errors, identify unusual behavior, and protect the service, with access limited to authorized personnel.

Support tickets

Retained for as long as needed to resolve issues, document outcomes, and identify recurring failures. Attachments that are no longer needed may be removed first.

Device project data

Managed directly by the user during the rental period. Users should complete exports, backups, credential revocation, and necessary cleanup before the rental ends.

After the retention purpose ends, information is deleted, aggregated, or de-identified according to its nature and system capabilities. Records that cannot be deleted immediately because of backup rotation, security isolation, or valid legal requirements remain access-restricted and are handled when the relevant condition ends.

The physical node selected by the user, team members, and relevant service providers may be located in different regions. Account, order, support, or necessary technical data may therefore be processed across regions. Processing locations depend on the services selected, support workflow, and infrastructure needed to provide the relevant functions.

We use safeguards appropriate to the data type and risk, including role-based access, identity verification, access logs, necessary transmission protection, anomaly detection, and limits on internal processing scope. Personnel who need access to business information act only within the scope required by their responsibilities.

No technical measure replaces the user’s own credential management. If account, key, or device access may have been compromised, immediately revoke the relevant credentials and submit a ticket through the console with the order number, node, time of occurrence, and redacted logs.

You may request access, correction, deletion, restriction of processing, or other applicable action regarding information related to you. You may also ask about the source, purpose, sharing scope, and retention logic for a category of information. The available scope depends on the nature of the request, account status, and necessary legal or security restrictions.

To prevent impersonation and unauthorized access to or modification of data, we may ask the requester for the account email, relevant order number, or other information sufficient to verify identity. Verification materials should be limited to what is needed and must not include passwords, private keys, or complete payment credentials.

Applicable rules and dispute resolution

This policy is interpreted and applied under the laws of the jurisdiction where the platform operator is based. Disputes related to this policy should first be raised through the support channel; if unresolved, they will be handled by a court with jurisdiction in that jurisdiction.

Policy updates

We may update this policy when the service scope, data processing methods, or applicable requirements change. We will announce material changes through the website, console, or another appropriate method. The updated version applies from its stated effective date.