LocaleStress
Privacy Policy

Effective date: 12 October 2026. Version: 0.3.0.

Publisher contact: ihorkharchyshyn@gmail.com.

LocaleStress is a local Chrome extension for synthetic text expansion and layout review. It has no backend, analytics, telemetry, advertising, account system, AI API, or external fonts. It does not transmit inspected page data to a service.

After you invoke the extension on an HTTP(S) page, it inspects visible text and layout measurements in that document's top-frame light DOM. It temporarily writes synthetic text into eligible text nodes. It does not read cookies, site storage, form values, or arbitrary page attributes. It excludes editable areas, form controls, code, and unsupported content.

Original text and references used for restoration remain only in the runtime memory of the inspected document. Application edits take precedence over extension edits. Navigation or reload destroys that runtime. Restore and Cancel release the mutation journal and observers.

chrome.storage.local stores expansion and test preferences, including user-entered CSS exclusions scoped by website origin and whether the on-page Restore control is enabled. Raw exclusion selectors may contain private IDs you enter; those preferences are local and are not inserted into reports or exports. chrome.storage.session stores bounded, latest-per-tab reports, explicit manual review labels, and the session metadata needed to route extension commands. Default reports contain page origin, structural selectors, geometric measurements, viewport information, classification, and coverage. They do not include page title, pathname, query, fragment, raw text, DOM dumps, or screenshots. Session reports do not persist across a browser restart, extension reload, or extension update.

Optional saved history is disabled initially. After you enable it, Save run explicitly saves a sanitized geometry report and its manual review labels to chrome.storage.local. History keeps at most 20 reports within a 3 MB budget; the oldest saved entries can be removed to stay within that limit. Saving the same run updates that saved copy. Saved history contains no text snippets, screenshots, page paths, query strings, fragments, semantic selectors, or raw exclusion selectors. History persists until you delete saved entries, clear saved runs, or uninstall the extension. Turning off saving keeps existing entries available for viewing and deletion. No background autosave or cloud synchronization is used.

Local storage also keeps a review-request counter capped at three completed, current tests with expanded text, up to three opaque random run IDs to avoid counting a completion twice, dismissal count, the date when a dismissed request may return, and whether the request has ended. Findings and manual review labels do not affect this counter. The first dismissal waits 14 days; the second dismissal or choosing Write a review ends the request. Choosing Write a review opens this extension's Chrome Web Store review page, whose data handling is governed by Google. Inspected page data is not included in that URL. A separate boolean marker records that the packaged welcome page opened on first installation; updates do not open it. These preferences remain local until the extension is uninstalled.

Reports can include opaque random document, route-state, exclusion-configuration, and element identity tokens. These support conservative comparisons without storing the pathname or content in an identity key. They are not hashes of private page text or URLs. Comparisons refuse incompatible or unreliable runs and never infer a fixed issue from a replaced or uninspected element.

Use Clear report to restore the active run and remove its session-cached report. Explicitly saved copies are managed separately under Saved runs. Uninstalling the extension removes extension storage. Downloaded exports and copied text remain wherever you chose to save or paste them; clearing extension reports does not delete those copies.

Screenshots require an explicit Capture visible area action. Only one current stressed viewport is captured. The extension validates the tested tab, document, run, and viewport before and after capture and discards mismatches. Screenshots remain in the report page's memory until it closes or you export them; they are not placed in session storage.

Export previews offer separate unchecked options for page path, text snippets, captured screenshot, and semantic selectors. Those data are obtained or included only when you explicitly select the option or request an individual snippet/selector. Snippets are bounded and remain in report-page memory. Query strings and fragments are removed even when the path is included. A path, snippet, ID, test identifier, or screenshot can still contain personal or confidential information. LocaleStress does not automatically anonymize these data.

HTML and JSON exports are local files created through a Blob download. HTML exports are static, contain no JavaScript or external resources, and use an embedded Content Security Policy. Copy issue as Markdown writes to the local clipboard only after your action. You decide whether and where to share these files or clipboard contents.

• activeTab: temporary access to the current website after invoking LocaleStress; optional screenshot capture.

• scripting: on-demand injection of the isolated runtime into the top frame.

• storage: local preferences, review-request and welcome markers, optional saved history, and session reports.

There are no broad host permissions, permanent content scripts, external messaging, or permissions for cookies, browsing history, downloads, debugger, tabs, or tab capture.

This policy describes LocaleStress version 0.3.0. Questions about the extension or its local data handling can be sent to ihorkharchyshyn@gmail.com. The publisher must make this policy publicly accessible for the Chrome Web Store listing. Preparing this document or an extension package does not mean a Store submission has occurred.