Trust center

What we do with your data, and what we don't.

The facts behind SwengleIO's security and reliability: where data is kept, how it is encrypted, who can reach it, how it is backed up and what happens when something fails. Where something is not in place, we say so.

Documents and contacts

Sub-processors

Every provider that processes customer data for us, what it does and where.

Sub-processor list

Security and reliability

The product's guarantees in short: durable messages, isolation, the availability levels, account security.

Security and reliability · Status

Security reports: security@swengle.com. Data processing and privacy: privacy@swengle.com. Everything else: support@swengle.com.

Infrastructure and data locations

SwengleIO runs in Swengle's own accounts with the cloud providers below; nothing runs in your cloud account. You pick an endpoint's region when you create it, and it stays there for its whole life.

RegionCloudMessages and backupsEncrypted off-site backup copies
aws-eu-central-1 (Frankfurt, Germany)AWSIn the regionEuropean Union, guaranteed
aws-eu-west-2 (London, UK)AWSIn the regionEuropean Union, guaranteed (in the EU, not the UK)
aws-sa-east-1 (São Paulo, Brazil)AWSIn the regionEastern North America, a preference, not guaranteed
aws-us-east-2 (Ohio, USA)AWSIn the regionEastern North America, a preference, not guaranteed
gcp-asia-northeast1 (Tokyo, Japan)Google CloudIn the regionAsia-Pacific, a preference, not guaranteed
gcp-europe-west2 (London, UK)Google CloudIn the regionEuropean Union, guaranteed (in the EU, not the UK)
gcp-europe-west3 (Frankfurt, Germany)Google CloudIn the regionEuropean Union, guaranteed
gcp-us-east1 (South Carolina, USA)Google CloudIn the regionEastern North America, a preference, not guaranteed
oci-eu-frankfurt-1 (Frankfurt, Germany)Oracle Cloud InfrastructureIn the regionEuropean Union, guaranteed
oci-uk-london-1 (London, UK)Oracle Cloud InfrastructureIn the regionEuropean Union, guaranteed (in the EU, not the UK)
oci-us-ashburn-1 (Northern Virginia, USA)Oracle Cloud InfrastructureIn the regionEastern North America, a preference, not guaranteed

Encryption

In transit

At rest

WhatHow it is encrypted
Disks on Google Cloud, Oracle Cloud Infrastructure and Microsoft AzureEncrypted by the cloud provider, always, with keys the provider manages.
Disks on AWSEvery disk we create asks for encryption with the region's AWS-managed key, and each region also encrypts new disks by default. This was put in place in November 2026: disks created before it were not encrypted, and AWS cannot encrypt a disk in place, so they are encrypted by replacing their machines.
BackupsEncrypted before they are written to storage (libsodium), with a key per database that a machine is given only for the database it backs up or checks. The cloud's storage also encrypts them at rest.
Off-site backup copies (Cloudflare R2)Copies of the already-encrypted backups, so Cloudflare holds only ciphertext and never the key. Each region's key is kept with the copies only sealed to a recovery key that Swengle holds offline.
Secret keysA secret key is shown once, when it is created; nobody can show it again, Swengle included.

Not offered

Access control

Your organization

Swengle staff

Backups and recovery

Dedicated and Cluster have an availability level that you choose; Shared always has the highest. What each can lose (recovery point) and how long it takes to serve again (recovery time) are by design, not commitments:

LevelIf the database host is lost, it losesServing again
No backups Cowboy mode the default for a new Dedicated or ClusterEverything: the endpoint comes back emptyMinutes, on a new host
Daily backups Safety net recommendedEverything since the newest full backup, up to about a dayMinutes, restored onto a new host
Continuous backups Flight recorderAt most about the last minuteMinutes, restored onto a new host
Replicated database Co-pilotNothing acknowledged, while the replica is in syncAutomatic failover (below)
Zone outage protection Twin engines, and SharedNothing acknowledged, while the replica is in sync, even if a whole zone is lostAutomatic failover (below)

Availability and failover

The five availability levels decide what a failure does. The numbers below are what we have measured in our tests, not commitments; design clients to ride out a pause, which the libraries do on their own (they retry publishes with the same idempotency key and resume subscriptions from their cursors).

Database failover
A replicated database host that stops reporting for 15 seconds is failed over to its synchronous replica, losing nothing acknowledged. On a Dedicated cluster at Zone outage protection, publishes and deliveries pause for about 15 to 25 seconds when its host alone is lost. On a Dedicated cluster at Replicated database, the standby host takes over and clients reconnect to it. A zone outage that also takes Swengle's regional control database in that zone, which fails over first, can pause publishes and deliveries for up to about 80 seconds, and a Dedicated cluster at Replicated database, whose clients reconnect, for up to about two minutes: in zone outage tests on our staging regions the longest pause in publishes was about 76 seconds at Zone outage protection and about 95 seconds at Replicated database. On a Cluster and on Shared, relay hosts stay up and clients stay connected while the database switches.
Without a replica
A lost host is replaced automatically and, with backups, restored: minutes of downtime, during which the endpoint shows Degraded.
A zone outage
With Zone outage protection, on every Cluster that has it, on Dedicated where offered and on every Shared endpoint, the other zone keeps serving.
Planned changes
Updates, operating system patching (on our regular schedule, during our maintenance windows) and new host sizes lose nothing at any level. Clients of an updated relay reconnect at once and resume; when a Cluster's relay host is replaced, deliveries pause for well under a second. Moving an endpoint up a plan pauses its publishes for about a second while it switches.
The Console
Changes in the Console pause for a few seconds (about 5) when its database switches to its standby, for example for patching. Running endpoints are not affected.

We don't publish or promise an uptime figure. A committed service level needs a separate agreement.

Incidents and status

Vulnerability management

Compliance and agreements