Skip to content
Test mode · no real payments Test mode — no real payments Pay with a Stripe test card, for example 4242 4242 4242 4242, with any future date and any CVC.

Draft — these documents are being reviewed by a lawyer before launch.

Technical and organisational measures

The measures we take to protect personal data (Art. 32 GDPR). They are annex 2 of the data processing agreement.

Hetzner Online GmbH · Falkenstein and Nuremberg, Germany. A cluster of three dedicated servers, two in Nuremberg and one in Falkenstein; every virtual machine is replicated to both other servers every 15 minutes. Two independent probe nodes outside this network (Hetzner Cloud Falkenstein; dogado GmbH, Leipzig; both in Germany) only check whether link destinations are reachable and store no customer data. Images and logos that customers upload are stored in Hetzner Object Storage in Nuremberg and delivered only from sends-at-usercontent.com through a cache server of dogado GmbH in Leipzig, Germany.

On this page

At a glance

Hosting
Own servers at Hetzner, data centres Falkenstein and Nuremberg, Germany

Confidentiality

  • Servers in certified data centres of Hetzner Online GmbH in Falkenstein and Nuremberg with access control, video surveillance and 24/7 staff.
  • Administrative access only with SSH keys through a single bastion host; no passwords, no direct SSH from the internet.
  • Independent probe nodes outside our network (Hetzner Cloud Falkenstein; dogado GmbH, Leipzig; both in Germany) only receive the destination URLs to check and send back the result. They store no customer data, have no access to the database or cache, accept no incoming connections except SSH from the bastion host, and fetch their work signed over HTTPS.
  • Images and logos that customers upload are kept in a private bucket in Hetzner Object Storage (Nuremberg), read only through a separate local reader on the delivery server. They are delivered only from a separate domain, sends-at-usercontent.com, never from sends.at and not through Cloudflare (cache server of dogado GmbH in Leipzig, Germany): no cookies, a strict Content Security Policy with sandbox, X-Content-Type-Options nosniff, only GET and HEAD requests, no directory listings, TLS (Let's Encrypt). QR code logos are private and only reachable through signed links that expire after minutes. The delivery server accepts SSH only through our bastion host and runs with a firewall, SELinux in enforcing mode, automatic security updates and monitoring including disk space.
  • Databases and internal caches (Valkey) on an internal network that is not reachable from the internet.
  • Separate virtual machines per role (edge, app, redirects, worker, mail, database, cache).
  • Workspace isolation in every database query; members only see the workspaces they belong to, with roles (owner, admin, editor, viewer).
  • Passwords hashed with a modern adaptive algorithm; passwords known from data breaches are refused; two-factor authentication for every account.
  • API tokens with scopes, optional IP allowlist and expiry; integration tokens and webhook secrets encrypted at rest with a separate key.

Pseudonymisation and data minimisation

  • Visitor IP addresses and user agents are never stored; unique visitors are counted with a salted hash whose salt changes daily.
  • Analytics show values with fewer than 5 clicks only as a group ("<5 / Other") — in the lists and totals of the dashboard, exports and the API; the live view shows totals per minute, one minute behind. The export "Individual clicks" and the single-click API contain single rows without IP address or user agent.
  • Bots and link-preview robots are only counted per link and day, without any other detail.
  • Abuse reports store the reporter's network only as a hash.
  • Personalised links carry only a pseudonymous CRM record ID; the person behind it stays in the customer's CRM. The customer can assign such clicks to a known contact.
  • Conversion tracking (off by default) uses a random, single-use click id per click instead of cookies; it is kept only for the customer's chosen period, and conversions are stored as totals only, reported with the same "<5" rule.

Integrity

  • TLS for every connection from the internet (TLS 1.2 and 1.3 with modern ciphers, HSTS); connections between our servers run inside the private network; strict Content Security Policy.
  • Audit log of changes to links, members, domains, integrations and billing.
  • Outgoing webhooks signed with HMAC-SHA256; requests to internal or private addresses are blocked.

Availability and resilience

  • A cluster of three dedicated servers at two sites (two in Nuremberg, one in Falkenstein); every virtual machine is replicated to both other servers every 15 minutes, with a documented failover procedure.
  • Redirects keep working when the database is unavailable (snapshot cache); links never expire because of billing.
  • Monitoring of every server with alerts; protection against attacks for dashboard and API via Cloudflare. Website, short links and pages run only on our own servers in Germany; the images and logos on them come from sends-at-usercontent.com (dogado GmbH, Leipzig, Germany).
  • A public status page (status.sends.at) on its own server outside the cluster (Hetzner Cloud, Falkenstein), so we can report on an outage even when the cluster is down.

Regular testing and evaluation

  • Automated tests on every change (unit, feature, end-to-end and visual tests) and static analysis.
  • Security reports to security@sends.at are answered; see the security page for the disclosure policy.
  • These measures are reviewed at least once a year and when the system changes.

Organisation

  • Processing only on documented instructions of the customer (data processing agreement).
  • Personal data breaches are reported to affected customers without undue delay.
  • Deletion according to the retention schedule; data of deleted accounts is removed after the restore window.

Questions about privacy: privacy@sends.at