Scope
This policy applies to data processing when you visit berryvm.com, use the ordering console, communicate with BerryVM about an order, submit a support request, or rent a BerryVM Cloud Mac service.
Services include configuring Berry M4 and Berry M4 Pro dedicated physical machines, confirming orders, checking USD payment status, assigning nodes, delivering access details, providing operational support, renewing rentals, and ending services. BerryVM provides a physical node dedicated to one customer throughout the rental period—not a virtual machine.
External code repositories, package sources, team collaboration systems, and third-party tools connected by customers are handled by their respective providers under their own rules. Customers should assess each tool’s data flows and permission settings before connecting it.
What Data We Collect
BerryVM collects only the information needed to activate services, manage orders, maintain security, and provide support. Different workflows require different data; visiting a page does not require you to submit a complete order.
- Account & Contact Information
- Email address, account identifier, verification status, language preference, and information needed to confirm the order contact’s identity.
- Order & Configuration Details
- Selected Berry M4 or Berry M4 Pro, rental term, node, additional storage, number of Thunderbolt 5 parallel connections, order identifier, and delivery status.
- Payment Status
- USD order amount, payment method category, transaction status, reconciliation reference, and refund or adjustment records. See the next section for payment-processing boundaries.
- Device & Access Logs
- Device allocation identifier, node, access time, originating network information, authentication result, credential update time, and necessary records related to security events.
- Support Communications
- Ticket subject, issue description, order identifier, incident time, impact scope, reproduction steps, reply history, and attachments submitted by the user.
- Technical Diagnostics
- System versions, error excerpts, redacted logs, and relevant configuration summaries submitted to diagnose connection, disk, dependency, build, or node-network issues.
Support requests must not include access passwords, private keys, complete authentication tokens, unredacted project secrets, or personal data unrelated to the issue. When diagnostics are needed, provide a time range, error code, reproduction steps, and trimmed logs whenever possible.
Payment Data Boundaries
All orders are settled in USD. BerryVM supports USDT-TRC20 and card payments by Visa, Mastercard, and Amex processed through Stripe. The gateway actually available at checkout is determined by the result returned by the console.
Information used to confirm on-chain payments
BerryVM processes the order amount, transaction status, transaction reference, and address information needed for reconciliation. We do not ask users to send wallet access credentials in support requests.
Authorization handled by the payment process
Card payments are processed through Stripe. BerryVM receives the status and references needed to complete the order, confirm payment, and reconcile transactions. Regular support tickets do not collect full card numbers or security codes.
Payment records may be retained for order fulfillment, financial reconciliation, dispute handling, security investigations, and applicable legal obligations. BerryVM does not use payment status for profiling or advertising unrelated to the order.
Data Is Used Only for Clear Service Purposes
BerryVM does not expand service data indefinitely into uses unrelated to delivery. Each processing activity must correspond to an identifiable service, security, or legal purpose.
- Activate & Deliver Services Verify the order, assign a dedicated physical machine, confirm the node and rental term, and deliver the required access details.
- Manage Orders Process term changes, renewal confirmations, configuration adjustments, billing reconciliation, service termination, and related communications.
- Protect Account & Device Security Identify unusual authentication, restrict unauthorized access, investigate security events, and retain necessary operational records.
- Handle Support Requests Diagnose and respond using the order identifier, node, incident time, and redacted logs provided by the user.
- Meet Legal Obligations Retain necessary order, financial, security, and rights-request records, and respond to requests with a valid legal basis.
- Improve Service Reliability Analyze incident categories, support workflows, and delivery steps using aggregated or minimized operational information, without reading customer project content unrelated to this purpose.
When the purpose of processing materially changes, BerryVM will assess whether this policy should be updated, additional information provided, or appropriate authorization obtained again.
Device Data & Access Boundaries
During the rental term, customer work data resides on the dedicated physical machine assigned to that customer. Customers manage project files, source code, build artifacts, keys, access policies, and tools they install themselves. BerryVM handles device allocation, core service delivery, and authorized support operations.
-
Requested by the Account Holder
Requests must be submitted from a verified email address or through the logged-in console and include a linkable order identifier.
-
Clear Scope & Purpose
Operations are limited to the device, time range, and technical items needed to resolve the specified issue and do not extend to unrelated data.
-
Use Least Privilege
Prefer diagnostic methods that do not access customer content. If further access is essential, explain the scope and intended actions first.
-
Keep a Traceable Record
Support requests, authorization context, key actions, and outcomes are recorded in the relevant ticket or service record.
-
Revoke Access When Done
Temporary support access must be disabled after the task is complete, and customers should update any credentials shared temporarily for troubleshooting.
BerryVM will not ask customers to send access passwords or private keys through regular email. If diagnosis cannot be completed without accessing project content, support staff will first explain the information needed, its purpose, and recommended redaction methods.
Retention, Deletion & Service Termination
Data is not retained indefinitely simply because it can be stored. Retention periods are determined by the service relationship, order fulfillment, security needs, dispute handling, and legal obligations. Once the purpose is met, data is deleted, de-identified, or access-restricted.
| Data Category | Primary Retention Basis | Deletion or Restriction Method |
|---|---|---|
| Account & Contact Information | Maintain the account, verify identity, process current orders and rights requests | Delete or restrict access after account closure and completion of necessary matters, except where retention is required |
| Order & Payment Records | Order fulfillment, financial reconciliation, dispute handling, and legal obligations | Delete or de-identify after applicable retention requirements end |
| Device & Security Logs | Access security, incident investigation, service integrity, and abuse prevention | Retain only for the shortest necessary period, then delete, aggregate, or de-identify |
| Support Records | Resolve issues, preserve processing context, verify authorization, and improve workflows | Delete unnecessary attachments and diagnostic materials after the issue is closed and the necessary review period has passed |
| Customer Data on Devices | Provide the dedicated physical machine service to the customer during the rental term only | Close customer access after service termination and clean data according to the device-recovery process |
Before service termination, customers should export any project files, build artifacts, and configurations they still need. Once termination takes effect, device access is disabled and the device enters recovery and data-clearing procedures. Support requests do not replace the customer’s own backup strategy.
If data is being used for an unresolved billing matter, security incident, rights request, or dispute, BerryVM may first restrict its use and access, then delete it after the matter is resolved.
Cross-Region Processing & Node Selection
BerryVM provides five nodes in Singapore, Tokyo, Seoul, Hong Kong, and the eastern United States. Depending on the node selected, device data, remote-access paths, support collaboration, and necessary service records may involve cross-region transfers or access.
Before selecting a node, confirm the project’s data-residency requirements, team locations, code-repository location, build-artifact destination, collaboration time zones, and internal access-control rules. Distance is only one factor and cannot replace the project’s own compliance assessment.
- Grant device access only to team members with a genuine work need.
- Prefer key-based authentication, source restrictions, and least-privilege configurations.
- Remove passwords, tokens, private keys, and unrelated personal data from logs, tickets, and collaboration tools.
- Before transferring project data across regions, confirm internal approvals, customer contracts, and project rules.
- After selecting a node, use real network tests to verify the connection path and workflow fit.
User Rights, Identity Verification & Contact
Where permitted by applicable rules, users may request access to relevant data held by BerryVM, correction of inaccurate information, deletion of data no longer needed, restriction of specific processing, or object to processing activities.
Access & Correction
Explain the data scope you want to access, or identify the fields and order along with the correct current information.
Deletion & Restricted Processing
Identify the target account, order, or support record. If the data remains subject to necessary retention obligations, BerryVM will restrict its use and explain its processing status.
Object to Processing
Identify the processing activity you object to, the relevant service context, and your reasons so we can assess the processing basis and available alternatives.
To prevent account or order data from being disclosed to an unrelated person, BerryVM verifies identity according to the request’s scope. Verification may include a confirmed email address, account identifier, order identifier, and information that only the order contact could reasonably provide. We will not ask you to send access passwords, private keys, or complete payment credentials through regular email.
Rights requests can be sent to support@berryvm.com, or submitted as a ticket after logging in to the console. The email or ticket should state “privacy rights request,” the request type, associated account email, relevant data scope, and an order identifier that helps with verification.
If a request concerns another person’s data, an unresolved security investigation, necessary order records, or a legal requirement, BerryVM will first assess what can be done and, without expanding the purpose of data use, apply deletion, restriction, de-identification, or retention measures as appropriate.
Policy Updates & Applicable Rules
This policy may be updated as service processes, data types, or applicable requirements change. Material changes will be explained through the website, account notifications, or order contact channels. Data processing and related disputes are governed by the laws of the jurisdiction where the platform operator is located and handled by courts with jurisdiction in that jurisdiction.