A status-aware inventory, rather than a list of services we might use someday.
Last updated: 26 October 2026
These terms are in force. One commercial detail is still being confirmed and is marked in the text below: how long a refund decision takes. Nothing else on this page is provisional.
Lemon Squeezy — optional affiliate referrals
Affiliate referrals are optional and separate from Google advertising consent. Only after you accept Affiliate referrals in Cookie settings do we load Lemon Squeezy’s affiliate.js from lmsqueezy.com and Lemon.js from assets.lemonsqueezy.com. Rejecting, closing the notice, or sending Global Privacy Control keeps them off. You can buy Purrge without accepting.
The affiliate script sends Lemon Squeezy the page URL, referrer, affiliate code or existing click ID, a browser fingerprint calculated on your device, and network connection information. Lemon Squeezy uses this to link a referring partner’s visit to a purchase and award referral credit. The script sets the ls_aff_ref cookie on this site. Our checkout reads the generated click ID through Lemon Squeezy’s API and passes it as aff_ref on the hosted checkout URL; the public aff code is not the tracking ID.
Lemon Squeezy supplies the cookie’s expiry in its tracking response. Referral validity and first- or last-affiliate credit are controlled by the merchant’s Lemon Squeezy settings. We do not set a separate referral lifetime or promise a fixed number of days. Provider-side record retention has not been confirmed. Return visits with consent use the provider’s cookie and tracking service, subject to its expiry and your browser’s storage limits.
Withdraw Affiliate referrals or press Reject optional in Cookie settings to clear the referral cookie this site can reach and reload without the scripts. Your preference is kept for 180 days in purrge_privacy. Withdrawal stops future website tracking; it does not erase provider records already received or cookies on Lemon Squeezy’s own domain. If you leave an affiliate landing page before giving consent, that referral may not be recorded. Blocked or slow tracking does not prevent purchasing.
Purpose: website hosting, TLS, asset delivery, operational diagnostics and protection against abuse. Data: technical request and connection information. Locations and retention depend on Cloudflare’s network, products and account settings; a specific residency commitment is not claimed. Exact operational-log retention and contractual safeguards remain operator verification items.
Google Tag Manager, Google Analytics 4 and Google Ads — consent-gated website tags
Google Ads tag AW-18528763321 is configured. It loads only after you accept advertising cookies. Rejecting optional cookies or sending Global Privacy Control keeps it off.
The Google tag (gtag.js) is loaded directly from googletagmanager.com after advertising consent. It records page visits for advertising measurement and audiences, and sends page, browser, device, referrer and connection information, including IP address, to Google LLC and its group companies, including in the United States. Google may also receive advertising click identifiers in the page URL.
Google Ads may set the _gcl_au cookie on this domain, with a documented default lifetime of 90 days, and contact googleadservices.com and doubleclick.net. Google may set its own cookies, such as IDE and test_cookie, under those domains where your browser permits them. Third-party cookie lifetimes are controlled by Google.
With advertising consent, the website can verify a completed order with Lemon Squeezy and send Google Ads the order transaction ID, actual paid amount and currency for purchase conversion measurement. A test, failed, unpaid or refunded order does not count. Visiting the thank-you page alone is not proof of payment. We do not send your email address, name or license key to Google. No sign-up or lead conversion is sent.
Google Consent Mode v2 starts with ad_storage, ad_user_data, ad_personalization and analytics_storage denied. No tracking script, preconnect, DNS prefetch or tracking iframe contacts Google before you choose. Reject optional and Accept all are available side by side. Details offers an unticked advertising choice. Closing the panel grants nothing.
You can withdraw advertising consent in Cookie settings. This denies the consent signals, clears the Google advertising cookies this page can reach and reloads without the tag. Your choice is remembered for 180 days. Withdrawing does not remove information Google already received.
Google Analytics 4 and the Meta Pixel remain unconfigured and do not load. Analytics and diagnostics cannot be enabled in Cookie settings.
Google’s Ads Data Processing Terms were accepted for the Purrge Tag Manager account on 14 September 2026. This notice does not assert additional account settings or retention choices. See Google’s advertising and measurement privacy information.
Meta Pixel — consent-gated website advertising tag
Status: a tag shell exists in the Tag Manager container design and is gated behind the advertising consent; not configured and therefore not running, and no consent for it is collected, until a Pixel ID is supplied. Creating the Pixel needs a Meta Business account, which is separate from Google. Purpose: report page views and build advertising audiences. No purchase or lead event is sent by this website. Data: page URL, referrer, browser and connection information including IP address, plus the _fbp and _fbc cookies described in the cookie notice.
Recipient: Meta Platforms, including in the United States, so accepting means an international transfer outside the EEA and the UK. Google Consent Mode does not cover Meta, so the tag is additionally blocked by a Tag Manager trigger that requires a recorded advertising consent. Not established: Meta’s controller/processor terms for this deployment, a documented transfer mechanism, data-use settings, and which Business account owns the Pixel. Unlike Google, whose Ads Data Processing Terms were accepted on 14 September 2026, nothing has been agreed with Meta at all.
Status: installed on the website and loaded only when a visitor presses Chat with us. Purpose: receive and answer support conversations. Data: connection information when chat opens, plus message text and any contact details the visitor chooses to provide. The website sends no automatic user identity or page path. UserJot may use browser storage to maintain the conversation; analytics and advertising cookie choices do not enable chat.
Status: native SDK integrated and enabled by default for new installs from version 0.4.1, with an off switch in onboarding and Settings; existing choices are preserved. Not installed on this website. Purpose: understand coarse product use and improve Purrge. Data: allowlisted events, random installation ID and SDK environment properties. The project region, retention window, deletion procedure and executed provider terms must be confirmed before production use. No provider setting is inferred from its availability.
Status: integrated in the native app, disabled by default and controlled separately in Settings. Purpose: diagnose crashes and handled errors. The app scrubs paths and excludes screenshots, file inventories, license values and session replay. Project region, retention and symbol-upload configuration remain operator verification items.
The “Explore Purrge” link takes you to a separately hosted here.now design preview. It uses example app data, but its host still receives ordinary web requests when you visit it. It is an external destination, not an embedded analytics SDK.
Lemon Squeezy provides hosted checkout, payment processing as merchant of record, receipt emails and license delivery. UserJot handles website chat after a visitor opens it. The Google and Meta entries above describe which services are configured and when consent is required; listing a provider does not establish additional agreements, regions or retention settings. This inventory must be updated when a new service is selected and before additional personal data is collected.
