Legal
Privacy notice
Information about data processing on this website.
Controller
SBS Deutschland GmbH & Co. KG, In der Dell 19, 69469 Weinheim, Germany. Represented by its personally liable partner SBS Deutschland Beteiligungs GmbH (Amtsgericht Mannheim, HRB 721711), represented by managing director Andreas Schenk. Contact: ki@sbsdeutschland.de, +49 (0) 6201 24469.
Website delivery
This public website is operated on a self-managed DigitalOcean Droplet in the Frankfurt, Germany region (fra1). DigitalOcean, LLC supplies the hosting infrastructure; we operate the website application. For delivery, troubleshooting and abuse prevention, technical connection details such as IP address, request time, visited URL, user-agent, referrer and error data may be processed. The legal basis is Article 6(1)(f) GDPR; our legitimate interests are secure and reliable operation. The Nginx reverse proxy is intended to run without ordinary HTTP access logging; operating-system security records, application error logs and provider infrastructure records may nevertheless contain technical identifiers. Operational records are access-restricted and retained only as long as needed for security, troubleshooting or legal requirements. Under DigitalOcean's Data Processing Agreement, DigitalOcean acts as processor for customer-controlled personal data, while some account and service information is processed under its separate controller role. The Frankfurt server location does not exclude provider processing or access in countries outside the EEA. Its Data Processing Agreement describes the EU-U.S. Data Privacy Framework and, where applicable, Standard Contractual Clauses for international transfers. See https://www.digitalocean.com/legal/data-processing-agreement and https://www.digitalocean.com/legal/privacy-policy. Information about applicable safeguards can also be requested from ki@sbsdeutschland.de.
ReleaseProof Jira app
ReleaseProof is provided as an Atlassian Forge app for Jira Cloud. To evaluate a configured release scope, the app uses the read:jira-work permission to read the Jira data required by its deterministic readiness rules. Depending on the customer's Jira configuration and selected scope, this can include project and version metadata, issue keys and summaries, issue types, statuses, labels, fix-version assignments, subtasks, issue links, resolutions, and the configured acceptance-criteria field. The app processes these data to calculate and display release-readiness results inside Jira. ReleaseProof does not persist copies of analyzed Jira issues or a history of analysis results. Using the storage:app scope, ReleaseProof stores project configuration plus non-personal technical schema-version metadata in Atlassian Forge KVS. The project configuration includes project ID and key, scope mode and the accepted JQL scope, configured status and field IDs, labels, issue types, approval settings, and technical timestamps. This configuration is stored per app installation. Before a JQL scope is persisted, ReleaseProof validates its field references against Jira field metadata. Scopes that reference Jira user fields, fields identified as user or multi-user fields, or fields whose schema cannot positively establish a non-user type are rejected and are not written to Forge KVS; the built-in project, key, and issuekey references remain explicitly allowed. This is intended to prevent Atlassian user identifiers from being persisted through the supported JQL configuration. The current ReleaseProof app declares no external remotes or egress and does not send Jira analysis data to an external ReleaseProof database, analytics service, or generative-AI/LLM service. ReleaseProof is not designed to persist Atlassian user profiles, email addresses, or account IDs as separate profile data. Administrators must not enter personal data in free-text configuration values. ReleaseProof free-text configuration is intended only for non-personal configuration values. Atlassian provides the Forge platform and may generate technical platform and app logs. Depending on the customer's administrator settings, the app vendor may be granted access to such logs for troubleshooting. ReleaseProof does not intentionally write Jira issue bodies or Atlassian user-profile data to application logs. Retention and deletion of data held by the Forge platform are additionally subject to the applicable Atlassian platform and privacy terms.
Contact and early-access requests by email
This website currently offers email contact instead of web forms. Clicking an email link opens your email app; the website does not receive or forward your message. If you send an email, your email provider transmits it to our displayed contact address. We process your sender address, message and any information you choose to include to respond to your inquiry or discuss early access. Our email infrastructure is provided by STRATO GmbH in Germany. The legal basis is Article 6(1)(b) GDPR for pre-contractual steps requested by you, or Article 6(1)(f) GDPR for our legitimate interest in handling other business inquiries. Providing information is voluntary; we need a reply address and enough context to respond. Retention depends on the purpose and status of the correspondence, applicable statutory retention obligations and the need to establish, exercise or defend legal claims. We do not promise automatic deletion of all correspondence after a fixed number of days. Send only information needed for your request.
Security reports by email
Send an initial security report to the displayed email address with a brief description of the affected public page or product area and safe reproduction steps. We process your sender address and the information you provide to assess the issue and follow up. This serves our legitimate interest in identifying and addressing security issues under Article 6(1)(f) GDPR. The email processing and retention criteria above also apply to security reports. Do not send passwords, API tokens, credentials, production Jira content or unnecessary personal data. Ask how to coordinate sensitive evidence before sending it.
Analytics
No third-party analytics or tracking provider is currently used on this website. The application contains only a local analytics event bridge and does not itself transmit those events to an external provider. If an external analytics provider is introduced, this privacy notice must be updated before that processing is enabled.
Your rights
Subject to the applicable legal requirements, you may have rights of access (Article 15 GDPR), rectification (Article 16), erasure (Article 17), restriction of processing (Article 18), data portability where applicable (Article 20), and objection (Article 21). You also have the right to lodge a complaint with a competent supervisory authority under Article 77 GDPR. The supervisory authority generally responsible for private companies headquartered in Baden-Württemberg is the State Commissioner for Data Protection and Freedom of Information Baden-Württemberg (LfDI BW), Heilbronner Straße 35, 70191 Stuttgart, Germany, email: poststelle@lfdi.bwl.de.
Right to object
Where processing is based on Article 6(1)(f) GDPR, you have the right under Article 21 GDPR to object at any time, on grounds relating to your particular situation, to the processing of personal data concerning you. We will then no longer process the personal data unless we demonstrate compelling legitimate grounds for the processing that override your interests, rights and freedoms, or the processing is necessary for the establishment, exercise or defence of legal claims.
Language authority
The German version of these legal notices is authoritative. The English version is provided as a convenience translation; if the wording diverges, the German version prevails.