Privacy

Who is responsible

Responsible party

VerdanTech (Pty) Ltd

Address

117 Stilgelee Ave, Die Wilgers, Pretoria, 0184, South Africa

Information Officer

Dennis Kriel

Information Officer's email

support@verdantech.co.za

Ask the Information Officer for a copy of what Forge holds about you, a correction or deletion.

What Forge keeps, why and for how long

• Your account

  Your name and email address, your password as a hash (never the password itself), your authenticator's secret and backup codes (encrypted), your passkeys' public keys and your notification switches.

  Why: so that only you can sign in, and Forge tells you what you asked it to.

  How long: while Forge runs. It is the only account, and Forge can't work without it, so it isn't offered for deletion.

• Sessions

  For each device you sign in on: its browser, its IP address and when you signed in. A password reset link you ask for works once, for an hour.

  Why: so you stay signed in, and can see and end your sessions on the Account page.

  How long: each session works for seven days from its full sign-in and isn't extended by use. Signing out deletes it at once. A session that simply runs out stops working, and its record is deleted soon after.

• Each project

  What Forge read from its repository (files, CI runs and the release check), your feedback draft, its role overrides and how its runs sign in, which settings are set or missing (never their values), its go-live ticks and the release you confirmed live, and its notification records.

  Why: so Forge can show what the factory is doing and what is waiting on you.

  How long: until you remove the project.

• The factory's runs

  Each command queued for the runner, the factory's event lines for it (the Activity feed and this month's usage), the answers you sent with it, and a job's files as the runner sent them.

  Why: so you can follow what the factory did and see this month's usage.

  How long: each run is deleted with its event lines 90 days after it ends, except a project's latest run, which stays until a newer one is queued. A job's files from the runner go once the job is on GitHub, or 90 days after they last changed. All of it goes when you remove the project.

• A new project's idea and attachments

  The idea you typed and the files you added on the New project form.

  Why: so the runner can start the project.

  How long: until the runner has them, or the command ends.

• Phone push devices

  For each device you turned Phone push on for: the address and keys its push service gave it, and its browser.

  Why: so notifications reach it.

  How long: until you turn Phone push off, or its push service says the device is gone.

• The audit log

  What was done in Forge, when and from which IP address, with project names, setting names, go-live item text and changes to how you sign in: passkey names and the browser of a device you signed out. Never a password, code, key or token, nor a setting's value.

  Why: so there is a record of who changed what.

  How long: each entry is deleted after 12 months.

• Backups

  Copies of Forge's whole database.

  Why: so Forge can be restored if something goes wrong.

  How long: nightly copies for 14 days on the server, the five latest copies taken before each update, and an off-server copy, where the owner has set one up, until the owner deletes it. Something removed from Forge stays in these copies until they roll over.

What Forge never keeps

• A setting's value: it goes straight to the app's server.
• An API key: it lives only in the runner's own settings.
• The GitHub token: Forge uses it to read, and never stores, logs or shows it.
• The runner's token: Forge keeps only a hash of it.

Who else processes it

• Hostinger runs the servers Forge and the runner work on, with Forge's database, its backups on the server and the runner's folders.
• GitHub holds the repositories Forge reads. Forge only reads them; it never writes to GitHub.
• Resend sends Forge's emails to you: password reset links, and notifications when Email is switched on. Until the server is set to send email, Forge writes them to its own log on the server instead.
• The push services of Google, Mozilla, Apple and Microsoft carry phone notifications to your devices, encrypted so they can't read them.
• Through the runner, Anthropic (Claude Code) and OpenAI (Codex) get the command, a new project's idea and attachments, and the project's files as the agents work.

Outside South Africa

These may keep or handle your information outside South Africa:

• Hostinger: Forge's server is in its data centre in Manchester, United Kingdom, and the runner's in Paris, France.
• GitHub: the repositories Forge reads.
• Resend: your email address and the emails Forge sends you.
• Google, Mozilla, Apple and Microsoft: phone notifications on their way to your devices, encrypted so they can't read them.
• Anthropic and OpenAI: through the runner, the command, a new project's idea and attachments, and the project's files as the agents work.
• Off-server backups: there are none yet.

Removing a project

Remove from Forge, at the foot of a project's board, deletes everything Forge holds about the project. The repository on GitHub stays untouched. The runner's folders on its machine (the project's checkout, and a new project's idea and attachments) stay too, for the owner to delete there. The audit log keeps its entries about the project for 12 months.