How is this different from RPA or a no-code automation tool?

Traditional RPA and no-code tools follow rigid, pre-defined paths and break the moment reality deviates. Brancle builds agentic workflows: agents that reason over context, handle exceptions, and make mid-level decisions within your rules. You get the reliability of automation with the adaptability of judgment — plus the integrations and guardrails to run it safely in production.

Will an AI agent make mistakes on work that matters?

Every workflow is engineered with confidence thresholds, validation steps, and human-in-the-loop checkpoints calibrated to the risk. Low-stakes, high-volume work runs autonomously; consequential decisions are escalated to your team with the context already prepared. Everything is logged, so you always have a complete, auditable trail of what happened and why.

How long until something is actually live?

Most first workflows are running in production within four to six weeks of kickoff. We deliberately scope the first engagement around a single high-impact process so you see measurable value quickly — then we expand from a proven foundation rather than a big-bang rollout.

Do we need to replace our existing software?

No. Brancle integrates with the systems you already use — your CRM, ERP, helpdesk, inboxes, spreadsheets, and databases. Automation lands inside your current stack, so your team keeps working in familiar tools while the agent handles the work behind the scenes.

How do you handle data security and compliance?

We operate on least-privilege access, keep your data within environments you control where required, and design workflows around your compliance constraints — including audit logging, retention rules, and approval gates. For regulated industries, oversight checkpoints are built in from day one, not bolted on later.

What does an engagement cost?

Pricing is scoped to the workflow and the value it returns — we model the ROI before you commit, so the investment is always measured against the hours and cost it removes. The fastest way to a number is a short discovery call where we map your highest-impact opportunity together.

Cookie Policy — Brancle

Only two sources set storage
Vercel hosting (security, balancing, logs) and Cal.com (scheduler availability and selection). That's the complete list.
Fonts are self-hosted
Inter, Fraunces, and JetBrains Mono ship with the site build. No runtime requests to Google, no font cookies.
No analytics or ads
No GTAG, PostHog, Hotjar, Meta Pixel, or ad cookies. We run no consent banner because there is nothing to consent to beyond the scheduler.
You hold the switches
Block or clear in your browser anytime, or skip the embed via the booking page link. Scheduler may need storage to render dates.

FIG. L-01A · SummaryNº 01SHA · Plain EnglishStart here

Nº 01

Overview

BRANCLE TECHNOLOGIES LLC (“Brancle,” “we,” “us”), 212 N. 2nd St. STE 100, Richmond, KY 40475, operates https://brancle.com (“Site”). This Cookie Policy explains which cookies and similar storage we and our processors use, the purpose and legal basis for each, and your controls. It expands Section 8 of our Privacy Policy (Policy #1) without changing its substance.

Under the EU ePrivacy Directive and GDPR, strictly-necessary storage needs no consent; functional storage for the scheduler is disclosed here with avoidance and choice paths in Section 8. Under the Kentucky Consumer Data Protection Act and California CCPA/CPRA, we do not sell or share personal information for cross-context behavioral advertising, and we honor Global Privacy Control signals for any future analytics.

Nº 02

What cookies and storage are

Cookies are small text files a site or embed asks your browser to remember. LocalStorage and sessionStorage are similar browser stores used to hold interface state (for example, a selected date). An iframe embed — such as our scheduler — can set its own cookies and storage under its own domain when it loads, governed by that provider’s policy in addition to ours.

Blocking or clearing storage is done in your browser and applies per domain. Blocking strictly-necessary storage can degrade security or balancing; blocking scheduler storage can prevent availability from rendering, for which we provide the direct booking-page fallback described below.

Nº 03

How we categorize

Categories in use today
Category	Needs consent?	In use?
Strictly-necessary (hosting, security, load-balancing)	No — exempt	Yes — Vercel + Next.js only
Functional (scheduler)	Disclosed; consent via choice to open scheduling	Yes — Cal.com only, on modal or booking-page click
Analytics (measurement)	Would require opt-in where applicable	None — no analytics cookies or pixels
Marketing / advertising	Would require opt-in and sale/share opt-out	None — no ad cookies or cross-context sharing

Rule going forward: we add no new category without updating this page and our Privacy Policy first and, where consent is required, obtaining it before the new storage fires.

Nº 04

Strictly-necessary — hosting

