# Clayform privacy policy **Effective date: 12 August 2026** Clayform is a local-first Chrome extension for visually customising websites. This policy explains the information Clayform processes and the choices available to you. ## Summary Clayform does not have an account system, advertising, analytics, telemetry, or a cloud backend. It does not automatically transmit personal information, browsing activity, website content, customisations, or diagnostics to Clayform's developer or to third parties. ## Information processed on your device Clayform processes the following information only to provide its user-facing customisation features: - The origins and URL scopes of websites on which you explicitly enable Clayform. - Target metadata needed to find customised page elements again, such as element types, selected attributes, class tokens, structural fingerprints, and hashed accessible names. - The visual changes you create, including style values, sizes, visibility choices, ordering, responsive breakpoints, titles, timestamps, and revision history. - Local resolution diagnostics indicating whether a saved target was found, ambiguous, conflicting, or unsupported. - Draft customisations held for the current browser session. Clayform does not intentionally store page text, form contents, passwords, authentication data, payment information, screenshots, cookies, or complete copies of webpages. ## Chrome permissions Clayform uses: - `activeTab` to identify the current page after you invoke Clayform. - `scripting` to run Clayform's packaged editor and customisation engine on a site you have enabled. - `storage` to save customisations and local diagnostics on your device. - Optional HTTP(S) host access, requested one origin at a time, so saved customisations can be reapplied on sites you choose. Clayform does not request browser-history, tabs, cookies, web-request, download, clipboard, file-URL, incognito, or unlimited-storage permissions. ## Storage and retention Published customisations, target metadata, and diagnostics are stored in `chrome.storage.local`. Drafts use `chrome.storage.session`. Data remains until you delete or reset it in Clayform, clear the extension's data, or uninstall the extension. Chrome controls the underlying extension storage. ## Sharing and transfers Clayform does not automatically share or transfer data. Export and support-bundle features create files locally only when you request them. You control whether those files are subsequently shared, and Clayform asks you to review a support bundle before sending it to anyone. Clayform does not sell data, use data for advertising or credit decisions, or allow the developer or other people to read your data. ## Your choices You can: - Grant or revoke access for each website using Chrome's extension controls. - Disable Clayform for a tab. - Delete individual customisations or reset all customisations for an origin. - Export your customisations and local diagnostics for inspection. - Remove all locally stored Clayform data by uninstalling the extension or clearing its extension storage. ## Security Clayform ships packaged code only. It does not download or evaluate remote code. Imports are validated and size-limited, messages are schema-validated, and page-derived labels are rendered as text. Clayform restricts styling operations to an allowlist and does not accept arbitrary JavaScript or raw CSS. ## Limited Use Clayform's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide or improve Clayform's single purpose: letting users create and reapply local visual customisations on websites they choose. ## Changes If Clayform's data practices change, this policy and the Chrome Web Store privacy disclosures will be updated before the new practices are introduced. Material changes will also be disclosed in the extension where required. ## Contact For privacy questions, use the developer support contact displayed on Clayform's Chrome Web Store listing.