Draft — these documents are being reviewed by a lawyer before launch.
On this page
- 1. Subject matter and duration
- 2. Nature, purpose, data and data subjects
- 3. Instructions
- 4. Confidentiality
- 5. Security of processing
- 6. Subprocessors
- 7. Transfers to third countries
- 8. Assistance
- 9. Personal data breaches
- 10. Deletion and return
- 11. Audits
- 12. Final provisions
- Annex 1 — Subprocessors (as of 2026-11-19)
- Annex 2 — Technical and organisational measures
- Annex 3 — Retention schedule
At a glance
- Version
- 2026-11-05-b
- Contact
- privacy@sends.at
Data processing agreement
Version 2026-11-05-b
This is the current version. To conclude it, an owner or admin of your workspace accepts it under Settings → Privacy & DPA; the PDF then contains your company details.
Data Processing Agreement
pursuant to Art. 28 of Regulation (EU) 2016/679 (GDPR) · Version 2026-11-05-b
| Controller (customer) |
[filled in when you accept] |
|---|---|
| Processor | sends.at – by Patrick Jarzabek c/o IP-Management #12088, Ludwig-Erhard-Str. 18, 20459 Hamburg, Germany Privacy contact: privacy@sends.at |
1. Subject matter and duration
1.1 The processor provides the controller with the sends.at service (short links, link health monitoring and fallbacks, analytics, QR codes, custom domains, landing pages and Link Hubs with media uploads, polls and interstitials, legal profiles, conversion measurement, integrations and related features) under the sends.at terms of service ("main agreement"). In doing so, the processor processes personal data on behalf of the controller.
1.2 This agreement applies for as long as the processor processes personal data for the controller under the main agreement. It ends automatically with the main agreement; clauses 10 and 11 continue to apply until all data has been deleted or returned.
2. Nature, purpose, data and data subjects
2.1 Nature and purpose: storing and redirecting links, hosting and delivering the controller's pages, checking link destinations, measuring and reporting clicks and page views, sending alerts and events to channels chosen by the controller, managing the controller's team, and billing.
2.2 Types of personal data: (a) account and team data: names, e-mail addresses, roles, sign-in and security data, audit log entries; (b) link and page data: destinations, titles, tags, page content, uploaded media, legal profiles and any personal data the controller puts into them; (c) click and view data: time, country, region, city, device type, browser and major version, operating system and major version, referring host and a category derived from it, QR marker, language, the country rule applied and, for personalised links, a pseudonymous contact ID, for conversion tracking a random click ID (sa_click); IP addresses and raw user agents are processed only in memory to derive these values and for a daily keyed marker of unique visitors, and are not stored; (d) billing data of paying customers.
2.3 Data subjects: the controller's employees and team members, persons who open the controller's links or pages, and contacts of the controller where personalised links are used.
3. Instructions
3.1 The processor processes personal data only on documented instructions of the controller, including with regard to transfers to third countries, unless required to do so by Union or Member State law; in that case the processor informs the controller before processing unless that law prohibits it. The main agreement, this agreement and the controller's use of the settings of the service are the controller's instructions.
3.2 The processor informs the controller without delay if it considers that an instruction infringes data protection law.
4. Confidentiality
Persons authorised to process personal data are committed to confidentiality or are under an appropriate statutory obligation of confidentiality.
5. Security of processing
5.1 The processor implements the technical and organisational measures described in Annex 2 (Art. 32 GDPR). They are part of this agreement.
5.2 The measures are subject to technical progress. The processor may replace them by adequate alternative measures provided the level of security is not reduced. Material changes are documented on the trust pages.
6. Subprocessors
6.1 The controller gives general authorisation to engage the subprocessors listed in Annex 1.
6.2 The processor informs the controller by e-mail at least 30 days before adding or replacing a subprocessor. The controller may object on reasonable data protection grounds within that period; if the parties cannot resolve the objection, the controller may terminate the affected services.
6.3 The processor imposes data protection obligations on each subprocessor that are no less protective than those in this agreement and remains liable to the controller for the subprocessor's performance.
6.4 Services the controller connects itself (for example its own CRM, chat or webhook endpoints) are not subprocessors; data is sent to them on the controller's instruction.
7. Transfers to third countries
All servers, databases and backups are located in Germany. Transfers to third countries take place only through the subprocessors in Annex 1 and only on the basis of an adequacy decision (in particular the EU-U.S. Data Privacy Framework) or the EU Standard Contractual Clauses.
8. Assistance
8.1 Taking into account the nature of the processing, the processor assists the controller by appropriate technical and organisational measures in responding to requests from data subjects (Chapter III GDPR). The service lets the controller access, export, correct and delete data itself; the processor forwards requests it receives directly to the controller.
8.2 The processor assists the controller in ensuring compliance with Art. 32 to 36 GDPR, taking into account the nature of processing and the information available to it.
9. Personal data breaches
The processor notifies the controller without undue delay, and where feasible within 48 hours, after becoming aware of a personal data breach affecting the controller's data, with the information available at that time (Art. 33(3) GDPR), and supports the controller in its notification duties.
10. Deletion and return
10.1 At the end of the main agreement the processor, at the controller's choice, deletes all personal data of the controller according to the retention schedule in Annex 3 or returns it, unless Union or Member State law requires storage. The controller exercises the choice of return by exporting its data in the service, which is possible at any time before deletion, or by request to the data protection contact.
10.2 Copies in backups are overwritten in the regular backup cycle and are not restored except to recover the service.
11. Audits
11.1 The processor makes available all information necessary to demonstrate compliance with Art. 28 GDPR, in particular this agreement, the annexes and the trust pages, and answers reasonable written questions.
11.2 Where that is not sufficient, the controller or an auditor bound to confidentiality may carry out an inspection after at least 30 days' notice, during business hours, without disrupting operations and not more than once a year, unless a personal data breach gives reason for it. Each party bears its own costs.
12. Final provisions
12.1 In case of conflict, this agreement takes precedence over the main agreement with regard to data protection. Liability follows the main agreement and Art. 82 GDPR.
12.2 Changes to this agreement are published as a new version; the controller accepts them in the service. This agreement is governed by German law.
Annex 1 — Subprocessors (as of 2026-11-19)
| Company | Purpose and data | Location and safeguard |
|---|---|---|
| Hetzner Online GmbH Industriestr. 25, 91710 Gunzenhausen, Germany | Hosting of our servers and of all databases and backups; storage of the images and logos customers upload (Hetzner Object Storage, Nuremberg) All data processed by sends.at | Germany (Falkenstein and Nuremberg) EU, GDPR applies directly |
| Hetzner Online GmbH — Hetzner Cloud Industriestr. 25, 91710 Gunzenhausen, Germany | One independent probe node that checks from outside our network whether link destinations are reachable Destination URLs of links to check (can contain personal data, e.g. in query parameters); nothing is stored on the node | Germany (Falkenstein) EU, GDPR applies directly |
| dogado GmbH Antonio-Segni-Straße 11, 44263 Dortmund, Germany | A second independent probe node that checks from outside our network whether link destinations are reachable; delivery and caching of the images and logos customers upload, under sends-at-usercontent.com Probe node: destination URLs of links to check (can contain personal data, e.g. in query parameters); nothing is stored on the node. Delivery: cached copies of uploaded images and logos, and the IP address of visitors who load them (for the connection; not stored in the access log) | Germany (Leipzig) EU, GDPR applies directly |
| Cloudflare, Inc. 101 Townsend St, San Francisco, CA 94107, USA | DNS for all sends.at addresses; TLS and protection against attacks for the dashboard and API. The website (sends.at), short links, Link Hubs, landing pages, media (sends-at-usercontent.com) and customer domains do not pass through Cloudflare. IP address, browser and requested address of our customers in the dashboard and API, in transit, plus Cloudflare's security logs. No data about visitors of your links | Global network, nearest data centre to the visitor EU-U.S. Data Privacy Framework and EU Standard Contractual Clauses |
| Stripe Payments Europe, Ltd. 1 Grand Canal Street Lower, Dublin 2, Ireland | Payments, subscriptions and invoices for paid plans Billing name, email, address, VAT ID and payment details of paying customers | EU (Ireland); transfers to Stripe, Inc. (USA) EU-U.S. Data Privacy Framework and EU Standard Contractual Clauses |
| Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA | Safe Browsing check of link destinations against phishing and malware Destination URLs of links (no visitor data, no account data) | USA and other Google locations EU-U.S. Data Privacy Framework |
Annex 2 — Technical and organisational measures
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.
Annex 3 — Retention schedule
| Data | Retention |
|---|---|
| IP address and raw user agent of visitors of your links | Never stored. Used in memory for the country and device, then discarded. |
| IP address in server logs of dashboard and API | 14 days, in memory only, never in a backup. |
| IP address in server logs of the website (forms, refusals, errors only) | 7 days, in memory only, never in a backup. |
| Sign-ins of an account (IP address, approximate place, browser family) | 14 days in the live system, database backups up to 7 days longer. |
| Unique-visitor marker (salted hash of IP and user agent) | Until midnight (UTC) of the same day; the salt changes daily. |
| Click analytics (single clicks and daily totals) | As long as your plan keeps history: 30 days (Free), 90 days (Starter), 1 year (Pro), 2 years (Agency), unlimited (Enterprise). Older clicks are deleted automatically. |
| Hourly totals | 35 days. |
| Conversion click ids (sa_click, only when the customer turned conversion tracking on) | As set by the workspace, 1 to 90 days (default 30); deleted at once when tracking is turned off. |
| Conversion totals (per link, campaign and day) | Like click analytics; single conversions are never stored. |
| Saved copies of landing pages (snapshot fallback) | One copy per link while the feature is on; deleted when it is turned off or the site forbids copies. |
| Images in the image library and QR code logos | Until you delete them; never deleted because of age. A deleted image goes to the trash (no longer delivered) and is deleted for good after 30 days or when the workspace or account is deleted for good. A replaced or removed QR code logo is deleted at once. |
| Cached copies of images and logos on the delivery server (sends-at-usercontent.com) | As long as there is room; the least recently used copies are removed first. When you delete or replace a file, its copy is removed from the cache at once. |
| Delivery server sends-at-usercontent.com: access log (without IP address, user agent, referrer or query string) and error log (can contain an IP address on individual errors) | 3 days. |
| Live view (clicks per minute, totals only) | 2 hours. |
| Saved analytics views (name and filter settings) | Until deleted by their author or with the workspace. |
| Deleted items in the trash (links, pages, domains and other workspace content) | Restorable for 30 days after deletion, then deleted for good. "Empty trash" and "Delete permanently" remove items from your view at once; they are deleted for good when the 30 days since deletion are over. |
| Guest links (without account) | 30 days. |
| Deleted account or workspace | Deactivated at once, restorable for 30 days, then deleted for good; an account is deleted together with the workspaces it owns alone. |
| Activity log (audit log) | Stored for 365 days on every plan, then deleted automatically. Shown to you as far back as your plan's activity log reaches: not included (Free), 30 days (Starter), 90 days (Pro), 12 months (Agency), 12 months (Enterprise). Origins are stored as a network range only, never as the full IP address. |
| Link health history | Single checks 30 days, daily summaries 400 days. |
| Preflight results | 90 days. |
| Beta requests and feedback messages | 12 months. |
| Application error logs | Up to 8 weeks. |
| Webhook and integration delivery logs | 30 days. |
| Exports (statistics, your data) | 7 days, then deleted. |
| Abuse reports | Reporter IP only as a network hash; reports kept while the link exists and 12 months after a decision. |
| Orders, accepted terms, withdrawals and cancellations | 6 years as commercial records (§ 147 AO), invoices 8 years; proof of a contract stays after the account is deleted. |
| Invoices and billing records | 8 years (§ 147 para. 3 AO, § 14b UStG); books and annual accounts 10 years. |
| Status page status.sends.at: access log (without IP address) and web server error log (can contain an IP address on technical errors) | Access log 14 days, error log 7 days. |
| Status page status.sends.at: email subscriptions to incident updates | Until you unsubscribe (deleted at once) or the address bounces for good; unconfirmed sign-ups 48 hours. Backups of the status server 14 days. |
| Backups | Being confirmed — published here before go-live. |
Questions about privacy: privacy@sends.at