Scope and roles
First, we identify who processes what information across three contexts: access, ordering, and support.
Website access
When you browse bookamini.com, view pricing, read technical content, or switch languages, this policy applies to information processed for normal display, security, access analytics, and preference storage. Simply viewing public pages generally does not require an account.
Ordering and service management
When you open the Console, create an account, verify an order, select one of the two available configurations, choose a node region, pay, or check service status, the system processes information needed to perform the contract, verify the transaction, and deliver a dedicated physical machine. Account details, order records, billing status, and node assignment information in the Console are also covered by this policy.
Support communications
When you submit a ticket through the Console or email support@bookamini.com, we process the contact details, order context, error text, log excerpts, and correspondence you provide. Do not include your account password, recovery code, or private key in a ticket or email.
Processing roles
BAMini determines the purposes and methods for processing personal data in website operations, account management, order fulfillment, billing, and support. You determine the purposes and access scope of code, project data, and automation tasks deployed on your dedicated physical machine. If you use the service on behalf of an organization, ensure you have the authorization required to submit the relevant information.
What information we collect
The scope of collection depends on the website features, order flow, and support channel you actually use.
Account and contact information
This may include your name or display name, email address, account verification status, language preference, and contact details provided during support communications. Email is used for login verification, order notifications, security alerts, and request responses.
Order and transaction records
This may include the order number, selected model, billing cycle, node region, additional storage or Thunderbolt 5 parallel connection options, amount, currency, payment status, transaction reference, and billing records. Full sensitive payment-card data is handled by the relevant payment flow; you are not asked to send it through a ticket.
Device and log information
This may include access time, browser type, device category, network address, security event records, login results, session identifiers, request paths, and system error records. This information helps maintain sessions, identify abnormal access, and troubleshoot service failures.
Support content
This may include ticket subject, problem description, occurrence time, node region, model, client information, reproduction steps, error text, log excerpts you choose to submit, and subsequent handling records.
Preference settings
This may include language, interface state, necessary session settings, and optional analytics preferences you actively select. Preference data reduces repeated setup and is not used to change the published model, pricing, or node catalog.
We do not require you to submit a complete project repository for routine support. When troubleshooting, provide minimal reproduction steps, necessary logs, and sanitized configuration excerpts first. You decide how to back up, migrate, or delete project data on your node based on your workload.
Purposes and legal bases
Each processing activity serves a defined service purpose, and support materials are not used for unrelated purposes.
- Provide and deliver services
- Create and maintain accounts, receive configuration choices, verify orders, assign physical nodes, generate connection details, display subscription status, and handle renewals, changes, or service termination.
- Verify orders and process payments
- Confirm order amounts, payment status, and transaction references; prevent duplicate submissions or unusual transactions; and generate order-related billing records. The basis is fulfilling the order and completing your request.
- Protect account and platform security
- Identify unusual logins, automated abuse, malicious requests, and activity that may affect other users or platform operations. The bases include measures necessary to provide a secure service and the platform’s legitimate security interests.
- Handle support requests
- Use the order number, region, model, time, and error text to reproduce issues, assign a handling status, request necessary additional information, and retain resolution records to avoid repeated investigation.
- Meet legal obligations
- Where required, retain necessary transaction, accounting, security, or rights-request records and respond to requests from authorized parties. We process only the information necessary to meet the relevant obligation.
- Improve site experience
- Analyze whether pages load correctly, whether documentation is easy to find, where processes fail, and how they work across different devices. Optional analytics settings follow your choice; necessary security logs do not depend on optional settings.
Your choices and personal data rights
The requests you can make depend on applicable rules, the processing basis, and whether the information must still be retained.
Access
Ask whether we process information about you and request the relevant categories, purposes, sources, sharing scope, and an available copy.
Correction
Update inaccurate or incomplete account and contact information. Where you can make the change yourself in the Console, use your account settings first.
Deletion
Request deletion of information that is no longer needed, no longer has a processing basis, or must be deleted by law. Information still needed for transaction records, security investigations, or unresolved disputes may not be deleted immediately.
Restriction of processing
Request temporary restriction of specific information while its accuracy, processing basis, or an objection is being reviewed. Restriction may affect related account features or the continued handling of support requests.
Object
Object to specific processing based on legitimate interests and explain the reasons relevant to your situation. We will assess the necessity and impact of continuing the processing.
How to submit a request
- 01Choose a channel
Sign in to the Console to submit a ticket, or email support@bookamini.com from the email address associated with your account.
- 02Specify the scope
State the request type, associated account email, order number, or time range. Do not submit your password, recovery code, or private key.
- 03Complete identity verification
To prevent impersonation, we may ask you to confirm account control, order-related information, or other minimally necessary verification details.
- 04Receive the result
We will use the original request channel to explain the processing status, any additional information needed, the outcome, or the specific basis for being unable to fulfill part of the request.