Skip to content

Wording for your privacy policy.

What to tell your visitors when you use Obelisk tracking.

Effective: November 6, 2026

If you add the Obelisk tracking script to your website, you must tell your visitors about it in your own privacy policy. Copy the wording below into your policy, replace the parts in square brackets, and delete what doesn't apply to your setup. It matches how the script works today. You remain responsible for your own policy, your cookie banner and your legal basis, so check the wording against the rest of your policy and the laws that apply to you.

How to use this template

  • Paste it under a heading such as "Analytics and enquiries" in your privacy policy.
  • Keep the paragraph about contact details only if you use lead capture or identify().
  • Keep the paragraph about Google Analytics only if your site also runs Google Analytics.
  • Keep the paragraph about linked websites only if you set data-domains.
  • If you use your own cookie banner instead of Obelisk's, change the banner paragraph to describe yours and remove cc_cookie.
  • Add _obk_id (and cc_cookie, if you use Obelisk's banner) to your cookie list. Our cookie policy gives the details.

Wording to copy

We use Obelisk, a marketing platform from The Obelisk App Inc. in the United States, to understand how people find our website and become customers. Obelisk processes this data for us as our service provider (processor), under a data processing agreement, and stores it in the United States. We are responsible for it as the controller. Obelisk doesn't sell it, use it for advertising or combine it with other businesses' data.

Before you choose in our cookie banner. Obelisk stores nothing on your device: no cookies and no local storage. It sends the page you are on (its address without most of its query string), the page title, the website that sent you here, your browser's language and screen width, the campaign tags in the address (such as utm_source, gclid, fbclid and msclkid), how far you scroll (25, 50, 75 or 100%), links you click to other websites, and the fact that you submitted a form, with the form's field names but none of the values you typed. To count your visit without cookies, Obelisk combines our website's ID, your IP address and your browser's user agent with a random value that changes every day, and keeps only the resulting code. Your IP address is never stored, and because the random value is deleted every day, the code can't link your visits from one day to the next. Obelisk keeps your browser and operating system name and a device type (phone, tablet or desktop), not the full user agent. We do this based on our legitimate interest in measuring how our website is used. [If you are in the EU or UK and your regulator requires consent for this, replace this sentence with: "We do this only after you accept analytics cookies."]

If you accept analytics cookies. Obelisk sets a cookie called _obk_id on our website. It holds a random ID, lasts 390 days and lets us recognise your later visits. If you accept partway through a visit, the pages you saw earlier in that visit are joined to it. [If your site uses Google Analytics: Obelisk also reads the client ID in Google Analytics' _ga cookie, so we can match our Google Analytics reports to visits.] We rely on your consent for this, and you can withdraw it at any time.

Contact details. [If you use lead capture:] Only if you have accepted analytics cookies, when you submit [our contact form / name your forms], Obelisk receives the email address and name you entered in that form, so we can see your enquiry together with how you found us. It never collects anything else you type. [If you use identify():] When you sign in to [our site / app], we send Obelisk our customer ID for you and, if you've accepted analytics cookies, your email address and name. We may record whether your enquiry became a customer and its value.

Across our websites. [If you link several websites:] If you have accepted analytics cookies, links between [list your websites] carry a short _obk code with your random ID, so both websites recognise the same visit. It is valid for 2 minutes and is removed from the address bar when the page loads.

Our cookie banner. [If you use Obelisk's banner:] Our cookie banner is provided by Obelisk. It stores your choice in a cookie called cc_cookie for 182 days, so it doesn't ask again on every page. If we use Google tags, the banner passes your choice to Google using Google Consent Mode.

How long we keep it. We keep this data for [your retention period, for example 25 months] and delete it sooner if you ask us to.

Your choices and rights. You can change your cookie choice at any time through [the "Cookie settings" link in our footer]. Withdrawing consent deletes the _obk_id cookie, and Obelisk goes back to counting visits without cookies. To see, correct or delete the data we hold about you, or to object to how we use it, contact us at [your privacy email]. We can delete everything linked to your email address, including your enquiries and the visits joined to them. Visits counted before you gave consent use a code that changes daily, so we can't link them to you or find them on request.