The Ordivis Platform runs on your servers. Your operational data — tickets, configuration items, user accounts — stays there and is not processed by us. At exactly three points, processing by Grams IT nevertheless takes place. This page names all of them, including where the answer is uncomfortable.
a) Online licence activation. Your installation checks in with our activation service at regular intervals. It transmits the licence number, a fingerprint of the installation, the product version in use, the technical contact address stored in the licence and the sender IP address. The purpose is to verify the licence and to be able to inform you if a vulnerability is being exploited (Article 14 of the Cyber Resilience Act). Any personal reference arises at most through the technical contact address.
b) Delivery of push notifications to the Android app. If you use the app, delivery runs through our push relay and from there through Google’s Firebase Cloud Messaging. Transmitted are the device delivery token, the title and short text of the message and the target it opens in the app. The details of the ticket do not travel with it — the app fetches them from your own interface once the notification is tapped.
c) Support. Whatever you send us for troubleshooting — logs, extracts, screenshots — we process for as long as the case is open. What it contains is your decision.
This situation is not new and is not a consequence of the relay. The Android app belongs to a single Firebase project, and that project belongs to Grams IT. A device token is valid only within it. A customer therefore cannot be the controller towards Google for delivery at all — that was already the case when every server still sent to Google itself.
The relay changes one thing for the better: the access key to that Firebase project now lies with us alone and no longer on every customer server. It is a master key to the devices of all customers and cannot be revoked per customer; distributing it was the actual flaw.
| Company | Service | Data | Place of processing |
|---|---|---|---|
| Hetzner Online GmbH, Gunzenhausen (Germany) | Operation of the servers on which the activation service and the push relay run | everything listed under 1a and 1b — solely in transit and storage | EU |
| Google Ireland Limited, Dublin (Ireland) | Firebase Cloud Messaging: the actual delivery to the end device | Device delivery token, title and short text of the message, target | EU and the United States (group structure) |
There are no further sub-processors. If you do not use the Android app, Google drops out entirely — only the activation service remains.
Recorded are exclusively metadata: timestamp, licence, a hash (SHA-256) of the delivery token, the type of event, the outcome of the send attempt and the sender IP address. Title and text are not stored; the database has no column for them. The metadata is deleted after 90 days.
The delivery token itself is never stored, only its hash. An extract of this database therefore contains nothing that could be used to send to a device.
Stated plainly, what is not yet solved: Title and short text pass through the relay in the clear. That we do not record them is a commitment — not a technical barrier. End-to-end encryption against the device key is planned; until then: do not write anything into a subject line that nobody but you should read. That is sound advice anyway, because a notification appears on a lock screen.
The following particulars apply to the annex of an agreement under Article 28 GDPR. They describe exclusively the processing named above; for everything that happens on your servers you are and remain solely responsible.
| Subject matter | Licence verification and delivery of notifications to mobile devices |
|---|---|
| Duration | Term of the software contract |
| Nature and purpose | Relaying and briefly holding notifications; verifying and evidencing the licence; informing about vulnerabilities |
| Type of data | Delivery token (as a hash), title and short text of a message, target, licence number, installation fingerprint, product version, technical contact address, IP address |
| Data subjects | Employees of the customer who use the Android app; the technical contact person of the licence |
| Erasure | Metadata after 90 days; a message is not held any longer once delivered or after six unsuccessful attempts |
| Place | EU; at Google additionally a third country on the basis of the standard contractual clauses |
| Sub-processors | those named under 3 |
We provide the full contract text on request: support@ordivis.eu. We announce changes to the list under 3 here in advance.
Both can be switched off, and both cost only convenience, not function:
Without push. No message is lost. It is in the application, and the app shows it the next time it is opened. Push is the notification, not the delivery path.
Without online activation. The Ordivis Platform runs entirely without a connection to the internet. In that case push falls away as well — without a route to Google, nobody reaches a mobile device, relay or no relay.
These particulars refer to the Ordivis Platform in the version delivered in each case. As at 17 August 2026.