Privacy Policy
Last updated: September 16, 2026
This policy explains what information BuildCores LLC (“BuildCores,” “we,” or “us”) collects, why we use it, and the choices you have when using our website and mobile apps.
Quick summary
- We collect information you provide and information needed to run, protect, and improve BuildCores.
- Analytics cookies are on by default in the United States and off until accepted elsewhere. Limited Google measurement signals are sent without analytics cookies when cookies are off.
- We share information with service providers that help us operate BuildCores.
- You can manage cookies and notifications, delete your account, or contact us about your data.
3. Cookies, analytics, and advertising
We use essential cookies and similar storage for features such as sign-in, security, and preferences. Whether or not you accept optional analytics, we count basic website page views and ad interactions without cookies or an account, client, or session identifier.
Separately, our website stores a random browser identifier and the dates on which it reports activity. When the site is visible, we send this identifier and the active day to our own API, even before you choose or after you reject optional analytics cookies. We use it to count distinct active browsers across selected date ranges. The request may include the standard sign-in or session headers used by our API, but we do not store those identifiers in the activity record or join the browser identifier to them. Activity records include coarse country, device, and bot classifications, but not raw IP addresses, user agents, page URLs, or referrers. Activity records are retained for up to two years. Clearing site storage resets the identifier; a new one is created on a later visit.
Google Analytics loads on our website even before you choose or after you reject analytics cookies. In those cases, Google receives limited measurement signals without reading or writing analytics cookies, which it may use to estimate aggregate activity. These signals include page URLs, which can contain profile, build, or share identifiers. We remove known sensitive query parameters such as authentication tokens and email fields. We do not add a separate account or client identifier field to these signals. The Firebase SDK also stores a Firebase installation identifier in your browser; rejecting analytics cookies does not disable that SDK storage. Google may derive coarse location from the network request. This is separate from our basic first-party counts described above.
Analytics cookies and Microsoft Clarity are enabled by default in the United States; elsewhere, they stay off until you accept. A saved rejection takes precedence. You can change your choice in Cookie preferences below. Advertising storage, advertising user data, and ad personalization remain denied for our Google tag. Clarity can collect interaction data for heatmaps and session replay using cookies and similar technologies. We use that information to improve the site, understand product popularity, and support advertising. Learn more in the Microsoft Privacy Statement.
The mobile app uses Firebase Analytics to help us understand how the app is used. Playwire may provide website advertising and process data under its own privacy policy.
Cookie preferences
Not chosen
Choose whether to allow optional analytics cookies. We still count basic page views and send Google limited measurement signals without analytics cookies. Separately, BuildCores stores a random browser ID to count active browsers. This continues even if you reject optional analytics cookies.
5. Your choices
- Manage website analytics from the Cookie preferences card on the Privacy Policy page.
- Update profile, notification, and marketing preferences in your account settings.
- Delete your account from account settings.
- Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your data, or to object to or restrict certain uses. Email us to make a request.
6. Account deletion
Deleting your account deletes your sign-in identity, including your email, and removes your username, bio, notification settings, notifications, favorites, price alerts, and profile-image references. We also remove stored profile images when those cleanup steps succeed. An anonymized ownership record, builds, setups, custom media, other content you shared, logs, backups, or provider records may remain where needed to keep shared content working, operate and protect BuildCores, or meet legal obligations.
Deleting your BuildCores account does not cancel an active subscription. Cancel it through the app store or payment provider you used.
7. Retention and security
We keep information for as long as reasonably needed for the purposes described in this policy, including to operate and protect BuildCores and meet legal obligations. Retention periods vary by the type of information and the provider that handles it.
We use technical and operational safeguards intended to protect information, but no system is completely secure.
