Privacy Policy
Last updated: October 20, 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. We measure website page visits and ad interactions through our API and Google Analytics regardless of your optional analytics-cookie choice. Web reports can include browser, session, and signed-in account identifiers. Older app versions send aggregate ad reports without those identifiers; our API forwards these reports to Google Analytics with a shared accounting identifier.
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 through our API to Google Analytics, even before you choose or after you reject optional analytics cookies. We use it to count distinct active browsers across selected date ranges. These requests also include standard request metadata, and may carry the sign-in and session headers used by our API. The event includes coarse country, device, and bot classifications. Clearing site storage resets the browser identifier; a new one is created on a later visit. Historical first-party records remain available for reporting.
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. Regardless of your analytics choice, Firebase Remote Config uses that identifier to assign your browser to product experiments and stores the assignment in your browser. We include experiment variants with these measurement signals and our first-party usage events. Google may derive coarse location from the network request. This automatic Google-tag traffic is separate from the product events 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.
5. Your choices
- Manage website analytics from the Cookie preferences card on the Privacy Policy page.
- Update your profile and marketing email preferences in account settings. Manage sales push notifications in the mobile app's sales filters. Account and security messages are separate.
- 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. To make a request, email [email protected] from the email address linked to your account. We may ask you to verify ownership before sharing or changing account data. Do not send passwords or sign-in codes.
6. Account deletion
Deleting your account removes your sign-in identity and account profile, builds, setups, public submissions, uploaded media, notification settings, notifications, favorites, and price alerts. We also request deletion of your RevenueCat customer profile. Shared links to deleted builds and setups stop working. Logs, backups, and records that providers must retain may remain where needed to operate and protect BuildCores or meet legal obligations.
If deletion fails, you will see an error and can retry. Some data may already have been deleted when an attempt fails. RevenueCat processes accepted deletion requests asynchronously.
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.
