Skip to content Skip to footer

Cookies policy

This Cookie Notice describes what kinds of cookies and similar technologies Programmatic uses in connection with our Services (as defined in our Privacy Policy), and how you can manage them.

1. General Information

Please read this cookies policy carefully before using the programmatic.law website operated by Programmatic (“Programmatic”, “us”, “we”, or “our”). By using our site, you consent to our use of cookies in accordance with this policy. This policy outlines the types of cookies we use, their purpose, and how they enhance your experience on our website. By continuing to browse or use our site, you agree to the use of cookies as described here and accept the rights and obligations it entails for both Programmatic and the site users.​

3. Types of cookies

Our website uses cookies. These are small text files that may be placed on a device while browsing our website which store certain information. Cookies cannot access, read, or modify other data stored on your device. By referring to “cookies” we include other technologies with similar purposes, such as pixel tags. We use two types of cookies on Company's website:

Necessary cookies: Without necessary cookies the proper functioning of our website would not be possible or only to a limited extent. The use of necessary cookies on our website is possible without your consent. You can deactivate necessary cookies at any time by modifying your browser settings, however in such case we cannot guarantee the proper functioning of our website.

Optional cookies: These types of cookies may be used to improve our website, optimise your experience, analyse your behaviour or customise marketing activities. Optional cookies may also be placed by external advertising companies ("third party cookies"). Optional cookies will only be used upon your consent which you may provide via the website's cookie banner. This consent can be withdrawn at any time with effect for the future.

Optional cookies can be analytical, functional or for advertisement.

3.1. Analytics Cookies

• _ga (Google Analytics)

Purpose: This cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. Storage period: 2 years

• _ga_* (Google Analytics)

Purpose: Google Analytics sets this cookie to store and count page views. Storage period: 1 year, 1 month, 4 days

• hjSessionUser (HotJar)

Purpose: Set by Hotjar to ensure data from subsequent visits to the site is attributed to the same user ID, which persists as a unique Hotjar User ID. Storage period: 1 year

• hjSession(HotJar)

Purpose: Hotjar sets this cookie to attribute data from future visits to the same user session. Storage period: 1 hour

3.2. Functional Cookies

• trx_addons_is_retina (ThemeREX)

Purpose: Set by ThemeREX to detect whether the user is using a retina display, which adjusts visual content accordingly. Storage period: session

• wpEmojiSettingsSupports (WordPress)

Purpose: Set by WordPress to determine if the user’s browser can display emojis properly. Storage period: session

3.3. Advertisement and Marketing Cookies

• bcookie (LinkedIn) Purpose: LinkedIn sets this cookie to track the usage of embedded LinkedIn services. Storage period: 1 year

• li_gc (LinkedIn)

Purpose: LinkedIn uses this cookie to store visitors’ consent regarding the use of non-essential cookies. Storage period: 6 months

• lidc (LinkedIn)

Purpose: LinkedIn uses this cookie to facilitate data center selection. Storage period: 1 day

3.4. Security Cookies

• rc::a (Google)

Purpose: This cookie is set by Google reCAPTCHA to identify and prevent bot traffic, protecting the website against spam and malicious attacks. Storage period: Never

• rc::c (Google)

Purpose: Set by Google reCAPTCHA to ensure security by identifying bots during browsing sessions. Storage period: Session

3.5. Other Cookies

• hjActiveViewportIds (Hotjar)

Purpose: Used by Hotjar to track the user’s active viewport dimensions for optimized display and tracking. Storage period: never

• hjViewportId (Hotjar)

Purpose: Used to store the user’s viewport dimensions for optimized display and user tracking. Storage period: session

What if your contracts could
manage themselves?

PRODUCT

Icon

Programmatic Studio

Where documents get written, structured, and brought to life.
Icon

Smart Templates

Your templates, upgraded with smart fields and built-in logic.
Icon

Deal Мanagement

Send proposals and track deal progress, terms, and milestones.
Icon

eSigning

Enterprise-grade e-signing, built in — secure and fully compliant.
Icon

Workflows & AI

Automate how documents come to life — from signature to payment to reporting.
Icon

Payments & Invoices

Trigger automated payments and invoice flows from contract terms.
Icon

Client Portal

Give clients real-time access to their contracts, tasks, and updates.

The Future of Contracts: Digital Property

SOLUTIONS

Pharma

Track budget, compliance, and be audit-ready.

Real Estate

Automate leasing, approvals, and payment collection.

Finances

Automate billing and operations to reduce overhead.

Legal

Deliver faster, standardised legal work, at scale.

Accounting

Auto-generate letters, fees, and onboarding docs—at scale.

Construction

Digitise contracts and track every milestone automatically.

Insurance

Generate and execute policies, renewals, and claims workflows without manual effort.

Supply Chain

Streamline POs and vendor terms with real-time automation.

The Future of Contracts: Digital Property