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 | To see where setup gets stuck |
| 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 |
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 don't keep a transcript of your chat with the bot, only the resulting feeds.
How long
| Data | Kept |
|---|---|
| Record of jobs sent to you | 14 days |
| Short links | 90 days; click records (country, device class) stay for statistics without the link |
| 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 |
| 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, to turn it into filters, and, for feeds with an AI filter, your AI filter rules together with each job's text, terms and the client's public stats (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 comes from public Upwork job postings. We never use your Upwork account. We don't sell your data and don't use it for advertising.
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.
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. - 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.