This notice explains what information Oakmini processes when you visit the website, use the portal, order a dedicated Mac mini physical node, confirm payment, or contact support. We use necessary data for defined purposes and provide channels for access, correction, deletion, restricted processing, and privacy requests.
Effective date: 2026-08-08 · Contact email: support@oakmini.com
This notice covers Oakmini’s public website, console, order activity, and support processes. It describes information-handling practices and does not change the model, node, billing period, or service configuration confirmed for a specific order.
This notice applies to information processed when you visit pages on oakmini.com, review plans and support materials, use information templates on the contact page, or communicate with Oakmini about cloud Mac services.
It also applies to account and order activity when you create and use a portal account at the Oakmini console, choose Oak Core or Oak Forge, select a node region in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or the western United States, place an order, view host status, manage a subscription, review billing, or submit a support ticket.
Support is available by email to support@oakmini.com and by submitting a ticket after signing in to the console. The contact page describes only these two channels and the information we recommend providing; it does not offer other contact methods. Order identifiers, timestamps, reproduction steps, and redacted logs you add by ticket or email are also support information covered by this notice.
We process different categories of information based on how you use the website, portal, and support channels. Not every visitor generates all of the information below; browsing public pages involves a different scope from placing a cloud Mac order.
This includes the email address used for your portal account, account status, login and security verification records, and any contact name or organization information you provide. We use this information to identify your account, send essential service notices, and protect portal access.
This includes the order identifier, Oak Core or Oak Forge plan, chip and memory configuration, storage add-ons, Thunderbolt 5 linking options, daily, weekly, monthly, or quarterly billing period, and selected node region.
This includes access times, session status, browser and device type, request results, necessary network identifiers, security events, and portal operation records. Logs support login protection, anomaly detection, troubleshooting, and activity tracing.
This includes issue category, order identifier, node region, system version, connection method, error timestamp, reproduction steps, redacted logs, handling progress, and final resolution records in emails or tickets.
This includes order amount, USD settlement currency, payment method type, payment completion status, confirmation status, and records needed for refunds or disputes. Do not submit payment credentials by email or ticket.
This includes page visits, referring pages, basic interaction events, and error states. We use it to assess whether documentation is useful, pages work properly, and troubleshooting paths need improvement.
Before sending logs to the support team, remove passwords, private keys, original signing certificates, access tokens, payment credentials, and other sensitive content that is not needed to diagnose the issue. If a specific configuration excerpt is required, provide only the relevant fields and necessary context.
We use information for purposes directly related to service delivery, reasonably expected by users, and capable of being explained. Different purposes require different information; an order action does not automatically make all information available for unrelated uses.
When existing information needs to be used for a purpose materially different from the original purpose, we assess the relationship between the purposes, the nature of the information, users’ reasonable expectations, and potential impact, and provide additional information or choices where applicable.
Oakmini orders support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All prices and orders are settled in U.S. dollars (USD). The gateway actually available is determined by the result returned by the console at checkout.
| Payment type | Information required for processing | Key status retained by Oakmini |
|---|---|---|
| USDT-TRC20 | Order identifier, USD order amount, and transaction status and timing information needed to confirm payment | Payment pending, confirmation in progress, confirmed, or requiring review |
| Visa / Mastercard / Amex (via Stripe) | Order identifier, USD amount, payment result, and necessary billing and dispute-handling information | Whether payment is complete, result identifier, and necessary records linked to the order |
Card payments are processed by Stripe. Oakmini receives the payment result and necessary order information required to manage completed orders. You do not need to send full card details, security codes, wallet keys, or other payment credentials by support email or console ticket.
Transaction status may be used to activate or continue cloud Mac service, verify duplicate or failed payments, handle billing inquiries, investigate disputes, and create necessary financial records. Payment status is linked to the physical node order but is not used to change your selected chip, memory, storage, node, or billing period.
Information is disclosed only as necessary for service delivery, security, infrastructure operations, payment processing, or legal requirements. Each processing activity must relate to a defined task and be subject to access permissions, role boundaries, and applicable data protection requirements.
Access is assigned by task. Processors may access only the information needed to perform their duties and must not use order, support, or access-log information for purposes unrelated to Oakmini services. If organizational changes or service transitions occur, the information remains subject to the purposes and applicable protections described in this notice.
Retention periods depend on the information type, service relationship, order status, support matter, dispute handling, security audits, and legal obligations. We do not apply one fixed period to every category; instead, we retain, archive, delete, or de-identify information based on the criteria below.
Usually retained while the portal account and order relationship continue. After the relationship ends, necessary records may still be retained for billing reconciliation, dispute handling, security investigations, or legal obligations.
Retained for the period needed for anomaly detection, incident investigation, access tracking, and system security audits. Once no longer necessary, they are deleted, aggregated, or made less identifiable.
Retained while an issue is being handled and, after closure, selected portions may remain available when directly relevant to recurring-issue investigation, service-quality review, or dispute handling.
Retention periods are determined by order management, transaction confirmation, refund or dispute handling, and applicable legal obligations. Complete payment credentials are not collected through support channels.
Security measures include role-based access controls, records of critical administrative actions, session and authentication safeguards, log reviews, necessary data-transmission protections, unusual-activity detection, and access revocation. Only personnel who need to perform service delivery, support, security, or compliance tasks may access relevant information according to their permissions.
You should also protect portal credentials, SSH keys, code repository access, build variables, and signing materials. Do not place passwords, private keys, original signing certificates, or payment credentials in tickets, emails, scripts, or shareable logs. Before sending diagnostic materials to support, redact them and keep the original copy locally.
Depending on the rules that apply to you and the specific processing circumstances, you may submit requests concerning information about you. To prevent unauthorized access, changes, or deletion of account information, we may verify your identity using your portal login status, order identifier, contact email, and necessary account activity.
Some requests may be limited by necessary retention requirements. For example, records may not be immediately deleted when needed to meet legal obligations, confirm transactions, protect account or platform security, establish or handle rights claims, preserve dispute evidence, or prevent deletion from affecting information about other users. Our response will explain the applicable scope and the categories of information that must remain retained.
To submit a request, send it from the email address associated with your portal account to support@oakmini.comor sign in to the console and submit a ticket. We recommend stating the request type, related order identifier, information scope, and approximate time period, but do not include passwords, private keys, original signing certificates, or payment credentials.
The law of the jurisdiction where the platform operator is based applies to matters concerning this notice and related disputes. Matters requiring judicial proceedings will be handled by a court with jurisdiction in that jurisdiction.
We may update this notice as website features, portal processes, order management methods, security measures, processor arrangements, or applicable requirements change. Updated versions will be posted on this page, with the effective date shown by the version date at the top.
When an update materially changes the information categories, processing purposes, sharing scope, or user choices, we will provide an explanation in a manner appropriate to the impact of the change. You may save the current page version and review the latest version before placing a new order or using newly added portal features.
We recommend providing your portal account email, order identifier, request type, relevant time period, and the action you want completed. Do not send account passwords, private keys, original signing certificates, access tokens, or payment credentials.
To learn which issues are best suited to each channel, visit thecontact pagefor submission paths and information templates. Orders, renewals, billing, and host management are all handled in the console.
Your login status and order-linked information help us verify your identity and locate the relevant scope. For general policy questions, email support@oakmini.com.