Browser storage and tracking.

Meta Pixel preference

The Meta Pixel choice is stored in this browser's first-party local storage until you change or clear it. Meta Pixel is not loaded before you accept. If you decline, it stays off; if you later withdraw acceptance, the app stops sending its events and asks the Pixel to revoke consent for the current page. When browser storage cannot be read, the app keeps Meta Pixel off.

Accepting enables PageView events when first enabled and on later in-app page changes, a Lead after successful signup, and a Purchase after verified payment. Purchase events include a payment value in 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. A first-party browser storage entry based on the checkout session ID prevents repeat purchase events when a payment is verified more than once.

Meta's third-party Pixel may use cookies or similar browser identifiers for measurement after acceptance. We do not name specific Meta cookies because their names have not been verified against the running SDK. See the Meta Privacy Policy for Meta's privacy information.

Other browser storage and site analytics

Purchase deduplication uses a first-party local storage entry derived from the checkout session ID. Separately, some deployments enable a Polsia site-analytics beacon. When enabled, it runs on page load and uses a browser identifier stored as polsia_vid. Your Meta Pixel choice does not disable that beacon; deployment-specific retention and processing details are not available in this app's code.