Terms

dropto.run publishes static websites. Using it means accepting what follows. Publishing is free and stays free; the paid tiers on the pricing page are a subscription, and Paying for a plan below says how they are charged. What we can point at sets out what is promised and what is not, and What we are liable for sets out the limit on what can be claimed when it is not.

What you may publish

Anything lawful that you have the right to publish. Specifically not allowed:

• Sexual content involving children, in any form. Reported to the authorities, and the account goes with the site
• Pages that impersonate another person, company, or service, or that collect credentials or payment details under false pretences
• Malware, or anything that attacks or misleads whoever loads it
• Infrastructure for an attack rather than the attack itself: a command-and-control endpoint, the backend of a phishing kit, or a page that mines cryptocurrency in the reader's browser
• Content that promotes terrorism, or incites violence against people
• Selling what cannot lawfully be sold — drugs, weapons, counterfeits, or data taken from somebody else
• Pages published to move search rankings rather than to be read: link farms, doorway pages, bulk generated text
• Content that is illegal where it is hosted or where it is read
• Using the service where trade sanctions forbid it. You confirm that you are not named on a sanctions list kept by the United Nations Security Council, the United States, the European Union or the United Kingdom, that you are not acting for or owned by somebody who is, and that you are not in a territory those lists put under embargo
• Material you do not hold the rights to
• Using the service as general file storage, a proxy, or a content delivery network for something hosted elsewhere
• Reselling the service, or putting it in front of your own customers as though the hosting were yours

A site that breaks these can be removed without notice. We would rather remove one site quickly than have every site on the domain blocked by a browser because of it.

Copyright complaints

If something published here infringes your copyright, tell us through the abuse form, or write to abuse@dropto.run if you would rather keep a copy of what you sent. Either way, include:

• The address of the page, and enough to identify the material on it
• Where the original can be seen, or what right you hold in it
• Your name and a way to reach you
• A statement that you believe in good faith that the use complained of is not authorised by you, your agent, or the law
• A statement that what you have told us is accurate, and that you hold the rights or are authorised to act for whoever does
• Your signature — typing your name at the foot of the message is enough

We take down what a complete complaint identifies, and we tell whoever published it what was removed and who asked for it. They can write back with their reasons. Where the two accounts cannot be reconciled we leave the material down and let the two of you settle it, because that is the outcome that can be undone and the other one cannot.

Repeated infringement ends an account. An account whose sites keep drawing complaints that hold up is closed, and its sites with it.

Limits

Publishing without an account is subject to limits on size, number of files and how long the site is kept: 1 MB per site, up to 20 files, at most 102.4 KB per file, deleted 7 days after the site is created. Every tier is listed on the pricing page, which reads the same figures the service enforces. Limits and retention may change; the service will tell you when you hit one rather than failing quietly.

A paid plan's limits are not narrowed without notice. If we lower a limit, shorten how long something is kept, or withdraw a feature on a tier you are paying for, it goes to the email on your account at least thirty days before it takes effect — the same notice as any other change that matters — and nothing you have already published is deleted inside that period. Cancel in those thirty days and the change never reaches you.

Signed-in plans also limit how many new or changed files may be published in a month. Republishing a file whose contents have not changed does not count towards it, so an ordinary update to a site already published is inexpensive against that figure. The first time an account goes past it in a month, the publish is allowed through anyway and we tell you; after that, publishing waits until the month resets.

Capacity. If the service as a whole is under extraordinary load, publishing without an account may be paused temporarily. Paid plans are not refused for that reason — only against their own limits.

Accounts

You must be at least 16 to use the service, with or without an account. If you are publishing for a company, you need to be allowed to accept these terms on its behalf.

You can publish without an account. If you make one, it is through Google, and you are responsible for what is published under it — keep access to it to yourself. One account per person; making several to get around a limit is a reason to lose all of them. What an account stores is set out in the privacy policy.

Your own domain

Pointing your own domain at a site is a paid feature; the pricing page says from which tier. The domain stays yours: you register it, you pay for it, and you keep the DNS records pointing this way. If the registration lapses or those records change, the site stops being reachable at that address and there is nothing we can do from this side.

The certificate is issued and renewed for you, which needs the DNS to be in place and to stay there. Add a domain you do not have the right to use, or use one for something the section above rules out, and we stop serving it.

Tokens and publishing from a script

