Privacy Policy — Save This Search 1.0.2

Publisher: arsalndev7. Effective date: September 27, 2026. Support email: arslandev7@gmail.com.

Purpose and local storage

Save This Search lets you save a website search page and supported search/filter settings, organize saved searches, and restore them later.

When you choose Save, it stores the admitted HTTPS URL, supported filters you interacted with, and bounded control identifiers/labels needed to find those filters again. Records also contain an internal ID, the time the search state was last saved, pin state, and an optional custom or preserved historical name. New saves display the hostname without storing a default name. Domain, page title, creation/restore timestamps, scroll position, and favicon URLs are not stored. Your appearance, favicon, and default restore-target preferences are stored in the same local extension storage.

This data is stored in your Chrome profile using chrome.storage.local. The extension has no developer backend, account system, analytics, telemetry, advertising, or cloud-sync feature. It does not upload your saved-search database to the developer.

Before Save and the search-only boundary

A content script runs in the top-level document of HTTPS pages only. Incognito operation is disabled. It observes trusted input/change events and the clicks or operational keys needed by supported filters. It keeps bounded control identities in first-touch insertion order and a transient search URL with monotonic timing needed to associate delayed filter URL changes. It stores no keys, click history, pointer coordinates, per-control timestamps, interaction counts, or scroll positions. It does not retain typed field values in the interaction registry. This state is reset on relevant navigation and disappears with the document. A page title may be examined transiently to reject sensitive page context; it is not saved or used to name new records.

Capture requires recognizable search/filter semantics. Sensitive metadata and surrounding login, profile, contact, payment, medical, messaging, and other unrelated form context override positive search signals. Unknown controls are skipped. Textareas and contenteditable editors are excluded entirely. URL checks reject credentials, known sensitive parameters, unsafe schemes, and malformed inputs. Additional value checks reject recognizable contact details, payment-card numbers, tokens, private keys, and credential assignments.

These checks are conservative heuristics, not a guarantee that all personal information can be recognized. A permitted search query, URL, option label, or saved-search name can still contain personal content. For example, you can search for a person's name, enter your health circumstances or financial/payment details as search text, search for a quoted message, or save a location filter. An unrecognized password or other secret entered as ordinary search text or a custom name can also pass these checks. Do not use this extension to preserve secrets or private records.

Types of information handled

The extension handles web history in the form of the current page URL and searches you choose to save; user activity needed to identify changed filters; and website content such as supported values and bounded matching text. It does not read Chrome's general history database, retain a keystroke/click log, or save whole webpages. Geographic search criteria such as cities, regions, destinations and radius filters are location information. They may describe a desired search area rather than your current position; the extension does not use device geolocation.

Because admitted text is not universally redacted, the saved content can also include personally identifiable information, health information, financial and payment information, authentication information or personal communications when you include such content in a search or name. The extension does not offer separate profile, medical-record, payment-record, credential or inbox collection features. These types describe possible content within the searches you choose to preserve. A custom name is used in the popup and is not itself applied to a website; saved URLs and filter values are made visible to the selected website during restoration.

Restore and websites

Restore navigates a tab to your saved URL and applies admitted filter values to the selected destination website. The destination receives the navigation URL, and its page scripts can read restored values and react to dispatched input/change or widget events. This can cause website requests and normal website processing. The destination's privacy practices apply to its handling of this information.

Local storage does not mean restored information never leaves the device. The extension admits HTTPS destinations only and never converts HTTP URLs to HTTPS. Live form targets are checked, including external form ownership, relative actions, base URLs, and submitter overrides. Replay rejects native submit, default-submit, image-submit, reset and link activation. Synthetic widget clicks are canceled before dispatch so a handler changing the element during that event cannot enable its native default action.

Safety is checked before focus, mutation and website-visible events, after synchronous handlers, and during bounded restoration retries. This is not a network firewall: website JavaScript can explicitly submit forms, navigate or make its own requests in response to events. Servers can also redirect a navigation before a content script runs. The extension cannot guarantee the destination site's subsequent transport or processing.

Restore revalidates stored data, the destination origin/path, matched control type, and live search/filter context. It skips unsafe, ambiguous, unsupported, or missing controls. Compatibility varies by website, especially for custom widgets, frames, and Shadow DOM.

Favicons

When enabled, the popup asks Chrome's internal favicon endpoint for the icon associated with a saved site's origin. The extension does not fetch website-supplied icon URLs or use an external icon service. Chrome controls its cache and normal browser favicon behavior. You can disable icons in Settings.

Temporary restore state

chrome.storage.session holds tab-scoped operation identifiers, saved-search identifiers, a navigation URL and timing information for pending restores, and result counts/reason categories. It does not need captured filter values or website-provided result labels.

Pending operations are accepted for up to 60 seconds and results for up to five minutes. These are validity deadlines, not scheduled deletion timers. Pending operations are consumed at handoff; expired/malformed records are removed on relevant reads or worker initialization, and tab closure removes that tab's entries. Chrome clears session storage on browser restart and extension reload/update/disable. Entries may remain in memory after their validity deadline until cleanup occurs.

Retention, deletion, and upgrades

Saved searches remain until you delete them, clear all saved searches in Settings, remove extension data, or uninstall the extension. Clearing searches preserves preferences. In-flight restore data can remain until the temporary cleanup described above; deleting a search does not undo a website navigation or values already applied to that website.

The 1.0.2 schema-v4 migration keeps valid HTTPS URLs, record identities, valid existing names, pins, last-saved timestamps, preferences, and supported schema-v3 controls. HTTP records are removed, never rewritten. Retired metadata is removed. Older schema-v1/v2 controls still cannot establish their original search context and are discarded; revisit and resave those searches to capture filters. Schema-v1 had no preferences and receives defaults. Unsafe/malformed records are purged when storage is loaded. The repaired root is written atomically through a serialized queue; a failed read or write does not authorize replacing valid data. Data written by an unknown future schema is left untouched in read-only mode. Incompatible pending restore operations/results are discarded.

The extension adds no application-level encryption to chrome.storage.local and does not provide a password vault. Chrome profile/operating-system protection is outside the extension's control.

Use and sharing

The extension uses handled data only to save, organize, and restore website searches and supported filters. The developer does not receive saved searches, sell them, use them for advertising, or use them to determine creditworthiness or lending eligibility. User-requested navigation and restoring filters to a destination website are part of the stated purpose.

Under the Chrome Web Store Limited Use requirements, information received from Chrome APIs is used only for the disclosed search-saving functionality. It is not sold, used for unrelated purposes, used for personalized advertising, or used for creditworthiness or lending decisions. The developer does not receive the saved-search database for human review. The destination website receives the URL and restored values as described above. This is a description of data use, not a claim of Chrome approval.

Contact

For questions about this extension's privacy practices, contact arsalndev7 at arslandev7@gmail.com.