First-party / hosting storage
Source	Purpose	Basis & duration
Vercel hosting (brancle.com)	TLS termination, edge routing, load-balancing, abuse prevention, error logs	Legitimate interest + legal obligation; session to short-lived, server logs 90 days rolling per Privacy §9
Next.js self-hosted fonts & assets	Serve Inter, Fraunces, and JetBrains Mono plus images from our own build	Legitimate interest; no third-party requests to Google Fonts at runtime, no font cookies
Interface state (non-persistent)	Hold booking-modal open state and scroll-lock while the dialog is open	Legitimate interest; in-memory only, cleared on close — not a tracking cookie

These are exempt from consent because the Site cannot be served securely and reliably without them. They are never used for advertising.

Nº 05

Functional — Cal.com scheduling

Scheduling runs on Cal.com, Inc. Opening the “Book a call” modal loads https://app.cal.com/embed/embed.js and mounts a scheduler iframe for event type arqamwithbrancle/30min (layout month_view, light theme). Choosing “Open in new tab” instead navigates to https://cal.com/arqamwithbrancle/30min under Cal.com’s own pages.

Cal.com storage — domains and purposes
Domain	Purpose	What to expect
app.cal.com (embed + iframe)	Render availability, hold your selected slot, remember theme/layout, report ready/failed status	Cookies + localStorage set when the modal opens; required for dates to render
cal.com (booking page)	Same scheduling functions on the standalone booking page	Set when you visit the booking page directly; alternative if you block the embed

Exact names live with Cal.com

Precise Cal.com cookie names and durations are controlled by Cal.com releases and are versioned in Cal.com’s own cookie and privacy documentation, which controls for Cal-operated storage. We name the domains and purposes here and link to Cal.com’s current docs rather than printing names that would rot. Booking records we retain on our side follow Privacy §9 (24 months from the event).

Built-in avoidance: if the embed script is blocked (ad blocker, offline, disabled third-party storage), the modal stops spinning after 12 seconds and offers the direct booking-page link — same audit, no embed required.

Nº 06

What we don't set

Explicitly absent today
Category	Status
Analytics (Vercel Analytics, GA, PostHog, Clarity, Hotjar)	None — no pixels, beacons, or analytics cookies
Marketing (Meta, Google Ads, LinkedIn Insight, retargeting)	None — no ad cookies and no sale/share for behavioral ads
First-party tracking cookies via document.cookie	None — verified absent in our first-party code
Social widgets that auto-load	None — Upwork/LinkedIn are plain outbound links, no widgets

Because there is nothing to consent to beyond the scheduler you choose to open, we run no cookie consent banner. If we add measurement in the future, we will update this page first and introduce consent controls before the new storage fires.

Nº 07

Third-party links — nothing until you click

Upwork (agency profile), LinkedIn (company page), and mailto:hello@brancle.com are plain outbound actions, not embeds. They set no Brancle-controlled storage. Once you click through to Upwork or LinkedIn, or open your mail client, that provider’s own cookie and privacy notices govern.

Nº 08

Your choices — manage everything

Browser controls: block, allow per-site, or clear cookies and site data in Chrome, Safari, Firefox, or Edge settings. Blocking third-party storage for app.cal.com and cal.com prevents scheduler storage but may prevent dates from rendering — use the direct booking-page link instead.
Scheduler choice: don’t open the modal if you prefer zero Cal storage; email us at hello@brancle.com or use “Open in new tab” so only the booking page you chose sets storage.
Signals: we honor Global Privacy Control for any future analytics; Do Not Track is noted but has no consistent legal meaning for our current stack.
No account needed: there is no Brancle cookie preference account to log into — browser controls plus the choices above are complete.

Nº 09

How long storage lasts

Retention windows
Store	Window
Hosting / security logs	90 days rolling, longer only to investigate abuse (Privacy §9)
Modal interface state	Cleared on close (in-memory)
Cal.com embed / booking storage	Per Cal.com’s docs for Cal-operated storage; our booking-record copy 24 months (Privacy §9)
Privacy requests about cookies	36 months to demonstrate compliance

Nº 10

Changes to this Policy & contact

We update this Policy as the Site, scheduler, hosting, or law changes by posting the revised version with a new Effective date; added categories require an update here before the new storage fires. The current version always lives at https://brancle.com/cookies and is the companion to Privacy (Policy #1) and Terms (Policy #2).

Controller contact

BRANCLE TECHNOLOGIES LLC

212 N. 2nd St. STE 100, Richmond, KY 40475

Email: hello@brancle.com · Site: https://brancle.com

This Policy is provided for transparency and does not constitute legal advice. Cal.com storage is additionally governed by Cal.com’s own notices, which control for Cal-operated domains.

Cookie Policy with nothing to hide