Singapore region first
Databases, files, self-hosted workflows and backups for client projects stay in Singapore unless you agree otherwise in writing.
Security & data
You’re trusting us with customer conversations, internal documents and business processes. Here’s exactly how we protect them, in plain language.
Where your data lives
Anything we host for you runs in the Singapore region of a major cloud provider: Amazon Web Services, Google Cloud or Microsoft Azure. Prefer your own cloud account or servers? We build there instead, so your data never leaves infrastructure you control.
Databases, files, self-hosted workflows and backups for client projects stay in Singapore unless you agree otherwise in writing.
Self-hosted n8n and custom code can run entirely inside your own cloud account or data centre, under your own security policies.
If a service you need only runs overseas, such as a particular AI model, we tell you before we build, and the transfer is covered by contract terms that keep the data protected to a comparable standard, as the PDPA requires.
AI providers
We use the business and API services of established AI providers, such as OpenAI, Anthropic and Google, whose commercial terms exclude customer data from model training by default. We never use your data to train shared or public models, including our own.
Before we build, we tell you in writing which AI provider and model each automation uses, and where it processes data.
Automations send a model only what the task needs. Where possible, names, IDs and contact details are removed or masked before anything leaves your systems.
We switch on the shortest data-retention settings each provider offers, including zero-retention options where they’re available.
For confidential or regulated data, we can use a private model trained or hosted for you alone, so it never touches a shared service.
How we protect it
In transit with TLS 1.2 or higher, and at rest with AES-256 on every database, file store and backup we manage.
Each automation can reach only the specific data and actions its one job needs. Nothing gets a broader export “just in case”.
Keys and passwords live in an encrypted secrets vault and are supplied only when an action runs, so revoking one cuts access everywhere.
Every account our team uses to reach client systems is protected by multi-factor authentication and a password manager.
Only the people working on your project can reach your data. We review access every quarter and remove it the day someone leaves a project.
Every permission is enforced on the server, not just hidden behind a button, so access can’t be bypassed.
New automations run supervised: actions wait for your team’s OK until you’re confident they can run on their own.
Every run is recorded with when it ran, what triggered it and exactly what it did.
A kill switch your team controls, quick undo on reversible actions, and instant rollback to the last working version.
We keep the systems we manage patched, and back them up automatically so we can restore quickly.
Retention
We keep personal and business data only as long as the project needs it. On request, we confirm deletion in writing.
| What | Covers | How long |
|---|---|---|
| During the project | Only the data each automation needs, in the Singapore-hosted environment for your project, or in your own systems. | Until handover |
| Copies we hold after handover | Sample files, exports and test data used while building. | Deleted within 30 days of handover |
| Encrypted backups | Point-in-time backups of anything we host for you. | Expire automatically within 90 days |
| Activity logs | Records of what each automation did and when. | 12 months by default, or as you choose |
| Anything on your infrastructure | Workflows, code and data on servers or accounts you own. | Yours: kept or removed on your instructions |
If something goes wrong
No system is risk-free. What matters is how fast and how openly a problem is handled.
Standards
Our practices follow Singapore’s Personal Data Protection Act (PDPA), the PDPC’s advisory guidelines on using personal data in AI systems, and IMDA’s Model AI Governance Framework.
We design automations to collect only what a task needs, use it only for that purpose, protect it, and keep it only as long as it’s needed.
Questions about how we handle personal data go to help@wunderwaffen.co, and reach the person responsible for data protection at WunderWaffen.
We don’t display certifications we don’t hold. If your procurement team needs evidence against ISO 27001 or SOC 2 controls, we’ll work through your questionnaire control by control.
For security teams
Send your questionnaire or requests to help@wunderwaffen.co, or book a call and talk it through.
Related: Privacy Policy · Cookie Policy · Website Terms
Questions
Yes. Many clients ask for one before sharing details of their processes, and we’re happy to sign before the discovery call.
Only the people working on your project, and only what the project needs. Automations themselves get the same least-privilege access: just the data their one job requires.
Yes. Self-hosted workflows and custom code can run on servers or cloud accounts you control, so your data stays where your policies say it should.
We delete the copies we hold, such as sample files, exports and test data, within 30 days of handover, and encrypted backups expire within 90 days. We confirm deletion in writing on request. Anything built on your own infrastructure simply stays with you.
No. We use the business and API services of AI providers whose commercial terms exclude customer data from training by default, and we never use your data to train shared or public models, including our own.
In the Singapore region of a major cloud provider by default, or inside your own cloud account if you prefer. If a service you need processes data overseas, we tell you before we build.
Yes. We notify your named contact within 72 hours of confirming an incident that affects your data, and support you with any PDPA breach notification you need to make.
Yes. Send it to help@wunderwaffen.co.
Free consultation
Explore how AI can automate your most complex workflows. No obligation, just a clear plan for what to automate first.