1. Scope
This policy describes acceptable use of the website preview and intended conditions for future services. It is not evidence that a live protection platform exists. Any future commercial agreement must incorporate final restrictions, a contact channel and an enforcement process.
2. Authorization
Only configure infrastructure you own or have explicit permission to administer when a real service becomes available. In this preview, enter example data only. Do not submit another person's private information, credentials or confidential infrastructure details.
Protection services must not be used as a platform to initiate attacks or hide unlawful activity.
3. Prohibited activity
- Launching or facilitating denial-of-service attacks, unauthorized scanning, exploitation or intrusion.
- Distributing malware, phishing pages, stolen credentials or tools used to compromise third-party systems.
- Using stolen payment methods, impersonating customers, committing fraud or circumventing access controls.
- Publishing unlawful content, infringing rights or violating applicable court orders.
- Interfering with the platform, overloading the checkout endpoint, bypassing limits or attempting to access other users' data.
- Routing assets without the necessary authorization or misrepresenting ownership and permitted use.
4. Security testing
A protection plan does not authorize attack simulation. Any load test, penetration test or DDoS simulation requires prior written authorization from every relevant asset owner and provider, with an agreed target, scope and schedule. There is no testing authorization for this preview.
5. Reports and enforcement
A PacketShield abuse and security reporting contact has not yet been established. It must be published before the service launches. Do not use the sample checkout form to report an incident or include evidence containing personal information.
Final service terms must explain how suspected abuse is assessed, how urgent incidents are handled, and when notice, suspension, appeal or termination may apply. This draft does not claim that those operational processes already exist.
6. Related policies
Read the terms of use for preview and billing status, the privacy policy for information handling, and the cookie policy for browser storage. These documents will be updated when the operator and final service are defined.