Your VPS activity stays your business.
We do not inspect or log the contents of your VPS, shell commands, browsing activity, application traffic or files for advertising, profiling or routine service analytics. Your operating system and installed applications may create their own logs; those are under your administration.
Platform availability and capacity measurements are separate from guest activity. We use resource and service-health information to keep the infrastructure operating. A no-activity-logs policy does not mean that account, invoice or security records cease to exist.
An account with a smaller footprint.
Ordinary account creation does not require an identity-document upload. We use the contact and access information you choose to provide to authenticate the account, communicate about the service and help you recover access.
Account-security events, active sessions and support conversations are handled for service protection and continuity. Keep your recovery details current, use a unique password and protect any recovery codes. We do not sell account information or use it to build advertising audiences.
The records that keep the service working.
Orders, invoices, payment references, service configuration and support history connect your resources to your account. These records allow us to resolve a payment, explain a charge and maintain the service you requested.
We minimize access to operational records and keep them only while needed for the service, dispute handling and applicable retention obligations. Request account closure through support; we explain what can be deleted and any record that must be retained. Closure is not represented as immediate erasure of every historic financial record.
Payment privacy has a context.
Crypto checkout avoids card-data collection by ASTRA. Depending on the asset, transaction information may be visible on a public blockchain. Exchanges, wallet reuse and third-party services can create their own links to a payment.
Never share a seed phrase, private key or wallet recovery file with ASTRA. A payment investigation needs the invoice reference, network and transaction reference, not control of your wallet.
Reports are assessed, not blindly forwarded.
We review abuse reports for sufficient detail, relevance and the applicable policy. A US DMCA notice is not automatically treated as a binding removal instruction. The service remains subject to its local legal framework and our acceptable-use terms.
Where a report requires customer action, we seek a specific and proportionate response. We do not promise immunity from valid legal process. We reject malicious activity, credential theft, child sexual abuse material and attacks against other services.
Domain ownership remains with you.
For eligible extensions, official WHOIS/RDAP privacy or redaction hides supported public fields while retaining your registrant status. Registry rules differ, so the exact public fields depend on the extension and permitted privacy service.
Accurate registrant details remain in the registrar’s private records. We do not invent an identity, country or address to obscure publication, and we do not silently transfer ownership to a proxy service.
Make privacy part of how you operate.
Control what your application stores, keep dependencies current and give each person only the access they need. Private application data can be exposed by a public database, a reused key or an overly broad firewall regardless of the hosting location.
Contact support to request access, correction, deletion or clarification about your account records. We verify control of the account without asking for wallet secrets. No service can responsibly guarantee absolute anonymity across every tool, payment route and user action.