VibeForge Privacy Policy (draft)

Effective: 2026-11-08 (amendment announced 2026-11-01 — sign-in with AppRun added · amendment announced 2026-10-24 — screen-view records, project environment variables and job notifications added · amendment announced 2026-10-23 — GitHub sign-in, AI change records, public release records, AppRun integration, Google sign-in, email sign-in links, source upload and building from a folder on your PC) · Privacy contact: projectteamforyou@gmail.com

What we collect, why, and for how long

Email and display name — account and notices — deleted when you close your account.
GitHub account ID, login and profile picture URL (when you sign in with GitHub) — sign-in and account linking — deleted when you close your account.
GitHub App installation ID, installing account name and connected repository names — repository connection, push builds and pull requests — deleted when the installation or your account is removed.
API keys and worker tokens (hashes only) — authentication — invalid immediately on revocation; hashes kept 1 year for audit.
Worker PC facts (OS, CPU architecture, RAM, free disk, installed developer tool versions) — job matching — 90 days after the worker is revoked.
Job records (spec, state, logs, artifacts, checksums, checked-out commit) — running, verification, disputes — logs 90 days; artifacts until you delete them; state and checksum records 1 year.
AI change records (file contents and diffs changed by AI, AI usage and cost reported by your PC) — verification, pull requests, continuing auto-fixes — same period as job records.
Release records (signed manifest: project name, repository, commit, artifact checksums, quality result, worker PC name and OS) — public verification — until you delete them. Anyone with the release URL can view them.
Google account ID, email, name and profile photo URL (when you sign in with Google) — sign-in and account linking (the same email is one account) — deleted when you close your account.
AppRun account ID, email, name and language (when you sign in with AppRun — passed with your consent by Project Team For You, the same operator) — sign-in and account linking (the same email is one account) — deleted when you close your account.
The address a sign-in link is sent to and the one-time link (hash only) — sign-in and abuse prevention (3 emails per address per 10 minutes) — the link expires after 15 minutes; the record is deleted 1 day after expiry.
Source code you upload (ZIP), its hash, size and file count — building and source verification (the hash appears in release records) — kept until you close your account or ask us to delete it.
Project environment variables (names and values — values stored encrypted and never shown again) — passed to build and test commands on your PC (never to public workers or AI steps) — until you delete them or the project.
Job notification settings (on/off, webhook URL, signing secret stored encrypted, last delivery result) — sending failure/success emails and webhooks — until you turn them off or delete the project.
AppRun deploy token (stored encrypted) and AppRun app status (review result, rejection reason, 30-day run count — held in server memory for one minute to show in the console) — releases you trigger and post-release status — token deleted immediately when you disconnect; status is not stored.
Daily usage statistics (aggregate counts such as requests, visits and active users that do not identify you) — operating and improving the service — 2 years.
Screen-view records (screen name, date, the site you first came from, utm_source, desktop/mobile, language, signed-in or not, and a visitor hash valid for one day only) — no IP address, raw browser string or cookie is stored, and bots are discarded — visitor counts, referrers and sign-up funnel analysis — 90 days.
Credit ledger — settlement — 5 years as required by law.
Audit records (permission changes, security alerts) — security — 1 year.

We do not collect personal files, other running programs or the screen of your PC. Values that look like secrets are masked before logs are stored. We never receive or store your GitHub password, email or access tokens (the token used to confirm sign-in is discarded when that request ends).

About AI steps. AI tasks and auto-fixes run on your own PC with the AI tool you signed in to there (Anthropic's Claude Code, OpenAI's Codex). Your repository code and the instructions the server prepares (part of the build log, with secrets masked) are sent to that AI provider under your account, governed by the terms between you and that provider. VibeForge does not receive your AI accounts or keys and does not send data to AI providers itself. AI steps work only if the PC owner turns them on.

When you build from a folder on your PC, only the folder you choose is copied and built on that PC; the original files are never sent to our servers (only logs and artifacts are reported). When you upload a folder, the console leaves out node_modules, .git and .env files.

Processors and international transfer: Railway Corporation (USA, servers and database), Google LLC (USA, Google sign-in — only when you use it), Resend, Inc. (USA, sending sign-in and job-notification emails: recipient address and message — only when you use those features), Cloudflare, Inc. (USA, web console and artifact storage), GitHub, Inc. (USA, GitHub sign-in, repositories you connect, commit statuses, pull requests and releases — only when connected). When you click "Release to AppRun", artifacts and the signed release record go to Project Team For You (Republic of Korea, operator of AppRun — the same company). You may refuse the transfer, but the service cannot be provided without it.

Your rights: access, correction, deletion and suspension of processing — via account settings or the email above. You can pause or revoke a worker at any time.

Security: hashed tokens, TLS in transit, signed job specs, least privilege, audit logs, secret masking.

Changes: announced in the service 7 days before they take effect.