Privacy Policy
Last changed: 15 November 2026
TECH BUDDIES LTD runs putlive and decides what is done with the personal data described here.
- Operator: TECH BUDDIES LTD
- Company number: 15175545
- Address: 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ
- Questions about your data: legal@putlive.dev
This page says what we keep, for how long, and who receives it. Every length of time below is the one the service is configured to. For personal data inside the files you publish, see the Data Processing Agreement.
What we keep about you
| What | Why | How long |
|---|---|---|
| Your e-mail address and the time you last signed in or used a key | To sign you in, to send you notices, and to find accounts that are not used | As long as the account exists. The clean-up of an unused account removes its sites, files, API keys and sessions; the account record with your address stays. |
| A sign-in code | To prove the address is yours | Valid for 10 minutes; removed 1 day after it expires. |
| A dashboard session | To keep you signed in | Lasts 30 days; removed 1 day after it expires. Only a hash of its token is stored. |
| An API key | To let your agent work for you | Until you revoke it or the clean-up of an unused account removes it. Only a hash and the first characters are stored. |
| Your sites and their files | To serve them | Until you delete the site, or the clean-up of an unused account deletes it. A site that is switched off, waits for a person to look at it or has a report that its sender confirmed and we have not decided yet is kept until that is settled, and cannot be deleted before. The files of a refused version are kept 30 days. |
| How much visitors downloaded from your sites, by month | To enforce the monthly limit | With the account. These are sums; they hold no visitor's address. |
| A viewer's e-mail address, when a visitor asks for a code to open an e-mail-protected site | To send the code | The code is valid for 10 minutes; the row is removed 1 day after it expires. The list of addresses you allow is yours and stays with the site. |
| What we did to a site and why (the record of moderation actions, with the note of the person who decided), and the statement of reasons we sent you | To be able to show what was decided, and why | Kept; it is not deleted. It holds no visitor's address. |
Encrypted backup copies of our database and of the files published on the service, kept only to restore the service after a failure, can still hold a record or a file that you deleted (or that a clean-up removed) for 35 days at most; after that it is gone from them too.
Reports about a site
When somebody reports a page, we keep the address of the page, the category, the explanation they wrote, and, if they gave them, their name and e-mail address, and the network their request came from.
- A report that its sender never confirms loses the sender's name, address and network when the confirmation link expires, 24 hours after it was sent.
- A confirmed report keeps them while it is open, and for 183 days after the decision. Then they are removed.
- The report itself (the page address, the category and the explanation) is never deleted. The statement of reasons we send the owner of a site never names the person who reported.
Visitors of published sites
When somebody opens a published site, the server that shows it sees their address, the page they ask for and their browser's headers. This is where those addresses are kept, as the service is configured today:
| Where | What it holds | How long |
|---|---|---|
| The full log of requests to published sites, readable only by the web server's own user | Time, the visitor's address, the page asked for with its query, the status and size, and the browser's headers (the values of cookie and authorization are replaced) | A line is gone after 8 days at most. |
| The log the meter uses to count downloads | Time, site, status, bytes: no address | The same limit, 8 days at most. The sums it produces hold no address. |
| The brake on wrong guesses at a password or an address, in the memory of the server that shows sites | The visitor's network, as the key of a counter | Short windows; gone when the server restarts. Never written to disk or to a log. |
| Counters that limit sign-in codes, reports and similar requests, in our database | The network only as a keyed hash, never as the address | The counter lives for its window; the daily clean-up removes it 1 day after the window ended. |
| A report's network field | The reporter's network, as text | As in "Reports about a site" above. |
| The output of our services (what the servers write when they run) | No visitor's address, no page asked for, no cookie, key or code | Each service keeps a bounded amount, the oldest dropped. |
In front of the dashboard and the API there is a reverse proxy of our hosting platform, and it keeps no log of requests.
Who receives data
- Our hosting provider stores and serves everything, including the files you publish.
- Our mail provider carries the e-mails we send you and your visitors: sign-in codes, viewer codes, notices, statements of reasons.
- Google Web Risk receives the web addresses of links found in published pages, to check them against its lists of dangerous sites. It receives no files and no account data.
- OpenAI, which runs the language model, receives the title, the visible text and a summary of the forms of the pages of a Free publication, with their file names, to judge whether a page imitates a well-known service. For a confirmed report, it may also receive what the reporter wrote about the page, but not the reporter's name, address or network. It receives no account data.
- Telegram carries alerts to our operators. An alert names a site's address or an identifier; it never holds a visitor's address, a key or a code.
We do not sell personal data and we show no advertising.
Cookies
app_sessionkeeps you signed in to the dashboard. It is set on the product's own address only, is not readable by scripts, and lasts 30 days.__Host-gateis set by a published site that asks for a password or an e-mail code, on that site's own address and for that site only, and works for 24 hours, so a visitor does not have to sign in again at every page.
The public pages of the service set no cookie and load nothing from another address: no analytics, no outside fonts, no outside scripts.
Your rights
To ask what we hold about you, to have something corrected, or to ask us to delete it, write to legal@putlive.dev. A person reads it and answers.