Skip to main content

Cookies

Short version: we set none. Two embedded services set theirs, and only on the pages that need them.

Last updated 29 July 2026

Firstline

Every page

No cookies and no analytics, so there is nothing to accept or refuse. We store one thing in your browser, and only if you arrived through a personal demo link one of us sent you: that person's name, so the booking buttons keep pointing at their calendar. It never leaves your browser, and clearing your browsing data removes it.

Cal.com

/book and personal demo links

The scheduler sets its own cookies to run the booking flow: keeping your place in the calendar, remembering your time zone and blocking abuse. It loads when you open the page, because the page is the scheduler.

Vimeo

/demo

The player sets cookies for playback. Nothing loads until you press play, and we request Vimeo's Do Not Track mode, which stops the session being used for tracking or profiling.

Why there is no cookie banner

A banner exists to ask permission for tracking. We do no tracking, so there is nothing to ask about. The two services above are there to do the thing you came to that page for: book a meeting, or watch a video. The video only loads once you press play, which is your decision to make.

If we ever add analytics or anything that follows you between visits, we will ask for consent first and say so here.

Clearing them

Every browser can block or delete cookies per site, usually under privacy settings. Blocking them for cal.com or vimeo.com will stop the scheduler or the player from working, but the rest of the site is unaffected.

Questions

Write to noah@firstline.so. Our privacy policy covers the rest of what we do with data.

Don’t lose technician time on routine tickets.

Predictable pricing with hard monthly ceilings designed for MSP contract margins. Scale your ticket capacity without adding tier-1 headcount.


Firstline

The AI technician that resolves IT tickets on the device.

noah@firstline.so
© 2026 Firstline