Privacy Policy

Controller

Understand This Page is provided by Finnzon Oy, Business ID 2849466-3, c/o Jussi Hyvärinen, Ankkurinvarsi 17, 02320 Espoo, Finland.

Finnzon Oy is the data controller for the service data it receives, including anonymous install IDs, usage counters, plan status, Pro subscription entitlement metadata, customer email addresses used for billing, technical request metadata used for rate limiting and subscription security, and support requests.

Privacy contact: info@finnzon.com.

Overview

Understand This Page is a Chrome extension by Finnzon Oy that analyzes the current page after you explicitly ask it to.

The extension is designed without user accounts, extension analytics, browser history sync, background page reading, or automatic page uploads. The built-in AI service is operated by Finnzon and forwards user-requested analysis to OpenAI.

The marketing website at understandthispage.com uses Umami website analytics, described below. The extension package itself does not include analytics tracking.

Information processed

When you run an analysis, the extension may process the current page URL, title, canonical URL, metadata, headings, readable page text, page structure, tables, links, image metadata, code blocks, transcripts, and page-type-specific signals such as product, job, restaurant, news, documentation, research, GitHub, Google Maps, search, or email context. After that explicit action, page-type extraction may also read disclosure panels or menu tabs and accordions whose content is already present in the current document, including panels that are not currently expanded on screen.

When the current tab is an HTTPS PDF and you explicitly analyze it or add it to a comparison, the extension downloads that document from its current address and extracts readable text locally with a parser bundled into the extension. After you explicitly analyze a restaurant page, it may also read linked same-site HTML food menus, eligible same-origin PDF menus, and directly linked cross-site PDF menus when the file host permits ordinary browser CORS access. Cross-site menu PDFs are fetched without cookies and are limited to 8 MB. Same-site downloads may use cookies Chrome already has for that site, but the extension does not read, store, or send those cookies to Finnzon or OpenAI. Scanned or image-only pages are not OCR'd.

For Gmail pages, the extension can analyze visible message content, visible labels, links, attachment signals, sender information, recipients, timestamps, and collapsed-message signals that are present in the visible page context.

Local storage

Your answer language, privacy acknowledgment, cache preference, optional personal profile fields, saved billing email for subscription actions, local usage estimates, current answer and follow-up session state, and cached answers are stored in Chrome extension storage on your device.

The saved billing email is used to prefill subscription management and purchase restore actions. It is stored locally on your device and is sent to Finnzon only when you start checkout, restore a purchase, or open subscription management.

The extension also stores an anonymous per-install identifier locally. Finnzon uses it only to meter built-in service quotas and subscription entitlements.

Answer caching is local and optional. When the side panel is open, the extension may read the active tab locally to check whether a cached answer is available for that page. This cache lookup is used only on your device and does not send page content to Finnzon or OpenAI.

Email analysis is excluded from persistent answer caching.

When you analyze a product page or job listing, the extension also keeps a device-local analysis history entry (page title, address, verdict, and analysis time, up to 20 per kind) so recent analyses of the same kind can be compared. This history exists only on your device, is kept only while local answer caching is enabled, and you can remove individual entries or clear the whole history in the side panel.

When you explicitly add a supported page with the + button, the extension captures and keeps its title, address, visible page context, metadata, page type, and addition time in a separate comparison list for the browser session. Deterministic and previously classified page types require no AI request. When the page type is unclear, the + action sends a limited page excerpt through Finnzon to OpenAI only to classify the page before adding it; it does not run the full analysis. A list contains up to eight compatible pages, depending on page type, and is removed when the browser session ends.

For current-tab PDF support, the extension may retain up to four locally extracted documents in browser-session storage, capped at 1.5 MB of UTF-8 text per document. This lets follow-up questions retrieve relevant passages without downloading the PDF again. For a linked restaurant-menu PDF, only a bounded structured menu context is retained with the analysis; the PDF bytes and full extracted menu-PDF text are not persisted. Session PDF text and temporary comparison data disappear when the browser session ends.

AI processing

Page content is not sent for AI analysis automatically. When you click analyze and have acknowledged the privacy notice, only the prompt and captured context needed for the requested analysis are sent for AI processing. If you have filled in the optional profile fields, their content is included in the request to personalize the answer.

The request is sent to Understand This Page's service, operated by Finnzon, which forwards it to OpenAI with Finnzon's server-side API key. OpenAI receives the submitted prompt and captured page context for AI processing and may process that data outside the EU under its applicable data processing terms.

During an explicitly requested restaurant analysis, the extension first tries to structure linked menu content locally. If that deterministic grouping is incomplete, a bounded list of exact source-text tokens may be sent through Finnzon to OpenAI in a separate preprocessing request that returns token relationships only. Dish names, descriptions, section names, and prices shown in the full-menu view are reconstructed from the captured source tokens rather than accepted as model-authored text.

When you explicitly click Compare, the extension sends the selected locally captured page contexts through the same Finnzon service to OpenAI in one comparison request. The pages are not read again at that point. A follow-up question about the comparison sends those same bounded inputs, the comparison answer, and earlier follow-ups again; the tabs are not re-read. Clicking + transmits only a limited classification excerpt when local evidence and the classification cache cannot identify the page type; otherwise + makes no AI request. The older product and job history comparison instead sends the selected locally stored structured analyses, also only after you click compare.

