Privacy Policy

1. Who this policy covers

This policy applies to the FixUI browser extension and to this website. FixUI is maintained by the FixUI developer as an individual, non-commercial project. In the language of data-protection law, we act as the controller only for the limited contact data you send us voluntarily (see section 8) — the extension itself does not transmit personal data to us at all, because it has nowhere to transmit it to.

2. The short version

• The extension has no server. There is no endpoint it talks to.
• There is no account, login, cloud sync, or user identifier.
• There is no analytics, telemetry, crash reporting, or advertising SDK.
• Your settings are stored in chrome.storage.local, on your device only.
• We cannot see your browsing history, your page contents, or your saved rules.

3. What the extension stores locally

Everything FixUI remembers lives in chrome.storage.local, scoped to your browser profile on the device you are using. It is not synced to any Google or Microsoft account, and it is not shared between browser profiles or devices.

Site settings

The origin (for example https://example.com), whether FixUI is enabled or paused there, your favorites-panel preference, and — only if you configure one — a preferred landing page for that site.

Rules

Each rule records the scope it applies to (a page or a set of pages), the rule type (hide, appearance, link favorite, or element favorite), the action configuration, and — for hide, appearance, and element-favorite rules — a bounded element fingerprint.

Element fingerprints

A fingerprint exists for one purpose: to relocate the same element on a later visit. It captures only the following, all bounded in size:

• The element’s tag name.
• A stable id, if present and if it does not look auto-generated.
• Up to five attribute name/value pairs drawn from a small fixed allow-list: data-testid, data-test, data-qa, name, role, and aria-label.
• The element’s resolved ARIA role.
• An accessible-label snippet of at most 40 characters.
• A normalized link destination — origin and path only. Query strings and fragments are dropped.
• A visible-text snippet of at most 40 characters.
• Up to four ancestor tag names, a weak sibling-index number, and up to five CSS selector strings.

Link favorites

When you explicitly save a link as a favorite, FixUI stores that link’s full destination URL and its visible text. This is a URL you deliberately asked to pin, not incidentally captured browsing data. Before saving, FixUI rejects anything that is not http: or https:, rejects URLs containing embedded credentials (user:pass@host), and warns you if the query string or fragment looks like it contains a token, session id, or similar credential-shaped value so you can decide whether it is safe to pin.

4. What is never captured, under any circumstance

• The contents of inputs, textareas, or contenteditable elements — passwords, form fields, notes, and drafts. These elements are explicitly excluded from the text-cue logic.
• Full DOM snapshots or full page text. Only the bounded per-element cues listed above.
• URL query strings or fragments in fingerprint link destinations.
• Data from cross-origin iframes, which are out of scope, or from closed Shadow DOM, which is inaccessible to any extension.
• Your browsing history, cookies, or network requests — the extension requests no permission that would expose them.

5. Permissions, and why each one exists

• storage — to save your settings and rules locally.
• scripting — to inject the content script into a page after you have enabled that origin.
• activeTab — a defensive fallback granting brief, gesture-scoped access to the tab you were viewing when you interacted with the popup. It is not the mechanism used for persistent per-site access.
• optional_host_permissions (http://*/*, https://*/*) — declared broadly so that any ordinary website can be enabled, but your browser only ever grants the specific origin you click “Enable for this site” on. FixUI never requests or receives blanket access to all sites.

No history, webRequest, cookies, or tabs permission is requested.

6. Chrome Web Store limited-use disclosure

FixUI’s use of information received from browser APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Concretely: FixUI does not transfer, sell, or share user data with any third party; does not use user data for advertising, creditworthiness, or lending purposes; and does not allow humans to read user data. It cannot do any of these things, because no user data is ever transmitted off your device.

7. This website

This website is a static marketing and documentation site. It sets no advertising or tracking cookies and runs no analytics or fingerprinting scripts. See our Cookie Policy for details. If you follow the Buy Me a Coffee link, you leave this site and are subject to Buy Me a Coffee’s own privacy policy, over which we have no control.

8. Contacting us, and bug reports

If you email karankartikeya2023@gmail.com, we necessarily receive your email address and whatever you write. That correspondence is retained only as long as needed to deal with your query, and is never used for marketing or shared with anyone.

The Report a bug link in the extension opens your own mail client with a prefilled template. The extension transmits nothing itself — you see and control exactly what is sent, and can edit or delete any of it first. The template prefills only the extension version and your browser’s user-agent string. It deliberately does not prefill the URL of the page you were on; it asks which site you were on as an optional question you may leave blank.

9. Your rights, and how to exercise them yourself

Because your data never leaves your device, you do not need to make a request to us to access, correct, export, or erase it — you already have direct control:

• Open Rules & favorites from the popup to view every stored rule for a site, with a Remove action on each.
• Reset in the popup deletes all rules and favorites for a site at once.
• Revoke site access removes the browser permission that lets FixUI run there.
• Uninstalling the extension removes its local storage entirely.
• You can inspect the raw data at any time via chrome://extensions → FixUI → “Inspect views” → Application → Storage.

10. Children

FixUI is not directed at children under 13 and collects no data from anyone, including children.

11. Changes to this policy

If this policy changes materially, the “last updated” date above will change and the revision will be reflected in the extension’s public repository history. Because we hold no contact details for users, we cannot notify you individually — please check this page after a major version update.