How tracking works on Kettlekin.

Meta Pixel and your choice

We use Meta Pixel for ad measurement. The Pixel script is loaded only after you accept Meta Pixel in the tracking preferences control. If you decline, the script is not loaded. If you withdraw after it has loaded, the app stops sending its events, asks the Pixel to revoke consent for the current page, and saves your declined choice for future visits. The choice is stored in this browser until you change or clear it. If browser storage cannot be read, Meta Pixel stays off.

Acceptance enables these events: a PageView when the Pixel is first enabled and on later in-app page changes; a Lead after signup succeeds; and a Purchase only after a payment is verified. A purchase event includes the payment value and the currency USD. Project setup uses the agreed project amount. The contractor tool uses the buyer-paid amount when the billing response includes it, with the configured checkout amount as a fallback for older responses.

After acceptance, browser storage records that a purchase event was sent for a checkout session so a repeated verification does not send the same event again. Meta's third-party Pixel may use cookies or similar browser identifiers for measurement. We do not list specific Meta cookie names here because they have not been verified against the running SDK.

Separate site analytics

Some deployments also enable a separate Polsia site-analytics beacon. When enabled, it runs on page load and uses a browser identifier stored as polsia_vid. The Meta Pixel choice does not control this beacon. Deployment-specific retention and processing details are not available in this app's code.

More information from Meta

For information about Meta's privacy practices, read the Meta Privacy Policy. For questions about this notice, email kettlekin-11@polsia.app.