Security

Last updated 27 October 2026

What we do to keep accounts, payments and data safe, written for the people who review suppliers. Ask us if you need more detail for a questionnaire.

Where data lives

  • The platform runs on a server we operate in Amazon Web Services' Stockholm region (Sweden, EU). The database runs on the same server and accepts connections only from it.
  • The database is backed up every night; backups are kept for 7 days.
  • Every page and API call is served over HTTPS. Cloudflare sits in front of the site and connects to our server over a verified certificate.

Signing in

  • Partner and staff passwords are stored as argon2id hashes, never in readable form. Repeated wrong passwords lock the account for a while.
  • Two-step verification works with any authenticator app (Google Authenticator, Microsoft Authenticator, 1Password and others), with one-time recovery codes. It is required for Roamline staff, and a partner can require it for its whole team.
  • We email you when your account signs in from a device or country it has not used recently, and Settings lists every signed-in device with a button to sign it out.
  • Travellers on the shop have no password: they sign in with a six-digit code sent to their email, valid for ten minutes and for a few attempts only, or with their Google or Apple account where offered.
  • Sign-in, password reset and code requests are rate-limited.

Keys and secrets

  • API keys are shown once when created and stored only as hashes. Each key has its own permissions, can be limited to your IP addresses, and can be revoked at any time.
  • Authenticator secrets and webhook signing secrets are encrypted in the database (AES-256-GCM).
  • Our keys for suppliers and payment providers are kept in the server's environment, never in the database.
  • Every webhook we send is signed (HMAC-SHA256 with a timestamp), so your system can check it came from us, and is only sent to public HTTPS addresses.

Payments

Card payments run on Stripe's hosted checkout page: card numbers go straight to Stripe and never reach our servers. Stripe is certified to PCI DSS Level 1.

Records and access

  • Every staff action and every money movement (wallet, refunds, payments) is written to an audit log with who did it and when.
  • Each partner sees only its own eSIMs, orders and wallet; team members get one of five roles, from viewer to owner.
  • Travellers can download their data or delete their account themselves from Account → Settings.

Companies that process data for us

  • Amazon Web Services: hosting, Stockholm, Sweden.
  • Cloudflare: DNS and network protection in front of the site.
  • Microsoft (Microsoft 365): sending email.
  • Stripe: card payments.
  • Our eSIM suppliers (mobile operators and their wholesale partners): they receive the plan and our order number to issue each eSIM, not the traveller's name or email. Business customers can ask us for their names.

Certifications

We do not hold a SOC 2, ISO 27001 or PCI DSS certificate of our own. Card data is handled entirely by Stripe, as described above.

Reporting a problem

If you think you have found a security issue, write to [email protected] with “Security” in the subject. We answer every report and fix confirmed issues as a priority.