InfraInbox v0.1 is in development. The self-hosted release and the Cloud beta open on the same day. Sign up for Cloud

This policy is also available in Romanian.

It explains what personal data INNOVA SOFTWARE S.R.L. handles when you use InfraInbox, why, for how long, who else sees it, and what your rights are. It is written to meet Articles 13 and 14 of the General Data Protection Regulation (EU) 2016/679 (“GDPR”).

1. Who we are and how to reach us

INNOVA SOFTWARE S.R.L. (“we”, “us”) is a company registered in Romania, sole registration code (CUI) 45402130, Trade Register no. J30/1284/2021. We make InfraInbox. Our legal notice has our company details.

We have not appointed a Data Protection Officer, because the law does not require one of us: we do not monitor people systematically on a large scale, and we do not process special categories of data on a large scale (Art. 37(1) GDPR; Romanian Law 190/2018, Art. 4).

2. Which parts apply to you

You are… Read Our role
Someone with an InfraInbox Cloud account (dash.infrainbox.app) §3 Controller for your account. Processor for the alert content your workspace receives
A user of the InfraInbox iPhone app §4 and §5 Controller for push delivery. For everything else, whoever runs the server you pair with
Someone who runs InfraInbox on their own server and uses our push relay §5 Controller for push delivery data only
A visitor to infrainbox.app, or someone who writes to us §6 Controller

Self-hosted InfraInbox runs on your own server. We cannot see anything on it, and whoever runs it is the controller of its data. The only thing that reaches us is what passes through our push relay (§5).

3. InfraInbox Cloud

3.1 Your account (we are the controller)

Data Why Legal basis (GDPR Art. 6(1))
Email address, optional display name, password (stored only as an Argon2id hash), optional two-factor secret (encrypted), recovery codes (hashed), optional passkey To create your account, sign you in and keep it secure (b) contract
The version of the Terms you accepted, and when To show what we agreed (b) contract; (f) our legitimate interest in proving the agreement
Workspace memberships and roles; invitations you send or receive To run shared workspaces (b) contract
Your paired phones: label, platform, app version, push endpoint, timestamps To deliver notifications to your phone (b) contract
Sign-in sessions: IP address, browser, times To keep you signed in and let you see and end your sessions (b) contract; (f) security
Audit log: who did what and when (sign-ins and failed sign-ins, changes to keys, rules, members and devices, exports, deletions), with IP address and browser. Never secrets or alert content To detect and investigate misuse (f) our legitimate interest in securing the service; Art. 32 GDPR
Rate-limit and quota counters, including per IP address at sign-up To keep the service fair and stop abuse (f) legitimate interest

You need an email address and a password to have an account. Without them we cannot provide Cloud. Our legitimate interests are keeping the service secure, available and fair. We have weighed them against your interests: the data is minimal, kept for short periods (§9), and never sold or used for advertising.

Sign in with Google or GitHub (optional, where offered). If you choose it, Google or GitHub tells us your account identifier, your email address, whether it is verified and, the first time, your name. We discard GitHub’s access token as soon as we have read your email address. Basis: (b) contract, because you chose this way to sign in. Google and GitHub handle the sign-in under their own privacy policies.

Emails we send you. Only messages about your account and the service: confirming your address, password resets, email-address changes, workspace invitations, a notice when a workspace reaches a daily limit, and notices we must give you (changes to our terms or sub-processors, security incidents). They go out through Scaleway’s email service in France. Basis: (b) contract, or (c) where the law requires the notice. We send no marketing email. If we ever want to, we will ask for your consent first (Art. 6(1)(a) GDPR; Romanian Law 506/2004, Art. 12).

3.2 What your workspace receives (we are the processor)

