1. Welcome & Acceptance of Terms
By accessing, browsing, uploading to, downloading from, or interacting with GPHosting (including our web application, file landing portals, raw CDN endpoints, and developer API routes), you acknowledge that you have read, understood, and agreed to be legally bound by these Terms of Service and our linked Acceptable Use Policy (AUP). If you do not accept these terms in full, you must not use or access GPHosting.
These terms govern every feature of GPHosting: web uploads, direct download URLs, preview routes (/f/...), direct raw links (/raw/...), short alias redirects (/x/...), static HTML previews (/site/...), and automated API calls.
2. Acceptable Use Policy (AUP) & Content Rules
GPHosting is built for lawful, respectful, and constructive file sharing—such as sending documents, photos, portfolio sites, media, and code assets. You unconditionally agree that you will never upload, distribute, link to, or store:
Viruses, trojans, ransomware, rootkits, spyware, keyloggers, botnets, or executable payload scripts designed to compromise, harm, or infiltrate devices.
Pirated movies, cracked software, stolen music albums, paid games, or any media protected by copyright where you lack explicit distribution rights.
Child sexual abuse material (CSAM), non-consensual intimate imagery, violent extremism, extortion, illegal arms, or controlled dangerous substances. Immediate termination and reporting to law enforcement authorities applies.
Breached database dumps, stolen credentials, credit card details, government IDs, private health records, or doxxing individuals without authorization.
Automated scripts that monopolize single-use slots, burner links, or attempt to circumvent rate limits or hardware device fingerprinting protections.
Denial-of-service (DoS) attempts, API scraping without valid authentication, proxy spoofing, or attempts to bypass authenticated file endpoints.
3. Fast Direct Uploads & Resumable Transfers
We designed GPHosting to be as fast, private, and resilient as possible using direct storage transfers:
Uploads travel directly from your browser to secure cloud storage using secure direct upload tokens. Our application servers never bottleneck or read your raw bytes.
You can upload files as large as 1 GB. Large files use chunked transfers with local browser persistence to recover seamlessly from network drops.
Image uploads can be automatically converted to modern WebP right in your browser, saving storage space while stripping privacy-invasive camera EXIF data.
4. Auto-Deletion, Expiration & Zero-Stale Purge
When a file reaches its expiration timer, exhausts its download count, or burns after preview, our zero-stale lifecycle engine immediately shreds the storage file, purges all database records, and flushes all temporary download sessions and cache memory. Nothing lingers in cold storage.
You can configure exactly how and when your files disappear:
The file starts a 60-second self-destruct timer the moment someone views it. When 60 seconds are up, the file is completely wiped.
The file vanishes permanently the very second someone finishes downloading it once. Single-use access controls prevent multiple concurrent downloads.
Pick a download limit (like 5, 25, or custom limits). Once that threshold is reached, the file is automatically purged.
Set a time limit: 10 minutes, 1 hour, 24 hours, 7 days, 30 days, or keep it permanent if you are signed in.
5. Direct Links, Custom Slugs & Multi-Channel Sharing
GPHosting allows you to share files effortlessly through multiple distribution channels and custom routing paths:
- Direct Raw CDN Links (
/raw/...): Stream images, icons, or documentation directly on your GitHub READMEs, portfolio, or blog with automatic Edge CDN 1-hour caching. - Custom Short Slugs (
/x/[alias]): Create branded, memorable short links (e.g.,/x/my-project) for fast sharing without long random character strings. - Multi-Channel Share Sheet: Instantly share links via WhatsApp, Telegram, direct clipboard copy, or generate scan-and-go QR codes for fast mobile downloads.
- Safe Content Headers: Raw files with potentially dangerous MIME types are safely served with strict Content-Disposition headers to prevent browser script injection.
6. Secret Zero-Knowledge Encryption & SHA-256 Anti-Tamper
When you activate Client-Side Encryption, your file is scrambled directly in your browser with AES-GCM 256 before leaving your computer:
The secret decryption key is stored exclusively after the # character in the URL. Web standards ensure browsers never transmit hash fragments to our servers. We never possess, see, or log your decryption key.
Every upload generates a cryptographic SHA-256 hash verified during download. This guarantees that your file is delivered bit-for-bit identical to the original and has not been altered or tampered with in transit.
7. Developer API Keys & 2-Step Security Flow
Developers can generate API keys (prefixed with gp_live_...) for terminal scripting, CLI uploads, and automated CI/CD integrations:
- 2-Step Confirmation Flow: Your secret key is shown exactly once in a copy-confirmation dialog. GPHosting stores only a secure one-way hash in our database, making it impossible for anyone to recover or view your plaintext key later.
- Rate Limits & Automated Protection: Programmatic uploads are governed by rate-limiting algorithms to ensure fair performance and prevent server exhaustion.
- Executable Guard: Automated uploads are screened to prevent the distribution of unauthorized executable scripts or payload viruses.
8. Accounts, Admissions & Anti-Abuse Shield
To maintain a clean platform free from spambots and abuse, we use verified Google Sign-In with an invitation PIN or administrative approval:
Sign in with Google and submit an onboarding PIN. Once approved, your account receives full storage quota and access to advanced security settings.
To prevent sybil attacks and slot hoarding on burner links, GPHosting uses lightweight, non-invasive hardware device fingerprinting. This signal is used strictly for real-time abuse defense and is never sold or used for ad targeting.
9. Storage Quotas & File Size Ceilings
Each verified account is assigned an allocated storage quota (typically 5 GB) and an individual file size limit of 1 GB:
- Real-Time Quota Accounting: Storage is computed accurately in real time. If an upload is canceled or aborted, storage reservations are immediately released.
- Fair Allocation: Creating multiple accounts to circumvent quotas is strictly prohibited and results in immediate account suspension.
10. Open Source & Disclaimers
The GPHosting architecture is available for learning and community security audits. However, running commercial clones, unauthorized re-hosting, or removing copyright branding is not permitted.
GPHosting is provided free of charge on an “as-is” and “as-available” basis without warranties of any kind. While we make every reasonable effort to ensure high availability, speed, and integrity, we cannot guarantee uninterrupted service or assume liability for lost files. Always maintain an independent local backup copy of your data.
11. Reporting Abuse & Contacting Support
If you encounter a file hosted on GPHosting that violates these terms, infringes on your intellectual property, or compromises user safety, please notify our team immediately:
- The exact URL of the offending file (e.g.,
https://gphost.eu.cc/f/...or/raw/...). - A clear description of the specific violation or harmful content.
- For copyright claims, verifiable proof of ownership or authorization to act on the owner’s behalf.
- A valid contact email address for follow-up verification.
Abuse reports are investigated promptly. Verified violations result in immediate, permanent file shredding across all storage buckets and cache layers.
12. What Changed Over Time (Audit History)
We believe in total transparency. Here is the complete chronological revision log of our Terms of Service:
| Version | Date | Status | Summary of Changes |
|---|---|---|---|
| v1.0.0 | September 14, 2026 | Original Launch | Initial release with basic temporary file sharing, auto-deletion timers, and core fair use rules. |
| v2.0.0 | September 16, 2026 | Superseded | Added direct raw links (/raw/...) for GitHub READMEs, client-side secret encryption, and modern dark mode. |
| v2.5.0 | September 17, 2026 | Superseded | Added “Burn on Preview” (60-second destruction), single-use downloads, and custom download limits. |
| v3.0.0 | September 18, 2026 | Superseded | Added developer API keys, 1 GB file uploads, bot protection, and edge speed optimizations. |
| v3.1.0 | September 19, 2026 | Prior Revision (Superseded) | Rewrote all terms into clear, simple, human English so anyone can easily understand our rules without needing a law degree. |
| v3.2.0 | September 30, 2026 | Active & Effective | Added hardware device fingerprinting for anti-abuse, Zero-Stale lifecycle purge, 2-step API key flow with hashed secrets, SHA-256 anti-tamper checksums, multi-channel sharing (WhatsApp, Telegram, QR code), custom slug routing, and formalized Acceptable Use Policy (AUP). |