Privacy Policy and Personal Data Processing Rules

01

Service scope

Scope

This policy applies to data processing when you visit setmini.com, create or manage an account, configure an order, check delivery information, submit a support ticket, or use SetMini cloud Mac services. Cloud Mac means Apple Silicon physical nodes provided by SetMini for remote access; rented instances run on dedicated physical machines with computing resources isolated from other tenants.

Website activity includes page requests, security checks, necessary session state, and language preferences. Account and order data includes registration details, model and datacenter selections, rental term, add-ons, payment status, and delivery records. Support data includes email correspondence, console tickets, incident times, error output, and diagnostic information you choose to submit.

Website Page requests, language preferences, and security-event detection

Accounts and orders Identity and contact details, configuration choices, and delivery status

Support communications Ticket content, issue context, and handling records

Physical node services Records required for access, operations, and security audits

This policy does not expand our rights to use your project content. Code, build artifacts, media assets, and business files stored on your dedicated physical node remain under your control. We do not read this content for advertising profiles, content training, or data sales.

02

Data categories

Data collected

We collect only the data needed to provide the service. Different actions create different records; simply browsing the website does not automatically create complete order details, and no ticket content is created if you do not submit a support request.

Account information: Work email, account identifier, verification status, login-security records, and contact information you provide.
Order information: Selected SetMini M4 or SetMini M4 Pro, rental term, datacenter, SSD upgrade, number of Thunderbolt 5 links, order number, and delivery status.
Payment status: USD amount due, payment-method category, transaction status, reconciliation identifier, and necessary refund or dispute records. We do not store complete card numbers or security codes in our own systems.
Device and access logs: Access time, network address, browser or client type, account actions, authentication results, node-access events, and security alerts. Logs protect accounts and physical nodes; they are not used for cross-site ad tracking.
Support records: Ticket subject, order number, target node, incident time, error output, steps taken, email correspondence, and resolution.
Information you submit: Team size, workflow context, system versions, and other details you provide during consultations, migration assessments, compliance requests, or troubleshooting.

03

Processing basis

Purposes

We use relevant data only to provide contracted services, protect accounts and nodes, meet applicable obligations, or handle requests you expressly make. Each purpose corresponds to the data category used; data collected for delivery is not repurposed for unrelated marketing.

Account and service delivery Verify your email, create your account, record configuration choices, deliver access details, and let you view orders and service status in the console.
Identity and security verification Detect unusual logins, repeated verification failures, unauthorized actions, and behavior that could affect the security of dedicated physical machines.
Service operations Monitor node availability, locate connection issues, confirm resource expansions, and maintain the capabilities required for continuous year-round operation.
Billing and reconciliation Generate USD order amounts, verify payment results, process renewals, add-ons, refund requests, and financial records.
Troubleshooting Reproduce issues using the order number, node, incident time, and error output; record steps taken and document the resolution.
Legal obligations Meet accounting, security-incident response, valid legal-process, and other obligations required by the laws of the jurisdiction where the platform operator is established, to the extent necessary.

04

Billing scope

Payment data

All SetMini orders are billed in USD. The only supported payment methods are USDT-TRC20 and card payments via Visa, Mastercard, and Amex processed by Stripe; the gateway actually available at checkout is determined by the result returned by the backend.

Digital-asset payment USDT-TRC20

We record the order amount, payment status, necessary transaction identifiers, and reconciliation result. We never require you to send a wallet private key through support communications.

Card payment Visa / Mastercard / Amex

Stripe processes card details through its payment flow. SetMini receives the payment status and limited transaction information needed to complete the order and reconciliation.

Payment records are linked to the order number, model, rental term, node, and add-ons to verify delivery, renewals, and disputes. We do not sell payment data or use transaction information to build consumer profiles unrelated to the service.

05

Data lifecycle

Retention and deletion

Retention periods depend on the data purpose, account status, order relationship, security needs, and applicable record-keeping obligations. We do not retain all data indefinitely for convenience; once its purpose is met, we delete it, de-identify it, or restrict access.

