Skip to main content
Skip to content

Security & privacy

How SAVIE protects your crew data

Crew data is personal data. This page says openly where it lives, who processes it and which measures we use. No badge promises, just what we can back up today.

Last updated: 25 September 2026

Where the data lives

  • The application runs on servers of Hetzner Online GmbH in Germany.
  • Backups are also stored with Hetzner in the EU.
  • SAVIE is hosted software (SaaS). We don't currently offer installation on your own hardware.

Access and accounts

  • Passwords are stored only as bcrypt hashes, never in plain text.
  • Sign-in attempts are rate limited to slow down password guessing.
  • Anyone can turn on two-factor authentication (TOTP, e.g. Google Authenticator, Microsoft Authenticator or 1Password) for their own account.
  • Admins decide per workspace whether 2FA is optional, required for admins, or required for all office accounts.
  • Roles separate admins from dispatchers, and each company only sees the data in its own workspace.

Technical measures

  • All connections are encrypted over HTTPS.
  • The database is not directly reachable from the internet.
  • Credentials for integrations (easyjob, Rentman, Eventworx) and calendar connections are stored encrypted.
  • Access to personal data is logged.
  • Security-relevant account changes, such as turning 2FA on or off, are logged.

Access, export and deletion

  • Everyone can export their own data from SAVIE themselves (GDPR Art. 15 and 20).
  • Deleting your own account can be started directly in the app (GDPR Art. 17).
  • When a contract ends, we return or delete customer data at the customer's choice, as set out in the data processing agreement.

Backups and availability

  • Backups are kept separate from the running application and deleted on a documented rotation schedule.
  • We don't currently offer a fixed SLA. Our B2B terms say the same.
  • Details on backup interval and recovery are available on request.

Data processing agreement

  • The data processing agreement under GDPR Art. 28 is annex A of our B2B terms. You don't need to request it separately.
  • We announce new subprocessors at least 30 days in advance, and you can object on reasonable grounds.

Subprocessors and providers

These providers take part in processing. The binding register is in the data processing agreement.

ProviderPurposeLocation
Hetzner Online GmbHApplication hosting and backups in the EUGermany
helloly GmbHService emails (e.g. invitations, booking notifications)Austria
GoogleOnly when Google sign-in is usedInternational, see privacy policy
StripePayments and subscriptions on paid plansInternational, see privacy policy

Documents

Found a security issue?

Please report it directly and confidentially by email. We reply personally and fix confirmed issues as quickly as we can: support@savie.cc

Common questions

Is SAVIE open source?

No. SAVIE is hosted software, and the source code is not public.

Can we run SAVIE on our own hardware?

Not as a product today. We handle updates, database migrations and backups centrally. If your IT or privacy policies require self-hosting, write to us and we'll discuss what's possible.

Where is our data stored?

On servers of Hetzner Online GmbH in Germany, with backups also in the EU.

Is there a data processing agreement?

Yes. The GDPR Art. 28 agreement is annex A of the B2B terms and applies automatically with the contract.

Can we require two-factor authentication for everyone?

Yes. Admins choose per workspace whether 2FA is optional, required for admins only, or required for all admins and dispatchers.

What happens if SAVIE goes down?

Services restart automatically and data is backed up regularly. There is no fixed SLA today. If something is wrong, you can reach us directly at support@savie.cc.

Your next production

Let's work through a real job.

Bring a typical crew requirement. We will show you how matching and booking fit your workflow.

Book a demo