Zazitek

Trust

This is the operating standard. It describes what is in place today. It does not list a certification we do not hold.

Where the data sits

The server is a Hetzner machine in Singapore. Each customer’s n8n and its database are separate from the next customer. The customer portal shows one customer. An admin can see the customer list.

Who can sign in

There is no public sign-up. An owner signs in with email, a password, and an authenticator app. Mail for that login is sent through Resend from login@auth.zazitek.com.

What is kept

Runs are stored with the tenant. A deletion function can remove runs older than 13 months. Nothing schedules that deletion yet. A failed new run emails Zazitek. A repeat of the same failure does not send another email.

Backups

Backups are not in place. The product shows last backup as not recorded. There is no recovery-time figure to publish.

When something breaks

n8n is checked every five minutes. The first time it is down, Zazitek is emailed. It is not emailed again while it stays down. The public status page is a separate monitor. This site links to it only after that monitor has a name of its own.

Subprocessors

  • Hetzner. The server in Singapore that runs the app, n8n, and the databases.
  • Resend. Sends login mail, failure notices, and the monthly report.
  • OpenRouter. The model call for an agent that needs one. The model name and cost are stored on the run.
  • Namecheap. The domain registrar.
  • Let’s Encrypt. The certificates on the public hostnames.

Dokploy is the software on our server that runs the containers. It is not a vendor holding a copy of customer data.