Effective September 4, 2026 · Last updated September 4, 2026

Privacy policy

PulseNotice watches public web pages you ask us to watch, for a goal you write in plain language. We do not sell personal data. This policy explains what we collect, why, and how you can ask us to change or delete it.

1. Who we are

PulseNotice operates the website at pulsenotice.com, the signed-in dashboard, the API, and the Chrome extension that captures a page URL, title, and selected text. We are based in Austin, Texas, United States.

Privacy questions and data requests: use the contact form or email alerts@pulsenotice.com.

2. What this policy covers

This policy applies to:

The marketing site, including the free checker and contact form
Accounts, monitors, alerts, billing, and settings in the dashboard
The Chrome extension when it talks to PulseNotice
Emails we send about your account or a satisfied monitor

It does not apply to the third-party websites you choose to monitor. Those sites have their own policies. We fetch only the public URL you give us; we do not log into those sites on your behalf.

3. Information we collect

Account

Email address and a hashed password (we do not store the password in plaintext). You may change your password while signed in. Forgot-password mail, when enabled, is sent to the address on the account.

Monitors you create

URL, page title, optional selected text, the goal in plain language, capture metadata from the extension (for example the tab URL at save time), monitor status (active or paused), and compiled rules derived from the goal.

Checks, evidence, and alerts

Each check may store fetch mode (HTTP or Playwright), HTTP status, content fingerprints, extracted facts (such as a price or keyword hit), a bounded evidence excerpt, whether the goal newly became true, and a relevance score when the semantic filter runs. We prefer excerpts over full page bodies. Alert records include channel (email and, on Pro+ / Team, a notify webhook), delivery status, and optional provider message ids.

Feedback

If you mark an alert useful or not useful, we store that rating and any optional comment so we can see when a rule is noisy.

Billing

Plan name (Free, Pro, Pro+, Team), subscription status, and Stripe customer and subscription identifiers. Card numbers are handled by Stripe, not stored on PulseNotice servers. See Stripe’s privacy policy for how they process payment data.

Notify webhook

On Pro+ or Team you may save an HTTPS webhook URL. We send alert payloads to that URL. You are responsible for the security of the endpoint you name.

Contact form

Name, email, and message, forwarded to our inbox so we can reply.

Chrome extension

The extension stores your API base URL in local extension storage and a session token in session storage so you stay signed in while the browser session lasts. It reads the current tab’s URL, title, and selected text only when you use it to create a monitor.

Technical logs

Application logs may include request paths, error codes, and timestamps. We do not log passwords, bearer tokens, cookies, or page authentication data. LLM usage logs record model, token counts, estimated cost, and purpose (compile or relevance)—not prompts or page bodies.

What we do not collect from target sites

We do not send cookies or Authorization headers to origin sites. We do not store Set-Cookie from fetches. Authenticated cloud sessions, CAPTCHA solving, and residential proxies are out of scope.

4. How we use information

Create and secure your account, including password reset
Run checks on the cadence of your plan and evaluate your goal
Email you (and optionally POST a webhook) when a goal is newly satisfied
Show evidence, history, and plan limits in the dashboard
Compile hard goals and score relevance with an LLM when your plan includes that
Process subscriptions and enforce monitor and Playwright limits
Reply to support and contact-form messages
Keep the service reliable, prevent abuse, and comply with law

We do not use monitor contents to train a public model, and we do not sell personal information.

5. How we fetch the pages you monitor

HTTP fetch always runs first, identified as PulseNotice/0.4 (+https://pulsenotice.com), with timeouts and a size cap. Playwright runs only after that HTML is insufficient and only on Pro+ or Team. Fetches are throttled. Target sites may still block automation, personalize HTML, or geo-restrict content. Those responses are not a PulseNotice privacy incident; they are a limitation of unauthenticated public fetching.

6. Cookies, tokens, and local storage

The dashboard keeps the signed-in JWT in the browser’s sessionStorage, not a tracking cookie. Closing the tab ends that session. The Chrome extension keeps a session token in extension session storage and the API URL in local extension storage.

Marketing pages load the Poppins font from Google Fonts. Google may process the connection in line with its own policy. We do not run a separate analytics or advertising pixel on the site today.

We share data only as needed to run the product:

Stripe — checkout, invoices, and subscription state for paid plans
Resend (or the mail provider we configure) — account, alert, and contact email
OpenAI — goal compilation and relevance classification when those features run
Infrastructure hosts — database, Redis, and application hosting under our control
Your webhook — if you configure one, alert JSON is sent to that URL

We may disclose information if required by law, to protect PulseNotice or users from fraud or abuse, or in connection with a merger or sale, with notice where reasonably possible. We do not sell personal information as that term is used in the California Consumer Privacy Act.

8. How long we keep it

Account, monitor, check, alert, and billing identifiers are kept while the account is open so the product can function. If you ask us to delete the account, we delete or irreversibly anonymize personal data unless we must retain a subset for legal, security, or billing disputes (for example Stripe records we cannot erase on our side). Contact-form messages are kept long enough to respond and for a reasonable support archive.

9. Security

Passwords are hashed. API access uses a signed JWT. Logs are filtered for secrets. Transports use HTTPS in production. No method of transmission or storage is perfectly secure. If we learn of a breach that affects your personal data, we will notify you and regulators as required by applicable law.

10. Children

PulseNotice is not directed at children under 16. We do not knowingly collect personal information from children. If you believe a child created an account, contact us and we will delete it.

11. Your choices and rights

You can:

Access and update email, password, monitors, and webhook from the dashboard
Pause or delete monitors
Cancel a paid plan in billing (limits then follow the Free plan)
Sign out, which drops the browser session token
Ask us, via the contact form, to export or delete your account

Depending on where you live (including the EEA, UK, and California), you may also have rights to know, access, correct, delete, port, or opt out of certain sharing. We do not sell personal information or share it for cross-context behavioral advertising. Submit requests through the contact form. We may need to verify the email on the account. You may use an authorized agent where the law allows it. We will not discriminate against you for exercising these rights.

12. International processing

We operate from the United States. If you use PulseNotice from another country, your information is processed in the U.S. and in the countries where our processors (Stripe, email, LLM) run. By using the service you understand that U.S. law may differ from the law where you live.

13. Changes

We may update this policy as the product changes. The “Last updated” date at the top will change. Material changes will be called out on this page and, when appropriate, by email to the address on the account. Continued use after the effective date means you accept the updated policy.

14. Contact

PulseNotice, Austin, Texas, United States. Contact form · alerts@pulsenotice.com · Terms of service