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 AWS accounts, 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:
| Value | Example | Used for |
|---|---|---|
| Organization abbreviation and its upper-case form | acme, ACME | Resource names, SSO group names |
| GitHub organization | your-github-org | Repository references |
| Primary domain and internal DNS zone | company.com, internal.company.com | Zone names, hostnames |
| Home region and its slug | us-west-2, usw2 | Region-specific names |
| The fourteen account ids | 111111111111 through 151515151515 | Account 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_consentfor 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. Sample sets are public but noindex. 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, your GitHub organization or your repositories. Personalization is text substitution in the browser.
- It does not store your AWS credentials, keys or secrets. The account 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
The platform is built so that no long-lived AWS credential exists for anyone:
- 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
autoaccount; no AWS key is stored in GitHub. - The BuiltForProd team deploys the Baseline into your accounts and hands over the repositories; after handover, human access exists only through the Identity Center 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.