Privacy

This page describes what the PagePulse software stores. The operator of this deployment has not published a legal name, mailing address, or privacy contact on this page. It is not a lawyer’s opinion.

An account stores the name and email you submit, a password hash, and a session cookie. The cookie is HTTP-only, Secure, and SameSite=Lax. PagePulse does not offer password reset by email. Google and X sign-in, when offered, go through the platform’s auth broker rather than a key stored in this app.

A monitor stores the public URL you submit and the visible text extracted from it, plus the before-and-after of a change and your alerts. Deleting a site deletes that site’s checks, snapshots, changes, and alerts. There is no self-serve button to delete the whole account. Card numbers are not stored here. When Stripe is connected, the account stores a Stripe customer id, subscription id, plan, and status.

Support messages you submit are stored with your email. Sign-in, sign-up, and support requests are rate limited. The limit table stores a hash of the network address, not the address itself. Sweep history stores counts for 14 days and is then deleted. Logs from a sweep are those counts. Secrets and page bodies are not written to the log line.

The application has no feature that sells account data to advertisers. When the operator connects them, Stripe processes payment, Resend sends email, and the host and database provider store the data needed to run the app. Fetches of pages you ask PagePulse to watch are anonymous GETs. They do not send your cookie to the watched site.