Independent projects are welcome.
You can run lawful websites, applications, development tools, private gateways and other workloads that fit your resource allocation. Controversial ideas are not automatically technical abuse.
Use the service with the permissions and rights your project requires. Hosting in an offshore jurisdiction does not remove your responsibility for the application, data or activity you control.
Do not use the platform to harm others.
Do not host or distribute child sexual abuse material, operate credential theft or phishing, deliver malware, coordinate attacks, sell unauthorized access or facilitate fraud. Do not threaten the safety of people or deliberately disrupt other services.
Unsolicited bulk messaging, abusive scanning, open relays and attempts to bypass resource or access controls are not acceptable. Security research must be authorized, scoped and coordinated with affected systems.
Use shared resources considerately.
The resource limits and product specifications in your order define the service. Unmetered transfer does not mean permission to saturate shared infrastructure or cause sustained degradation for other customers.
If a workload creates unusual contention or network risk, we investigate the cause and seek a suitable configuration or limit. We explain the issue and a practical remediation route where circumstances permit.
A complaint is reviewed for substance.
ASTRA does not automatically remove material solely because a US DMCA template was submitted. We assess the report, its evidence, the applicable local framework and this policy.
A useful report identifies the affected service, specific conduct, relevant timestamps and evidence. We avoid broad, unsupported demands and do not treat a complaint as permission to expose unrelated customer information.
Contain the risk, then work toward a fix.
A compromised server may need temporary restrictions while you restore control. Keep recovery access available, rotate exposed credentials and preserve the evidence needed to understand the incident.
Urgent harm can require immediate suspension. For remediable issues, we aim to explain the affected service, required correction and next review step. Repeated or serious misuse can lead to termination.
Report with enough context to investigate.
Open a support request with the affected address or service, a concise description and time-stamped evidence. Share only the material needed to substantiate the issue; do not send unrelated personal data or account secrets.
For a concern involving your own service, use the account that controls it. We keep the investigation and remediation history together so that the next engineer can continue from the same facts.