What this site does with your data.

The Workflow Cost Scan form collects your name, work email, company and website, revenue and employee bands, role, optional workflow description, assessment-funding answer, and executive sponsor details when relevant. We store the application and its eligibility result, notify our team, and link a resulting booking to that application. Directors and applications needing clarification are reviewed before we share booking access.

We also record limited first-party usage of the scan: page visits, button clicks, whether the form or its Continue button appears in view, whether the page stays visible for 10 or 30 seconds, form starts, which fields have a nonempty valid entry (without the entry itself), validation categories, saved submissions, eligibility outcomes, and opening the calendar. These records use a temporary random identifier for that page visit, a fixed campaign bucket, and a page-version label. They do not contain your contact details, form answers, or a full browsing URL, and opening the calendar is not recorded as a confirmed booking.

We also keep coarse country and, within the US, state, an approximate device category, and a fixed referral-source category. Country and state come from our hosting provider; device type is derived from the request and the raw User-Agent is discarded. We do not add raw IP addresses, full referrer URLs or form answers to these usage records. These breakdowns describe page loads, not identified or unique people.

The page-visit identifier is held only in page memory in your browser, rather than a cookie or local storage. Usage records are retained for 90 days. We honor Global Privacy Control and Do Not Track for this collection. These operational records are separate from optional Meta advertising measurement; accepting Meta cookies is not required to use the form.

Advertising measurement on that page is optional and off until you open Privacy choices at the bottom of the scan page and choose Accept in Cookie preferences. Those controls open within the page and do not appear automatically. If accepted, the Meta Pixel can send page visits and qualified applications to Meta and may set Meta advertising cookies. When the server integration is configured, we also send events for qualified applications and confirmed bookings with a hashed email address, available Meta browser/click identifiers, and the browser user agent. Hashing supports matching; it does not make the email anonymous. Workflow answers, company revenue, and sponsor details are excluded from those events. We keep delivery status for troubleshooting and deduplication.

Global Privacy Control and Do Not Track disable browser advertising measurement and advertising measurement for new applications. You can submit the form and book an eligible scan without allowing it. A functional cookie, fs_ads_consent, remembers your Accept or Decline choice for up to 90 days. Use Privacy choices on the scan page to change it; declining stops browser measurement and measurement for new applications, and clears the Meta identifiers we can access. A previously submitted application retains the measurement choice made at submission, including for its confirmed-booking event. To withdraw that application's permission before a later event is sent, email info@foresightaipartners.com. Changing the browser choice does not remove events previously sent or subscribe you to marketing email. The existing Calendly privacy terms apply when you choose a booking time.

When you visit, we may set one first-party cookie, fs_attr. If you later submit the contact form or book a call, it lets us credit that to the marketing channel that first brought you here — for example, a search result, a link from an AI assistant, or a paid ad — rather than guessing.

It holds:

• a random id generated for your browser, not tied to your name or any account;
• how you arrived — a broad category (organic search, a referral from an AI assistant, paid, partner, direct, or unknown), the domain of the site that referred you (not the full URL), the five standard campaign parameters if your link included them (utm_source, utm_medium, utm_campaign, utm_content, utm_term), the page you landed on, and a timestamp — captured once for your first visit, and again for the most recent visit that came from somewhere other than typing our address directly or clicking a link on our own site;
• the id, position, and page path of the last button or link on this site you clicked, if any.

It's read by this site's own script, in your browser, and by our own server when you submit the contact form or start a booking. That's what lets the submission be credited correctly. We don't send its contents to any advertising network, and we don't currently send it to any other analytics service either.

It's Secure (sent only over HTTPS) and SameSite=Lax, and expires automatically after 90 days.

Small, functional items live in your browser's session storage (cleared when you close the tab, and never sent to our server on their own):

