Privacy
Effective date:
Captures stay in the browser. The licence service does not receive page content or page URLs. Copy, files, and ZIP exports stay on your machine unless you share them yourself.
The extension does not collect card numbers. Stripe hosted Checkout handles payment on Stripe’s pages.
What a licence call sends
- Checkout: the plan and the purchase email. A renewal also sends the existing licence token.
- Activate, release, and recheck: the signed licence token and a browser id. The token carries the licence id, plan, purchase time, and feature cutoff.
- “Email me my licence”: the purchase email address. The server uses it to find and email usable licence keys. The hosting request also carries an IP address for rate limiting.
What the licence database stores
- Email, licence id, plan (
proorlifetime), and a revoked flag. - Times: purchase, feature cutoff, renewal, and when the row was created.
- Stripe Checkout Session id and PaymentIntent id, and whether that payment was a purchase or a renewal.
- Browser ids and when each was activated, up to three.
- Stripe event id, event type, and when it was processed.
- Refund processing records: PaymentIntent id and time, including a refund that arrives before the licence row exists.
- Recovery requests: hashes of the normalized email and IP address, plus the request time, for rate limiting. Requests do not store message bodies or keys.
How licence records are used and kept
These records let PageRip issue and restore keys, check which features a licence unlocks, enforce the three-browser limit, process renewals and refunds, and avoid processing the same payment twice. Captured page content is not used for these purposes.
Licence, payment, processed-event, and refund records have no automatic expiry in the service. They remain in the database unless manually deleted, including after a refund or the end of a Pro feature-update period. Releasing a browser deletes its activation record; other activation records have no automatic expiry.
Hashed recovery rate-limit records are deleted once they are at least 24 hours old, on the next recovery request. This is request-triggered cleanup, so records can remain longer if there are no further requests. The service does not save sent email bodies or licence keys. If lookup, signing, or sending fails, it keeps the rate-limit reservation and logs a generic failure message, without the email address or message body.
Who else sees data
Stripe processes the payment and can email its own receipt. Managed Payments, if Stripe approves it for live mode, would make Stripe the merchant of record. Stripe retains payment and related personal data under itsprivacy policy, including for legal, tax, accounting, and fraud-prevention purposes. PageRip’s database cleanup does not delete Stripe’s records.
Cloudflare hosts the site and the licence database. It handles network request information, including IP addresses, to deliver and protect the service. D1’s recovery history can retain earlier database states for 7 days on Workers Free or 30 days on Workers Paid, separately from the active records above. Where Workers Logs is enabled, its log retention is 3 days on Workers Free or 7 days on Workers Paid. Other Cloudflare operational and security data follows its privacy policy; it is not covered by PageRip’s 24-hour rate-limit cleanup.
Amazon Web Services (AWS) processes licence recovery email through Amazon Simple Email Service (SES) inus-east-2. AWS receives the recipient address and the message containing the licence keys, plans, and feature cutoffs to deliver that email. No captures or page URLs are included. SES may retry temporary delivery failures. If an address is added to an enabled account-level bounce or complaint suppression list, AWS keeps it until it is removed (or clears it after 90 days if the account’s sending ability remains paused). SES processing and any provider-side delivery records followAWS’s data-handling rules; we do not promise they are deleted with PageRip’s rate-limit records. Delivered mail is also retained according to the recipient’s email provider and mailbox settings.
Website analytics
The marketing site uses Google Analytics to measure website visits, separately from extension captures. Google receives website usage and device information and uses analytics cookies to distinguish visits. User- and event-level retention depends on the Analytics property settings; aggregated reports have separate retention. Cookie expiry can be refreshed by later visits. See Google’sdata retention andcookie documentation. These legal pages do not load analytics.
Contact and privacy requests
Email support@webpagerip.com to ask about this policy or request access, correction, or deletion of your licence records. Use your purchase email and receipt details so we can identify the records. Do not send card numbers, captures, or page content. Requests are handled manually; records needed for legal obligations or preventing payment replay may need to be retained.
Limited Use
PageRip uses information received from Google APIs in compliance with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Licence calls support purchasing and managing a licence. They do not send browsing history, page URLs, or captured content to the licence service.