Your data belongs in the right places.
What BuildFuel stores, what is public, and what stays private.
Effective September 11, 2026Account information
ChatGPT sign-in supplies a site-specific account identifier and may supply an email address and display name. BuildFuel uses the trusted account identifier for access and ownership. The application does not store your ChatGPT password, session token, payment credentials, or AI-credit balance. Public profile names do not default to an email address.
Public content
Published project content, public profiles, milestones, build updates, and the public portions of confirmed support may be visible to anyone. Your settings control public following activity. Anonymous contributions do not publish the supporter’s identity. Bookmarks are always private.
Private delivery email
A creator may opt in to storing a private delivery email and preferred billing currency. The email is excluded from public pages, search, metadata, and normal project responses. It is intentionally disclosed only to authenticated supporters who start an eligible support flow. Access is rate limited and audited. Recipients of the disclosed email must use it only to deliver the intended gift.
Support, reports, and audit records
BuildFuel stores reported amounts, status, dates, visibility preferences, messages, and confirmation decisions. A creator can review support for their project; a supporter can review their own records. Private reports and moderation records are available to authorized administrators. Gift claim links are never requested and recognizable claim URLs are blocked before text is stored.
Hosting and measurement
Sites hosts the application, with Cloudflare D1 for structured records and R2 for project media. Basic first-party analytics record project views, shares, and sponsored-placement views and clicks using hashed account or browser-session identifiers. No third-party advertising tracker or external analytics vendor is enabled. External provider, product, and video links have their own privacy policies.
Ad campaigns
BuildFuel stores campaign creative, review decisions, status, and placement dates. Creators can view their own campaigns; administrators can review them. There is no checkout or payment collection during beta. Ad views and clicks use hashed browser-session identifiers, are counted at most once per session per day, and are estimates rather than independently verified people.
Browser storage and account access
Essential browser-session identifiers support basic measurement. Your sign-in email and recent account activity are stored separately from your public profile and are visible only to the platform administrator. ChatGPT handles sign-in; BuildFuel does not receive or store your password.
Retention and requests
Project, support, and account records are retained to operate the service and maintain an accurate support history. Audit and moderation records may be retained to investigate abuse or resolve disputes. Sign in and use Settings to request access, correction, deletion, or a privacy review. Requests are reviewed by the platform administrator; this page does not promise automatic deletion of records needed for legitimate operational obligations.
Your choices
Edit your public profile and notification preferences in Settings, hide individual support activity from Support, unfollow builds, remove bookmarks, and revoke delivery-email consent through a project’s Support settings. The platform does not sell your personal data.
Sign in to submit a privacy request or report an issue. Project reports are also available on every project page.