Trust and security
1. In short
Guildwise HQ lets AI agents do real work, so it is built around control: you decide what an agent may touch, you can see everything it did, and a person approves the steps that matter.
2. Agents run in a sandbox, on your machines
Agents do not run on our servers. They run on a workstation, a VPS or a GitHub Codespace that you control, through the small runner program you install. Each run works in its own checkout, and the sandbox allows only what the card needs: the project's files and the network hosts you have approved. A tester, for example, may reach exactly the address you configured and nothing else.
3. Secrets stay on your workstation
Passwords, API keys and tokens that agents use are kept in a vault on the workstation. Guildwise HQ does not store the values and its server never sees them. When you type a credential for an agent, your browser sends it to the runner over an encrypted channel, end to end, and the server only relays sealed data it cannot read.
4. Every action is recorded
Everything that happens is written to an append-only event log: who or which agent did what, and when. Cards, approvals, budget changes, role changes and sign-ins are all in it. The log is kept for the life of your organization, and it is the answer to "who approved that?".
5. People approve what matters
Workflows can require a person before work moves on. A card is not finalized without an approval, manual QA steps are done by a named person, and agents ask on the decision desk instead of guessing when they are unsure. Budgets stop runs that would spend more than you allowed.
6. Data handling
- Your organization's content (cards, transcripts, vault metadata, repository information) is kept apart from every other organization.
- We do not sell your data, and we do not use your organization's content to train any model.
- Passwords are hashed, two-factor login is available and can be required, and authenticator seeds are encrypted at rest.
- Traffic to and from the service is encrypted in transit.
- Retention periods and your rights are in the Privacy policy and the POPIA notice.
7. Where data is hosted
The service is hosted with Namecheap in Phoenix, Arizona, United States. Because that is outside South Africa, personal information is transferred to the United States; the POPIA notice explains the safeguards. Source code and secrets of your projects stay on your own workstation and are not hosted by us.
8. Who we use (sub-processors)
- Namecheap: hosting of the servers and database (Phoenix, Arizona, United States).
- SendGrid: sending e-mail (invitations, notifications, briefings) and receiving e-mail for the inboxes of organizations and for our support address.
- Paystack: payments and invoices. Card details are handled by Paystack; we keep only a token, the card brand, last four digits and expiry date.
Model providers
Agents use the model provider and account you connect. Your data goes from your workstation to that provider under your agreement with them; Guildwise's servers do not send it anywhere.
| Provider | Used for | Whose account | What happens to data | Terms |
|---|---|---|---|---|
| Anthropic | Your agents (Claude Code, running on your workstation) | Your account, connected on your workstation | Sent from your workstation to Anthropic under your agreement with them | Anthropic commercial terms |
| Anthropic | Guildwise's landing-page assistant and blog writer | Guildwise's platform key | No customer data: only public product information and visitors’ questions | Anthropic commercial terms |
We will update this list when it changes. The Privacy policy explains how providers process data and how transfers are protected.
9. Report a concern
If you think you have found a vulnerability, or have a security question, write to us through Contact us. We will answer, and we will tell affected customers and the Information Regulator of a breach as the law requires.