FOR YOU. BY YOU.
Privacy Policy
Sharing an opportunity should be simple—and you should know what happens to the information you share.
Effective and last updated: October 14, 2026
Who we are
fyby is a community job board operated by Muhammad Jazeb Javed. This policy covers the website and the fyby Chrome extension. Contact us at jazebjaved52@gmail.com.
What the extension collects
The extension reads supported LinkedIn page content to find posts and display a sharing button. When you choose to share, it sends the selected announcement’s text, original link, platform, capture time, adapter version and completeness information to fyby. If you edit the announcement before sharing, your supplied text is sent instead.
For supported image posts, it also sends URLs for up to the first three detected images. The server downloads those images for processing. Announcement text and images may contain names, contact details or other personal information included by their authors. Share only information intended for public job seekers; do not submit private messages or sensitive information.
The extension does not collect your LinkedIn password, authentication cookies, private messages, comments, unrelated browsing history or existing clipboard contents. To obtain a post link, it may trigger LinkedIn’s “Copy link to post” action, which writes that selected link to your clipboard.
Information stored in your browser
The extension stores your latest 200 share records, their status and links, plus published submission identifiers used for your contribution count, in Chrome’s local extension storage. A sharing token is stored locally if you connect one. It is not sent to LinkedIn or the AI provider. Background checks retrieve the status of unfinished shares. Removing the extension clears its local data, but does not delete submissions already stored by fyby.
The website can check whether the extension responds on the configured fyby website. That connection check does not reveal your sharing token or share history.
How we use and publish information
We use submitted content to identify hiring announcements, extract job details, categorize opportunities, detect duplicates, process images and display sharing results. Published job information—including any application instructions or contact details present in that information—and the original source link are visible to everyone on the community board. Submitted raw captures and stored images are not served publicly by the website.
Reports include the job identifier, your written reason and creation time. Network requests expose technical information such as IP addresses to our hosting infrastructure. fyby uses hashed IP-derived identifiers for rate limiting and records operational events such as submission IDs, processing status and errors.
Service providers and AI processing
Railway hosts our website, worker, database, queue and persistent image storage. Submitted text and relevant image content are sent to Google’s Gemini API to transcribe images and extract job information. These providers process data under their own policies; this policy does not promise that their retention or model-training practices are the same as ours.
See Railway’s privacy policy and Gemini API terms. Opening a source post, application link or other external website is subject to that website’s policies. We will update this policy when the providers or processing practices change.
Website usage analytics
When enabled, we use PostHog to understand website visits, searches, filter usage, job-detail views and clicks on source posts and installation links. We also record external referring website domains and approved campaign source, medium and campaign labels to understand where visits come from; full referrer URLs and arbitrary campaign values are excluded. We send counts and interaction metadata, such as job identifiers, rather than typed search or location text, job content, report reasons, or source URLs. Automatic click capture is disabled. We use masked session replay to understand website interactions and diagnose problems: text and input values are masked, report dialogs and images are blocked, and network payloads and console recording are disabled. We also collect unhandled browser errors and rejected promises, with error messages and source context redacted. These recordings cover our website, not LinkedIn or the extension. Analytics identifiers are kept in memory and reset on page reload; we do not create identified user profiles. We skip analytics when your browser signals Do Not Track or Global Privacy Control. This integration does not collect extension activity or LinkedIn browsing.
PostHog receives technical connection information when your browser sends analytics requests. See PostHog’s privacy policy. Analytics can be blocked through browser privacy tools. Analytics retention is controlled in our PostHog project.
Retention and your choices
Submissions, extracted results, reports and image files currently have no automatic deletion period. We retain them until removed for operational reasons or following an applicable deletion request. Provider logs and copies may have separate retention periods.
You can stop collection by not sharing, disabling the extension or uninstalling it. To request access, correction or removal of submitted or published information, email jazebjaved52@gmail.com with the original post link or submission ID. We may need information to verify your relationship to the data. A request does not remove the original LinkedIn post or copies outside our control.
Security and limited use
Production transfers use HTTPS. Sharing tokens and provider credentials are not included in public job listings. No service can guarantee absolute security.
fyby uses information collected through its extension only for its disclosed job-sharing purpose and related operation and security. We do not sell extension data, use it for personalized advertising, or transfer it to data brokers. Our use of extension information adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Authorized operators can access server records; individual content review is limited to user-authorized support, security investigation or legal requirements.
Updates and questions
We will revise this page and its updated date when these practices change. For privacy requests or questions, visit Support or email jazebjaved52@gmail.com.