All posts
CommunityThe Garmingo Team

EU hosting and GDPR by default

How Garmingo Status and Garmingo Voice handle data in the EU: worldwide checks, on-device voice, RAM-only cloud, and no training on your content.

privacygdpreu

Privacy is not a feature toggle at Garmingo. It is the baseline we design around before we ship a monitor, a status page, or a single line of dictation code.

We build in Germany and host in the European Union because operational and personal data should not be an afterthought. If you run Garmingo Status for uptime or Garmingo Voice for speech on your desktop, this is how we think about GDPR, storage, and what never leaves your control.

One company, two products, same rulebook

Garmingo Status and Garmingo Voice solve different problems, but they share the same privacy posture:

  • Process in the EU unless you explicitly choose otherwise (enterprise only).
  • No opaque retention. We say where data lives and what happens to it.
  • No training on your content. Your uptime history and your voice are not model fuel.
  • Your rights by default. Export or delete account data from account settings.

The details differ because the products do different work. Here is how each one handles it.

Garmingo Status: monitored worldwide, stored in Europe

Status teams need two things that sound contradictory until you separate them: checks that run close to your users and a record of those checks that stays in Europe.

That is exactly how Garmingo Status works. Monitors can run from global check regions so you see latency and availability where it matters. Your uptime data, incident timelines, status page content, compliance reports, and team activity are processed and stored in Germany, within the European Union. We do not replicate that data to regions outside the EU.

What that means in practice

  • Monitors and incidents live in your EU-hosted workspace. Timelines, maintenance windows, and subscriber lists stay there too.
  • Compliance reports (uptime SLAs, incident counts, maintenance history) are generated from EU-stored data. Useful for regulated teams that need a paper trail without a surprise region.
  • Integrations (Slack, Teams, email, webhooks, and the rest) receive the alerts you configure. The source of truth remains your EU-hosted Status account.
  • Custom domains and branding on status pages do not change where the underlying data is stored. Your page can look like yours; the ops data still stays in Europe.

Our mindset for Status is simple: monitored worldwide, saved only in Europe. Your uptime data stays yours. Read more on the Status product page or in the Status docs.

Garmingo Voice: your machine first, EU cloud when you opt in

Voice is a desktop app. That changes the privacy story in a good way. Most of what you do every day never needs the network at all.

On-device by default

Voice enhancement, system-wide dictation, and local meeting capture run on your machine. With on-device models, audio does not leave your computer. That matters for confidential notes, patient documentation, legal drafts, and any workflow where uploading raw audio feels wrong (because it is).

You sign in once to activate your license. After that, on-device dictation and transcription keep working offline for several days before a quick recheck. The AI itself does not need a constant connection for core workflows.

When you choose the cloud

Optional cloud features exist for speed and capacity: cloud transcription, cloud dictation, Composer in the cloud, and AI chat on your transcripts. When you use them:

  • Processing happens in the EU.
  • Audio is not persisted. Cloud transcription is RAM-only: processed in memory and discarded the moment the job finishes. Nothing is written to our disks.
  • We do not train on your voice or transcripts. Neither do our inference partners, for the workloads we use.
  • Cloud credits power these features. On-device work never touches them.

There are no tracking pixels and no hidden analytics in the Voice app. Privacy is not optional. It is the core mindset. See the full picture on /voice or in the Voice docs.

Shared infrastructure and account data

Across both products, account data, billing metadata, and product telemetry stay in EU regions unless an enterprise agreement explicitly configures otherwise.

We do not sell your data. We do not use your Status incident history or your Voice recordings to improve models for other customers. Billing is handled through secure checkout (Stripe). Tier limits are hard caps, so privacy and pricing stay predictable.

If you have a question we have not answered here, write to hello@garmingo.com. For product-specific setup, start with the docs or pick the product that fits your work:

Made in Germany. Hosted in the EU. Built for teams that want calm software and a clear answer to where their data lives.