Skip to content
Gelhaus Solutions

GPlatform Identity data processing annex

The Art. 28(3) specifics for an organisation or a group that signs its own people in through GPlatform Identity, and where the line runs between what we process on its behalf and the account each person holds with us.

Version 2026-10-27, in force since 27 October 2026Auf Deutsch lesen →
This applies alongside the general terms of service and privacy policy. Where they differ on a point about GPlatform Identity specifically, this page wins.

When this applies

This annex supplements the data processing agreement and applies where an organisation or a group ("you") uses GPlatform Identity for its own people: to hold them in a directory, to invite them, to give them access to products with a role, to set rules for how they sign in, to sign them in through its own provider, to run service accounts and to hold its projects, and, as a group, to keep its people up to date from its directory provider, to suspend and offboard them, to read, export and stream its audit, to claim domains and to manage the accounts on them. A group is what earlier versions of this annex call an enterprise. Where the annex is silent, the data processing agreement applies, and the GPlatform Identity terms describe how the service works. GPlatform Identity (formerly GPlatform SSO) runs at identity.gplatform.org; the older address sso.gplatform.org forwards there.

Where the line runs. Each person's own account is not yours: their addresses, credentials, passkeys, linked providers, sessions, the protection of their sign-in, our audit log and our mail log are ours, as controller, and the privacy notice tells them so. What you record about your people in GPlatform Identity is yours, and for that we are your processor. The one exception is a group that manages its people's accounts: for the accounts it manages, we process the account itself on its instructions as well.

Subject matter and duration

Running your directory in GPlatform Identity and signing your people in to the products you give them, for as long as your organisation or group exists in GPlatform Identity, and then until the deletion described below.

Nature and purpose

  • holding your members, their roles and your teams, and showing them to your owners and admins;
  • sending the invitations you issue, and admitting the people who accept them;
  • telling the products you give your people what they need to sign them in: who the person is to that product, their name and primary confirmed address, your organisation, their role in it, their teams and the role you gave them in that product;
  • applying the rules you set when your people sign in;
  • running the service accounts you make, and the tokens they use;
  • carrying the integrations your organisation installs and the permissions you give them, and applying fine-grained access where you switch it on for an application;
  • showing your owners and admins your organisation's activity;
  • ending access when you remove somebody or close the organisation, so that the products concerned stop admitting them;
  • signing your people in through your own provider over OpenID Connect or SAML, linking each of them to the identifier your provider gives, testing it when your owners ask, and, where you require it, refusing other ways in to the accounts a group owns and not telling products about you from sessions that came in another way;
  • sending the letters your owners and admins ask for, such as asking your people to set up a second factor;
  • holding your workspaces, projects and environments, telling our own products which of them each of your people may see, and deleting an archived project 30 days after it was archived;
  • keeping your logo and showing it beside your name in lists and to products;
  • for a group: checking the domains it claims and telling it when an address on a proven domain is confirmed;
  • for a group: receiving its people and directory groups from its directory provider over SCIM, making accounts for addresses on its proven domains, and suspending and offboarding people as it or its directory provider decides;
  • for a group: showing its owners, admins and auditors its people and its slice of our audit log, exporting that slice and posting it to the address the group sets;
  • for a group that manages its people's accounts: writing to the people whose accounts it takes over, holding the window, carrying out the takeover, the split or the return of an account, and carrying out on the accounts it manages what it decides.

Your instructions

Your instructions are this annex, the data processing agreement, and what your owners and admins do in the GPlatform Identity console. Where you ask us to act for you, for example to set up a group, to place an organisation in it, to switch managed accounts on or off, or to enrol one of your applications, we act on a documented request from you, and the act is recorded with its reason. If we believe an instruction infringes data protection law, we tell you and do not carry it out until it is confirmed or changed.

Categories of data subject

  • your members, in every role: owner, admin, member, billing and auditor, and in a group also security admin and people admin;
  • people you invite, including people who do not yet have an account;
  • people in your teams and people you give access to a product;
  • the people who make your service accounts;
  • people who sign in through your own sign-in, and the people your owners send a link to test it;
  • for a group: people who confirm an address on a domain it has proven, the people in its organisations, the people its directory provider sends, the people it suspends or offboards, and people whose accounts it takes over or manages.

Categories of personal data

Your directory: each member's account reference, display name, picture and primary confirmed address as your people see them, their role, their teams, and when they joined; for your owners and admins also whether each holds a second factor and when they last signed in, and for a group's administrators how many sessions each has open now. This is your processing, on your own legal basis, with us as your processor.