Your sources send events to your workspace: alerts from Proxmox, backups, monitors and other tools. They can contain hostnames, IP addresses, usernames and other details about your systems and the people who use them. For this content, you (or the organisation you work for) are the controller and we are the processor (Art. 4(7)–(8) and Art. 28 GDPR). For organisations, our Data Processing Agreement sets out the terms. If you use Cloud only for yourself or your household, we apply the same safeguards.

  • We use this content only to receive, store, group, route and deliver it as you configure your workspace. We read it only to fix a problem you report, to keep the service secure, or where the law requires it.
  • Destinations you add (Telegram, Slack, Discord, webhooks) receive what you route to them, under those services’ own terms. You choose them; they are not our sub-processors.
  • Raw payloads of incoming requests are kept for troubleshooting: the last 20 per source, for 7 days, at most 64 KB each. Credentials are removed before storage, and requests without a valid key are never stored. You can switch this off per source or purge it at any time.

If a person named in your alert content asks us about it, we pass the request to you.

4. The InfraInbox iPhone app

The app has no account of its own. You pair it with an InfraInbox server, ours (Cloud) or one that you or your organisation runs, by scanning a QR code from that server’s dashboard.

  • What the app sends to the server you pair with: the pairing code, a device label, the platform and the app version; later, your actions on incidents (acknowledge, snooze, mute, mark read), and your phone’s push endpoint and encryption keys. For Cloud we handle this as §3 describes; for a self-hosted server, its operator does.
  • What the app sends to us for push: your phone’s Apple push token and the paired server’s public key, so notifications can reach the phone (§5).
  • What stays on your phone: the list of servers, sign-in tokens and push keys (in the iOS Keychain), a cache of recent incidents, and actions waiting to be sent. Removing a server deletes its push registration, signs the phone out of that server and wipes its data from the phone.
  • Camera: used only to scan the pairing QR code. The image is processed on the phone and never sent anywhere.
  • Local network: used only to reach a server on your own network.
  • No analytics, crash reporting, advertising or tracking. The app contains no third-party code that collects data.

Apple handles your App Store and device data under its own privacy policy: https://www.apple.com/legal/privacy/.

5. Push notifications, our relay and Apple

Notifications reach an iPhone only through Apple’s push service (APNs), and Apple accepts them only from the app’s publisher. So every InfraInbox notification to an iPhone, from Cloud or from a self-hosted server, passes through our push relay (push.infrainbox.app), which we run ourselves, and then through Apple.

The content is end-to-end encrypted. Each notification is encrypted on the server for one phone (RFC 8291). Only that phone can read it. Neither our relay nor Apple can.

What the relay keeps:

Data For how long
Each phone registration: an opaque ID, platform, the Apple push token (encrypted at rest), the paired server’s public key, a hash of the registration’s management secret, the critical-alert setting, timestamps Until the app removes it. Deleted 7 days after Apple reports the token invalid, or after 180 days without use
A daily count of notifications per server key (the key stored only as a hash), for fair-use limits 8 days
Service and web-server logs: the sending server’s or phone’s IP address, time, path (registration IDs masked), errors. Never push tokens, secrets or message content 7 days

What Apple receives: the encrypted envelope, the phone’s push token, our relay’s IP address, and the time and size of each notification.

Why, and on what basis: to deliver the notifications you and the server asked for (Art. 6(1)(b) GDPR, contract), and to keep a free relay available and fair (Art. 6(1)(f), legitimate interest).

Apple is in the United States and is not certified under the EU–US Data Privacy Framework, and it offers no data-transfer clauses for its push service. So before your phone asks iOS for permission to show notifications, the app asks for your explicit consent to send this data to Apple, and tells you the risks: US authorities could access it, with fewer safeguards and rights than you have in the EU (Art. 49(1)(a) GDPR). Consent is optional: without it the app still works, and you can refresh by hand or use another destination such as Telegram or Slack. You can withdraw it at any time in the app’s Settings; the app then removes its push registrations. Withdrawing does not affect notifications already delivered.

If you run your own server, you can also switch the relay off (push.relay.enabled: false). Our relay terms apply to servers that use it.

