Free alerts
Background alert settings.
A separate, explicit opt-in. Availability and checking health are shown below; an unconfigured preview stays inactive.
Checking this site’s alert availability…
Stored choices and checking health.
Checking health has not been confirmed.
Subscription enablement, complete source checks and notification delivery are separate. Neither an enabled subscription nor provider acceptance proves an operating-system notification was displayed.
These are this browser session’s stored choices. Drafts below do not update them until an explicit replacement is confirmed. Check status again to read the latest retained result; this page does not continuously poll.
What opting in stores and sends.
Background delivery needs a chosen HTTPS site, a configured enabled server and your explicit opt-in. It remains inactive in an unconfigured preview. An opt-in copies only your explicitly selected structured rules and filters to this site’s private storage. Opt-ins expire within 30 days; expiry does not promise immediate deletion. Normal cleanup after subscription expiry or removal keeps only a minimal batch-frequency and scheduling record until the original server session expires. If stored alert data is corrupt, its existing private records may remain until a confirmed Stop removes them, or cleanup runs after that original session expires. This does not extend that expiry. Enabling again does not reset the minimum gap. Confirmed server revocation or session expiry clears that frequency record. Minimal revocation records may remain until the server session expires. Saved-list names and free-text searches are not copied. Editing a local saved list does not update that copy.
The browser’s push platform receives a subscription endpoint and encrypted messages. This site stores the endpoint and encryption keys privately to deliver those messages. A secure browser-session cookie controls your subscription here; clearing cookies can lose server-management access. Use Stop before clearing site data, or revoke notification permission in browser settings. Subscriptions expire; delivery is not guaranteed.
Lock-screen notices use generic wording without products, prices, rules or location. They open this settings page only. Current sources must be checked separately; a notice is not a purchase, stock reservation or report verification.
Prepare draft rule copies.
These page drafts are separate from the stored choices above. Load local saved filter choices, then add each rule you want copied. Nothing is sent until you choose Enable or replace. Free-text searches cannot be used.
Delivery and optional area.
The minimum gap applies across all background rules. An admitted batch can contain up to 3 notifications. Pending batch members and bounded busy retries may be attempted later within their original expiry; retries do not renew that window. New quiet or throttled changes are skipped, not queued. Equal quiet start/end pauses delivery all day. Checks use this site’s retained source observations, not a continuous merchant feed. Provider acceptance does not prove an operating-system notification was displayed.
No device location is requested or copied. Only explicitly supported manual ZIP references can be retained; an unsupported or missing area does not become a broader search. Your area is never put in a notification, link or analytics event.
Stop and clean up.
Stop first asks the dedicated worker to durably disable app notices and close displayed notices. It then attempts server revocation and browser unsubscription separately. Offline failures stay unconfirmed and can be retried. Your local visit alerts, saved lists, favorites and targets are not changed.
Browser permission remains under your browser’s site settings. Browser-owned fallback notices or already displayed operating-system messages may have platform-specific behavior; this page cannot promise absolute operating-system silence.