Privacy policy

Last updated 16 October 2026. brln.tv is operated by Aleksandr Brilliantov.

What you publish is public

A file you upload — through the website, the API, the MCP server at https://brln.tv/mcp or the Claude Code plugin — is served at a URL on pages.brln.tv that anyone who has the link can open. Do not upload anything you would not want a stranger to read.

Artifact pages are marked noindex and robots.txt refuses search and training crawlers. AI assistants that fetch a link on a person's request (for example Claude-User) are allowed to read it, so that a link you hand to an assistant works.

What we collect

The file and its metadata: name, size, type, upload time and a view counter.
The uploader's IP address, stored with each upload. It enforces the anonymous upload quota and lets us act on abuse.
Account details, if you register: username, email address and a bcrypt hash of your password. We never store the password itself.
Usage statistics: for each request, a coarse path category, status code, user-agent, referring site, country (from Cloudflare) and a digest of the IP address salted afresh every day, so a visitor cannot be followed from one day to the next. No full URLs and no raw IP addresses.
Web server logs: standard access logs including IP addresses.

When you connect through an AI assistant, we receive only the tool calls it makes — the file you ask it to publish, or the artifact id you ask about. We do not see your conversation.

How long we keep it

Anonymous uploads are deleted after 30 days. Registered users' uploads are kept until they delete them.
Deleting an artifact removes the file immediately. A record that the artifact existed — its name, size, uploader IP and deletion reason — is kept for abuse handling.
Usage statistics are deleted after 90 days; web server logs after 14 days.

Cloudflare proxies brln.tv (not pages.brln.tv) for security and DDoS protection, and so handles those requests in transit.
Google Analytics runs on the landing page only — not on the documentation, the API or any artifact.
Telegram carries operational notices to the operator, including each new upload's filename, URL and size, and the IP address for anonymous uploads.

Files and the database are stored on our own server, not with a storage provider. We do not sell data, use uploads for advertising, or use them to train models.

Your choices

Delete an anonymous upload with the delete_token returned when you published it.
Delete a registered upload through the API (DELETE /api/artifacts/{id}) or the MCP delete_artifact tool.
To delete your account, or to report content that should not be here, contact us below.

Contact and support