The API, the command-line tool and the MCP server all publish with an access token. A token is your account. Anything done with it is done as you, so keep it out of anything public — a repository, a build log, a screenshot — and revoke it from your account the moment you think it has got out.

Publishing from a script counts against the same limits as the dashboard, and requests are rate limited. Working around a limit — several accounts, several tokens, hammering past a refusal — is a reason to lose the account. Building your own thing on top of the API is welcome; selling the hosting underneath it as your own is what the section above rules out.

Forms, and what your visitors send you

Turn forms on and what your visitors type is stored here for you to read. That is their data, not ours and not yours to do anything with: you choose what the form asks for and why, and we hold the answers on your behalf, use them only to deliver the feature and keep it free of spam, and pass them to nobody.

Which makes the rest yours. You need a reason to collect what you collect, you need to tell the people filling the form what happens to it, and you have to answer them if they ask for a copy or ask for it gone. Do not use a form to collect payment card details, passwords, health information, or identity documents — none of that should be in a form on a static site, here or anywhere.

Submissions are kept for ninety days from when they arrive, and then deleted. Deleting the site or closing the account does not remove them earlier — they are held apart from both so that a site taken down by mistake does not take the enquiries with it. There is no button for removing one today; ask at privacy@dropto.run and it is done by hand.

The processor terms we can give you today, in writing, are these: we process submissions only to deliver the feature and stop spam, never for anything of our own; Cloudflare is the only sub-processor on this path, carrying the form endpoint, the spam check and the mail we send you about it, and the privacy policy says what it does; submissions travel over HTTPS and are reachable only by the account that owns the site and by the operator of the service; we delete them on the ninety-day schedule above, or sooner if you ask; we help you answer a request from somebody who filled your form, including handing you a copy or deleting what they name; and if submissions here are ever exposed we tell you rather than only the people who filled the form.

Three things a full processor agreement would add and this does not: submissions are not returned or deleted when you stop using the service, they are deleted on the schedule either way; there is no audit or inspection right; and access is not covered by a separate written confidentiality undertaking. If your own obligations need those, write to hello@dropto.run before you rely on forms here.

Forms are a paid feature — the pricing page says which tiers carry them — and the privacy policy says what the spam check does and what it sends where.

Paying for a plan

The free tiers stay free. Publishing without an account is free, an account is free, and neither is a trial with an end date — no card is asked for and none is kept. The paid tiers are additions for people who want more, not a bill arriving later for what you already have.

Every tier and its price is on the pricing page, in US dollars. A paid tier is a subscription: you pay for a month or a year up front, and it renews at the same price until you cancel.

Payment is taken by our payment provider rather than by us. They are the seller of record for the transaction, their name is what appears on your statement, they handle any tax due where you are, and the receipt or invoice comes from them.

Cancelling: any time, and it stops the next payment. A cancelled subscription stays active until the end of the period already paid for, and the remainder of that period is not refunded — except inside the first fourteen days, where the paragraph below gives a consumer in the EU or the UK the money back in full. Cancel from your billing page, or write to hello@dropto.run. Whatever you cancel from, you keep the free tier — an account never stops working because a subscription did.

Fourteen days to change your mind, if you are a consumer in the EU or the UK. Inside that window you can have the payment back in full, whether you are on a monthly plan or a yearly one. We do not ask why, and we do not deduct for the days you used — the checkout never asked you to waive the right, and until it does there is nothing to deduct. Write to hello@dropto.run and say so.

Cancelling from the billing page does not do this. That button stops the next payment and leaves the plan running to the end of the period; taking the money back instead ends the plan the day the refund goes out, because the period you paid for is the thing being handed back. So it is one or the other, and the email is how to ask for this one.

When a paid plan ends — cancelled, expired, or a payment that could not be taken — your published sites keep serving. A site that fits inside the plan you are on is never taken offline over money.

While a payment is unsettled, publishing is paused: new sites, new deploys and new domains are refused until it goes through. Everything already published carries on being served, and deleting a site or a domain always works — that is how an account gets back inside a limit. The retries run for about a week, and the date the plan would end is shown on your billing page from the moment the first attempt fails.

A payment reversed by your bank is treated the same way: publishing pauses, your sites keep being served, and the plan is not taken away — whether a dispute is upheld is not ours to decide, and we would rather sort it out with you than cut off somebody who turns out to have been right. Write to hello@dropto.run and it gets dealt with.

