Public support, documentation, and policies for browser extensions by buondevid.
View the Project on GitHub buondevid/browser-extension-support
Last updated: July 23, 2026
FINNlog is a local-first browser extension that creates before-and-after revision history for supported FINN listings when the user visits them or explicitly requests a manual update. The current release supports FINN Torget item pages plus allowlisted real-estate categories covering home and leisure-home sales, plots, residential rentals, commercial property sales and rentals, and commercial plots. Torget tracking is free; real-estate tracking requires FINNlog Pro.
For supported Torget listings, FINNlog reads the canonical URL and item ID, title, description, price, favorite count, category path, attributes, status, postal-level location, image URLs, and FINN edit timestamp. This is website content and browsing activity under Chrome Web Store policy.
Users may optionally write a personal comment about a tracked item. Comments are stored with that item only in the extension’s local database and are not part of the captured FINN listing content.
For supported residential real estate, FINNlog locally reads asking and total price, purchase costs, shared debt and assets, recurring costs and their description, property and ownership type, pre-emption rights, room and area details, build year, floor, plot and energy details, facilities, viewing times, title, an allowlisted subset of property-description sections, status, coarse postal location, and stable image identities. It also reads the public favorite count as non-revision observation metadata.
For residential rentals, FINNlog locally reads monthly rent, deposit, included costs, property type, bedrooms and area, floor, furnishing, whether pets are allowed and refugees are welcome, availability dates, facilities, viewings, and allowlisted description sections. For commercial categories it locally reads the applicable sale price or annual-per-area rent, sale costs, taxes and municipal fees, property and ownership types, gross or ranged areas, plot details, construction year, floor, availability, facilities, viewings, regulations, and category-specific allowlisted descriptions. The stored primary price records its basis so rental amounts are not presented as ordinary sale prices.
Owner, broker and contact sections, lead-generation fields, cadastral identifiers, analytics data, and precise coordinates are not included in stored snapshots.
When a user uses Pro, the FINNlog account service handles their name, email address, Google profile-image URL, internal account ID, Google account link, Google and FINNlog OAuth token records, Stripe customer and subscription identifiers, subscription status and billing-period timestamps, server-derived entitlements, registered device label, P-256 public key and thumbprint, security challenges, IP address, browser user-agent metadata, timestamps, and rate-limit metadata. Device private keys never leave Chrome.
FINNlog does not receive Google passwords, FINN login information, FINN cookies, messages, payment card numbers or security codes, or precise device location.
The listing data is normalized into local snapshots so FINNlog can show what changed between checks. FINNlog checks supported listings when the user visits them. A user may also explicitly check a saved listing from the All items view; checking real estate still requires a current Pro licence. FINNlog does not schedule or monitor listings automatically in the background.
Personal comments are used only to help the user remember details about tracked items. Editing a comment does not create a listing revision.
FINNlog requests a supported listing’s public favorite counter from www.finn.no when it checks it.
If the structured data already present in a visited page is unavailable or invalid, FINNlog may also
request listing data from www.finn.no over HTTPS and interpret the Torget JSON or real-estate
.data response locally. Manual updates use the corresponding local request path for their
vertical. All real-estate data is normalized in the extension service worker and is never sent to
the account backend.
The latest normalized snapshot is updated after every successful capture. Revision-producing changes additionally create immutable historical snapshots; display-metadata changes update the current view without creating a revision. The latest and initial favorite counts are stored as item observations, so a favorite-count change also does not create a new listing revision.
Optional account, session, billing, entitlement, and public-device-key data is used only to authenticate the user, manage Pro access, protect the account, and issue device-bound licences.
Snapshots, revision history, personal comments, manual-check timestamps and result markers, and extension settings are stored in IndexedDB under the browser extension’s local origin. The developer has no access to this database.
An item, its comment, and all its revisions are automatically removed after 90 days without a successful visit or manual check. Users can also delete an individual item from FINNlog at any time. Uninstalling the extension removes its browser-managed local storage according to the browser’s normal behavior.
FINNlog access tokens, refresh tokens, and signed Pro licences are kept in Chrome’s session-only extension storage and restricted to trusted extension contexts. The non-exportable device private key is kept in extension-owned IndexedDB. Account, authentication, billing, entitlement, public device key, and security metadata is stored in the FINNlog backend’s PostgreSQL database.
Account and security metadata is retained while needed to provide and protect the account. Stripe may retain billing records according to its policies and applicable legal requirements. A user may request deletion of their FINNlog account data through the support contact below.
FINNlog operates an account and licence backend for Pro. It never receives FINN URLs, listing IDs, page HTML, embedded ad data, prices, descriptions, addresses, images, image URLs, snapshots, hashes, history, or comments. There is no listing cloud sync, analytics, or advertising, and listing history is not sold or shared.
Google handles the interactive sign-in and Stripe handles hosted Checkout and the Billing Portal. Those providers receive the account or billing information needed for their services under their own privacy terms. Stripe webhook state, rather than the browser redirect, controls Pro entitlement. Stripe, not FINNlog, receives payment-card details.
Listing thumbnails are loaded directly by the browser from the image URL provided by FINN. Requests to FINN and its image infrastructure are subject to FINN’s own privacy practices.
FINNlog uses handled data only to provide its disclosed user-facing purpose: local tracking, revision history, and personal comments for supported listings. It does not use data for advertising, profiling, credit decisions, lending, or unrelated purposes, and no human can access the locally stored data through FINNlog.
If FINNlog’s data practices change, this policy and the extension’s prominent disclosures will be updated before the changed behavior is introduced.
For privacy questions or support, open an issue.