Settleframe · Cookies & tracking

Cookies & tracking

Sign-in and privacy preference cookies, and optional Meta conversion measurement.

Updated November 15, 2026 · Version 2026-11-08

Necessary sign-in cookie

Settleframe sets one necessary first-party cookie, sf_session, after you sign in. It keeps you authenticated for up to seven days. It is marked HttpOnly and SameSite=Lax; production uses a secure HTTPS cookie. Signing out clears it.

This cookie is necessary for the account service you request. You can block or delete it in your browser, but signing in and private projects may then stop working.

Privacy preference cookies

When you use the Privacy choices control, Settleframe sets a first-party HttpOnly sf_privacy cookie for up to 180 days to remember your allow or deny choice. After you consent, Settleframe may also set an opaque sf_marketing consent identifier as a first-party HttpOnly cookie for up to 180 days; it is created only after consent and is not a marketing permission for email.

These preference cookies record and enforce your choice. You can change or withdraw your choice at any time through the Privacy choices control, which is equally accessible for allowing, rejecting and withdrawing consent.

Optional Meta conversion measurement

Optional Meta conversion measurement is off until you explicitly opt in through the Privacy choices control. Reject and withdraw are equally accessible. If Global Privacy Control is enabled in your browser, Settleframe will not enable this opt-in. There is no Meta browser script, no Meta Pixel, no Meta third-party tag, no session replay, and no fingerprinting that follows you from one day to the next: visits are counted with a hash that changes every day (see the privacy policy). Fonts and images are local.

When you have consented and the operator has configured the integration, Settleframe’s first-party backend sends PageView, ViewContent, CompleteRegistration, InitiateCheckout and Purchase to Meta through the Meta Conversions API. The purpose is to measure advertising and improve campaigns. Sent fields may include a hashed email or hashed account or consent identifier when known, your browser user-agent, the Meta ad click identifier fbclid when present, and the event type, time and, for Purchase, the amount and currency. No IP address is transmitted to Meta. No photos, placement notes, property addresses or sign-in tokens are sent. Hashed identifiers are still personal data and are not anonymous.

The consent reference lasts for up to 180 days; an expired or withdrawn record is removed within a further 30 days. Local event records and campaign labels are retained for up to 30 days, and event payloads are erased after delivery or withdrawal. Withdrawal stops future sends and cancels pending events; a request already in transit cannot be recalled. Meta acts under its own policies and terms for information it receives, and that processing may take place outside your country. Locally, Settleframe cannot recall data Meta has already received; contact the operator privacy contact to exercise applicable rights. See Meta’s privacy policy.

When you open checkout

Checkout is run by Paddle, our reseller. When you click a Buy button, the page loads Paddle’s checkout script from Paddle and opens Paddle’s secure checkout window over the page; nothing from Paddle loads before that click. Paddle’s cookies and privacy practices apply inside that window. See Paddle’s privacy policy.

Read more about account, photo and optional Meta measurement processing in the privacy policy.