Skip to main content

Privacy and data handling

This site stores three kinds of data about a reader: a sign-in session, the organization profile that admins fill in to personalize the pages, and page-view analytics that run only after consent and never carry an identifier. Nothing on this site connects to your cloud accounts, subscriptions or projects, and after handover BuiltForProd holds no credentials to them.

Sign-in and sessions​

Sign-in is handled by Clerk, a hosted identity provider. When you sign in, your browser holds a session cookie that the site's Cloudflare Worker verifies on every request to a gated page; the Worker reads your organization id, your role in it and the products the organization holds, and serves the page or redirects you to the public overview. Public pages need no session and are served to everyone.

Your account record consists of what you gave at sign-up: your email address and your name. Your organization record holds its name, its members and their roles, pending invitations by email address, the products it is entitled to, the cloud it runs on, and the profile values below. BuiltForProd staff create organizations and set their products when a purchase completes; organization admins invite members from the same email domain and change roles.

The organization profile​

An organization admin enters the values that replace the sample placeholders on every page. The profile asks only for the clouds your organization holds:

ValueExampleUsed for
Organization abbreviation and its upper-case formacme, ACMEResource names, SSO group names
GitHub organizationyour-github-orgRepository references
Primary domain and internal DNS zonecompany.com, internal.company.comZone names, hostnames
AWS home region and its slugus-west-2, usw2Region-specific names
The fifteen AWS account ids111111111111 through 151515151515, and 171717171717Account references
Azure home region and its slugeastus2, eus2Region-specific names
Azure tenant id and the fifteen subscription idsaaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa, 11111111-1111-1111-1111-111111111111Tenant and subscription references
GCP home region and its slugus-west1, usw1Region-specific names
GCP organization, billing account and customer ids161616161616, AAAAAA-BBBBBB-CCCCCC, C0aaaaaaaOrganization and billing references

These values are stored as public metadata of your organization in Clerk, are readable by every member of the organization, and are validated before they are saved. They are substituted in your browser when a page renders; the pages themselves, the search index and any screenshot contain only the sample values. Nothing is written to a page on the server with your values in it. An admin can change or clear the values at any time on the Organization profile page.

Analytics​

The site can run Google Analytics, and only when a measurement id is configured for the deployment. Its rules:

  • Consent first. Google Consent Mode defaults deny analytics storage before any tag loads. A banner asks once; your answer is stored in a cookie named bfp_consent for 365 days on .builtforprod.com, so one choice applies to every BuiltForProd site. Declining is as easy as accepting.
  • Global Privacy Control honored. If your browser sends the Global Privacy Control signal, analytics stays off even if consent was granted earlier.
  • No identifiers. Each page view carries three custom dimensions: which part of the web estate (docs), which documentation set, and whether the page is public or private. Never a user, an email address or an organization identifier. The banner says the same: it never receives your name, email or organization.
  • A cookieless complement. Cloudflare Web Analytics, when configured, is a beacon that sets no cookie and needs no consent.

Caching and indexing​

Gated pages are served with no-store and noindex, nofollow headers, so a shared cache never keeps a private page and a search engine never lists one. If the public layer is switched off for a deployment, the whole site is served as private.

What this site does not do​

  • It does not connect to your AWS accounts, Azure subscriptions or Google Cloud projects, your GitHub organization or your repositories. Personalization is text substitution in the browser.
  • It does not store your cloud credentials, keys or secrets. The account, tenant, subscription, organization and billing ids in your profile are identifiers, not credentials.
  • It does not share your organization's profile with other organizations. Membership is the only way to read it.

Credentials to your accounts​

Every edition of the Baseline is built so that no long-lived cloud credential exists for anyone:

  • AWS edition. People sign in through your IAM Identity Center with MFA; a service control policy denies IAM users and access keys in every member account. Pipelines authenticate through GitHub OIDC from your GitHub organization into your auto account; no AWS key is stored in GitHub.
  • Azure edition. People sign in with Microsoft Entra ID and receive Azure roles only through groups; an Azure Policy denies role assignments to individual users, and Conditional Access requires MFA once you move its policies from report-only to enforced. Pipelines use one federated managed identity per blueprint repository and stage, trusted only for your GitHub organization's repositories; no client secret exists.
  • GCP edition. People sign in with their Google identities, and the Baseline grants IAM roles to Google groups only. Pipelines use Workload Identity Federation limited to your GitHub organization, and organization policies block the creation and upload of service account keys.

The BuiltForProd team deploys the Baseline into your cloud and hands over the repositories; after handover, human access exists only through the groups your administrators control.

If you engage BuiltForProd Managed, its engineers work through those same groups and pipelines, and access ends when you remove them. The shared responsibility model draws the full line; the security posture summary lists the controls that enforce it. Questions about how the platform handles your own data (encryption, retention, who can read what) are answered on that page and in the security FAQ.