Account information: Retained while the account is active. After closure, it is deleted or de-identified once open orders, disputes, security checks, and necessary record-keeping obligations are completed.
Order and payment records: Retained as necessary to prove delivery, reconcile accounts, maintain financial records, and handle disputes. After the applicable period, non-essential fields are deleted; legally required records remain subject to restricted use and access.
Support records: Retained while a ticket is handled and during a reasonable follow-up period to avoid repeated troubleshooting and confirm the resolution. You may request deletion of attachments or details unrelated to continued service.
Security logs: Retained as long as needed to identify unusual access, investigate security incidents, and protect physical nodes. After their security purpose ends, they are deleted or aggregated.
User data on nodes: Managed by you during the rental period. Before service ends, you should move out required files and remove sensitive content; after termination, the environment is released according to the delivery and cleanup process.

A deletion request does not automatically override data tied to an active order, unresolved dispute, security investigation, or legal retention obligation. Where deletion is temporarily unavailable, we explain the category, reason, and conditions for later action and restrict further use.

06

Access controls

SetMini does not sell personal data. Access follows role-based need and least privilege. Only personnel and service providers who need the information to perform order, billing, security, support, or compliance duties may process it.

Internal authorization

Support staff may view account, order, and diagnostic information related to a ticket; billing staff access only what is needed for reconciliation; node operations access is governed by permissions and logging.

Necessary service providers

Payment, infrastructure, security, and email-delivery providers process data only to perform specified functions and are subject to applicable confidentiality and security requirements.

Legal requirements

When we receive valid and binding legal process, we disclose only what is necessary and verify the requester’s authority, scope, and target.

Security-incident response

To prevent unauthorized access, malicious-code propagation, or effects on other physical nodes, we may provide limited incident information to necessary security partners.

For data processing across jurisdictions, we use contractual, access-control, and transfer-protection measures proportionate to the data’s sensitivity. Disputes related to this policy are governed by the laws of the jurisdiction where the platform operator is established and handled by courts with jurisdiction there.

07

Request process

Your rights

To the extent allowed by applicable rules, you may request access to, correction of, deletion of, or restriction of processing for data about you. You may also ask about specific data categories, processing purposes, retention basis, and sharing scope.

1
Submit a request
Send from your registered email to support@setmini.com, or log in to the console and submit a ticket. State the request type and relevant order number.
2
Verify your identity
To prevent others from obtaining or deleting account data, we may verify your registered email, order identifier, and recent account activity. Do not send passwords or private keys by email.
3
Confirm the scope
We distinguish data that can be handled immediately, data affected by active orders, and data that must be temporarily retained for security, disputes, or record-keeping obligations.
4
Receive the result
Once complete, we explain the actions taken through the original request channel. If your request is restricted, we explain the restriction category, reason, and information you may provide next.

Privacy questions and rights requests do not affect your normal use of existing services. To help us locate records accurately, contact us from your account email and include an order number where applicable. Do not submit project files unrelated to your request.

08

Protection and changes

Security and updates

We use layered measures to protect account, order, support-record, and physical-node service data. No single measure replaces complete access management; encryption in transit, permissions, logs, incident response, and user-side credential management together form the protection boundary.

Protection in transit
The website, account actions, and support channels use encrypted connections to reduce the risk of data being read or altered in transit.
Access controls
Internal access is authorized by role; sensitive actions require authentication, least privilege, and approval where necessary.
Audit logs
We record necessary authentication, account-action, and node-security events to detect anomalies, review handling, and limit unauthorized access.
Incident notifications
If we confirm an incident may materially affect user rights, we provide necessary notification and response guidance based on its scope, available contact information, and applicable requirements.

We may update this policy when services, processing practices, or applicable requirements change. Material changes will be notified reasonably through the website, console, or registered email. Updated versions show a new effective date; continued use of the service after that date means you have received and understood the updated processing rules.