If the payment is never settled the account returns to the free tier: free limits, and the dropto.run link comes back to the corner of your pages. If the account then holds more than the free tier allows, you get a week's notice in the dashboard, and after it the excess is put to sleep — oldest first, and only as far as it takes to fit. A sleeping site keeps every file and comes back on its own as soon as there is room for it. Domains over the limit are removed rather than slept, and those have to be added again.

Prices can change. A change never applies to a period you have already paid for, and the price on the pricing page at the moment you subscribe is the price that renews.

Your content stays yours

You keep every right to what you publish. You give us only what is needed to run the service: permission to store your files, to serve them to whoever visits your URL, and — on the tiers that carry it — to add a small dropto.run link to the corner of your pages as they are served. The link is plain HTML with no script and no tracking, the files we store are not modified, and the pricing page says which tiers carry it.

What we can point at, and what we do not promise

Your published site is served from a global edge network, not from a server of ours. Nothing about serving it calls back to us — so if this dashboard is broken or offline, your site carries on being served as normal. That is how it is built, which is why it is stated as a fact and not as a guarantee.

Beyond that, the service is provided "as is" and "as available", without warranty of any kind. We work to keep it running and your files safe, but we do not guarantee that it will be uninterrupted or that stored data can never be lost, and we may change, suspend or discontinue any part of it. As with any host, keep your own copy of what you publish.

What we are liable for

Some liability cannot be signed away, and where you live may be one of the places that says so — the European Union, the United Kingdom and Australia all give a consumer rights that survive a page like this. Nothing here takes those away, and nothing here is meant to.

Past that, and as far as the law allows: we are not liable for lost profit, lost business, lost data, or for any loss that follows from the first one rather than being it. And whatever a claim is about, everything we could owe you over it together is capped at what you paid us in the twelve months before it arose, or USD 100 if that is the larger — which it is if you have never paid us anything.

The cap is low because the price is, and because the section above says plainly that none of this is guaranteed. If a site here is worth more to you than that, keep a copy somewhere else, or buy hosting from somebody willing to sell you a promise.

If what you publish costs us

This section is about publishing as a business. If you are a consumer, it does not apply to you — you are answerable for what you publish under the ordinary law where you live, and nothing here adds to that.

Otherwise: if somebody brings a claim against us over something you published — what was on the page, what it collected, whose material it was — you cover what it costs us to deal with it, including legal fees. We tell you about a claim as soon as we know of it, and we do not settle one in your name without asking you first.

Ending it

You can delete a site at any time, and your whole account from your profile page — the privacy policy says what that removes and what has to be kept. We can suspend or remove a site or an account that breaks these terms, or where keeping it would put the rest of the service at risk.

If we take something of yours down or close your account, we tell you which of these terms it was and you can write back to hello@dropto.run and argue it. A person reads it, and a decision made in error is reversed — which is most of the reason the appeal exists, because the ones made quickly to protect the domain are the ones most likely to be wrong.

When these terms change

They change when the service does, and the date at the top of this page is the date they last did. A change that matters to you — the price, what you may publish, what we are liable for — goes to the email on your account before it takes effect, and carrying on using the service afterwards is how it is accepted. If you would rather not, cancel, delete, and it never reaches you. Smaller corrections just appear.

Which law, and where a dispute goes

These terms are read under the law of Vietnam, which is where the service is run from, and a dispute about them goes to the courts there.

If you are a consumer somewhere that has its own rules about this, that sentence does not move you. You keep whatever protection your own law gives you and you can bring a claim where you live — it sets where we can be taken, not where you can.

Before either of us goes near a court, write to hello@dropto.run. Almost everything that looks like a dispute is a disagreement about what the service actually did, and those are quicker to settle by reading the same page together.

The rest of it

If one part of these terms turns out not to hold, the rest still does, and the part that fails is read as narrowly as it has to be rather than as a hole through the page. Not enforcing something once does not give it up for good.

You cannot hand your account or these terms to somebody else without asking us. We can hand them on if the service is — sold, merged, or passed to whoever keeps it running — and the privacy policy says what happens to your data if that ever comes up.

These terms and the privacy policy are the whole of what is agreed between us about the service, and they replace anything said about it anywhere else — including on the pages that summarise them.