Privacy information
Version: 10 October 2026
Controller and contact
Lars Feldeisen, Kapellenweg 8, 45768 Marl, Germany; lars@polsum-systems.de, 01792282531.
Data and purposes
Registration, verification and login store your email, display name, salted password hash, verification status and the accepted terms version and timestamp. Passwords are not stored in plain text. Your saved scene contains images, layout, device identifiers and audio settings. The legal basis is GDPR Article 6(1)(b) where necessary to provide the service. Technical data such as IP addresses, connection states and errors support operation, security and troubleshooting on the basis of legitimate interests under Article 6(1)(f). Notices and complaints are processed to handle the matter and meet applicable legal duties, notably under Article 6(1)(c) or (f).
Organizations and meetings
Organization spaces store names, owners, memberships, meeting rooms, and invitation email addresses and expiry times. Invitation links last seven days; only a token hash is stored. Owners and administrators can see member names and email addresses. We also store groups, memberships, resource permissions, and changes to groups and permission settings with actor, target and time. Organization data remains until the owner deletes their account; rooms can be deleted and members removed earlier. For public meetings, people with the link can see the organization and room name and join with a guest name. Internal and group-restricted meetings require the corresponding permission. Names, camera, microphone and chat are transmitted to currently connected participants. Meetings and meeting chats are not recorded or archived; later participants receive no chat history.
Live chat
Chat messages and your chosen display name are transmitted to people currently connected to the channel. Guests choose a name and are labelled as guests; signed-in users use their account display name. We do not archive chat messages. The browser keeps up to 100 received messages visible until you leave or reload the page. People connecting later receive no previous history.
Live content and recipients
Camera and microphone access requires browser permission. Live media is processed for transmission. Buffered HLS playback uses short-lived media files on the server; older segments are continuously removed and remaining files are deleted when the broadcast ends. No on-demand recording archive is created. Authorized participants, including guests for public resources, receive your content and may record it themselves. Your display name and stream title are visible on the viewing page. Your email and saved scenes are not shown to guests. Technical hosting and email service providers process data needed to deliver the service. Projects involving processing outside the EEA require applicable safeguards; contact us for current provider and location details.
Error diagnostics and performance monitoring with Sentry
We use Sentry, provided by Functional Software, Inc. (USA), to identify and resolve technical errors and monitor the stability and response times of jemmox. Our server sends error reports, operational logs and performance measurements to Sentry for these purposes. The legal basis is GDPR Article 6(1)(f): our legitimate interest in providing a secure, reliable service and resolving faults, where this processing is necessary and is not overridden by the interests or fundamental rights of the people concerned.
Data transmitted and minimization
Diagnostics may include timestamps, error types and messages, technical call stacks (stack traces), software versions and server environment, HTTP method, normalized route name, status code, connection state, durations (including database queries and connection acquisition), hashed query identifiers, database error codes, row counts and technical stream, resource and connection identifiers. Identifiers and information in error messages may relate to individuals; filtering does not make all diagnostics anonymous.
Automatic collection of user profiles, HTTP request bodies, HTTP headers, cookies and URL query parameters is disabled for Sentry. Known credentials, email addresses, URLs and structured client IP fields are removed or masked before transmission. Camera, microphone, screen and chat content are not intentionally collected as diagnostics. The integration runs on our servers: we do not load a Sentry SDK in your browser, set Sentry cookies or use Sentry Session Replay. Connecting to Sentry exposes the network address of our sending server.
Recipient and processing location
Sentry receives diagnostics as our service provider. Our integration uses Sentry’s European ingestion endpoint. According to Sentry, regional event data is stored in Frankfurt, Germany, with backups within the EU. The EU data region does not mean that all processing takes place exclusively in the EU: certain administrative and integration data, and access for operations and support, may involve other countries, particularly the USA.
We have entered into a Data Processing Addendum (DPA) with Sentry. Sentry describes its data processing terms and intended safeguards for international transfers, including EU Standard Contractual Clauses, in its Data Processing Addendum. Further information is available in its subprocessor list, data region documentation and privacy notice. You can request information about the safeguards applicable to our processing using the contact details above.
Retention and objection
Automatic retention of error events, logs and performance data depends on the data type, the Sentry subscription and available retention settings. Backups follow additional provider deletion cycles. Deleting your jemmox account does not automatically delete individual diagnostics already sent to Sentry. You can contact us to request information about the relevant data and its retention and to have a deletion request assessed. Under GDPR Article 21, you may object to this processing on grounds relating to your particular situation.
Cookies and browser data
An HTTP-only session cookie carries a signed JWT and lasts up to twelve hours. Logout revokes the account's existing logins. An optional language preference is stored for up to a year. These features support login and your requested language. The application has no advertising or analytics trackers. Scenes are stored on the server within the organization and are accessible to its members who are allowed to stream. Browser permissions are controlled by the browser.
Retention and your rights
Account data is retained until account deletion. Organization scenes and permission audit records remain until organization deletion; scenes can be deleted individually earlier. Verification links expire after 24 hours; expired tokens and accounts still unverified after seven days are removed regularly. The application does not archive operational logs itself; infrastructure determines retention. Messages and specific legal matters may be retained longer according to purpose and legal obligations. You may request access, correction, deletion, restriction and data portability, and object to processing based on legitimate interests where the legal conditions apply. You can complain to a data protection supervisory authority, including the North Rhine-Westphalia authority at ldi.nrw.de. There are no automated decisions with legal or similarly significant effects.