Privacy policy
flconsole never asks for your Upwork login and has no accounts on this site. This page lists what we store and why.
What we store
| Data | Why |
|---|---|
| Your Telegram user ID, chat ID and the language setting of your Telegram app | To send you jobs and answer your messages |
| Your feeds: name, search, filters, AI filter rules, status, and counts of jobs sent and dropped by the AI filter | To find and filter jobs for you |
| Which jobs were sent to you | So the same job isn't sent twice |
An event log: setup steps, feeds launched and deleted, /stop, /resume, pauses, blocking the bot, the label of the link that brought you, the commands and buttons you use | To see where setup gets stuck |
| The messages you send to the bot (not the bot's replies) | To see how people try to use the bot and fix what confuses them |
| Daily activity counts: messages to the bot, link clicks, jobs received | To pause alerts nobody reads and to measure retention |
| Short links to jobs and clicks on them: time, country and device class (mobile, desktop or bot) | To see whether alerts are read |
| AI agent connections: app name, when it was connected and last used, and hashes of its tokens | To let your agent in and let you disconnect it |
What your AI agent saves on our server through MCP: its notes about you (a personal instruction: your preferences and its conclusions), and feeds for your agent with Telegram alerts off (search, filters, your AI filter and the agent's notes for each feed); you see them in the bot under /feeds | So any agent you connect picks up where the last one stopped |
| The live demo on this website: the steps you take and the buttons you tap, the search, filters and AI filter rule you type, and how long you watched | To see where the demo helps and where it confuses people; see Live demo |
We don't store your Telegram name or username. During an AI agent sign-in, your Telegram name is kept only with that sign-in request, to show which account approved it, and is deleted with the request.
When you click a short link, the country is looked up from your IP address at that moment. The IP address and user agent are not stored.
We keep the text of the messages you send to the bot for 90 days, then erase it. The bot's replies aren't stored.
How long
- Record of jobs sent to you14 days
- Text of your messages to the bot90 days
- Text you type in the live demo90 days
- Short links90 days
- AI agent sign-in requestsAbout a day after they expire
- FeedsUntil you delete them
- Agent notes and saved MCP searchesUntil you delete them
- Telegram ID, event log, activity countsWhile the service runs
| Data | Kept |
|---|---|
| Record of jobs sent to you | 14 days |
| Text of your messages to the bot | 90 days; the latest filter descriptions you wrote for each feed stay while the feed exists, to sort out a wrongly read filter |
| Short links | 90 days; click records (country, device class) stay for statistics without the link |
| Live demo log | 180 days; the text you typed in the demo (search, filters, AI filter rule) is erased after 90 days |
| AI agent sign-in requests, with your Telegram name | Deleted about a day after they expire (a request expires in 10 minutes) |
| Feeds | Until you delete them, or 90 days after you block the bot |
| Your agent's notes about you and saved MCP searches | Until you delete them |
| Telegram ID, event log, activity counts | While the service runs |
Who processes it
- Telegram delivers messages between you and the bot.
- TypeSafe (typesafe.ai) is the AI provider. It receives the filter text you write in the bot or in the live demo on this site, to turn it into filters, and, for feeds and demo searches with an AI filter, your AI filter rules together with each job's text and terms and the client details shown with the job: country and city, payment verification, rating and reviews, total spent, hire rate, registration date, company size and industry (never the client's name).
- Your AI agent receives the jobs and feeds it asks for; its provider's terms apply to them.
- Google Analytics (Google) receives website visit statistics and, for visitors who came from the website, anonymous events from the bot and the MCP server, as described in This website.
- Microsoft Clarity (Microsoft) records how pages of this website are used (clicks, scrolling, mouse movement) so we can find confusing places. Text on the page is masked.
- Error reports may be sent to an error-tracking service.
- Hosting: the bot, the MCP server and the database run on rented servers.
Job data
flconsole collects new Upwork job posts itself. It never asks for your Upwork login, never connects to your Upwork account and never sends anything in your name.
A job is stored as Upwork shows it to freelancers: title, description, budget or rate, terms, category and skills, and what Upwork shows about the client: country and city, payment and phone verification, rating and reviews, total spent, hours paid, average rate paid, jobs posted and open, hires, hire rate, registration date, company size and industry. Alerts and the MCP server show these client details but not the client's name.
This website
flconsole.com uses Google Analytics to count visits and see which pages and buttons lead people to the bot and the MCP server: pages viewed, scroll depth, clicks on links to the bot, copied setup commands, opened FAQ questions. Google Analytics sets its cookies (_ga, _ga_*) and doesn't store IP addresses. We turned off advertising features and Google signals, and Google keeps the data for 14 months. Microsoft Clarity sets its cookies (_clck, _clsk) and records page interactions as described above.
In the EU, the EEA, the UK and Switzerland, analytics cookies are set only after you click Allow; until then Google and Microsoft receive visits without cookies or identifiers. You can change your choice at any time.
Fonts are served from our own server, not from a third party.
Links to the bot carry a label like site_home_hero, saved in the event log when you start the bot. If analytics cookies are allowed, the link also carries your anonymous Google Analytics ID. The bot then reports to Google Analytics that the visit led to starting the bot, creating a feed and receiving the first alert. The MCP sign-in page on mcp.lite.flconsole.com reads the same ID, if your browser has it, and reports opening the page and connecting an agent. Only these event names and the ID are sent, never your Telegram ID, name, feeds or chats.
Live demo
The live demo on this website keeps a log of what happens in it: which steps you reached, which ready-made answers you tapped, the search, filters and AI filter rule you typed yourself, which jobs were shown and opened, how long you watched, and whether you continued in Telegram. The text you typed is erased after 90 days; the rest of the log is kept for 180 days.
The log isn't tied to you: it uses a random ID that lives only in this browser tab and is gone when you close it, and a scrambled form of your IP address that changes every day, so visits on different days can't be linked. Your IP address itself isn't stored. The demo log sets no cookies and works the same whatever you chose for analytics cookies. If you continue in Telegram, the bot learns which demo search you came from, so it can set your feed up the same way.
The same steps, without any text you typed, are also sent to Google Analytics as events, under your analytics cookie choice above.
How to delete your data
- Delete a feed:
/feeds→ tap the feed → Delete. The feed, its filters and its AI filter are deleted. - Pause, don't delete:
/stoppauses all alerts and keeps your feeds. - Disconnect an AI agent:
/mcp→ Disconnect. Its tokens stop working right away. - Delete your agent's notes or feeds: delete a feed in the bot (
/feeds) or ask your agent to (delete_feed), ask it to clear its notes about you (save_agent_instructionswith empty text) or a feed's notes (update_feedwith emptyagent_notes), or email privacy@flconsole.com. Disconnecting an agent doesn't delete them. - Stop everything: delete your feeds and block the bot. Any feeds left are deleted 90 days after you block it.
To have your Telegram ID, event log and other records deleted, email privacy@flconsole.com from any address and include your numeric Telegram user ID (we don't store usernames, so we can't find you by one). We delete the records within 30 days and confirm by email.
Questions about this policy: privacy@flconsole.com.
Changes
When this policy changes, we update this page and the date above.