TERMS OF SERVICE

You must be sixteen or older, and one person or legal entity may hold one account. Neither is checked at signup: there is no age gate and nothing links two accounts to one person, so both are conditions you accept rather than gates you pass. Hosting and earning are separate permissions — an active account can store and share files straight away, and is only paid once a person has reviewed the traffic source it declared. Accounts we find farming downloads, reselling access, or evading a prior suspension are closed without payout.

Files you created, own, or hold a distribution licence for. No copyrighted material you do not control, no malware, no credential dumps, no material depicting minors. What is accepted is an allowlist decided by the bytes and never by the extension — archive, document, image, audio, executable, font, text — so renaming a file changes nothing, anything that cannot be identified is refused rather than waved through, and video is refused outright whatever it is called. Archives are opened and their entries checked: one that will not list, or that is encrypted without a password that actually opens it, is refused, because a screen that cannot read a container proves nothing about what is inside it. Filenames and captions are screened too, including for instructions to rename a file after downloading it. Every refusal is recorded against the account, and an account refused repeatedly is looked at by a person. A file is checked against our takedown ledger before going live only when its hash is known at that point, which excludes large uploads and every remote fetch; those are caught by the scheduled hash sweep instead.

Storage is a ceiling earned by traffic rather than an allocation you buy: starter 5 GB, growing 10 GB at 1,000, established 20 GB at 5,000, scale 50 GB at 10,000 qualified downloads in the trailing 30 days. A tier is granted the moment that traffic earns it and lost only after 90 days below its threshold, one step at a time. Files do not live indefinitely. A file with no download at all is deleted 45 days after it was uploaded, and a file with fewer than 10 downloads is deleted 100 days after it was uploaded — including files with earnings on them. Deletion is permanent: one copy in one bucket, no mirror, no undelete. Nothing but being downloaded extends the clock, and no warning is sent before a file is reaped.

A download counts once 90% of the file has reached the visitor, added across every request they made. There is no time threshold and no minimum size. One credit per visitor per 24 hours across the whole service, not per file, and at most 4 devices behind one address in that window. Requests from known datacentre networks, requests the edge scores as automated, and downloads from the address you last signed in on are refused. Counting decisions are not disputable.

A download ticket is minted for the visitor who walked the funnel, and is sealed rather than merely signed, so the file, its owner and its storage key cannot be read out of the URL. It is bound to a hash of that visitor's address and a hash of their user agent. Passing the URL to another person, another machine, a download manager or a remote fetcher fails — that is the design, not a fault, and download managers are unsupported deliberately, because a link that survives leaving its browser is a link that can be shared. A ticket also carries a byte budget, a cap on requests and a cap on simultaneous streams, and an expiry that never exceeds a day, all of them shared by every copy of that URL. Walking the funnel again is the only thing that mints a new one.

An earning is written when a download completes, priced from the rate card in force at that moment; the card can change and an event keeps the price it was written at. Whole past days roll up into day buckets while today is left alone, because today is still moving. A day becomes withdrawable 7 days after that day ended, at which point one ledger credit is written for it. Money inside that window is on hold and is shown to you as such. Storage earns nothing on its own — only completed downloads do.

Each publisher-day is scored against the traffic that produced it: how long visitors actually spent in the funnel, how their addresses and devices are spread, how much arrived from datacentre networks, the shape of the referring hosts, and how far the account's identifying details overlap with other accounts. A day that scores badly enough is held automatically before it is credited, and it is deliberately left unreviewed rather than closed by the job that raised it, because holding your money is a delay that still owes you an answer from a person. A reviewer then clears the day or holds it, with a note. Releasing a held day keeps the record that it was held. A held day is not payable while the hold stands, and your available balance is calculated after holds, not before.

A withdrawal can be requested once $5.00 or more has matured and is available, and it needs a payout destination and a traffic source that have both been reviewed. Requesting one holds that amount out of your available balance. A withdrawal is settled by a reviewer, not on a schedule, and a person may refuse it. A cancelled request does not restore its amount automatically; an administrator may return it to the wallet after review. Nothing reverses a payout once it is marked complete: there is no clawback mechanism, and a confirmed infringement claim is answered by removing the file and by a strike on the account, not by taking money back.

We may suspend an account immediately for infringement or fraud, and will state the reason in writing. A suspension stops uploading, downloading and payouts at once. Infringement is recorded as a strike carrying its reason, the file it came from and its date, and you can read your own strikes on your security page. What a count of them leads to is decided by a person: nothing closes an account automatically on a number. Closing your own account is not self-serve yet: write in, and any balance at or above $5.00 is paid out before the account is closed.

The service is provided as it stands. There is one copy of your file in one bucket, no mirrors, and no uptime guarantee. Nothing here promises that a file, a link, an earning rate or a feature survives, and the deletion schedule in clause 03 applies to every file whatever it has earned. We are not liable for indirect losses, and nothing here limits liability that cannot be limited by law.