Scope and roles across each process
This policy applies to the public content, contact communications, Cloud Mac ordering and management processes G-Mini provides to visitors and customers. Each access point serves a different function, so the types of data accessed and the processing purposes vary.
globemini.com content site
Used to present dedicated physical Cloud Mac configurations, nodes, billing rules, connection guides and policy documents. The content site processes basic access information needed for page delivery, security protection and language presentation, but does not process device connection credentials on public pages.
Contact requests
Users can contact support by email for pre-sales selection, technical support, orders and billing, or partnership inquiries. Email content is provided voluntarily and should contain only the context needed to resolve the issue. Redact data before sending logs, screenshots or configuration details.
Console processes
The console supports account verification, model and node selection, order submission, billing-status viewing, instance management and ticket creation. It processes information needed for service delivery, account security and order identification, with access limited according to the current action.
This policy does not change how responsibility for project code, build artifacts, development-tool configuration or access authorization is allocated between users and their team members. Team account administrators should ensure that console and Cloud Mac access is granted only to members who need it.
What information we collect in each scenario
We process only the minimum information needed for each workflow. You can browse public content without providing order details, and we never ask for login passwords or private keys through public contact channels.
| Data category | Typical contents | Collection scenario |
|---|---|---|
| Access logs | Request time, pages visited, response status, network address, security-event identifiers and necessary request-header information | Page delivery, error diagnosis, abuse detection and security audits |
| Device and browser information | Browser type, operating-system category, screen-adaptation information, device category and basic compatibility parameters | Page adaptation, display troubleshooting and accessibility improvements |
| Language preferences | The site language selected by the user and related local-storage state | Maintaining the interface-language selection without forcing redirects to content pages |
| Contact content | Name, work email, issue type, preferred node, model, rental period and descriptions entered voluntarily by the user | Pre-sales selection, migration advice, technical troubleshooting and partnership communications |
| Order identification information | Account identifier, order number, selected model, billing cycle, node, add-ons and order status | Creating orders, delivering physical nodes, verifying service scope and billing |
| Support communications | Ticket subject, issue description, time of occurrence, macOS and tool versions, reproduction steps and redacted logs | Request routing, fault diagnosis, solution records and follow-up review |
Remove passwords, private keys, access tokens, repository secrets, complete connection credentials and personal information unrelated to the issue. To reference an existing order, provide the console order number instead of forwarding complete payment credentials.
Data is used only for defined service and security purposes
We process data based on user-initiated actions, service-delivery needs, account and infrastructure security requirements, and the scope needed to meet necessary obligations. The main purposes are as follows.
Service delivery
Confirm the GlobeMini M4 16 or GlobeMini M4 24 model, rental period, node and add-ons in the order, then deliver the corresponding dedicated physical node to the account.
Account security
Verify account actions, identify unusual logins or abuse, restrict unauthorized access and record key security-related actions.
Troubleshooting
Use the order number, node, time of occurrence, macOS version, tool version, reproduction steps and redacted logs to locate connection, build or environment issues.
Customer support
Route requests, preserve issue context, record troubleshooting steps already performed and avoid asking users to resubmit the same materials in later communications.
Billing verification
Link the order amount, payment method, transaction identifiers and payment status to the relevant service order to confirm settlement and address billing questions.
Website improvements
Use aggregated page visits, error statuses, browser compatibility and language-usage data to improve content structure and page performance.
Meeting necessary obligations
Retain necessary records, respond to valid requests and maintain audit trails related to services, billing and security incidents to the extent required by applicable rules.
If a later processing purpose materially differs from the purpose at collection, we will first assess its necessity, impact and applicable requirements, and update this notice or obtain appropriate authorization when needed. Order-support information will not be repurposed for unrelated uses without notice.
Boundaries for processing payment-related data
All G-Mini orders are settled in USD. We support only USDT-TRC20 and Visa, Mastercard and Amex processed by Stripe. The gateways currently available are shown in real time in the console.
Create an order
The console records the model, period, node, add-ons, amount due in USD and order-identification information.
Process payment
The relevant payment processor completes the transaction. G-Mini receives the transaction identifiers, status and necessary risk results required to verify the order.
Link delivery
The payment status is linked to the order number to confirm service activation, billing inquiries and subsequent order support.
What we process
- Order number, USD amount and payment status
- Payment-method category and necessary transaction-identification information
- Billing verification, anomaly investigations and support-communication records
Public contact requests must not include
- Complete card credentials or security codes
- Wallet private keys, seed phrases or account passwords
- Complete transaction details unrelated to order verification
Retention periods depend on the purpose of each record
Different records serve different purposes, so we do not apply one unverified fixed period to all data. Retention decisions consider whether the service is still being provided, whether records are still needed for billing or support verification, whether security risks exist and whether necessary obligations apply.
| Record type | Primary retention criteria | Deletion or de-identification conditions |
|---|---|---|
| Order records | Used for service delivery, order status, billing verification, dispute handling and necessary audits | After the relevant purposes are complete and no continued retention is required, delete unnecessary fields or de-identify the record |
| Support records | Used to preserve troubleshooting context, verify resolution, identify recurring faults and handle follow-up requests | When the issue is closed and further support is no longer needed, assess deletion of attachments, redacted logs and nonessential context |
| Security logs | Used for anomaly detection, account protection, incident investigation, access audits and preventing repeated abuse | After risk assessment and audit purposes are complete, delete, aggregate or de-identify as security needs require |
| Contact requests | Used to complete pre-sales responses, migration advice or partnership communications, or to route an issue into support | When the request is complete and there is no ongoing business relationship or necessary follow-up, delete contact content that is no longer needed |
After receiving a valid deletion request, we will verify the requester’s identity, confirm the data scope and determine whether continued retention is necessary. If some records cannot be deleted immediately because of billing verification, security audits or necessary obligations, we will restrict their use and access and explain the outcome to the requester.
Access isolation, transmission protection and cross-region access
G-Mini uses organizational and technical measures to reduce the risks of unauthorized access, misuse, loss or improper disclosure. Security controls are configured separately for accounts, orders, support and node operations so that no role automatically accesses all data.
Access isolation
Permissions for content management, order support, security investigations and node operations are granted by role, with access no longer needed reviewed regularly.
Transmission protection
Appropriate protections are applied to data transmitted through the website, console and support processes to reduce the risk of interception or alteration in transit.
Log auditing
We record events related to account security, order status and key administrative actions for anomaly detection, issue tracking and accountability checks.
Node access controls
Node operations process only the information needed for delivery, networking, device status and fault diagnosis. A node’s location does not expand access to user project content.
Why cross-region access may be necessary
Users can access the console from different regions and choose physical nodes in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong or the western United States. To complete node delivery, support troubleshooting, security response and order verification, authorized personnel or processors may access necessary data at relevant operating locations. Such access is controlled by role, purpose, permissions and auditing.
Choosing a node does not mean that all account and contact data will be copied to that node. Whether data requires cross-region access depends on order delivery, the scope of a fault, a security incident and support requests initiated by the user.
How to request access, correction, deletion or restriction
Users may request access, correction, deletion or restriction of processing for data related to their account, contact requests, orders or support records. Requests should identify the target data, relevant process and preferred action so we can locate the records accurately.
Access
Confirm whether we process information about the requester and learn the relevant data categories, purposes and retention standards.
Correction
Correct inaccurate or incomplete account contact information, order-linked information or factual errors in support records.
Deletion
Request deletion of data that is no longer needed. We will also check whether billing, security or necessary obligations require some records to be retained.
Restriction of processing
Request temporary limits on the use of relevant data while accuracy, processing grounds or a dispute is being reviewed.
Send a support email
Send an email from the address associated with your account or order to support@globemini.com, put “Data request” in the subject line, and state the request type, relevant process and order or ticket number that can help locate the records.
Send a data request emailSubmit a ticket through the console
After signing in, create a ticket to link the request directly to an existing account, order or support record. Do not enter passwords, private keys or complete payment credentials in the ticket.
Submit a ticket in the consoleTo prevent others from impersonating you to access or delete data, we may ask the requester to complete reasonable verification through the account email, console session, order number or an existing ticket. Verification materials are used only to confirm the requester’s relationship to the target records; do not submit passwords, private keys or complete payment credentials.
Policy updates are not made without notice
When data types, processing purposes, payment processes, node operations, user choices or applicable requirements change significantly, we will update this page and retain identifiable version information, revision dates and change summaries.
Significant changes will be communicated in a manner proportionate to their impact. Historical versions will not be directly replaced by new text without version identification. If an update concerns an order currently being fulfilled, the specific service relationship should also be understood together with the valid order confirmation and applicable terms.
Applicable rules and dispute resolution
This policy is interpreted and enforced under the laws of the jurisdiction where the platform operator is based. Any dispute arising from this policy that cannot be resolved through communication may be submitted to a court with jurisdiction in that jurisdiction.