What feedql does with your data.

What we collect

• Your account. Your email address, and the sign-in method you use (email and password, or Google). Sign-in is handled by Firebase Authentication; we never see or store your password.
• What you set up. Topics, channels, sources, filters, the “About me” text and memory you write, digests, exports, API keys (stored only as hashes), webhooks and inbound webhooks (including the addresses you send to).
• What you do. Votes, read marks, saved items, notes, which items matched which topic and with what score, item reports you send, and counts of opens and clicks. The history of your feed is yours only; other users cannot see it.
• Assistant chats. Your questions and the answers, kept for 30 days so you can come back to them.
• Browser extension. If you install it, the posts it reads from X, LinkedIn or Medium search in your own logged-in browser are sent to your feedql account. It does not read your cookies.
• The iOS app. Crash, hang and performance reports (which screen, how fast it starts and scrolls, how much memory it uses) and a few counts of events such as app open or push opt-in. No content, no advertising identifier, no tracking across other apps or sites. A switch in the app’s Settings turns this off.
• Email we send you. We log when, to whom, which kind (invite, confirmation, digest, notice) and the subject, plus whether it was accepted. System mails are logged without their text.
• Web push. If you opt in, your browser’s push address, so we can notify you.
• The waitlist. Your email, the optional text about what you follow, the job you picked, your country (from Cloudflare) and your browser’s user-agent.
• Technical logs. Operational error logs, kept 14 days, to fix faults. On the public site we count visits from AI assistants and search bots in aggregate, without IP addresses or people.

The sources you follow bring in public posts written by other people. Those are not your personal data and are stored once for everyone who follows the same source.

What we use it for

To run feedql for you: collect, score and show the feed, send digests and notifications, keep the service safe and fix it. We do not sell data, we show no ads, and we do not use your data to train AI models. There is no advertising or analytics tracking on feedql.com or in the app.

AI processing

Scoring, summaries and the assistant use AI language models. To do that, we send the text of posts that matched your topics, your topic descriptions, your “About me” and, in the assistant, your questions and the data it looks up for the answer, to AI providers through our own gateway. The gateway passes each request to the company that runs the model. What each receives:

• Anthropic (Claude models). Scoring posts against your topics, summaries of events, setting up topics, reading pages you add, and the assistant (your question, the post or topic you are looking at, and the data it looks up in your account). When the assistant searches the web, Anthropic runs the search through the same gateway.
• OpenAI (embeddings). The text of posts and the phrases you search by meaning are turned into number vectors, so that reports of the same event can be grouped and posts can be found by meaning. Only the text is sent, not your account.

Each of these companies acts as our data processor for this purpose, and its own privacy policy applies to the data sent to it.

Who else handles your data

• Google (Firebase Authentication). Sign-in and the account email. Google Fonts also loads the typefaces on this site and in the app, so Google sees your IP address when a page opens.
• Cloudflare. Sits in front of feedql.com (DNS, CDN, security), so it sees requests to the site. Cloudflare R2 stores cached post pictures and our encrypted backups.
• Hetzner. Hosts the servers and databases, in the European Union.
• Anthropic and OpenAI. AI models and embeddings, as above.
• ImprovMX. Sends our email and forwards mail sent to hello@feedql.com and privacy@feedql.com.
• Your browser’s push service (Apple, Google or Mozilla), only if you turn on web push.

Beyond these, we share your data only if the law requires it. Webhooks you create send new items to the address you choose; that address is yours to trust.

Legal basis and where data is stored

If you are in the European Economic Area or the UK, we process your data to provide the service you asked for (performance of a contract); for security, abuse prevention and improving the service (our legitimate interests, which you can object to by contacting us); and, for web push, on the basis of the permission you give in your browser or in iOS, which you can withdraw at any time. Your data is stored on our servers in the European Union and is encrypted in transit (TLS).

How long we keep it

• Collected posts and their matches: 365 days from when feedql first saw them, unless you saved, noted or pinned them. A channel can set its own retention, from 30 days up to 10 years.
• Assistant chat history: 30 days.
• iOS diagnostics: 90 days.
• Email log: 90 days.
• Webhook delivery logs: 14 days. Error logs: 14 days.
• Nightly backups: the 7 most recent are kept, so deleted data leaves them within a week.
• Everything else: until you delete it or your account.

Your choices and deleting your account

• Export. Download your items as JSONL or CSV, or read them through the API and MCP.
• Delete a topic, channel, key or webhook in Settings at any time; the data under it goes with it.
• Delete your account. In the web app, Settings → Delete account, then type delete; in the iOS app, Account → Delete account. Your topics stop collecting and your data is removed within 24 hours: your account and sign-in, topics, channels, votes, marks, notes, saved items, history, keys, webhooks, digests, exports, assistant chats, diagnostics and email log. Posts that were shared with other people stay, with no link to you. You can also email privacy@feedql.com and we will do it for you.
• Access, correction, objection. Email privacy@feedql.com. If you live in the EU, UK or a similar region you have these rights by law, and the right to complain to your data protection authority.

Cookies

The public pages on feedql.com set no cookies of their own. When you sign in, the app sets one session cookie (__session, valid 5 days, only sent over HTTPS, not readable by scripts). Following an invite link sets a one-hour cookie, and connecting an AI tool sets a short one that remembers where to return to. A few layout choices (such as column widths) are kept in your browser’s local storage. We use no analytics or advertising cookies. Cloudflare may set a security cookie to tell people from bots.

Children

feedql is not for people under 16. If you think a child has signed up, tell us and we will delete the account.

Changes and contact

When we change this page, we change the date at the top; for a material change we will also tell signed-in users by email. Questions or requests about your data: privacy@feedql.com; anything else: hello@feedql.com. The rules of the service are in the terms of use.