Scope
This policy applies to public pages on pingmini.com, pre-sales and technical inquiries, console access from this site, and service delivery activities such as order confirmation, physical node allocation, access credential generation, billing, and support requests.
After you enter the console from this site, orders, payments, subscription management, instance management, and ticket records are processed only to the extent needed to complete the relevant action. Site navigation does not automatically add unsubmitted contact-form content to an order.
If you submit information on behalf of a team, make sure the member information provided is directly relevant to the current purchasing, delivery, or technical support task, and inform those members of the processing scope described in this policy.
You are responsible for organizing and managing code, build artifacts, model files, assets, and project data deployed to your cloud Mac. We process related context only when handling a specific support request, security response, or service operation you authorize, and only as necessary.
Information We Collect
Contact details you provide
When you send a pre-sales, partnership, billing, or technical inquiry, we process the name or preferred form of address, contact email, team use case, desired model, target node, rental period, expected start time, and any additional details you choose to provide.
Order and service details
To match an order with the correct dedicated physical cloud Mac, we process the order number, selected model, billing period, node, additional storage, payment status, service start and end status, and records related to instance delivery and renewal.
Technical issue context
When you submit a support request, you may need to provide a node code, incident time, connection method, error messages, reproduction steps, troubleshooting already performed, and relevant log excerpts. Remove unrelated keys, tokens, project secrets, and personal information before sending.
Basic access and security logs
The website and console may record access times, request paths, network addresses, browser and device types, session identifiers, referring pages, response statuses, and security events. These records help operate the service, identify abnormal requests, and diagnose issues; they are not used to build sensitive profiles unrelated to the service.
Purposes of Use
We use necessary information for specific tasks and do not extend context provided in one inquiry indefinitely to unrelated purposes. Our main processing purposes include:
- Responding to inquiries:Understand workflow, configuration, node, and rental-term needs, then recommend options matching the three configurations currently available.
- Delivering the service:Confirm orders, assign physical nodes, generate connection details, record service status, and handle renewals or configuration changes.
- Protecting account security:Verify account actions, identify unusual sign-ins, investigate credential risks, and apply necessary access controls.
- Troubleshooting:Use order, node, timing, error, and reproduction details to locate connection, build, storage, or performance issues.
- Handling billing:Confirm payment results, create billing records, and gather the information needed for refunds or payment disputes.
- Meeting necessary obligations:Retain transaction, security, and dispute records where required, and respond to valid requests from appropriately authorized parties.
If we need to use collected information for a materially different new purpose, we will first assess the processing basis, necessary scope, and available user choices, and provide additional information where needed.
Payment Information Boundaries
PingMini supports USDT-TRC20 and Visa / Mastercard / Amex via Stripe. All orders are settled in USD; available gateways are determined by the result returned by the console.
Card payments
Card numbers, expiration dates, and security codes required for card payments are handled through Stripe’s payment flow. PingMini retains only the payment status, amount, currency, transaction reference, and limited identifying information needed to complete orders, verify payments, and handle billing issues; we do not store full card numbers or security codes.
USDT-TRC20 payments
For USDT-TRC20 payments, an order may be associated with the payment amount, transaction hash, confirmation status, necessary portions of sending and receiving addresses, and verification time. Blockchain transaction records are public by design and cannot be deleted by PingMini alone.
Payment records are linked to order and billing records to confirm service delivery, resolve payment discrepancies, verify refunds, and support necessary security investigations.
Retention and Security
Retention periods are determined by the processing purpose, order and support relationship, billing requirements, security investigation needs, dispute status, and applicable obligations. When the purpose is complete and continued retention is unnecessary, the information is deleted, anonymized, or moved to restricted archives.
Retention guidelines
- Inquiry records are retained until the issue is resolved, including the necessary period for follow-up communication.
- Order, payment, and billing records are retained for transaction reconciliation, dispute handling, and necessary obligations.
- Support records are retained only as needed to reproduce issues, verify resolutions, and support security investigations.
- Access and security logs are retained on a rolling basis for operational diagnostics, anomaly detection, and incident investigation.
- Information in backups is removed as backups rotate and is not used as routine query data.
Security measures
We use role-based access controls, least privilege, authentication, transmission protection, operational logging, anomaly detection, and incident response procedures. Only authorized personnel responsible for order delivery, billing, security, or support may access relevant information within the scope required for their tasks.
If we discover a security incident that may affect user information, we first contain the impact, verify the scope, preserve investigation records, and remediate the cause. When users need to take action, we provide specific steps through the contact channels on file.
Your Choices and Contact
You may request access, correction, deletion, restriction of processing, or raise other privacy questions about information related to your orders or your team’s orders. To prevent order information from being disclosed to unrelated parties, we may request information that verifies the relevant account or order.
Requests are assessed based on the information type, processing purpose, identity verification result, necessity of transaction and security records, and applicable obligations. Information that has been anonymized or is required for security investigations, billing reconciliation, dispute handling, or necessary obligations may not be immediately deletable.
Submit a privacy request by email
State the request type, associated order number or account email, the information scope to be reviewed, and the necessary context to help verify the request. Do not send passwords, private keys, or complete payment credentials by email.
Send to support@pingmini.comSubmit a ticket through the console
For existing orders, nodes, billing, or technical records, a ticket submitted after signing in makes it easier to associate the service context and reduces the need to repeat account-identifying information.
Submit a request in the consolePolicy updates and dispute handling
If our information practices, service structure, or applicable requirements change, we will update this page, with the current public version describing the rules in effect. Matters relating to this policy are governed by the laws of the jurisdiction where the platform operator is established. Disputes that cannot be resolved through communication will be handled by a court with jurisdiction in that jurisdiction.