Collect only what supports the workflow
We keep account, workspace, watchlist, signal, reply, and subscription records needed to run the product and show your history.
Privacy policy
Privacy Policy for FiboAgent
This policy explains what FiboAgent and the FiboAgent Chrome extension may collect, how that data is used, and how data moves between your browser workflow and the product.
Last updated: April 24, 2026
Policy summary
What matters most, in plain English
FiboAgent is designed around a LinkedIn workflow: browser-side page analysis happens through the extension, product settings and history live in the app, and AI requests use task-specific context for scoring, summaries, and reply drafting.
Core principles
Keep local actions local when possible
The browser extension handles LinkedIn-side interactions in your own browser environment instead of pretending to be a remote bot.
Use AI context narrowly
When scoring content or generating replies, we send only the relevant prompt and content context required for that specific task.
What data we may collect
Depending on the feature you use, this may include account profile details, authentication state, workspace settings, watchlist targets, synced signal records, generated replies, digest outputs, subscription state, and operational logs needed to keep the product reliable.
What the extension may access on LinkedIn
When you use the extension on supported LinkedIn pages, it may access page content such as post text, visible metadata, URLs, author details, and reply context so it can analyze posts, identify signals, and support reply drafting in place.
Authentication, cookies, and local storage
To keep your extension and web app sessions aligned, FiboAgent may use cookies, local storage, and extension storage for account state, selected workspace, language preference, lightweight cache data, and other settings needed for the core workflow.
How we use collected data
We use collected data to provide core product functionality, including post analysis, signal scoring, reply generation, workspace management, watchlist sync, activity review, billing operations, and product reliability or abuse prevention.
How data may be shared with service providers
Some workflows rely on infrastructure and service providers such as hosting, authentication, billing, analytics, or model providers. When needed to deliver a requested feature, task-specific data may be processed by those providers within the relevant product flow.
How long data may be retained
We keep data for as long as it is reasonably needed to provide the service, maintain account history, support billing and operational needs, and preserve workspace records you rely on. Some local extension state may remain in browser storage until you clear it or remove the extension.
Your choices and control
You can change workspace settings, remove watchlist items, manage subscription status, stop using the extension, clear browser-side extension storage, or contact us regarding account-level privacy requests through the support paths made available by FiboAgent.
Chrome extension quick view
This is the shortest useful view of how the extension relates to privacy and browser permissions.
•
The extension uses storage for settings, selected workspace, lightweight cached state, and workflow continuity.
•
The extension accesses supported LinkedIn pages to read visible page content needed for analysis and reply support.
•
Cookies and auth state may be used to connect the extension with your FiboAgent account session.
•
Alarms and tab access may be used to keep runtime status and workflow-related sync tasks up to date.
•
FiboAgent is not designed as a general browsing monitor and is scoped to its supported workflow.
Questions about privacy
If you need help with privacy-related requests, account data questions, or extension-specific concerns, use the support contact path provided through the FiboAgent product, repository materials, or official website.
Want the workflow context too?
Read the docs if you want to see how workspaces, signals, replies, and extension sync fit together end to end.