Invitations: the address invited, the role offered, who sent it, and when it was sent, accepted, withdrawn or expired.

Access: which product, which role, and whether given by name, through a team or to the whole organisation; the role sets and rules you define.

Service accounts: name, description, who made it, and for each token its last four characters, its expiry, who made it and when it was last used. The token itself is stored only as a hash.

Fine-grained access: the relationships an application writes for your organisation once you switch it on for that application: the object, the relationship, and the person or team it is for.

Integrations: the integrations installed on your organisation or a team, who installed them, the products and permissions they may use, and when. What a person lets an integration do as themselves is that person's own consent and stays with their account, under the privacy notice.

Your own sign-in: its settings (the issuer, the client and the added scopes, or the SAML entity, sign-in address and certificates; a client secret is stored encrypted), who made it, the outcome of its last test, and the last tests with who ran each or, for a test from a link, the address the provider gave; for each person linked to it, the identifier your provider knows them by, the address and name it gave when the link was made, and when it was last used; which sign-in each session came through; and, for the minutes of a sign-in or a test and at most a day after, what your provider said. These links are part of your sign-in.

Places: your workspaces, projects and environments, with who made and who archived each project.

Your logo: the image you upload, rebuilt as a clean PNG.

Your activity view: for an organisation, 90 days of what happened in it, who did it and when; for a group, its slice of our audit log, every entry about the group and its organisations, which it may also export and have posted to an address it sets. It never shows the IP address or the country, which stay in our own audit log. We give a group its slice as the controller of our audit log; once a copy leaves us, the group is the controller of that copy.

What the products you grant are told: the identifier each product knows a person by, their display name and primary confirmed address, and the membership facts listed above, and, at /v1/places, your organisations with their group and logo and the workspaces, projects and environments each person may see.

