Privacy Policy

Effective Date: June 18, 2026

At NotifyOnChange.com, we take privacy seriously — both yours and the internet's. Our infrastructure is engineered to monitor public architectural shifts on the web without participating in the corporate surveillance economy. This document outlines exactly what telemetry we log, how your workspace data is isolated, and what we deliberately refuse to know about you.

1. What We Track (and What We Don't)

We monitor public e-commerce configurations and structural modifications, not human behavior. When you initialize our browser extension or deploy server-side tracking nodes, we record metadata exclusively from the target storefront domains you configure.

• We do not: Monitor your personal browsing history, inject tracking scripts, or inspect unrelated browser viewports.
• We do not: Package, monetize, or lease your target monitoring lists to third-party data brokers or competitive analytical systems.
• We do: Securely retain configured storefront domain vectors and active webhook coordinates.
• We do: Log structural differences, asset mutations (theme swaps, script injections), and minor DOM snapshots required for diff visualizations.

2. Infrastructure Data Collection

The depth of logged data depends entirely on your workspace allocation model:

Local Telemetry Node (Free Extension Platform):

• Target domain arrays configured for local tracking (stored natively inside your local runtime).
• Basic platform metadata (extension build version, core browser engine type).
• Optional email authentication records (strictly if you initialize console synchronization).

Premium Matrix Architectures:

• Target domain configurations synchronized across our automated server checking nodes.
• Historical changelogs and tech-mutation text entries.
• Workspace parameters including account designations, email routing targets, and active secure webhooks (Slack/Discord payloads).
• Minimal transactional keys required to maintain authorization and synchronization with our billing infrastructure.

3. Application of Telemetry Data

Collected configuration details are applied strictly to:

• Coordinate, process, and accurately distribute structural alerts.
• Optimizing network response speeds and reducing proxy latency overhead during storefront observation tasks.
• Resolving server runtime exceptions and technical support inquiries submitted via your console dashboard.

4. Zero Data Brokerage Policy

We do not run advertising networks, deploy tracking pixels, or distribute user lists. We are completely in the business of auditing technical footprints on public storefronts—not logging the workflows of the engineers running the searches.

5. Cookies & Session Storage

We apply minimal, non-intrusive local authentication structures exclusively to:

• Maintain active workspace console sessions securely.
• Retain interface configuration flags (such as console styling rules or sorting parameters).
• We deploy zero tracking scripts that follow you across the public web.

6. Isolation, Retention & Deletion

Your agency data remains entirely under your jurisdiction. You can request a complete system scrub directly from your workspace dashboard at any time.

• Upon data erasure execution, all configured storefront arrays, alert histories, and authorization profiles are fully dropped from active processing databases within 7 business days.
• Encrypted system backup nodes automatically cycle out and purge residual transactional fragments within a strict 30-day window.

7. Secure Payments & Transaction Verification

All premium subscription billing transactions are processed through highly secure, encrypted transactional gateways. In strict adherence to our system design guidelines, we store zero raw payment card data within our main database infrastructure. We maintain only secure verification reference tokens and encrypted license attributes required to authorize your node limits.

8. Architectural Security Architecture

We enforce TLS/HTTPS encryption across all transmission vectors, encrypt critical console database schemas at rest, and strictly isolate system processes. Access to target lookup logs is structurally constrained to automated node processes and accessed by developers only under audited conditions for platform troubleshooting.

9. Regulatory Compliance Matrix

NotifyOnChange operates globally across decentralized node components. We construct our data isolation boundaries to maintain thorough alignment with international privacy principles, including GDPR and CCPA. If any baseline update to this privacy design occurs, it will be communicated explicitly inside your main console environment.

Contact Us:
For strict privacy audits, operational telemetry questions, or targeted data inquiries, route requests directly to: help@notifyonchange.com with the subject line Privacy Inquiry - Human Request.