Privacy policy

What we collect

When you sign in we receive your email address and display name from our identity provider (signin.ounie.com). When you run a check we store the check record: the URL you nominated, the selector or field map you gave us, which volatile classes you masked, the normalised extraction of the page, its hash, the diff, a snapshot image, and the credit reservation and settlement. A monitor also stores its schedule, its destination, and a log of every alert we attempted to deliver.

The normalised extraction is the text of somebody else's public page. We store it because a diff needs a “before” — that is the whole mechanism — and because re-reading a check you already paid for should be free.

What we don't do

We don't track you across the web. There are no third-party analytics scripts, no advertising pixels, no session replay. We don't sell or share the pages you watch, we don't use them to train any model, and no model is involved in deciding whether a page changed — the comparison is a hash, not a judgement.

Your checks are private

There is no public page for a result and no share link. A check is visible to you when you are signed in, and to API keys you have minted — nobody else. Snapshot images are stored privately and served only through a signed link that expires; they are never on a public prefix. A baseline can only be read back by the account that created it, so naming somebody else's check id cannot hand you their page content. We keep your checks so that re-reading one later is free; if you would rather they were gone, ask and we will delete them.

What is sent to third parties

To run a check, the URL is sent to a page-rendering provider and, when a snapshot is requested, to Ounie's own capture service. Both fetch the page and see the URL. The site you are watching sees an ordinary request from those services, as it would any visitor. Neither receives your email, your account, or your Ounie identity.

Treat a URL you submit as something that leaves our servers, and treat a monitor as something that will visit that page repeatedly and visibly. Do not put credentials or one-time tokens in a URL — a signed or session-bearing link is stored on the check record and fetched by a third party. Non-public addresses are refused outright.

A webhook you nominate receives the diff, which contains extracts of the watched page. Choose an endpoint you control, and verify the signature we send so nobody who learns the URL can feed you anything else.

Where data lives

Check records, monitors, delivery logs and credit ledger entries are stored in a Neon Postgres database hosted in the US. Snapshot images are stored in a private S3 bucket in us-east-1.

Payments

Credit purchases happen on ounie.com, where Stripe processes payment. This product never sees your card number; it only reads and debits your Ounie credit wallet. x402 calls are settled in USDC on-chain and are pseudonymous — we record the paying wallet address and transaction hash, nothing more. Stripe's privacy policy is at stripe.com/privacy.

An x402 check is stored without an owner, because a keyless caller has no account to attach it to.

Deletion

To delete your account or download your data, open a privacy ticket. We respond within 7 days and complete the deletion within 30.

Contact

/contact · routed to ounie@ounie.com