For PDFs, the initial analysis sends a bounded best-effort extracted context rather than the PDF file. Restaurant analysis may similarly send bounded locally extracted dish, description, dietary-label, and price context from linked same-site HTML, same-origin PDF menus, or directly linked CORS-readable cross-site PDF menus. A follow-up may also send the retained structured restaurant context or question-relevant passages retrieved from a current-tab PDF extraction. Mixed PDFs are analyzed from their readable pages with a coverage notice; scanned or image-only PDFs are not supported in the current version.

Finnzon records quota counters, plan status, request kind, model, token counts, upstream status, and estimated cost data, but does not store captured page content, generated answers, follow-up conversations, raw AI request bodies, or browser history on its server.

For abuse prevention, Finnzon may use the request IP address transiently for short-term rate limiting and store a salted hash of the IP address for daily network quota enforcement. The AI request log does not store the raw IP address.

Payments and subscriptions

Paid Understand This Page plans are processed by Stripe. Stripe may process checkout, subscription, invoice, payment method, tax, billing, and customer portal information according to Stripe's terms and privacy policy.

Finnzon stores subscription entitlement metadata such as product, plan, status, Stripe customer or subscription identifiers, billing period, customer email, and anonymous install ID so the extension can receive the correct quota.

The extension may remember your billing email locally so Restore purchase and Manage subscription can be opened without typing the same email again. Card details and payment method details are entered on Stripe's hosted pages, not in the extension.

Moving a Pro purchase to another installation requires a six-digit code sent to the billing email. Finnzon stores only a keyed digest of the code with its installation binding and expiry, and removes expired or used restore challenges after a short retention period. The plaintext code and challenge identifier are not stored in Chrome local storage.

Finnzon may store subscription-related audit events, including request origin and IP address, to prevent abuse, troubleshoot subscription access, and protect billing flows.

Service providers

Finnzon uses infrastructure providers to run the website, license server, AI processing service, quota counters, database, and admin tools. These providers process service data only as needed to operate the service.

Stripe processes payment and subscription data. Stripe may also act as an independent controller for fraud prevention, legal compliance, and payment network obligations.

OpenAI processes the page context and prompts sent when you explicitly request an analysis.

Umami processes privacy-focused website analytics for understandthispage.com, such as page views, referrers, approximate location, device and browser information, and event metadata. Umami analytics is used to understand website traffic and does not run inside the Chrome extension.

Website analytics

The understandthispage.com website uses Umami analytics to measure aggregate website usage and improve the public website. This analytics is separate from the Chrome extension.

Finnzon does not use website analytics data to profile extension page content, target advertising, or decide what pages you analyze in the extension.

Retention

Local settings, cached answers, the local analysis history, and the anonymous install ID remain in Chrome storage until you remove them in the extension, remove the extension, or clear extension data. The separate comparison list and locally extracted PDF text are stored only for the browser session.

Finnzon retains quota, entitlement, request-log, technical audit, billing, website analytics, and support data for as long as needed to provide the service, prevent abuse, troubleshoot issues, meet accounting or legal obligations, maintain subscription records, and understand public website usage.

Captured page content and generated answers are not stored by Finnzon on its server.

What Finnzon does not collect

The extension does not create Finnzon user accounts, does not include extension analytics, does not sync browser history, and does not send page content for AI analysis before a user action.

Finnzon does not store captured page content, cached answers, generated answers, follow-up conversations, or a list of pages you visited on its server.

The extension does not perform mailbox actions. It does not send, draft, archive, label, delete, or otherwise modify your email.

The extension does not collect GPS location, keystrokes, mouse movement, clipboard contents, payment card numbers, bank account details, website passwords, login cookies, or third-party account credentials.

Chrome Web Store Limited Use

Finnzon's use of information received from Chrome extension permissions complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Data accessed through extension permissions is used only to provide and improve the extension's single purpose: analyzing the page you choose, showing the answer, supporting follow-up questions, managing local settings and caching, enforcing plan limits, and handling subscription status.

Finnzon does not sell user data, does not transfer user data to advertising platforms or data brokers, and does not use page content or browsing activity for personalized, retargeted, or interest-based advertising.

Humans at Finnzon do not read captured page content or generated answers unless you explicitly choose to share specific content with Finnzon for support, or where access is necessary for security, legal compliance, or aggregated internal operations allowed by the Chrome Web Store User Data Policy.

Chrome permissions

The extension uses Manifest V3 permissions for active-tab access, script injection after user action, clipboard writes, local storage, context menus, an offscreen document used for clipboard support and the bundled local PDF Worker, and the Chrome side panel.

PDF support adds no broad host permission. The PDF parser and its WebAssembly module are packaged inside the extension; no remote parser code is loaded.

Network access is used to send the analysis request to Understand This Page's service.

Your controls

You can avoid analyzing sensitive pages, disable local answer caching, remove individual entries or clear the persistent analysis history, edit or clear the browser-session comparison list, remove the extension, or clear Chrome extension storage to delete locally stored settings and cached data.

You may contact Finnzon to request access, correction, deletion, restriction, objection, or portability where applicable under data protection law.