Terms of Service
Last changed: 15 November 2026
These terms are between you and TECH BUDDIES LTD (the operator), who runs putlive at https://putlive.dev. Using the service means you accept them.
- Operator: TECH BUDDIES LTD
- Company number: 15175545
- Address: 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ
- Questions about these terms: support@putlive.dev
Who decides what you publish
You decide whether you may publish something, and you alone are responsible for what you publish. Whether a text, a picture, a piece of code, a data set or a person's details may go online is your decision, not ours. The same holds for what an AI agent publishes with your account or your API key: it counts as published by you.
The checks described under "Content moderation" look for danger to other people. They are not a legal review, and a publication that passes them is not thereby allowed.
What the service is
putlive stores the files you send (a page, a small site, a single-page app, a file) and serves them under an address on putlive.page.
- It serves static files only. No code of yours runs on our servers.
- A new site has a long random address and tells search engines to skip it. Anyone who has the address can open it. You can add a password or a list of e-mail addresses, and you can switch access off.
- Accounts are by invitation for now. You sign in with a code sent to your e-mail address and work through the dashboard, the API or an agent that holds one of your API keys. A key is shown once. Keep it secret: what is done with your key is done by you.
- Every account is on the Free plan, and there is nothing to pay.
The Free plan
- 5 sites, 1 GB of stored files, 100 MB for one file.
- 10 GB of downloads by visitors in a calendar month. When it is used up, visitors of your sites get an error until the month turns over; nothing is deleted.
- An e-mail list of up to 5 addresses for one site.
- The mode "public" (searchable, no secret in the address) is not available.
- Every HTML page of a Free site carries a small bar, "Published with putlive", with a link to report the page.
Where the service is offered
putlive is not offered in the United Kingdom. Signing up from there and opening published sites from there are both refused.
Content moderation
This section describes what is restricted, how we look for it, and how you can object.
What is restricted
What the Acceptable Use Policy forbids: phishing, malware, illegal content, sexual content, other people's works, redirect pages and link shorteners, and whatever else breaks these terms. The policy is at Acceptable Use Policy.
How we look for it
Automatic checks before a publication is served. Every publication of a Free account is checked before anyone can open it:
- Every file is scanned by an antivirus scanner.
- The links found in the pages are checked against Google Web Risk's lists of dangerous addresses.
- A language model reads the title, the visible text and a summary of the forms of the pages and says how likely it is that a page imitates the sign-in or payment page of a well-known service. The model gives a score. It does not decide.
- A page with a password field, or a form that sends its data to another address, is held for a person.
A page that is too large, or a site that is too big, for the automatic check to read in full is held for a person at once. A check that cannot run is never counted as passed: the publication waits and the check is tried again. A file the scanner flags, a link on Google's lists, or a page the model is sure imitates a known service is refused. When a check is in doubt, the publication is held for a person, who approves or refuses it. A held publication that nobody has decided after 72 hours is refused. If it was an update, the version that was live keeps being served meanwhile.
A weekly look at every live site. Every live site is checked again about every 7 days with the current malware signatures and the current lists of dangerous links. A definite finding switches the site off. If a person restored that version after looking at it, the service tells that person instead of switching the site off again.
When a person looks at your files. Only when a publication is held for a review, when a site is reported or switched off and a decision is needed, and when you appeal.
Reports. Anyone can report a published page with the form at /report or by e-mail to abuse@putlive.dev. A report from the form counts only after the reporter opens the link we e-mail and presses the button, so nobody can report in somebody else's name. A report nobody confirms is closed after 24 hours. A confirmed report is decided by a person, except in the automatic cases below. A language model may read a confirmed report and the results of our own checks and propose a decision to that person; it never acts alone.
When a site is switched off without a person. Only in these cases: a confirmed report from a reporter whose address is at a domain we have put on our list of trusted reporters; two confirmed reports from different people, on different networks, that both say phishing or both say malware; a confirmed report of phishing or malware while our own check of the newest version is unsure; our own scanners finding malware or a dangerous link. After a person restores a site, the report rules do not act on it for 7 days.
Orders of authorities. When an authority orders us to remove or restrict something, a person switches the site off first and then answers the authority. See Digital Services Act contacts.
What a restriction does
- It is against one publication or one site, not against your account. The moderation rules act on a site or a publication, never on an account (the clean-up of unused accounts, below, is a separate matter). If a site is switched off for something serious, a person may look at the other sites of that account; each one is judged on its own and restricted, if at all, with its own statement of reasons.
- Switching a site off deletes nothing. Visitors see a page that says the site is not available. Your files are kept. An update that is refused leaves the live version online; the files of the refused version are kept 30 days so that you can ask us to look again, and are then removed.
- Every restriction comes with a statement of reasons, by e-mail, whoever or whatever decided it: a site switched off after a report, by a rule, by the weekly look or by a person, and a publication refused by the checks, by a person or when a hold ran out. It has five parts: what was restricted, the facts we relied on, whether automated means were used, which rule it was and how to appeal. It never names the person who reported. A publication that is only held gets a message that says why and what happens next; it is not a restriction yet.
Appeals
If you think a restriction is wrong, reply to the e-mail with the statement of reasons and tell us why. A person reads your reply and answers it. If that person decides we were wrong, the site is restored or the publication approved, and you are told. If the reply does not reach us, write to support@putlive.dev. We do not promise how fast we answer.
You can also take the matter to an out-of-court dispute settlement body or to a court; using our appeal does not take that away.
Free accounts that are not used
A Free account counts as used when you sign in or use one of its API keys. An account with sites that is not used:
- after 60 days gets an e-mail that its sites will go offline and later be deleted;
- after 80 days gets a second e-mail;
- after 90 days, and at least 10 days after a warning was sent, has its sites taken offline (the files are kept);
- after 120 days, and at least 30 days after the sites went offline, has its sites and files deleted and its API keys removed. The account itself, with your e-mail address, stays.
Signing in or using an API key at any time starts the count again. After an outage of ours these dates move later, never earlier. A site that is switched off, has a report that its sender confirmed and we have not decided yet, or waits for a review is left alone by this clean-up until that is settled.
You can delete a site
When you delete a site, its files are removed from the servers that show it. A site that is switched off, that waits for a person to look at it, or that has a report that its sender confirmed and we have not decided yet cannot be deleted until that is settled: we keep its files meanwhile, so that the case can be decided and you can ask us to look again. The message you are shown says so; reply to the e-mail we sent you about the site, and delete it once the case is closed.
No promise of availability
The service is offered as it is. We do not promise that it is always available, that it is fast, or that we answer a message within a set time. The page /status shows whether each part answered over the last days. Keep your own copy of everything you publish.
Changes
When these terms change, the date at the top changes.