Security & Abuse Policy
Ferrisvheel.net — Security & Abuse Policy
Effective date: 19 September 2026
Website: ferrisvheel.net
Security contact: support@ferrisvheel.net
1. Purpose
Ferrisvheel relies on website, server, network, and account security to provide a safe and reliable service.
Attempts to deliberately compromise, disrupt, or gain unauthorised access to Ferrisvheel systems are prohibited.
2. Prohibited Activities
Users must not intentionally:
- Attempt to gain unauthorised access to Ferrisvheel systems;
- Attempt to access another user's account;
- Steal or obtain account credentials;
- Deploy malware;
- Conduct denial-of-service attacks;
- Deliberately disrupt server or website infrastructure;
- Exploit vulnerabilities to obtain unauthorised information;
- Circumvent security controls;
- Attack hosting or network infrastructure;
- Attempt to compromise databases; or
- Use Ferrisvheel services to facilitate attacks against others.
3. Exploits and Vulnerabilities
Not every software bug or unusual Minecraft mechanic is considered a security vulnerability.
However, significant vulnerabilities affecting Ferrisvheel infrastructure should be reported privately rather than deliberately exploited.
4. Responsible Disclosure
If you discover a security vulnerability, please contact:
Where possible, include:
- A description of the issue;
- The affected service;
- Steps necessary to reproduce it;
- Potential impact; and
- Any relevant screenshots or technical information.
Please do not access, modify, download, or disclose information that does not belong to you while investigating a vulnerability.
5. Security Investigations
Ferrisvheel may investigate suspected abuse using information reasonably available through server, website, hosting, security, and moderation systems.
This may include connection information, logs, account information, and other relevant technical records.
6. Immediate Action
Ferrisvheel may immediately restrict or suspend access where necessary to protect the server, website, users, or infrastructure from an active security threat.
7. Contact
Security concerns should be reported through: