1. Scope
This policy applies to services OSXPort provides through osxport.com and its console, including account setup, dedicated physical Mac mini rentals, order and invoice management, and service communications by email or console ticket. Whether you're exploring plans or already using a dedicated build server, this policy explains how related information is handled.
We distinguish between two types of data: account, transaction and support information processed to provide our services, and code, signing materials, configuration and build artifacts stored on your dedicated physical server. A server is assigned to one customer and is not a virtual machine, but account and billing systems still need to process certain information. The access boundaries for each type are explained below.
Code repositories, package sources, CI services and distribution tools that you configure process data you send them under their own policies. Review their permissions before connecting them, and avoid putting unnecessary personal information in build logs, branch names or public artifacts.
2. Information We Collect
Account information.We process the email address you use to register, sign in and contact us, along with records needed for account verification, sign-in security and account settings. This information helps us identify your account, verify authorization, send service-related notices and prevent unauthorized access. Never send your password or a one-time verification code to support.
Orders and billing records.We record your selected model, region, billing period, add-ons, order and payment status, and associated invoices. We use these records to provision servers, manage rental periods, reconcile payments and resolve transaction issues. You don't need to share project source code to ask which plan is right for you; details about project size, build frequency and required tools are usually enough.
Support tickets and email.When you contact us for help, we process your issue description, relevant order identifiers, error messages and any troubleshooting materials you choose to provide. This helps us follow up on the issue and keep a record of how it was handled. Before sharing screenshots or logs, redact access tokens, private keys, signing passwords and other sensitive information unrelated to the issue.
Essential access logs.We process network addresses, request times, paths, essential browser or device information, and records related to sign-ins, errors and security incidents to operate the service, protect it and diagnose issues. We limit data use to these purposes and don't require access to your contacts or personal files on your device to provide build servers.
3. Data on Your Server
Code, signing certificates, provisioning profiles, build caches, configuration and build artifacts that you or your team store on a dedicated physical server belong to you or their respective rights holders. Hosting your server does not give us rights to use this content, and we don't use it for marketing, model training or analysis unrelated to the service.
We don't access your server to read project content unless needed to help troubleshoot an issue. Any such access requires your explicit authorization in a console ticket, specifying the server, issue and permitted scope of inspection. Support staff must limit their actions to what is necessary to resolve the issue. If a broader inspection is needed, we'll confirm with you first; authorization to access all projects is never assumed.
Where possible, share redacted logs or steps to reproduce the issue to minimize the need for direct server access. Never send private keys, long-lived access tokens or signing passwords in ordinary email. If you find credentials in a ticket, log or build artifact, revoke or rotate them promptly and tell us in a ticket which materials need to be removed.
You configure team access, CI secret injection, artifact permissions and backups. We recommend separating permissions for automated tasks from those for human administrators, and removing access when a team member leaves a project, a pipeline is migrated or a rental ends.
4. Payments
Services are billed in US dollars (USD). The only payment methods are USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. Available payment gateways are shown in the console. When you select a payment method, the transaction information needed to complete the payment is shared with the relevant payment processor.
Card payments are processed by Stripe. OSXPort does not store full card numbers. We retain the payment status, transaction identifier and necessary reconciliation details associated with an order to confirm provisioning, reconcile invoices and resolve payment issues. Never include your full card number, security code or payment verification details in an email or support ticket.
For USDT-TRC20 payments, we use the transaction hash, amount and order association for reconciliation. On-chain transactions are publicly viewable; deleting your account information on our site does not remove on-chain records. We will never ask for your wallet's private key or recovery phrase. To ask about a payment, provide the order identifier and transaction hash so we can begin checking it.
5. Cookies & Analytics
The website and console use cookies or browser storage necessary to provide the service, maintain sign-in sessions, secure requests and remember essential interface preferences. This storage does not give us access to other files on your computer. Disabling or clearing session storage may sign you out or require you to verify your account again.
We use first-party analytics to understand page visits, clicks on key links and technical issues during use. This helps us improve content and service flows; it does not let us read code, certificates or build artifacts on your server. Analytics events should not include passwords, verification codes, signing materials or project file contents entered in forms.
You can view and clear our cookies and local storage in your browser settings, and restrict future storage. Some preferences may reset to their defaults after clearing storage. To ask how logs or analytics related to your account are handled, contact us using the channels in Section 8. After verifying your identity and protecting system security, we'll explain what information is covered.
6. Data Retention & Server Wiping After a Rental
We retain records as needed for their purpose: account details to provide ongoing account services; order and payment records to fulfill orders, reconcile payments and resolve transaction issues; support tickets to follow up on issues; and access and security logs to operate and investigate security matters. When information is no longer needed for its original purpose, we delete it, de-identify it or stop processing it, except where retention is required by law or the information relates to an unresolved matter.
This policy does not set a single retention period for all data. Retention needs may vary depending on transaction status, security incidents or applicable obligations. You can ask how specific records are handled. If a record still needs to be retained, we'll explain why and how that affects your deletion request; closing an account does not automatically delete every billing record.
When a rental ends and a server is reclaimed for redeployment, we wipe or reset customer data on it to prevent the previous customer's data from being passed to the next customer. Data is not retained as a customer backup after reclamation and should not be considered a recoverable archive.
Before your rental ends, export any code, certificates, configuration and build artifacts you need to keep, and check that your backups work. To confirm the server's reclamation status or make a data-handling request, submit a console ticket linked to that server. Don't rely on build caches to restore a project after the server has been reclaimed.
7. Access, Correction & Deletion
You can request access to personal information about you, correction of inaccurate account details, or deletion of information that is no longer needed. You can also ask us to explain a processing purpose, category of records or retention reason. To help us locate the information, specify whether your request concerns account details, order records, support tickets or access logs. Don't attach project files unrelated to your request.
If you're signed in, submit a support ticket in the console. If you can't sign in, email us from the address associated with your account at support@osxport.com. We may ask for identity verification proportionate to your request to prevent others from accessing or deleting your information. Never prove your identity by sending a password, verification code or server private key.
Deleting information may affect sign-in, order history and future support. We may need to retain necessary information related to active orders, unresolved transactions, security investigations or legal retention requirements, and will explain any restrictions. A request to delete personal information does not cancel a server rental, terminate an order or manage its rental period.
We will review your request and let you know the outcome. If we need more information, we'll explain what to provide. Applicable law and dispute resolution for personal information processing are governed by the laws of the jurisdiction where the platform operator is based. Disputes will be handled by courts with jurisdiction in that jurisdiction.
8. Contact & Policy Updates
For questions about privacy, data access authorization, correcting or deleting information, email us at support@osxport.comor sign in to the console and submit a support ticket. You can also use either channel to report a security issue or request materials related to data processing. If your server is already provisioned, we recommend using a support ticket so we can link your request to the relevant account and server.
In your request, include the email address associated with your account, the type of request and any relevant order or server identifiers. If you need us to check a specific action, you can also include an approximate time and time zone. Share only what is needed to resolve the issue, and redact logs or screenshots before submitting them.
If our service processes or data-handling practices change, we'll update this page and identify the new version. Changes that significantly affect personal information processing will be communicated through the website, console or email address associated with your account. The revised policy takes effect as stated in the update notice. Please review it before continuing to use the affected features.