Acceptable Use Policy

This policy applies to every BlinkHost user, project, connected repository, preview session, deployment, project asset, database, domain, backend module, API and integration. You are also responsible for people acting through your account.

Prohibited conduct and content

You must not use BlinkHost to: violate law or another person's rights; distribute malware; phish, defraud or impersonate; exploit or scan systems without authorisation; interfere with service availability; evade technical or plan limits; send unlawful or unsolicited bulk messages; expose secrets or payment-card data in logs; host child sexual abuse material, non-consensual intimate content, credible threats or content that facilitates serious harm; infringe intellectual-property rights; operate deceptive credential collection, botnets or abusive cryptocurrency workloads; or use stolen credentials, payment methods or infrastructure.

Security research is permitted only against systems you own or have written authority to test. Do not test BlinkHost infrastructure outside a published vulnerability-disclosure scope.

Resource fairness

Do not generate traffic, preview activity, builds, database activity, storage, workers or network use intended to impair shared service or materially degrade other tenants. We may apply documented limits, isolate a workload or require a suitable plan. A legitimate traffic spike is not abuse; contact support where planned demand may exceed published limits.

Enforcement

We consider severity, evidence, intent, history, urgency, affected people, law and available less-restrictive measures. Responses may include warning, removal of specific content, rate limiting, isolation, suspension or termination. We may act immediately for imminent harm, security compromise or legal necessity. Where safe and lawful, we will give notice, reasons and an opportunity to cure or challenge the decision.

Reporting and appeals

Report abuse to abuse@blinkhost.me with exact URLs or resource identifiers, dates, the issue, evidence you are authorised to share and your contact information. Do not send secrets. An affected customer may reply with a factual challenge and supporting evidence. Knowingly false reports may cause harm and legal liability.

Uploaded application content

You must not use Hosted Object Storage to upload, store or distribute malware, unlawful content, exploit material, content that infringes another person's rights, or files intended to evade security controls. Do not expose private files through public links or attempt to use upload capabilities outside the project and purpose for which they were issued.

Automated functions

You must not use event, scheduled, or background functions to evade usage limits, send abusive or unlawful communications, probe systems without authorization, run malware, or create uncontrolled retry loops. Configure bounded retries and stop or disable a trigger that repeatedly fails.