For a group: the domains it claims, the result of each proof check and the first 200 characters of what came back; a notice naming the account and the domain when an address on a proven domain is confirmed; the people its directory provider sends (the user name, the directory's own identifier for them, their name and whether it says they are active), its directory groups and their members, and its directory's token as a hash; who it suspended, by whom, when and why; the address of its audit stream, its secret (stored encrypted) and how its deliveries went; for each takeover, the account, the address on its domain, the way chosen, the window, the reminder, the answer and the outcome; and, for accounts it manages, the account itself and the state of its credentials, never a password, a recovery code or an authenticator secret.

No special categories of personal data are processed.

Processing operations

Receipt, storage, display to your owners and admins, transmission to the products you grant through the session protocol and through OpenID Connect, sending invitations by mail, checking domain proofs every 15 minutes by fetching a file from your web server and looking up a DNS record, signed notices to products that access has ended (carrying only the identifier the product knows the person by), enforcement of your rules at sign-in and whenever a product asks about a session (comparing the address and the country a session was made from with the ranges and countries you allow), restriction and deletion. For your own sign-in and, for a group, its directory provider and audit stream, also: receipt of what your provider says about a person at sign-in (OpenID Connect claims or SAML attributes) and of what your directory provider sends over SCIM, exports of your audit slice, and signed posts of it to the address you set.

Your own provider, directory and stream. Your sign-in provider, your directory provider and the address you set for your audit stream are yours, not our sub-processors: what we send them and receive from them is at your direction.

Your own applications. Where we enrol an application of yours as an OpenID Connect client, each person is asked on a consent screen before it learns who they are, and the application receives what they agree to. What your application does with it is your responsibility, outside this annex.

Sub-processors

  • IONOS SE, Elgendorfer Straße 57, 56410 Montabaur, Germany: the server in Germany on which our own mail server (Stalwart) runs.

GPlatform Identity and its database run on our own hardware in Germany, which also holds the key that signs every token and our encrypted backups. You are told before a new sub-processor is engaged and may object, as the data processing agreement sets out.

Where the processing takes place

In Germany.

Technical and organisational measures

Credentials and secrets. Passwords are stored as argon2id hashes, with at least 12 characters. Authenticator secrets are encrypted (AES-256-GCM). Session tokens, the codes in our letters, invitation tokens, application secrets, service account tokens and personal access tokens are stored only as SHA-256 hashes, and every token is shown once. The key that signs every OpenID Connect token is held in HashiCorp Vault, made there and never exported; the service refuses to start in production with a key held on disk.

Sessions and revocation. Every token descends from one sign-in, and ending the sign-in ends them all. Our products check a session again at least every 60 seconds and receive signed notices when it ends; a token issued over OpenID Connect lasts five minutes at most; PKCE is required of every OpenID Connect client, and a client excused from it is marked as such in our registry. A sign-in lasts at most 12 hours, and your rules can shorten it.

Separation between applications. Each application knows a person by an identifier of its own. What an application may do is fixed by its tier in one table: only our own products may create accounts, and somebody else's software is never told which other products a person uses.

Sign-in protection. Ten failed sign-ins in a row pause sign-in for 15 minutes, counted per account and per address. A letter can be asked for once every 60 seconds per address. Your rules can require a second factor.

Your own sign-in and directory. A sign-in through your provider resolves only through the identifier it gives, never through an address, and an address an account already holds is linked only after a letter to it. A client secret is stored encrypted, bound to its own record. A SAML answer must be signed with SHA-256 or stronger, be meant for us and answer our request, unless you let your provider start a sign-in, and is accepted once. A sign-in can be turned on only after a test that passed since it last changed. A test link is stored as a hash, works once and lasts a day. A directory token is stored as a hash, and a rotation keeps the old one only for the overlap you choose. A directory never acts on an owner of the group and never erases an account. Every delivery of your audit stream is signed, and its address is checked before it is used.

Transport. The service refuses to start in production if mail to another host would travel unencrypted, and requires mutual TLS for its internal workflow engine (Temporal).

Access on our side. Our staff work in three roles (admin, support and auditor). Every act on an account records a reason, and searching for and opening an account are recorded too. No role can read a password, a recovery code or an application secret. Our support can act as a person only with that person's consent, for at most seven days, and the person is told afterwards every time. Disabling and erasing an account are for admins only. Switching managed accounts on or off for a group needs an owner's request, which is recorded.

Records and retention. Every sign-in, refusal and change is written to an audit log in which each entry carries a sequence number and the hash of the one before it; entries are kept for as long as GPlatform Identity exists and name only the identifier once an account is erased. Raw IP addresses are kept for 90 days, in sessions and in audit entries, and after that only a keyed hash; user agents are not stored, only a coarse device label. The country of a sign-in is read from a database on our own server; no address is sent to a lookup service. Request logs are kept for at most 30 days. Sessions, tokens, codes and challenges are deleted once they have expired or been used. A person's account data is erased 12 months after their account ends, leaving only its identifier.

Availability and recovery. Encrypted backups are made every night to our own hardware in Germany and kept for 90 days.

Assistance

Your people can change most of what concerns them themselves, in the console. For the rest, we help you answer a data subject's request, and we help you meet your obligations under Art. 32 to 36 GDPR. If a person asks us about what you record, we pass the request on to you. We tell you without undue delay about a personal data breach affecting your data.

Deletion and return

As you go. Removing a member, a team or an access grant deletes it at once, and the products concerned see the change at their next check, within a minute. Switching off a service account revokes its tokens at once; its record stays so that our audit log can name it, and its tokens are deleted once they have expired. An invitation is deleted once it has been accepted or has expired; a withdrawn one stays on your list, marked withdrawn, until then. A domain claim a group releases is deleted. Removing your own sign-in deletes its links, and the people linked to it keep their other ways in. Removing a directory stops it at once and deletes the directory groups it pushed; the people it provisioned keep their accounts. A person your directory provider removes is suspended and offboarded, never erased. Removing your audit stream stops it; what was delivered is yours. An archived project is deleted with everything in it 30 days after it was archived. A logo you remove is deleted.

When the organisation is closed. Its owner closes it in the console. Every access grant, membership, team and invitation is deleted at once, the products concerned are told, and its service accounts stop working. The organisation's record (its name, its short name and the mark that it is closed) and the records of its service accounts stay, so that our audit log goes on naming what its entries are about. Before you close it, your owners and admins can read everything in it on its screens, and on request we give you a copy.

What stays. Audit entries about acts in your organisation are our own record, as controller, kept for as long as GPlatform Identity exists, and hold who did what and when. Each person's account stays theirs, under the privacy notice. A takeover's record, a suspension, what your directory provider sent about a person and a person's link to your own sign-in stay until they are lifted or removed, and at the latest until the person's account data is erased, 12 months after the account ends. Backups are made every night, are not edited and are kept for 90 days.

Where the law requires data to be kept, it is kept for that period and for that purpose only.

Versions of this document
2026-10-27 in force since 27 October 2026
2026-10-20 in force 20 October 2026 to 27 October 2026
2026-10-03 in force 3 October 2026 to 20 October 2026
2026-10-01 in force 1 October 2026 to 3 October 2026