• a note of whether the cookie check above said you're in a restricted region, kept until you close the tab, so we don't have to ask again during the same visit;
• if you fill out the contact form or scan application, a random id stored under a fingerprint of what you typed, so that retrying after an interrupted send doesn't record your message twice. The contact form's key is removed after a successful send. The scan application's retry key remains for the tab's session and is replaced when application details change.
• after a qualified scan application, only its Calendly scheduling link and an expiry time, so you can resume choosing a time after reloading. This record lasts at most 60 minutes, or less if the server booking link expires sooner. It contains no name, email address, form answers, or advertising event IDs. It is removed on expiry or when you choose Start a new application; it does not confirm a booking.

• If your browser sends Global Privacy Control or Do Not Track, we honor that and don't set the cookie at all.
• If we detect you're visiting from the European Economic Area, the United Kingdom, or Switzerland, we don't set this attribution cookie either. The scan page's separate Meta measurement choice does not enable this first-party attribution cookie in those regions.

Either way, the contact form and booking flow work exactly the same. We simply won't know which channel to credit.

Contact form

The name, company (if you give one), email, subject, and message you type, plus whatever attribution snapshot described above existed in your browser at that moment, the page you submitted from, and the time.

We also compute a salted hash of your email address, the same way as the IP hash below. We use it only to limit how many messages we accept from the same address in a short window (currently 5 every 10 minutes).

Booking a call

Clicking a “Book a call” button takes you straight to Calendly — there's no separate booking page in between. At that moment, our server creates a random token and passes it to Calendly along with fixed tags saying the visit came from our website and which offer it was for. Only that token and those tags leave our server; the attribution snapshot itself never does — it stays on our side, stored against the token.

For Workflow Cost Scan bookings, our team checks the Calendly confirmation and manually links the confirmed time to your application and its captured marketing source. Opening the scheduling link does not count as a confirmed booking. Reminders, cancellations, reschedules, and attendance are handled manually under our current Calendly plan.

The Calendly notification itself

Where a Calendly webhook integration is enabled for another booking flow, we can also store the underlying booking notification. That automatic integration is not enabled for the current Workflow Cost Scan. Depending on what you entered while scheduling, a notification can include:

• your answers to the booking questions;
• a phone number, if you gave one for text reminders;
• your timezone;
• the cancel/reschedule links; and
• the host and guest email addresses on the event.

It falls under the same retention as below — we don't yet have an automatic deletion schedule for it either.

Your IP address

Our application never stores your raw IP address. We compute a salted, one-way cryptographic hash of it, using a secret held only on our server. We use that hash only to apply reasonable limits on how many submissions we accept from the same visitor in a short window. Separately, our hosting provider's standard request logs do contain IP addresses, the way any web server's do.

Internal notes

After a call happens, our team may add internal notes to that record — for example, whether the conversation was a good fit and what stage a resulting engagement reached.

• The attribution cookie: gone from your browser automatically after 90 days.
• A booking token that never turns into an actual scheduled call: the token itself expires after 30 minutes, and the unused record is deleted automatically 30 days after that.
• Submitted contact-form messages, completed bookings, and the underlying Calendly notification: we don't yet have an automatic deletion schedule for these. Formal retention periods are still being finalized. Contact us at info@foresightaipartners.com to ask about or request deletion of your data.

• Vercel hosts this site and runs the servers that handle every request.
• Convex is our database — it stores the inquiry, booking, and attribution records described above.
• Resend sends our team the email notification when you submit the contact form.
• Calendly runs the scheduling itself: “Book a call” sends you to Calendly's own site (calendly.com), and the calendar, invite, and reminder logic are Calendly's. Calendly may set its own cookies on its site. Anything you enter there, and any cookies it sets, are subject to Calendly's own privacy policy, not this one.

The Workflow Cost Scan page additionally offers the optional Meta advertising measurement described above. Other pages do not load that Pixel through this integration.

Email info@foresightaipartners.com with any question about this page, or to ask about, correct, or request deletion of information we hold about you, and we'll get back to you.