1. Acceptance & Scope of Agreement
By accessing GPHosting, creating an account, uploading or transferring files, downloading shared media, embedding /raw/... or /x/... links, or interacting with our developer API endpoints, you enter into a legally binding agreement to comply with this Acceptable Use Policy and our linked Terms of Service.
If you do not accept these terms or cannot comply with these standards, you must immediately cease all access and use of GPHosting.
2. Permitted & Recommended Uses
GPHosting is optimized for high-speed, temporary, and friction-free file transfers. Welcomed use cases include:
Sending homework documents, lecture recordings, project archives, photography, family clips, and creative assets to friends and classmates.
Hosting README badges, screenshots, architecture diagrams, benchmark logs, and build artifacts via direct /raw/... CDN links.
Deploying HTML/CSS mockups and portfolio pages under /site/[slug] for instant client feedback within isolated sandboxes.
Sharing sensitive keys, contract drafts, or credentials utilizing client-side AES-GCM 256 encryption and 60-second Burn on Preview self-destruction.
3. Strictly Prohibited Content & Actions
GPHosting maintains zero tolerance for dangerous, illicit, or predatory material. You agree that you will never transmit, store, or share:
Viruses, worms, trojans, ransomware, keyloggers, botnet droppers, or automated script exploits designed to compromise target devices.
Cracked commercial software, unauthorized movie/audio streams, serial keygens, or proprietary works you lack authorization to share.
Child sexual abuse material (CSAM), non-consensual intimate imagery, terrorism, violent extortion, illegal weapons, or hate crimes.
Breached database dumps, credit card collections, national identification numbers, private medical logs, or unconsented doxxing packages.
4. Anti-Abuse, Device Fingerprinting & Slot Protection
To guarantee that file download slots and bandwidth remain available for legitimate users, GPHosting implements strict defense measures:
- Hardware Device Fingerprint Compliance: Our platform computes a privacy-preserving mathematical hash from client entropy to prevent bots from exhausting single-use links. Attempts to spoof, bypass, or flood requests using headless bot farms are strictly prohibited.
- Prohibition on Slot Hoarding: You may not trigger concurrent download requests or maintain artificial open connections designed to monopolize or prematurely deplete limited-download or burner links.
- Denial-of-Service (DoS) Attacks: Any attempt to stress, overwhelm, probe, or exhaust our edge network, database systems, or caching infrastructure will result in instantaneous IP/device blacklisting.
5. Developer API & Automated Access Rules
Programmatic uploads via our REST API (gp_live_... keys) must adhere to these operational criteria:
API keys are issued with a 2-step confirmation modal and stored as one-way cryptographic hashes. You are solely responsible for securing your key; do not commit live keys to public repositories.
Automated scripts must respect HTTP 429 rate limit responses. Automated scrapers attempting to systematically probe link IDs or brute force password-protected links are permanently barred.
6. Enforcement & Zero-Stale Shredding
We enforce these standards decisively to protect our platform and community:
- Instant File Shredding: Files reported and verified to breach this policy are purged immediately from storage buckets, database tables, and active cache layers with zero opportunity for retrieval.
- Account Termination: Repeated or severe violations result in immediate account revocation, quota forfeit, and permanent device/IP bans.
- Law Enforcement Referral: In cases involving CSAM, imminent physical harm, or severe cyberattacks, GPHosting cooperates fully with competent law enforcement and regulatory authorities.
7. Reporting Violations & Abuse
If you encounter content hosted on GPHosting that violates this policy, please submit an urgent notice including:
- The exact URL of the offending file (e.g.
https://gphost.eu.cc/f/...,/raw/..., or/x/...). - A concise statement detailing the violation.
- For copyright claims, proof of intellectual property ownership.
- Your contact email for verification purposes.
8. Revision History & Audit Trail
| Version | Date | Status | Summary of Updates |
|---|---|---|---|
| v1.0.0 | September 14, 2026 | Original Launch | Initial acceptable use guidelines and core fair sharing restrictions. |
| v2.0.0 | September 16, 2026 | Superseded | Added guidelines for direct raw CDN embeds (/raw/...) and encryption key confidentiality. |
| v2.5.0 | September 17, 2026 | Superseded | Integrated terms for Burn on Preview (60s countdown) and single-use slot mechanics. |
| v3.0.0 | September 18, 2026 | Superseded | Expanded restrictions on automated API flooding, executable bot payloads, and automated bot deterrence. |
| v3.1.0 | September 19, 2026 | Prior Revision (Superseded) | Re-architected all fair play provisions into accessible, plain-English principles. |
| v3.2.0 | September 30, 2026 | Active & Effective | Formalized standalone Acceptable Use Policy (AUP) with explicit rules covering hardware device fingerprinting for anti-abuse, Zero-Stale lifecycle purging, SHA-256 anti-tamper checksums, and 2-step API key management. |