Skip to content

Search

Privacy Policy

What balaurengine.org and Balaur Cloud keep about you: your account, your projects and builds, your signing keys and store logins, and how long each is kept.

balaurengine.org and Balaur Cloud are run by Dragos Daian (appsinacup). This page lists what we keep, why, and for how long.

The engine and the editor are yours to run. They send us nothing. This page covers the website and the cloud builds.

What we keep

  • Your account. Email, display name, and the ID of any provider you sign in with, such as GitHub.
  • Your projects. Name, settings, the repository and branch to build, and the engine version.
  • Your builds. Status, targets, timings, logs and the files a build produces.
  • Your GitHub installation. Which account or organisation installed the Balaur GitHub App, and which repositories it can reach.
  • Your signing keys and store logins. Certificates, keystores, passwords and API keys for Apple, Google Play, itch.io and the other stores you publish to.
  • Your hosted games. The web builds you choose to host, and the address they are served at.
  • Reports you send. What you write, the page it is about, any screenshot, your browser and screen size.
  • Network data. Your IP address, for security, rate limits and abuse prevention.

What we read from GitHub

The GitHub App asks for:

  • Repository contents, read only. A build checks out your code.
  • Metadata, read only.
  • Checks, read and write. A build reports its result on your commit.
  • Email addresses, read only. Used to link the installation to your account.

A build reads only the repositories you connect to a project.

How your code is handled

  • Your code runs in an isolated sandbox, one per build target.
  • The checkout is deleted when the build ends.
  • Signing keys never enter the sandbox. A build is signed after it leaves.
  • Imported assets are cached by a hash of their bytes. A cache entry holds the processed asset, never your name or project.

How your secrets are stored

Signing keys, store logins and store settings are encrypted at rest. Each one is bound to its owner and its field, so a copied value cannot be read under another account. We read a secret only to sign or publish a build you asked for.

How long we keep it

  • Builds and their files. Deleted 30 days after the build ends.
  • Build logs. Kept with our server logs, which rotate.
  • Reports. Deleted 180 days after they are closed.
  • Banned IP addresses. Kept until the ban expires or is lifted.
  • Everything else. Kept until you delete it or your account.

Data deletion lists what goes when you delete your account.

Cookies

Cookies and local storage hold your session, sign-in, security tokens, theme and dismissed banners. We use no analytics, advertising or tracking cookies.

Who else processes it

  • GitHub. Sign-in, and the code a build checks out.
  • Our server host. Stores builds, hosted games and the cache.
  • Cloudflare. Human verification on sign-up and sign-in forms.
  • Stripe. Payments, when you pay for a plan or hosting.
  • The stores you publish to. Apple, Google, itch.io and others receive the build and your credentials for them.
  • An email provider. Sign-in links and account messages.
  • Error monitoring. Crash reports from our servers.

Their own privacy policies apply to what they receive.

Your rights

You can see, correct, export or delete your data:

We reply within 30 days.

Changes

We change this page when what we keep changes. The date below is the last change.

Last updated: 21 October 2026.

Biztos vagy benne?