Cookies Policy

Last updated: January 7, 2026

This Cookies Policy explains how Score Intent Sp. z o.o. ("ScoreIntent", "we", "us", or "our") uses cookies, local storage, session storage and similar technologies on https://scoreintent.com/ and on pages where our scnt.js script is active. It describes what types of information are stored, why we use these mechanisms, how long data is retained, and how you can control cookie and tracking preferences.

If you have questions about this policy or wish to exercise your privacy rights, contact: privacy@scoreintent.com.

1. What are cookies and related technologies

• Cookies are small text files placed on your device by a website that can store identifiers and preferences.
• localStorage and sessionStorage are browser storage mechanisms that allow scripts to store data on a user's device. localStorage persists beyond browser sessions; sessionStorage persists only until the browser/tab is closed.
• Pixel tags / web beacons are small, invisible images or script calls used to record page loads or events.

We use these technologies to make the site work, to measure and improve our services, to provide features (for example behavioral scoring and overlays), and — where applicable and lawful — to enable marketing or integrations.

2. Categories of cookies and purposes

We use cookies and storage for the following purposes:

• Essential / Functional: cookies required for the operation of the website, session management and security. These cannot be disabled if you wish to use core site functionality.
• Performance / Analytics: cookies and storage items used to measure usage patterns, errors and to improve site performance and product features.
• Personalisation / Product features: cookies and browser storage used to show overlays, remember UI choices, and store behavioral scores used by our platform for prioritisation and routing.
• Advertising / Targeting (where applicable): cookies and identifiers used to support audience activation and to match or synchronise identifiers with client systems; these are used only where lawful and with appropriate opt-in/choices.

3. ScoreIntent script (scnt.js) — specific storage keys and cookie names

The ScoreIntent front-end script (scnt.js) stores a small set of values in the visitor's browser to operate scoring, overlays and to support reliable event delivery. The following are the storage keys and cookie names used by the script and their purpose and retention:

localStorage (persistent storage — retained across browser restarts; renewed on activity):

• scnt_session_timestamp — timestamp (milliseconds) of session start / last activity. (number / Date.now())
• scnt_excluded — flag to indicate visitor is excluded from analytics ("true" / "false").
• scnt_converted — flag indicating conversion event occurred ("true" / "false").
• scnt_purchased — flag indicating purchase event occurred ("true" / "false").
• scnt_failed_events — buffer of failed events (JSON object used for retry).
• scnt_session_id — session identifier (random string / UUID).

These localStorage entries are persistent and are renewed on activity; in typical configuration they are refreshed every 30 minutes of inactivity to maintain session continuity.

sessionStorage (cleared when the browser tab/window closes):

• scnt_score — behavioural score or numeric rating (e.g., "42").
• scnt_scoring_overlay_shown — flag indicating if scoring overlay has been shown ("true" / "false").
• scnt_exit_overlay_shown — flag indicating if exit overlay has been shown ("true" / "false").

These values are short-lived and exist only for the lifetime of the tab.

Cookie(s):

• scnt_user_id — persistent, anonymous user identifier (UUID v4 or similar). Retention: 365 days (used to recognise returning devices/browsers).

Note: the script may use additional ephemeral identifiers for network requests (for example request ids). The names above are the primary persisted keys the script creates by default.

4. Third-party cookies and integrations

Where ScoreIntent integrates with third-party services (hosting, analytics, identity providers, advertising partners or payment gateways), those third parties may set their own cookies or use other storage mechanisms. We do not control third-party cookies; please consult the privacy/cookie policies of those providers for details about how they use cookies and how to opt out.

When ScoreIntent acts as a processor for a customer (for example, when providing audience activation or hashed-identifier matching), the customer determines whether data is shared and for what purpose. Any identifier sharing will be done consistent with contractual and legal obligations.

5. Your choices — how to control cookies and storage

Cookie preferences / consent banner

Where required by law, ScoreIntent will present a cookie consent banner or preference centre. Non-essential cookies (analytics, advertising) will not be set until you consent, except strictly required cookies.

Browser controls

You can control and delete cookies and local data using your browser settings. Typical actions: block third-party cookies, clear cookies, or block storage for a specific site. Blocking or deleting cookies/localStorage may break some features (for example, scoring overlays, persistent session continuity, or demo/trial functionality).

Device / app opt-outs

If you have used an opt-out mechanism provided on our site (for example to opt out of interest-based activation on that browser), that opt-out is typically implemented using a persistent opt-out cookie and will apply to the specific browser and device where it was set. For cross-device or cross-browser opt-outs, please follow any additional steps described in our product documentation or contact privacy@scoreintent.com.

Global Privacy Control (GPC)

Where a browser or extension presents a Global Privacy Control (GPC) signal, ScoreIntent will treat that signal as a valid opt-out preference for sale/sharing and interest-based advertising for the browser/device presenting the signal, subject to applicable law.

6. How long we keep cookie and local data

Retention depends on the cookie/localStorage item and the purpose:

• scnt_user_id cookie — 365 days (persistent identifier).
• localStorage keys (scnt_session_timestamp, scnt_excluded, scnt_converted, scnt_purchased, scnt_failed_events, scnt_session_id) — persistent but effectively rotated/renewed on activity and refreshed every ~30 minutes of inactivity under standard script configuration; retained until deleted or cleared by the user.
• sessionStorage keys (scnt_score, scnt_scoring_overlay_shown, scnt_exit_overlay_shown) — exist only until the browser tab is closed.

We also keep aggregated or anonymised analytics data for longer periods as needed to support product improvement and reporting.

7. Blocking or removing ScoreIntent cookies and storage

• Use your browser settings to delete cookies and site data for scoreintent.com.
• To clear localStorage/sessionStorage values, you can open browser developer tools (Application / Storage panel) and remove the listed keys for the site. (If you are not familiar with developer tools, consider the browser's "clear browsing data" options.)
• If you have an account or an integration that stores identifiers server-side, deleting local cookies/localStorage may not remove identifiers stored with your account — to remove server-side records, submit a deletion request to privacy@scoreintent.com.

8. Changes to this Cookies Policy

We may update this Cookies Policy to reflect changes in law or in our use of cookies and storage technologies. The date at the top of the policy will be revised when material changes are made. Where required by law, we will obtain fresh consent for newly introduced non-essential cookies.

9. Contact and enforcement

If you have questions about this Cookies Policy, would like a copy of the data linked to the cookies/local identifiers we hold about you, or wish to request deletion, please contact: privacy@scoreintent.com

You may also contact our Data Protection Officer at the same address. If you are not satisfied with our response you have the right to lodge a complaint with your local supervisory authority.

10. Technical appendix (quick reference)