Privacy notice
This is the privacy notice for builtforprod.com. It is short because the site does very little: one contact form, analytics that only run if you allow them, and no tracking.
Scope and date
These are the terms for this website. If you are a BuiltForProd customer, how we handle data inside an engagement is governed by your customer agreement, not by this page. What the documentation site stores about a signed-in reader is described in its own knowledge base and privacy pages.
One principle runs through all of it: nothing that identifies you loads until you choose, and we never ask for more than we need to answer you.
What we collect, and why
| What | Which details | Why | On what basis |
|---|---|---|---|
| What you send us on the contact form | Your name, email address, and optionally your company and role; the topic you chose, your message, and a short note of how you reached the form (described below). The network address the message came from is passed to the customer record system with it. | To read your message, reply to it, and judge whether we are the right fit for what you need. | You chose to send it. Nothing on this site collects these fields any other way. |
| The email address you give to book a call | The address you enter on a Meet page, or in a booking form elsewhere on our sites, the kind of call you chose, and a short note of how you reached the page (described below). If you book, the name you give in the calendar and the time you picked. | To send the calendar invite and, if you stop before picking a time, one reminder about an hour later with a link back to the calendar and a way to write to us. At that same moment, and not before, the address is passed to the person who would have taken the call and recorded in our customer record system. Booking or sending a message before then cancels all of it; if you book, the calendar adds you to the customer record instead, with the name you gave it. | You entered the address to book a call. We send one reminder and never add the address to a list. |
| Page views, if you allow analytics | The page, the referrer, approximate location from the network address, and the kind of device. No name, no email address, no account identifier. | To see which pages help and which do not, so we write fewer useless pages. | Your consent, recorded in one cookie, which you can withdraw at any time. |
| Ordinary server and security logs | Request logs kept by our hosting provider, including network addresses, for delivering the page and blocking abuse. | To serve the site and to keep it available. These are operational records, not a profile of you. | Necessary to run the website at all. |
| Abuse limits on the forms | A count of recent sends and booking starts, kept against a one-way hash of the network address and of the email address, never against the address itself. | To stop a script from flooding our inbox or using the booking reminder to mail strangers. The contact form takes up to 4 messages an hour from one email address and 8 from one network address; after that it asks you to wait an hour or to email us directly. | Necessary to keep the forms available and to protect the people whose addresses could be misused. |
Do not send us secrets
The contact form is a web form, not a secure channel. Never send credentials, access keys, tokens, private key material or decrypted secrets through it, to us or to anyone else. If you need to share something sensitive during an engagement, ask and we will agree a proper channel.
Analytics, and the consent cookie
Analytics on this site is consent-first. Before you answer the banner, the analytics tag is not on the page
and your browser requests nothing from Google. If you decline, that stays true on every page. If you allow
it, the tag is added, with Google signals and ad personalization turned off, and your answer is stored in a
cookie named
bfp_consent on .builtforprod.com for
365 days, so one choice covers this site, the blog and the documentation. If you decline,
the same cookie records the refusal so we stop asking.
If you allowed analytics and change your mind, the button on the cookies page switches the tag off on that page at once and deletes its cookies. If your browser sends the Global Privacy Control signal, we treat that as a decision: analytics stays off, the banner does not appear, and an earlier grant is not used. Cloudflare Web Analytics, where configured, is a cookieless beacon and sets nothing in your browser.
Each page view carries at most three non-identifying dimensions describing which part of the site the page belongs to. It never carries a user, an email address or an organization identifier. The cookies page lists every cookie by name.
How you reached us
When you book a call or send a message, a one-line note goes with it saying how you got there, for example
page=/meet/; ref=/pricing/; cta=header; land=/; utm_source=newsletter: the page you booked or
wrote from, the page before it, which button you used, the first page of your visit, and any campaign tags (utm_source and the like) in the link that brought you. It tells us which pages lead to conversations. It holds nothing
that identifies you.
To build it, this site keeps the first page of your visit, its campaign tags and the page you were on last in your browser's session storage, which the browser clears when you close the tab. Nothing is sent until you give an address to book a call, or send a message. The note then travels with your booking or message to the people and processors named below, and is kept as long as the booking or message it belongs to.
Who processes your data
| Processor | What it does | What it sees |
|---|---|---|
| Cloudflare | Hosts and serves this site, runs the spam check on the contact form when it is enabled, and, where the site runs on Cloudflare, stores pending booking reminders and the abuse counters in its key-value storage. | Requests to the site, including network addresses; the contact form submission passes through it on its way to us; a pending reminder holds the address you gave, the call you chose, the note of how you reached the page and the network address it came from. |
| An email delivery provider | Delivers the contact form message to the BuiltForProd inbox that matches the topic you chose, and sends the one booking reminder. | The contents of your message and the address to reply to; for the reminder, the address you gave to book a call. |
| HubSpot | Records the enquiry as a customer record so it is not lost between people. It never decides whether your message reaches us. | Your name, email address, company, role, message, the topic you chose, the note of how you reached us and the network address it came from; for a booking you did not finish, the address you gave, the call you chose, that note and the network address it came from, passed on only when the reminder goes out; once you book, your name, email address and the meeting from the calendar. |
| Cal.com | Runs the booking calendar on the Meet pages (loaded in the background once the page has loaded, and shown once you give an email and continue), and sends the calendar invite and video link. | The email address you gave, the call you chose, the note of how you reached the page, and the name and time you enter in the calendar. |
| Google Analytics, only with consent | Measures page views. It never loads until you allow it, and it is not loaded at all on a deployment with no measurement id configured. | Page views with three non-identifying dimensions. Never your name, email address or organization. |
How long we keep it
- Your message. We keep it while the conversation is live and for as long as we have a reason to remember it, such as an engagement that followed from it. We delete it on request.
- The customer record, where one exists. Kept while you are a customer or an active prospect, and removed on request.
- A pending booking reminder. Kept by the website's own backend (in Cloudflare's key-value storage, or in a private folder on the web host, depending on where the site runs) and deleted when the reminder is sent, when you book or write to us, and in any case after 7 days.
- Abuse counters. Hashed, and they expire on their own: after an hour for the form limits, after 12 hours for the one-reminder-per-address limit.
- Analytics. Aggregated reporting data with no identifier attached to you, retained under the analytics provider's own retention settings.
- Server and security logs. Kept for a short operational period by the hosting provider and then rotated away.
What we do not do
- We do not sell personal data, and we do not share it with advertising networks.
- This site runs no tracking pixels, no advertising cookies and no cross-site identifiers. The one email we send you unasked, the booking reminder, goes out with our email delivery provider’s open and click tracking on: it carries a tracking image, and its links pass through the provider’s redirect.
- We do not build profiles of readers, and we do not make automated decisions about you.
- We do not load analytics before you say yes, and we honor the Global Privacy Control signal even if you said yes earlier.
- This site does not connect to your cloud accounts, your repositories or your data. It is a website.
Your choices
See what we hold
Ask, and we will tell you what is in the inbox and the customer record for your address. Write to [email protected].
Have it deleted
Ask us to delete your enquiry and any record of it, and we will do so and confirm, within 30 days. Write to [email protected].
Correct it
If we have your name, company or role wrong, tell us and we will fix it. This is usually faster than asking.
Change your analytics choice
Use the "Change your analytics choice" button on the cookies page, delete the consent cookie, or turn on Global Privacy Control in your browser, and analytics stops. The cookies page explains all three.
Who is responsible
BuiltForProd is a brand of Nexstella, which is responsible for the personal data described on this page. Questions, requests and complaints about privacy go to [email protected], with "Privacy" in the subject line so the request is handled as one.
If we change this notice we change the date at the top, and a change that affects what we collect will be announced on the site rather than made quietly.