privacy policy
1.0 — what we collect, and why
Everything below is collected because the build service can't function without it — that's the legal basis for all of it (performance of a contract, GDPR Art. 6(1)(b)). Nothing here is used for advertising, and nothing is sold or shared beyond what's listed in section 3.0.
- ·
GitHub identity
Your GitHub login, numeric ID, and email if GitHub shares it — from signing in.
- ·
GitHub access token
Encrypted at rest with a key unique to your account. Used only when you click "sync repos" to list which repos you've installed the forgeQueue GitHub App on.
- ·
Repo + build records
Repo name, your chosen CI branch, and per-build metadata (commit, status, logs, credits charged, timestamps).
- ·
iOS signing material, if you upload it
Distribution certificate, its password, provisioning profile, and an optional App Store Connect API key — each encrypted server-side with your account's key before it's stored. Plaintext exists only in a build worker's memory during your build, in a temporary keychain destroyed immediately after.
- ·
Credit balance
A number. Nothing else.
2.0 — cookies
One cookie: fq_session, httpOnly, used only to keep you signed in. No analytics, no advertising, no tracking. Because there's nothing non-essential, there's no consent banner — a banner with nothing real to consent to is worse than no banner (ePrivacy Directive Art. 5(3) exempts strictly necessary cookies from consent requirements).
3.0 — who else sees this data
- ·
Google Cloud / Firebase
Hosting, database, and the encryption key infrastructure. Data resides in us-central1.
- ·
GitHub
Your source code is read, and build artifacts are written back, via the forgeQueue GitHub App you install.
- ·
Apple
Only if you provide an App Store Connect API key — used to keep signing valid.
4.0 — retention
Build log text is cleared after 90 days; the build's status and metadata stay so your history still makes sense. Signing material, the GitHub token, and everything else is kept only while your account exists — deleting your account (5.0 below) destroys all of it immediately, including making previously-encrypted material permanently unrecoverable.
5.0 — your rights
Access and export your data, or delete your account and everything tied to it, any time from your account page — both are self-service, not a support ticket. You can also request correction of inaccurate data, or object to processing, by contacting us (see below). If you believe we've mishandled your data, you can lodge a complaint with your local data protection authority.