PAGECRAFT STUDIO

Privacy policy

Updated 24 September 2026 · Extension version 0.7.0 AI Preview

PageCraft Studio lets you customize the text, appearance and behavior of webpages in your own browser. This policy describes the extension's built-in handling of information and the additional network activity that can result from resources or scripts you choose.

Your saved page edits and settings are stored locally in your Chrome profile. PageCraft Studio has no built-in publisher analytics, advertising, account service or backend that receives your page edits.

Information used locally

This information is used to provide the page customization, preview, persistence, editing, import and export features you request. Website content can contain personal information; avoid saving sensitive content unless you intend to keep it in your local rules or exported backups.

On-device AI page review and editing

When you open AI edit, PageCraft reads a limited snapshot of rendered text and computed styles from the current page's top level document. Each generation takes a fresh scan of at most 5,000 nodes and retains up to 80 eligible targets. Your request, text, element meaning, page region and viewport information help rank relevant targets. Fast mode passes at most 24 targets and 6,000 page-context characters to Chrome's built-in LanguageModel API; Thorough passes at most 60 targets and 12,000 characters. Model context excludes the snapshot's URL, selector and saved original-text fields; visible text can still contain URLs. The scan excludes form input values, form subtrees, editable regions, hidden content, iframe contents and shadow-tree contents. It does not capture a screenshot or visit other pages. Other visible page text may still contain personal information.

AI inference runs on your device. PageCraft does not send your prompt or page snapshot to a publisher server or external AI API, and it has no AI account service or API-key requirement. Chrome may download and manage its AI model during setup; that browser-managed download is separate from processing your page content. AI availability depends on your Chrome installation and device.

Your current request and model session are held in the editor. Page snapshots, proposed preview state and the latest AI-save undo record use temporary extension memory and browser session storage. A scan is no longer usable after its validity checks fail or it expires. Session data does not provide permanent history. Closing the AI editor discards its unsaved preview; closing the target tab or ending the browser session removes the associated undo record.

Where supported, PageCraft keeps a prepared model session containing only fixed instructions and clones it for each request. Page content, requests and responses are never added to that baseline. Each request session is destroyed after use or cancellation, and the baseline is destroyed when the editor closes. If cloning is unavailable, requests use fresh sessions. Earlier pages and responses are not reused as model conversation history. Generation may show a draft summary, but only a complete validated plan can be previewed or saved.

Only choosing Save for this page persists AI changes. Saved AI rules contain the exact-page URL pattern, local selectors, original and replacement text, supported CSS, batch metadata and a shortened part of your request as the rule name. They use the same local storage and import/export controls as other rules. The AI proposes plain text and bounded style values; it does not generate executable JavaScript or HTML. AI editing does not require Chrome's Allow User Scripts setting. Version 0.7.0 adds no new extension permissions or external AI service.

Remote files and scripts you choose

You can configure remote resource URLs or import rules from external sources. Fetching those resources contacts the selected servers, which can receive ordinary request information such as your IP address, requested URL and browser headers. PageCraft's direct remote file requests omit stored credentials; requests made by a webpage, a stylesheet, an embedded image or your own script follow their respective browser rules.

Custom JavaScript runs in the target webpage through Chrome's userScripts API and requires Allow User Scripts. Scripts you enter or import can read or change page content and make network requests according to their code and browser permissions. The practices of third-party scripts and resource hosts are controlled by their providers. Only enable rules and sources you understand and trust. A remote resource may change after you first add it.

The built-in extension does not send your saved text rules to a publisher service. It does not sell user data or use it for advertising, unrelated profiling or creditworthiness decisions. User data handled by PageCraft's built-in functionality is limited to providing the user-facing customization features described here, consistent with the Chrome Web Store User Data Policy and its Limited Use requirements.

Storage, retention and your controls

Saved rules and settings remain in your browser profile until you delete them, clear the extension's data or uninstall it. You can edit, disable, delete or export rules. Disabling a rule stops it from applying but does not delete its saved data. Use the extension's Options to manage or clear rules. Chrome's site access controls determine where the extension can run.

Exports are files you choose to save and are not automatically deleted when the extension is removed. They can include page URLs, original and replacement text, code and resource paths. Anyone you share an export with can read its contents. PageCraft does not provide cloud backup or synchronize these rules through its own service.

Security and permissions

Chrome isolates extension storage within your browser profile. PageCraft does not add its own encryption layer to saved rules or exported files. Protect access to your device, browser profile and backups. Host permissions allow page customization on the sites you use; navigation, scripting, storage, userScripts and offscreen permissions support the features described above. HTML rules accept only a restricted static-markup subset; executable behavior belongs in explicitly enabled JavaScript rules.

Contact and updates

For privacy questions, use the publisher contact email shown on PageCraft Studio's Chrome Web Store listing. If you contact the publisher directly, the information you choose to send is outside the extension's local storage. This policy describes the extension itself; any separately operated support or website service should disclose its own additional processing.

This policy may be updated when the extension's behavior changes. The revision date and applicable extension version are shown above.