Updated 4 October 2026

Security

What protects your data, what we have checked, and how to tell us about a problem.

In short

  • Two-step sign-in with recovery codes, open to every account
  • No IP address stored, ever
  • Payment-provider keys and backups encrypted with AES-256-GCM
  • Servers in Amsterdam (EU), backups in the EU
  • Open source, with security checks on every change
  • Found a problem? legal@trckable.com, within three working days

Sign-in#

  • Email code, or an existing account; no passwords in Cloud
  • Two-step with an authenticator app (TOTP), on any account
  • Eight recovery codes, each works once
  • A two-step code signs in once; a replayed code is refused
  • Trusted devices for 30 days, stored only as a hash and forgotten when two-step changes
  • Admin pages need two-step, and a fresh emailed code for every destructive action
  • Single sign-on through your own identity provider (OIDC): coming

Data#

  • No IP address stored: used in memory while a request is handled, never written to a log, database or disk
  • Payment-provider keys encrypted at rest with AES-256-GCM
  • Two-step secrets encrypted, recovery codes stored as keyed hashes
  • Card details never reach us
  • Nightly backups, encrypted with AES-256-GCM before they leave the server, kept in the EU
  • A deleted account leaves our backups within 30 days of its deletion
  • Read-only API keys can read your numbers and never change anything

Hosting#

  • Servers in Amsterdam (EU)
  • HTTPS everywhere, with HSTS and a strict content security policy
  • Session cookies are HttpOnly, Secure and SameSite
  • Every company that handles data is in the DPA and the privacy policy

The application#

  • Open source: AGPL-3.0 server, MIT tracker, on GitHub
  • On every change: gofmt, go vet, golangci-lint (with gosec), govulncheck and pnpm audit
  • Dependency updates every week, grouped into a few pull requests
  • The npm package is published with a provenance statement

The audit#

  • Version 0.2.0 (25 September 2026) came out of a full security audit of the code
  • Fixed: one-time passwords limited to choosing a new password, owners unable to reset other owners, JSON-only sign-in, rate limits on password and two-step, more blocked address ranges for webhooks, and API keys and viewers kept from alert destinations
  • Version 0.3.0 followed with more: two-step codes that work once, encrypted two-step secrets and private database files
  • Every release lists its security fixes in the changelog

Reporting a vulnerability#

  • Email legal@trckable.com, or use GitHub's private reporting
  • Say what you found, how to reproduce it and what someone could do with it
  • You hear back within three working days, and we keep you updated until it is fixed
  • No paid bounty; we credit you when the fix is out, if you like
  • In scope: trckable.com, docs.trckable.com, Cloud and the open-source software
  • Out of scope: denial of service, brute-forcing, social engineering, services run by others, and reports that only say a header could be stricter
  • Safe harbour: research in good faith within this scope, with your own data, and telling us first, will not be met with legal action
  • security.txt

Where data lives#

WhatWhere
Your analyticsServers in Amsterdam (EU)
BackupsEncrypted, in the EU
EmailA dedicated email service
PaymentsOur merchant of record, never your analytics
Peek questionsAn AI service, only when you ask
  • 30 days' notice before a sub-processor changes

Accessibility#

  • WCAG 2.1 AA, checked with axe-core in three browsers on every change

Continuity#

  • Full export as one file within 7 days of asking
  • Restores on your own server with trckabled restore (self-host)
  • 90 days' notice before any shutdown

More#

Start free