Builder Army Back to the count

privacy, plainly

Privacy
Policy.

Effective: August 29, 2026
Version 1.0

Builder Army counts builders without turning private account data into public content. This Policy explains what we collect, what the world can see, and the choices you have.

Who controls your data

Builder Army is the controller of personal data processed through this service. Privacy questions and rights requests can be sent to hello@builderarmy.com.

Data we collect

When you sign in with Google or GitHub, we receive basic identity information made available under the permissions shown by that provider, which may include your provider account ID, name, email address, username, and avatar.

When you claim a number, we collect your name, email address, profile picture, optional X handle, builder role, location, assigned builder number, join date, and any project names, website URLs, or logo URLs you choose to add. For aggregate visitor statistics, we store a randomly generated browser identifier, first and last visit times, and a visit count. Realtime Presence temporarily indicates that the browser is connected while the page is open. We may also process basic technical and security information such as authentication events, device or browser data, and error logs.

What is public

Public profile information: your builder number, name, profile picture, optional X handle, role, location, join date, and submitted project names, links, and logos may appear in the public builder directory, count, and share card.

Private account information: your email address, authentication identifiers, provider tokens, security records, and random visitor identifier are not included in the public directory. Only aggregate online and total visitor numbers are displayed. Access to private database records is restricted through authentication and row-level access controls.

How we use data

  • to authenticate you and assign one persistent builder number;
  • to operate the global count, directory, and share-card tools;
  • to prevent duplicate accounts, fraud, abuse, and security incidents;
  • to support users, debug problems, and improve the service; and
  • to comply with law and enforce our Terms.

Depending on where you live, our legal bases include performing our agreement with you, our legitimate interests in running and securing Builder Army, your consent where requested, and compliance with legal obligations.

Sharing and service providers

We use Supabase for authentication and database infrastructure. Google and GitHub process information when you choose their sign-in options. Google may also receive a submitted public project domain when its favicon service is used to suggest that project's logo. If you choose to share on X, your browser opens X with a suggested caption; the image is copied or downloaded on your device, and you decide whether to attach and publish it.

We may also disclose information when required by law, to protect rights and safety, during a business reorganization, or to vendors that process data for us under appropriate obligations. We do not sell your personal information or share it for cross-context behavioral advertising.

Device storage

Builder Army and its authentication provider use browser storage needed to keep you signed in, remember join intent, distinguish a browser for aggregate visitor counting, and operate the service. In an unconfigured demo or local preview, signup records may be stored only in that browser. We do not currently use third-party advertising cookies.

Retention

We keep account and profile information while your builder record is active and for a reasonable period afterward where necessary for security, dispute resolution, legal compliance, and backups. We may retain a minimal record of an assigned number to protect the integrity of the count. Data that is no longer needed will be deleted or anonymized.

Your choices and rights

You may ask to access, correct, export, or delete your personal data. Depending on your location, you may also have rights to restrict or object to processing, withdraw consent, and complain to your local data protection authority. You may disconnect Builder Army from your Google or GitHub account through that provider's account settings.

Send requests to hello@builderarmy.com. We may need to verify your identity before acting on a request.

International transfers and security

Our providers may process data in countries other than yours. Where required, we rely on recognized transfer mechanisms and contractual protections. We use reasonable technical and organizational safeguards, but no internet service can guarantee absolute security.

Children

Builder Army is not directed to children under 16, and we do not knowingly collect their personal data. If you believe a child has submitted information, contact us so we can review and remove it.

Changes

We may update this Policy when the product, providers, or legal requirements change. We will post the revised version here, update the effective date, and provide additional notice when a change is material.

© 2026 BUILDER ARMY
MADE BY BUILDERS, FOR BUILDERS.

TermsPrivacy