Fold the page, not your privacy.
Page Fold temporarily compresses selected blocks in the current webpage. This policy explains the local DOM inspection required for that interaction and the data the extension deliberately does not keep.
Purpose of this policy
This policy explains how Page Fold 1.0.0 handles information when you use the extension. Page Fold has a narrow function: it lets you temporarily fold selected sections of the webpage in the current tab into compact, reversible placeholders. The extension is designed so this interaction can happen inside the page without a publisher-operated server, user account, analytics service, or persistent browsing database.
The descriptions below refer to the production extension distributed as Page Fold. They cover the extension code, the injected interface used for Fold Mode, and the temporary DOM changes created during a fold. They do not describe the independent privacy practices of the websites you visit, your browser vendor, your operating system, or the Chrome Web Store.
Quick data summary
Page Fold does not transmit page content to us or to a third-party service. It does not use a backend API. It does not create advertising identifiers, analytics identifiers, user profiles, or cross-site tracking records. It does not request the Chrome storage permission and it does not intentionally keep a record of folded pages after the current page session ends.
When Fold Mode is active, local code in the current tab necessarily reads limited DOM information so it can determine what block is under the pointer and how large that block is. This processing occurs in the browser. A short text-derived label may be displayed inside a folded placeholder so you can recognize what you folded, but that label remains part of the current page DOM and is not sent elsewhere.
When Page Fold can access a webpage
Page Fold uses Chrome's activeTab model. The extension does not ask for blanket permission to read every website you visit. Access to ordinary webpage content is requested for the active tab when you explicitly invoke the extension through its toolbar action or configured keyboard shortcut.
The production background script also checks that the current address begins with HTTP or HTTPS before it attempts to inject Page Fold. Browser-internal pages such as chrome:// settings, extension-management pages, and other restricted surfaces are therefore outside the normal operating scope. Chrome may impose additional restrictions on protected pages regardless of this check.
Information examined during block selection
To draw the selection outline, Page Fold examines the DOM element beneath the pointer and a limited chain of its ancestors. The code checks element type, computed display, visibility, positioning, and bounding rectangle. Those values are used only to decide whether an element is a useful fold target and to position the on-screen outline.
The extension does not build a full semantic copy of the document. It does not send DOM trees, screenshots, form values, cookies, authentication tokens, or browsing history to a server. Candidate information exists transiently in JavaScript memory for the current page while Fold Mode is active.
Text used in a folded placeholder
When you click a selected block, Page Fold creates a small placeholder before the original element. To make the placeholder recognizable, the extension may derive a short label from an aria-label, a heading contained in the block, the block's visible text, or the element tag name. The label is normalized and truncated to a short length before display.
This label is not written to extension storage and is not transmitted over the network. It exists only in the page DOM for as long as that fold remains on the current loaded document. Reloading the page, navigating away, closing the tab, or unfolding the block removes the extension-created placeholder as part of normal document lifecycle or explicit restoration.
How a fold changes the page
Page Fold inserts a compact placeholder adjacent to the selected element and marks the selected element with an extension-specific data attribute. Packaged extension CSS uses that attribute to hide the selected element while the placeholder is present. The original element itself remains in the page DOM; Page Fold does not replace its content with a remote copy and does not permanently delete the source node.
When you unfold the section, the placeholder is removed and the extension-specific fold attribute is restored to its prior state. Page Fold intentionally avoids replacing the element's entire inline style attribute. This means ordinary inline style changes that the website itself makes while a section is folded are not intentionally discarded by the extension when the section is restored.
Session-only state
Folded-element references, the current selection depth, pointer coordinates, and Fold Mode status are maintained only in JavaScript memory associated with the loaded page. Page Fold does not request the storage permission and does not implement synchronization of fold states between tabs, browser restarts, or devices.
Because the state is session-only, refreshing or navigating the page resets the extension's in-page state as the document is replaced. This behavior is intentional. Page Fold is a temporary reading tool rather than a persistent page-customization database.
Network behavior
Page Fold has no product server and contains no code that uses fetch, XMLHttpRequest, WebSocket, EventSource, remote script loading, or an analytics SDK. The packaged extension does not need the network to perform folding. Its JavaScript and CSS are included inside the extension package.
The webpage itself may continue to make its own network requests while Page Fold is active. Folding a block does not place the webpage into an offline mode and does not control requests initiated by the site. Those site requests are governed by the site and browser, not by Page Fold.
Analytics, advertising, and tracking
Page Fold does not include analytics, crash-reporting services, advertising libraries, fingerprinting code, affiliate tracking, telemetry beacons, or behavioral profiling. We do not use the extension to measure what pages you fold, how often you fold them, which domains you visit, or what text appears inside selected sections.
Because there is no extension-operated analytics channel, there is no Page Fold analytics opt-out switch to configure. The absence of analytics also means we do not receive aggregate usage dashboards from the extension itself.
Cookies and website storage
Page Fold does not read or write cookies through Chrome extension APIs. It does not request cookie permission. It also does not deliberately read localStorage, sessionStorage, IndexedDB, Cache Storage, or other website storage as part of its folding function.
Websites can continue to use their own cookies and storage while the extension is active. Page Fold does not claim to block, modify, or isolate those mechanisms. If a website reacts to its own DOM changes or user interactions, that behavior remains under the website's control.
Forms, passwords, and sensitive fields
Page Fold does not have a feature for extracting form submissions, passwords, payment details, or authentication credentials. Its block-selection code is based on structure and geometry rather than a credential-collection workflow. The extension does not send form field values to a remote service.
You should still use judgment when folding areas of sensitive pages. Hiding a section is a visual and layout action, not a security feature. Folded content remains part of the document and may still be accessible to the webpage's own scripts, assistive technology depending on browser behavior, or anyone who can unfold the block in the same page session.
Permissions: activeTab
The activeTab permission is used so Page Fold can operate on the specific tab you deliberately activate the extension on, without requesting standing host access to all websites. Chrome grants this access temporarily in response to the user action permitted by the browser.
Page Fold uses that temporary access to inject its packaged interface and interact with the current document. It is not used to maintain a background record of every tab you open. The extension does not request the broader tabs permission.
Permissions: scripting
The scripting permission allows the extension background worker to insert the packaged fold.css stylesheet and fold.js script into the active tab after user activation. Those local files implement selection, depth controls, placeholder creation, folding, unfolding, and the small in-page Fold Mode interface.
Page Fold does not use scripting permission to download or execute remote JavaScript. All executable extension code is part of the installed package. The extension does not attempt to bypass the page-access rules enforced by Chrome.
No storage permission
The production manifest does not request Chrome's storage permission. Page Fold therefore does not maintain a Chrome extension storage database of URLs, folded elements, text labels, preferences, or usage events. The session state described in this policy lives only in the current document's injected runtime.
The browser and operating system may independently keep ordinary artifacts such as extension installation information, browser history, caches, or crash data under their own policies. Those systems are not a Page Fold data store and are not controlled by this extension.
User controls and deletion
You can unfold any folded block by clicking its placeholder. You can leave Fold Mode with Escape while keeping existing folds available for manual unfolding. Reloading the page, navigating away, or closing the tab discards the in-page runtime and removes the temporary state along with the document.
Because Page Fold does not upload or persist a user profile, there is no remote Page Fold account to delete and no cloud deletion request is required for fold history. Uninstalling the extension removes the installed extension code from the browser according to Chrome's normal extension-management behavior.
Interaction with website code
Page Fold changes the DOM by adding its own interface nodes and placeholders and by adding a temporary data attribute to folded elements. Some websites observe DOM mutations or rely on precise layout measurements. On such sites, the website may notice or react to these temporary changes.
The extension cannot guarantee compatibility with every dynamic webpage. If folding causes a site-specific layout or interaction problem, you can unfold the affected block, reload the page, or stop using Fold Mode on that page. Reloading returns the page to the site-provided document state.
Security design
The extension follows a minimal-permission design: activeTab and scripting are the only requested permissions. It does not request broad host permissions, history, cookies, webRequest, downloads, clipboard, identity, notifications, or native messaging. A smaller permission surface reduces the amount of browser data the extension can access by default.
No remote code is used. The extension package contains the executable JavaScript and CSS needed for its function. Security also depends on Chrome, the operating system, and the websites you visit, so this policy should not be read as a guarantee that unrelated webpage content is secure.
Third parties and data sharing
Page Fold does not integrate third-party analytics, advertising, cloud storage, AI, payment, or social-sharing providers. Because the extension does not transmit operational page data to a Page Fold server, we do not sell, rent, or disclose such extension-collected page data to advertisers or data brokers.
If you follow links or interact with third-party content on a webpage while using Page Fold, that interaction is between you, the browser, and the relevant website or service. Page Fold does not change the privacy policy that applies to the destination service.
Children
Page Fold is a general browser utility and is not designed as a service directed specifically to children. It does not ask users for a name, age, email address, profile, or other account information. The extension does not include targeted advertising or social features.
Parents or guardians who manage a child's browser should evaluate the websites the child visits separately. Page Fold does not provide parental filtering, content moderation, or supervision functions.
Managed and enterprise browsers
An administrator may configure Chrome policies that prevent extension installation, restrict webpage access, or disable certain extension capabilities. Page Fold respects the browser's enforcement of those policies. It does not attempt to override an administrator's restrictions.
Organizations using Page Fold should review the extension permissions and this policy in the context of their own internal data-handling requirements. Page Fold itself does not provide an organization-facing telemetry console or centralized activity log.
Policy changes
If a future version materially changes how Page Fold handles information—for example, by introducing persistent storage, optional synchronization, or a network service—this policy will be updated to describe that behavior before or with the relevant release. Permission changes would also be reflected in the extension manifest and Chrome's permission model.
Changes that only clarify language without changing product behavior may be published without altering the extension version. The effective date at the top of this document identifies the revision represented here.
Contact
Questions about this privacy policy or Page Fold's data-handling behavior can be sent through the publisher support contact shown on the extension's Chrome Web Store listing. Using the store-listed support channel avoids placing an invented or unrelated personal address inside the extension package.
When contacting support, avoid sending passwords, authentication tokens, payment data, or confidential webpage content. A description of the behavior, browser version, extension version, and non-sensitive reproduction steps is normally sufficient for troubleshooting.