Privacy Policy
What I collect, and what I do not
Privacy Policy
TweetFeed
Who I am
I am Daniel López. I run TweetFeed alone, from Spain. I am the data controller for tweetfeed.live, api.tweetfeed.live, and mcp.tweetfeed.live.
No accounts
TweetFeed has no accounts and no login. The website, the API, and the MCP server do not ask for your name, your email address, or a key. I set no cookies.
Your browser
The website saves your light or dark theme choice in your browser. It saves nothing else. My servers never read it.
Analytics
The website uses Umami, which I host myself at s.tweetfeed.live, and Ahrefs Web Analytics. Both work without cookies. They count page views, referrers, and coarse device and country data. Umami does not store your IP address. The API and the MCP server have no browser analytics. When a known AI agent calls the API, the API sends one event to my Umami. The event holds the path and a shortened User-Agent. It holds no IP address.
Logs and rate limits
Cloudflare serves all requests. It sees your IP address and User-Agent, and it applies a rate limit of 50 requests in 10 seconds for each IP. The API also counts single-IOC lookups (
The data
The IOCs come from public posts on X. For each IOC, I keep the post link and the handle of its author as source data. I do not read private accounts or private messages. The data is public domain (CC0 1.0).
Sharing
I do not sell your data. Cloudflare processes requests for me. GitHub hosts the website and the public data. The website also loads fonts from Google Fonts and code libraries from public CDNs. Each of these services has its own privacy policy. The Terms of Service list them in section 13.
Your rights and contact
You can ask me to give you, correct, or delete your data, or to stop using it. You can also complain to the Spanish data protection authority (AEPD). To contact me, open a GitHub issue. Do not post private data in it. TweetFeed has no email address.
Last updated: 18 October 2026
I am Daniel López. I run TweetFeed alone, from Spain. I am the data controller for tweetfeed.live, api.tweetfeed.live, and mcp.tweetfeed.live.
No accounts
TweetFeed has no accounts and no login. The website, the API, and the MCP server do not ask for your name, your email address, or a key. I set no cookies.
Your browser
The website saves your light or dark theme choice in your browser. It saves nothing else. My servers never read it.
Analytics
The website uses Umami, which I host myself at s.tweetfeed.live, and Ahrefs Web Analytics. Both work without cookies. They count page views, referrers, and coarse device and country data. Umami does not store your IP address. The API and the MCP server have no browser analytics. When a known AI agent calls the API, the API sends one event to my Umami. The event holds the path and a shortened User-Agent. It holds no IP address.
Logs and rate limits
Cloudflare serves all requests. It sees your IP address and User-Agent, and it applies a rate limit of 50 requests in 10 seconds for each IP. The API also counts single-IOC lookups (
/v1/ioc) for each IP. It does not block them today. When one IP sends more than 20 in a minute, the API writes one log line with that IP address, User-Agent, and request path. Cloudflare Workers Logs is on for the API and the MCP server. It can record the request URL and status for a short time (days). For a lookup, the URL can contain the value you look up. The MCP server writes no log lines of its own and does not read your IP address.
The data
The IOCs come from public posts on X. For each IOC, I keep the post link and the handle of its author as source data. I do not read private accounts or private messages. The data is public domain (CC0 1.0).
Sharing
I do not sell your data. Cloudflare processes requests for me. GitHub hosts the website and the public data. The website also loads fonts from Google Fonts and code libraries from public CDNs. Each of these services has its own privacy policy. The Terms of Service list them in section 13.
Your rights and contact
You can ask me to give you, correct, or delete your data, or to stop using it. You can also complain to the Spanish data protection authority (AEPD). To contact me, open a GitHub issue. Do not post private data in it. TweetFeed has no email address.
Last updated: 18 October 2026