6. The website, and messages you send us

  • No cookies, no analytics, nothing loaded from other companies. Fonts and scripts come from our own domain. Your browser stores your light/dark theme (starlight-theme) and, in the docs, which sidebar sections are open (sl-sidebar-state, cleared when you close the tab). These never leave your browser.
  • The Cloud dashboard sets two cookies, both strictly necessary: __Host-iib_session keeps you signed in (it ends after 7 days without use, or 30 days at most) and __Host-iib_flow holds a sign-in that is halfway through (10 minutes). It also remembers two layout choices in your browser (infrainbox.nav.collapsed, infrainbox.rules.coveragePane). None of these tracks you, so we don’t ask for consent (Art. 5(3) of the ePrivacy Directive 2002/58/EC; Romanian Law 506/2004, Art. 4(6)).
  • Server logs: our web servers record each request’s IP address, time, page and browser, to keep the sites running and secure. Basis: (f) legitimate interest. Kept 14 days.
  • The update check: if you turn it on in a self-hosted server’s setup (it is off by default), the server fetches our release list from infrainbox.app about once a day. The request carries nothing about your server; our web server logs it like any other request.
  • Messages you send us at contact@innovasoftware.ro: your name and email address, your message and our replies. We use them only to answer you, to handle a request about your rights, a notice of illegal content or a security report, and to keep a record of how we handled it. Basis: (f) our legitimate interest in answering you; (c) where a law requires us to handle the request (GDPR, the Digital Services Act, the Cyber Resilience Act). Our mailbox is hosted by Zoho Corporation B.V. (Netherlands) in its EU data centres. We keep messages for 3 years after our last exchange, the general limitation period for claims under Romanian law (Civil Code, Art. 2517), unless you ask us to delete them sooner and nothing requires us to keep them.
  • Vulnerability reports through GitHub are handled by GitHub under its own privacy statement; we keep what we need to fix the issue and meet our reporting duties.

7. Who receives personal data

We do not sell personal data or share it for advertising. It goes only to:

  • Our processors, under written contracts that meet Art. 28 GDPR: our hosting provider (DanubeData, with Hetzner’s data centres in Germany), our email-sending service (Scaleway, France) and our mailbox provider (Zoho, EU). The current list, with each company, purpose and location, is on our sub-processors page.
  • Companies acting under their own terms when you use them: Apple (push notifications to iPhones), Google and GitHub (if you sign in with them, or report a vulnerability on GitHub).
  • Authorities, only when the law requires it, for example under a court order. We will tell you unless the law forbids it.

8. Transfers outside the European Economic Area

Our servers and backups are in Germany. Personal data leaves the EEA only in these cases:

Recipient What leaves Basis
Apple Inc. (US), for push notifications to iPhones The encrypted envelope (unreadable to Apple), the phone’s push token, our relay’s IP address, the time and size of each notification Your explicit consent in the app (Art. 49(1)(a) GDPR), see §5. Apple is not certified under the Data Privacy Framework
Google LLC (US), if you sign in with Google The sign-in exchange EU–US Data Privacy Framework (Art. 45 GDPR; Commission Implementing Decision (EU) 2023/1795); Google LLC is certified
GitHub, Inc. (US), if you sign in with GitHub or report through it The sign-in exchange, or your report Data Privacy Framework; GitHub is certified

The Data Privacy Framework was upheld by the EU General Court on 3 September 2025 (case T-553/23); an appeal is pending (case C-703/25 P). If it is struck down, we will rely on standard contractual clauses or stop the transfer.

9. How long we keep data

