Last updated: 6 October 2026
The controller is the operator of pagerdeck.com:
Gonzi Tech UG (haftungsbeschränkt) An der Mannsfaust 10 60599 Frankfurt am Main Germany Phone: +49 69 247422680
The authorised representatives and the register details are stated in the imprint.
For questions about data protection and to exercise your rights: privacy [at] gonzi [dot] tech.
Appointing a data protection officer is not required by law and none has been appointed.
PagerDeck receives alerts from monitoring systems and delivers them to your devices as push notifications. The sender only proposes an urgency. Which alert level results from it is decided by a rule chain that lives in your account.
For those rules to match, the service has to read the content of an alert: a rule on title, body or tags cannot be applied without knowing title, body and tags. That is the purpose of this processing rather than a side effect, and it is the reason alert content is held unencrypted on the server.
If you sign in with Apple, we additionally store the refresh token issued by Apple, encrypted. Its only purpose is to revoke the link at Apple when you remove it or delete your account; for that it is sent to Apple and deleted afterwards.
For every alert the following is stored: title, body, tags, an optional URL, the urgency proposed by the sender, the alert level decided from it, the key the sender supplied for collapsing repeated alerts, and the times of arrival, acknowledgement and resolution.
What those fields contain is determined by the system that sends the alert, not by PagerDeck. Whoever writes personal data into alert texts has it processed through this service; responsibility for choosing what is sent lies with the sending party.
For every paired device the following is stored: the platform, a device name you choose, the time of pairing and, where a push service is used, its delivery address.
On Apple devices that is a device token issued by Apple, and delivery runs through the Apple Push Notification service. Apple receives the content of the notification in the process, that is the title and body of the alert.
In the browser, delivery runs through Web Push. On Android devices it runs through UnifiedPush and the built-in distributor of Google Play services, that is also through a Google web push endpoint. In both cases the payload is end-to-end encrypted per RFC 8291: the push service sees the delivery address (push endpoint), the time and the size of the encrypted packet, not the content of the alert.
On the desktop, delivery does not run through a push service: the Windows app holds the connection to PagerDeck open itself. No delivery address of a third party is stored for it, and no third party sees the alert. What is stored is the device together with its session and the delivery record.
For systems that only speak email, every source can be given its own intake address under in.pagerdeck.com. When a message arrives there, PagerDeck processes the sender address, the subject, the body and the technical headers of the delivery.
These intake addresses are credentials and are treated as such: the database holds only their hash, and the plaintext is shown exactly once. Each address can carry a list of permitted senders.
The email intake is active by default in Business and Team. In case of abuse the team can withdraw it for an account. We store the time, the reason and who made that decision, as well as the time of any renewed request (Art. 6(1)(b) and (f) GDPR).
Payments are handled by Stripe. Payment details such as card numbers never reach PagerDeck; they are entered at Stripe and processed there. PagerDeck stores the Stripe customer identifier, the plan booked and its term.
Invoices are subject to statutory commercial and tax retention periods and remain stored for as long as those require, independently of any account deletion.
The server logs requests with IP address, time and the route called. This serves to detect faults and abuse, such as large-scale guessing of credentials.
In addition PagerDeck keeps a change history of writing operations in an account: who changed which rule, source or setting, and when. It is a security feature. Without it there would be no way to establish afterwards whether a rule came from you or from somebody else.
No data is passed on beyond this. No data is sold, and there are no advertising networks.
A transfer to third countries takes place insofar as Apple, Cloudflare, Stripe and, where you sign in through them, GitHub, Google and Microsoft process data in the United States. It rests on the Standard Contractual Clauses of the European Commission and, where the recipients are certified, on the EU-US Data Privacy Framework.
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20), as well as the right to object to processing based on legitimate interests (Art. 21).
You can download a copy of the data PagerDeck stores about you personally as a JSON file at any time yourself, under Settings, Your data.
For everything else, write to privacy [at] gonzi [dot] tech.
Independently of this you have the right to lodge a complaint with a data protection supervisory authority.
The competent authority for PagerDeck is:
Der Hessische Beauftragte für Datenschutz und Informationsfreiheit Postfach 3163 65021 Wiesbaden Germany Phone: +49 611 1408-0 Email: poststelle [at] datenschutz [dot] hessen [dot] de
Independently of that you may address the supervisory authority of your place of residence or work.
To find faults in the website, PagerDeck uses Unseenr, a service operated by Gonzi Tech UG (haftungsbeschränkt) - the same company. The data therefore stays in house and on servers in Germany; beyond the Cloudflare network named above, no further processor is involved.
Without your consent, none of this is transmitted. If you agree to the fault diagnosis category, what is needed to investigate a fault goes to Unseenr: the error message and its stack, the address you were on, the time, the browser type, the window size, the page language and the version of the application. Ingest keys, mail aliases, session cookies and access tokens are redacted before anything leaves your browser. The legal basis is your consent under Article 6(1)(a) GDPR together with section 25(1) TDDDG.
Fault diagnosis also covers measurements of how fast the page loads, such as how long the largest element takes to appear. They contain nothing about you personally, only numbers and the path of the page.
While you are signed in, the account number is attached to an error so that we can match a report to you if you get in touch. Your email address is not part of that.
On the error page you may voluntarily write to us about what happened. What you enter there goes to the same system and is used only to fix that fault. An email address is optional and is used only to reply to you.
Your decision is stored locally in your browser and is not transmitted to the server. You can change it at any time with effect for the future; the button at the end of this page and the cookie settings link in the footer of every page do exactly that. Error reports are deleted after 90 days. Your session is not recorded; PagerDeck does not capture what you do on the page.
PagerDeck sets technically necessary cookies: for the signed-in session, for the chosen language, for the state of a sign-in in progress through an external provider, for an open device pairing, for dismissing the billing notice and, when you open the website from the app, for 24 hours as a marker that no purchase prompts are shown there. They are required for operation and therefore need no consent. The language choice sits in a cookie and is sent with every request, because the page is rendered on the server in the chosen language. Colour scheme and your decision about the optional services, by contrast, stay in your browser and are not transmitted to the server. Without that decision, PagerDeck loads no optional service.
If you agree to audience measurement, it sets a cookie to recognise your browser; the next section describes it. There is no cross-site tracking: the cookie belongs to this website and is read by no other.
PagerDeck measures how often the public pages are opened, where visitors come from and which steps they take in the application. We run an instance of the Vemetric software ourselves, on the same server rented from Hetzner Online GmbH in Nuremberg, Germany, that previously ran the earlier solution. This adds no further processor for the measurement itself: Hetzner already hosts PagerDeck's servers and is named in the list of subprocessors. The route there, however, runs through Cloudflare's network, as every request to this website does; the measurement data passes through that network and is readable there.
Without your consent nothing is measured. If you agree to the audience measurement category, the following is recorded: the page you opened, the referring address, the UTM parameters used, browser type, operating system, device type and the length of your session. In addition, clicks and individual steps are counted, including in the signed-in area: clicks on sign-up, download and purchase buttons, registration, sign-in, pairing a device, creating a source, and the start, completion and cancellation of a purchase. These steps are linked to the same pseudonymous identifier (_vuid) as the page views, without name, e-mail address or account identifier, and likewise only with your consent. To attribute page views within a visit and across several visits to the same browser, Vemetric sets a cookie named _vuid. It contains only a randomly generated identifier, no name and nothing else about you personally, and stays valid for about 13 months. The IP address reaches the measuring instance for this and may appear in its logs and in those of the layers in front of it; it is not stored in the measurement data itself. No location is currently derived from the IP address. The measurement data is deleted automatically 24 months after it was collected. The legal basis is your consent under Article 6(1)(a) GDPR together with section 25(1) TDDDG.
The script and the measurement data travel over addresses of this website rather than a foreign domain. That changes only the route they take, not what is collected.
You can change your decision at any time with effect for the future, using the button at the end of this page or the cookie settings link in the footer. If you withdraw, PagerDeck deletes the _vuid cookie immediately, sends no further calls to Vemetric and does not set the cookie again.
If the processing changes, this policy is updated. The date above states when it was last changed.