Fenavia Sync

Privacy Policy

Last updated: May 22, 2026

Fenavia Sync is a browser extension that helps a signed-in user move their own data — requests for quote (RFQs) and inventory listings they are already working with on an aviation parts marketplace — into their own Fenavia portal account. This policy explains exactly what the extension accesses, how that data is handled, and what the extension never does.

1. Information the extension accesses

  • RFQ and inventory data — the RFQ details and inventory listings the signed-in user is already viewing in their own marketplace session, read only when the user clicks a sync action.
  • Fenavia pairing key — a per-device key created when the browser is paired to the user's Fenavia portal. It identifies the device to the portal; it is not a password.
  • Marketplace access token — the access token the marketplace already issued to the user's own signed-in browser session, used so the extension can act on the user's behalf within that session.
  • Marketplace message broadcasts — the public “for sale” and “wanted” notices the marketplace shows to every signed-in member, read only when the user clicks the sync button. These are posts other companies chose to publish; the extension stores their text, the posting company's marketplace code, and the contact details the poster published alongside the notice. Because these notices are public to the whole marketplace, they are held in one shared pool: a sync by any Fenavia customer updates the same feed that every other Fenavia customer reads.
  • Sync state — which records have already been synced, so the same item is not sent twice.

2. How the information is used

The data is used for one purpose only: to transfer the user's own RFQ and inventory records into that same user's Fenavia portal account, and — only when the user explicitly confirms a specific change in a dialog — to apply that change back to the user's own marketplace listing. The extension does not profile users, show advertising, or make automated decisions.

3. Where the information is stored and sent

  • On the device: the pairing key, paired portal origin, and sync state are stored in the browser's extension storage (chrome.storage.local). The marketplace access token is held in memory only (chrome.storage.session) and is cleared when the browser closes — it is never written to disk.
  • Off the device: RFQ and inventory data is sent only to the user's own Fenavia portal, over HTTPS, authenticated with the per-device pairing key. It is stored in that user's own tenant account in the Fenavia system.
  • The data is not sent to any other server, advertiser, data broker, or analytics provider.

4. What the extension never does

  • It does not store marketplace usernames, passwords, or cookies.
  • It does not crawl, scrape in the background, or run when the user has not asked it to — every sync is initiated by the user.
  • It does not sell or share data with third parties.
  • It contains no third-party trackers, no analytics SDKs, and no remote code — all extension code ships inside the package (Manifest V3).

5. Permissions

The extension requests only the browser permissions needed for the features above: storage for the pairing key and sync state, access to the active tab when the user triggers a sync, and host access to the marketplace domains and the user's Fenavia portal domain. Each permission is tied to a specific, user-initiated feature.

6. Data retention

On-device data remains until the user disconnects the extension or removes it, which clears the stored keys and state. Data synced into the Fenavia portal follows the retention rules of the user's Fenavia account and can be managed or deleted there.

7. Affiliation

Fenavia Sync is not affiliated with, endorsed by, or sponsored by ILS, Inventory Locator Service, or the ILS Marketplace. It operates within the user's own authenticated marketplace session to move data the user is already working with into their own Fenavia account.

8. Changes to this policy

If this policy changes, the “Last updated” date above will change. Material changes will be communicated through the Fenavia portal.

9. Contact

Questions about this policy or about data handled by the extension can be raised from within the Fenavia portal, or by emailing support@fenavia.com.