Skip to content

Privacy policy

Updated 20 September 2026

This policy describes the Build Order Timer website and Android application operated by Build Order Timer. It matches the software as shipped: a local-first timer. It does not invent collection that the app does not perform.

Who we are

Build Order Timer helps you run a timed build order — typically during a StarCraft II game — from a phone or desktop. Contact: buildordertimer@outlook.com. Website: https://build-order-timer-rsug.vercel.app.

No accounts

There is no sign-up, no sign-in, and no cloud profile. We do not operate a user database. Builds you create stay on the device you use.

Data stored on your device

The app stores the following locally in your browser or Android WebView (IndexedDB and localStorage):

  • Build orders you create, import or edit, including action titles, times, icons and optional images.
  • Preferences such as voice, beep, warning lead time, wake-lock and reduced motion.
  • Optional run history (date, duration, build name) if you leave that setting on.
  • A short in-progress timer snapshot so a refresh mid-game can resume.
  • Whether you dismissed the install tip, and your advertising consent choice if ads are enabled.

This data does not leave your device unless you export a backup file yourself, or unless you later enable a third-party service described below.

Permissions

  • Notifications — only if you turn them on in Settings, used for due-action alerts while the tab is hidden.
  • Screen wake lock — optional, keeps the timer visible during a run.
  • Network — needed to load the app the first time and, if enabled, to show ads or send crash/analytics events.

The app does not use the camera, microphone, contacts, location or files except when you choose to import/export a JSON backup.

Optional advertising

Advertising is off by default. If it is turned on in a later release, the website may load Google AdSense and the Android app may load Google AdMob. Those services may use advertising identifiers, cookies or similar technology as described in Google's own policies. Ads are not shown on the live timer screen.

When ads are enabled you can accept or decline them in the in-app banner. Declining stops the app from requesting ads. It does not control cookies Google may already have from other sites.

Optional analytics and crash reporting

If a measurement or crash reporting key is configured in production, anonymous events such as “timer started” or uncaught errors may be sent so we can fix bugs. These events do not include your build contents. If those keys are not configured, nothing is sent.

Children

Build Order Timer is not directed at children under 13. We do not knowingly collect personal information from children.

Retention and deletion

Local data remains until you delete a build, clear run history, or clear this site's storage in your browser or by uninstalling the Android app. There is no server copy to erase on request because none is kept.

Changes

If the app starts collecting new categories of data, this page will be updated before that change ships.