BossBack

Legal

Cookies & Analytics

A plain-language explanation of the tracking technologies BossBack currently uses—and, importantly, the ones we do not.

  • Effective: August 15, 2026
  • Last updated: August 26, 2026

1. Current BossBack position

BossBack does not use advertising cookies, retargeting pixels, cross-site marketing trackers, or third-party behavioural analytics to build advertising profiles on the public website.

BossBack also does not currently use Google Analytics, Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, Microsoft Clarity, Hotjar, session-replay software, or similar marketing and behavioural analytics products on the public site.

Our Phase 1 measurement approach uses privacy-conscious aggregate analytics and limited first-party measurement rather than advertising or cross-site tracking.

2. Cloudflare and Web Analytics

BossBack uses Cloudflare for DNS, network delivery, TLS edge services, traffic protection, and security. Depending on security features and visitor traffic, Cloudflare may use strictly necessary technology or process technical signals for rate limiting, bot detection, security challenges, network delivery, and diagnostics.

BossBack may also use Cloudflare Web Analytics to understand aggregate website traffic and real-user performance, such as visits, page views, page paths, external referrers, device or browser categories, and Core Web Vitals.

Cloudflare describes Web Analytics as privacy-first and states that its usage metrics do not use cookies or localStorage and do not collect or use visitors’ personal data. BossBack does not use Cloudflare Web Analytics to create advertising profiles or track people across unrelated websites.

3. First-party measurement

BossBack records a limited set of first-party events when they are needed to understand meaningful actions that ordinary page-view analytics cannot measure. For the Phase 1 public site, these events are limited to a Try Answers click and a successful Contact form submission. Product adoption and activation are measured from BossBack’s application database instead of this public-site event ledger.

These measurement records are intentionally limited. They are designed not to contain raw visitor questions or AI answers, contact-message text, names, email addresses, IP addresses, full user-agent strings, OAuth or authentication data, session cookies, or arbitrary URL query strings.

If BossBack measures campaign attribution, we may retain only specifically recognized campaign fields such as utm_source, utm_medium, utm_campaign, utm_content, and utm_term rather than storing arbitrary query-string parameters.

4. Server and security logs

Our server and infrastructure providers may record IP addresses, request paths, timestamps, browser or user-agent information, response status, security signals, and other technical details in ordinary web, network, and security logs. These records help operate the site, diagnose errors, detect abuse, enforce limits, and maintain security. They are separate from the limited analytics event records described above and are not used for behavioural advertising.

5. Cookies and browser controls

BossBack does not currently have a non-essential advertising-cookie category or cross-site marketing tracker for visitors to opt into on bossback.ai. Cloudflare Web Analytics usage metrics are designed to operate without analytics cookies or localStorage.

For that reason, BossBack does not display a cookie-preference banner solely for the Phase 1 measurement described in this notice. If we later introduce technology that requires consent or additional controls, we will update this notice and implement those controls before or when that technology is enabled.

Most browsers also let you view, block, or delete cookies. Blocking strictly necessary security technology may cause features to work incorrectly or trigger additional security checks.