We process only the information necessary to deliver services, verify orders, protect security and troubleshoot issues. Selling personal information is not our business model, and we will never ask you to send access keys or other valid credentials through public channels.
Scope of this policy
This policy applies to information processing when you visit hireamac.com, read product and help content, access the console through on-site links, or contact HireAMac by email or console ticket.
Public pages primarily provide configurations, prices, regions, remote access, security information and legal documents for three Apple Silicon cloud Mac tiers. When you only browse this content, we may process limited technical data needed to deliver pages, detect security issues and analyze basic access activity.
Our contact page explains available contact channels and submission requirements; it currently does not provide an online message form. For pre-sales, migration, technical, billing, partnership or privacy questions, contact support@hireamac.com or log in to the console to submit a ticket. Information you actively send through either channel is contact and support information covered by this policy.
When you access the console to register, log in, place an order, make a payment, manage an instance, view billing information or submit a ticket, we process the relevant information only as needed for that action. Console order and service records may be linked to inquiries submitted on the public website to identify the relevant order and physical node.
This policy does not cover software you install yourself, connected code repositories, uploaded business files or other services you choose to connect. You should assess how those tools handle data under their own rules and project requirements.
Information we collect
We process necessary information only in clearly defined service contexts. The scope depends on whether you browse the website, submit an inquiry, create an order, manage a node or request technical support.
Contact details
This may include your name or preferred form of address, support email address, team or project context, requested response and workflow requirements you voluntarily provide in an inquiry.
Order details
This may include the order ID, selected model, rental period, node region, additional storage, Thunderbolt 5 daisy-chaining option, payment status and service status.
Technical support information
This may include when the issue occurred, reproduction steps, system version, toolchain status, error messages, redacted logs, session status and screenshots you voluntarily provide.
Basic access logs
These may include request time, page visited, browser type, device category, network address, security event markers, request result and error status, among other limited records.
Payments support USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only; all orders are settled in USD. We may process payment results, transaction references, amounts, times and statuses related to order verification, but we do not directly collect full card details on website pages.
Do not include access keys, private keys, complete payment credentials, unredacted tokens or sensitive files unrelated to troubleshooting in emails, tickets, screenshots or logs. If support materials contain more information than needed, we may ask you to resubmit a redacted version.
How we use information
We do not use collected information arbitrarily outside the service context. Each processing activity has a defined purpose and is limited to what is reasonably necessary to fulfill it.
- Provide and manage services
- Create and manage orders, associate them with dedicated physical nodes, display rental and billing status, provide remote connection details, and handle model, node or add-on changes.
- Handle inquiries
- Understand pre-sales configuration, node selection, migration planning, partnership or privacy questions, and route requests to the appropriate person.
- Troubleshoot issues
- Use the order ID, node region, time of occurrence, reproduction steps and redacted logs to locate connection, build, storage or console issues.
- Protect service security
- Identify unusual logins, unauthorized access attempts, malicious scans, credential abuse and activity that may affect physical nodes or management systems.
- Verify billing and payments
- Confirm order amounts, rental periods, add-ons, payment results and transaction records related to refunds or disputes, preventing discrepancies between order status and processing results.
- Meet necessary obligations
- Retain transaction and security records required by applicable law, respond to valid legal processes, and establish, exercise or protect legal rights where reasonably necessary.
Where applicable rules require consent, we process information based on your explicit choice. For service delivery, security, dispute handling or necessary legal obligations, processing may instead rely on the relevant contract, legitimate interest or legal obligation.
Technical and diagnostic data
To ensure the website and console return pages correctly, identify errors and prevent abuse, we may process the minimum technical and diagnostic information necessary. Browsers, servers or security systems typically generate this information when a request occurs.
| Data category | Typical fields | Processing purpose |
|---|---|---|
| Device and environment | Device category, operating system category, screen and language settings | Deliver compatible pages and determine whether interface issues are environment-related |
| Browser information | Browser type, version and feature support | Locate page-rendering, login or console interaction issues |
| Access records | Access time, page path, referring page and request result | Analyze request paths, find broken entry points and verify event order |
| Network and security | Network address, session identifier and security event markers | Protect accounts, limit abnormal requests and investigate unauthorized activity |
| Errors and diagnostics | Error codes, failed steps and service response status | Reproduce issues, confirm impact and verify resolution |
Technical logs should avoid including business file contents and valid credentials wherever possible. When manual investigation is needed, support staff should access only records relevant to the specific issue and narrow the search by order ID, time range and error status.
Basic access analysis helps us understand whether pages work, whether entry points are broken and where errors occur. It is not used to build profiles unrelated to cloud Mac services. Browser privacy settings may limit some basic analysis, but should not prevent you from reading public policy and help content.
Information sharing and processors
We do not sell personal information. We provide information to processors with defined functions only when needed to deliver services, process payments, protect systems or meet necessary legal obligations.
- Service delivery: To create orders, assign dedicated physical nodes and provide connection and management functions, relevant order IDs, models, nodes, rental periods and service statuses may move between necessary operational systems.
- Infrastructure: To host the website, route requests, retain necessary records and prevent abnormal access, infrastructure processors may access limited network, device and log information.
- Payment processing: For Visa / Mastercard / Amex (via Stripe), information needed for payment processing is handled through the relevant payment flow. For USDT-TRC20, we process the address, transaction reference, amount and status needed to verify the transaction. Both methods record order amounts in USD.
- Professional services: Where necessary for billing verification, security investigations, compliance assessments or dispute handling, limited information may be provided to professional service providers bound by confidentiality obligations.
- Legal requirements: When we receive a binding, specific and lawful request, we may provide information that must legally be disclosed, and where permitted, review the requester, scope and validity.
We require processors to handle information only for agreed purposes and to apply access controls and security measures appropriate to their role. Sharing follows the data-minimization principle: for example, payment processors do not need technical support logs, and infrastructure processors do not need the full business context of an inquiry.
Cloud Mac services include five node locations: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and the Eastern United States. The region you select may affect where business data is processed. Consider your collaboration paths, internal policies and applicable requirements before choosing a region.
Retention and security measures
Retention periods are determined by the processing purpose, order relationship, support needs, security risks, dispute handling and necessary legal obligations. We do not retain all information indefinitely simply because it is technically possible.
Retain only as needed
Order and billing information is retained for the period needed to provide services, verify transactions, handle disputes and meet necessary recordkeeping requirements. Routine inquiries and diagnostic materials are reduced or deleted as needed after the matter is resolved.
Limit access
Access permissions are assigned by role and task. Billing staff should not automatically receive complete technical logs, and staff handling routine support should not access records unrelated to the issue.
Redact logs and materials
Diagnostic materials should remove access keys, private keys, tokens and irrelevant personal information. Log searches should prioritize order IDs, nodes, times and error codes rather than copying large amounts of raw data.
Protect credentials
Users should securely maintain and regularly update account credentials. Do not send valid credentials by email or through public channels. If you suspect a credential has been exposed, replace it immediately and report the incident through a console ticket.
We use access restrictions, transmission protection, event logging, permission reviews and operational isolation to reduce the risk of unauthorized access, modification or disclosure. No system can eliminate every risk, so users remain responsible for device security, credential management, least privilege and data backups.
Before the rental period ends, export your business data and build artifacts and remove sensitive files no longer needed. After service ends, data is handled according to order status, support needs and necessary recordkeeping obligations; service nodes should not be treated as the sole backup location.
User rights and requests
Subject to the rules applicable to you and the specific processing context, you may request access to, correction or deletion of, or restriction of processing for information about you. You may also object to certain processing or ask about its legal basis.
Confirm whether we process information about you and learn about its main categories, purposes, sources and recipient groups.
Request correction of inaccurate contact details, order information or factual errors in support records.
Request deletion when information is no longer necessary and there is no basis for continued retention.
Request temporary restriction of specific processing while accuracy, legal basis or a dispute is being verified.
When submitting a request, state the request type, related order ID, support email used, information involved and a helpful time range. Do not send access keys, complete payment credentials or sensitive files unrelated to the request to prove your identity.
To prevent impersonation when accessing or deleting information, we may ask you to reply from the original support email, submit a console ticket or provide order-related verification information that does not expose valid credentials. Verification information is used only to confirm a reasonable connection between the requester and the relevant records.
If a request concerns another person’s information, records that must be retained by law, an ongoing transaction dispute or system security records, we may limit its scope and explain why it cannot be completed immediately. Actionable portions will be handled separately from restricted portions.
Policy updates and contact
This policy takes effect on August 18, 2026. We may update it when our services, information practices, payment processes, security measures or applicable requirements change.
The updated version will be published on this page, with the effective date at the top identifying the current version. If a change materially affects processing purposes, user rights or sharing scope, we will explain it in a manner proportionate to its impact.
If you have questions about this policy, personal information processing or rights requests, email support@hireamac.com or log in to the console to submit a ticket. We recommend including “Privacy Request,” the request type, related order ID and a verifiable support email in your email or ticket to speed up identification.
This policy is governed by the law of the jurisdiction where the platform operator is established. Disputes that cannot be resolved through reasonable communication should be submitted to a court with jurisdiction in that jurisdiction.