Data Kept
Account data, including the record of the Terms you accepted While your account exists
Your account, when you delete it Erased at once: your email address, username, display name, password, two-factor secret and recovery codes, linked Google or GitHub identities, sessions, paired phones and push registrations. Only an opaque identifier remains until the account record itself is removed, within 30 days. In a workspace you share, what you wrote stays, shown as “Deleted user”. Backup copies age out within 35 days
A deleted workspace (including one you owned alone when you delete your account) Deleted from the live system at the next hourly clean-up, at the latest within 30 days; backup copies age out within 35 days
Events 30 days (the first and last event of a kept incident stay with it)
Incidents 90 days after they are resolved; open incidents are kept
Delivery records 30 days
Raw payloads The last 20 per source, for 7 days
Heartbeat pings The last 100 per check, plus daily summaries for 90 days
Audit log 1 year. IP addresses are shortened (to /24 for IPv4, /48 for IPv6) after 90 days. Once you delete your account, its entries name you only by the opaque identifier
Expired sessions, pairing codes and account links (confirmation, reset) 30 days after they expire
A paired phone Kept with your account until you remove it or close the account. A phone not seen for 90 days and with no working push registration is signed out automatically
Our service and web-server logs (never alert content or secrets) 14 days
Push relay data See §5
Messages to us See §6

A workspace owner can choose shorter periods for their own workspace’s events, incidents, delivery records, raw payloads and audit log.

10. Your rights

You can ask us to:

  • see the personal data we hold about you and get a copy (Art. 15 GDPR);
  • correct it (Art. 16);
  • delete it (Art. 17);
  • restrict how we use it (Art. 18);
  • get it in a machine-readable form, or have it sent to someone else (Art. 20);
  • object to processing based on our legitimate interests (Art. 21);
  • withdraw your consent at any time, for example to push through Apple (§5), without affecting what happened before (Art. 7(3)).

In Cloud you can do some of this yourself: correct your email address or display name in Settings › Profile; see and end your sessions in Settings › Security; remove phones in Settings › Phones; and delete your account with Delete account in Settings › Profile, which erases your personal data at once (§9). A workspace owner can also download a workspace as JSON, or delete it, in Settings › Usage and data.

To get a copy of your personal data (Arts. 15 and 20), write to contact@innovasoftware.ro from your account’s email address. We send it to that address in a machine-readable form (JSON).

For anything else, write to contact@innovasoftware.ro too. We answer within one month, or tell you within that month if we need up to two more months because the request is complex (Art. 12(3)). It is free unless a request is manifestly unfounded or excessive (Art. 12(5)). We may ask you to confirm the request from your account’s email address (Art. 12(6)).

  • Alert content in a Cloud workspace: ask the workspace’s owner or organisation, the controller. If you write to us, we pass your request to them.
  • A self-hosted server: ask whoever runs it. We have no access to it.

We make no decisions about you by automated means that have legal or similarly significant effects (Art. 22).

11. Complaints

You can complain to the Romanian data protection authority, Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP), B-dul G-ral Gheorghe Magheru 28-30, Sector 1, 010336 București, Romania, https://www.dataprotection.ro, or to the authority where you live or work, or where you think the infringement happened (Art. 77). You can also go to court (Art. 79). We’d be glad of the chance to put things right first.

12. How we protect data

In short: encrypted connections everywhere; passwords hashed with Argon2id; stored credentials and two-factor secrets encrypted with AES-256-GCM; workspace owners in Cloud must use a second factor; each workspace’s data separated by row-level security in the database; an append-only audit log; logs that never contain secrets or alert content; end-to-end encrypted push; daily encrypted backups. The full list is in Annex II of our Data Processing Agreement. If a breach puts your rights at high risk, we will tell you without undue delay (Art. 34).

13. Age

InfraInbox is a tool for people who run servers. You must be at least 16 to create a Cloud account; you confirm this when you sign up. If we learn that someone younger has given us personal data, we delete it.

14. Changes

We publish every change here, with a new effective date, and keep earlier versions available on request. If a change matters to you, for example a new purpose or a new country, we email Cloud account holders at least 30 days before it applies.


Version 1.0, effective 5 October 2026.