Privacy Policy
Last updated: October 28, 2026
Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) and other data protection legislation is:
Sebastian Software GmbHDalheimer Straße 12
55128 Mainz
Germany
- Managing Directors:
- Sebastian Fastner, Sebastian Werner
- Email:
- info@sebastian-software.de
A data protection officer has not been appointed, as the legal requirements for this do not apply. For data protection inquiries, you can contact the email address listed above.
Overview of Data Processing
This website does not process personal data beyond what is technically necessary. No cookies are set. For statistical analysis of website usage, we use Rybbit, which operates entirely without cookies and does not permanently store any personal data (see section "Web Analytics"). There is no contact form – contact is made exclusively by email.
Hosting and Content Delivery Network
This website is operated via the infrastructure of Bunny.net (BunnyWay d.o.o., Slovenia, EU). Bunny.net provides the following services:
- CDN (Content Delivery Network) for delivering static files (HTML, JavaScript, CSS)
- Edge Scripting for server-side logic at Bunny.net nodes
- Storage for static files and assets
Processed Data
Each page request processes the following categories of technical connection data: network identification data (IP address), time-related metadata (timestamp), usage data (requested URL), technical metadata (browser type, operating system, and device information), and the language preference transmitted by the browser (Accept-Language). According to a contractual assurance by Bunny.net, this data is held exclusively in working memory (RAM) and automatically deleted after 20–30 seconds. According to this assurance, no persistent storage takes place.
The language preference is used solely to route the request to the matching language version. The German and English versions are on separate domains, so this redirect may also lead to the respective other domain. No cookie is set in the process.
Legal Basis
Processing is based on Art. 6(1)(f) GDPR. Our legitimate interest lies in ensuring the availability, integrity and security of the website. This interest outweighs the data subjects' interest in non-processing, as, according to a contractual assurance by Bunny.net, connection data is processed exclusively transiently in working memory and automatically deleted after a few seconds. Insofar as information on the user's terminal device is accessed (e.g. through edge scripting), this is permissible without consent pursuant to Section 25(2)(2) TDDDG, as the access is strictly necessary to provide the service explicitly requested by the user.
Place of Processing
Bunny.net is based in Slovenia (EU/EEA). This website is delivered exclusively via nodes located in EU member states; no connection data is transferred to third countries. Bunny.net contractually commits that connection data on CDN nodes is only processed transiently and not stored permanently. Furthermore, a data processing agreement pursuant to Art. 28 GDPR is in place, in which Bunny.net ensures that sub-processors implement adequate data protection measures in accordance with the GDPR.
Obligation to Provide Data
The transmission of your IP address is technically necessary to access this website. Without this data transmission, no connection to the server can be established and the website cannot be displayed. There is no legal or contractual obligation to provide any further personal data.
Further information can be found in the Bunny.net privacy policy and on the Bunny.net GDPR page.
Web analytics with Rybbit
This website uses Rybbit for statistical analysis of website usage. Rybbit is self-hosted on our own server at the domain t.sebastian-software.de. Data is not shared with third parties.
How It Works
Rybbit operates without cookies and without persistent identifiers. To count unique visitors, Rybbit generates a pseudonymised hash from the IP address and user agent. The IP address is processed only transiently in working memory for hash generation and is never permanently stored or logged. A daily rotating random component (salt) resets this identifier every day, so tracking across days is ruled out.
Processed Data
The following data is collected and stored exclusively in aggregated form:
- Page views (URL, referrer)
- Device information (screen size, operating system, browser)
- Approximate geographic location (country level, derived from the IP address, which itself is not stored)
- Triggered interaction events (such as clicking the booking button or the PDF download), each without any personal reference
Legal Basis
The use of Rybbit is based on Art. 6(1)(f) GDPR. Our legitimate interest lies in analyzing website usage for the needs-based design and optimization of our website. This interest prevails because Rybbit is designed in such a way that no personal data is permanently processed and no conclusions can be drawn about individual users. Since Rybbit does not set cookies and does not access information already stored on the user's device, consent under § 25 TDDDG (German Telecommunications Digital Services Data Protection Act) is not required.
Hosting and Third-Country Transfer
Rybbit is operated on our own server, hosted by Hetzner Online GmbH in Germany. No third-country transfer takes place. This does not constitute a data processor within the meaning of Art. 28 GDPR, as data processing takes place exclusively on our own infrastructure.
For more information about Rybbit, please visit the Rybbit website.
Contact via Email
When you contact us by email, the data you provide (email address, name if applicable, and message content) will be processed to handle your inquiry. If your inquiry is aimed at concluding or performing a contract, the legal basis is Art. 6(1)(b) GDPR (pre-contractual or contractual measures). For general inquiries without a contractual context, the legal basis is Art. 6(1)(f) GDPR; our legitimate interest lies in the proper handling of incoming inquiries. This interest prevails, as processing is limited to what is necessary for responding and data is deleted upon completion. Your data will be deleted once the inquiry has been fully resolved. Where tax or commercial law retention obligations apply (§ 257 HGB, § 147 AO), the relevant data will be retained for up to 10 years.
Processors
We use the following processors pursuant to Art. 28 GDPR, with each of whom a data processing agreement is in place:
- BunnyWay d.o.o. (Bunny.net), Slovenia
- CDN, hosting and edge scripting for this website
- Hetzner Online GmbH, Germany
- Hosting of the Rybbit analytics server
External Links
This website contains links to third-party websites. When you click on these links, you will be redirected to the respective third-party site. The respective operators are responsible for data processing on these external sites. We recommend that you read the privacy policies of the linked sites.
Automated Decision-Making
No automated decision-making, including profiling, pursuant to Art. 22 GDPR takes place.
Your Rights
Under the GDPR, you have the following rights regarding your personal data:
- Right of access (Art. 15 GDPR)
- Right to rectification (Art. 16 GDPR)
- Right to erasure (Art. 17 GDPR)
- Right to restriction of processing (Art. 18 GDPR)
- Right to data portability (Art. 20 GDPR) – applies only to processing based on a contract (Art. 6(1)(b) GDPR), that is, when booking appointments through Terminaro and for contract-related email communication
- Right to object (Art. 21 GDPR) – see separate section below
To exercise your rights, you may contact us at any time at: info@sebastian-software.de
Right to object (Art. 21 GDPR)
Where we process your personal data on the basis of legitimate interests pursuant to Art. 6(1)(f) GDPR, you have the right to object to such processing at any time pursuant to Art. 21 GDPR. If you object, we will no longer process your personal data for these purposes unless we can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims.
To exercise your right to object, you may contact us at any time at: info@sebastian-software.de
Right to Lodge a Complaint with a Supervisory Authority
You have the right to lodge a complaint with a data protection supervisory authority regarding the processing of your personal data. The supervisory authority responsible for us is:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-PfalzPostfach 30 40
55020 Mainz
www.datenschutz.rlp.de
Optional usage reports from our developer tools
This section applies when one of our developer tools offers optional usage reporting through app-tracking, operated by Sebastian Software GmbH. Visiting our websites does not create these reports or grant permission for tool reporting.
With your permission, we use reports to understand which tool versions, commands, and platforms are used and to decide what to maintain and improve. We measure participating installations and repositories, not individual people or everyone who uses a tool. Reporting views are restricted to authorized maintainers; we do not publish individual reports.
Permission and legal basis
The legal basis for optional usage reporting is your consent under Article 6(1)(a) GDPR. Consent also covers the associated storage and access on your device under section 25(1) TDDDG. Reporting stays off until you agree in the tool. You may decline without losing tool functionality or its separately configurable update checks. CI reporting requires separate explicit authorization.
Reporting data
Depending on the tool and reporting contract, reports contain the tool and version, UTC day, registered command or event category and count, local or CI context, batch ID, tool- and profile-scoped installation ID, and consent revision or grant time. Legacy installation and batch IDs contain creation times. The unified client uses random hexadecimal IDs and sends the grant time separately. Its system context can include operating system and version, executable architecture, CPU family, and Linux distribution and kernel version. Legacy invocation reports contain no system context.
Where reliable repository metadata is available, the tool calculates a SHA-256 hash of the normalized repository URL locally. The original URL is not sent. Clones and developers of the same repository share its hash, including across our tools; forks have different hashes. Someone who knows or guesses a URL can calculate and match its hash. Reports are therefore pseudonymous, rather than anonymous. Reports exclude source code, file contents, command arguments, local paths, repository URLs, usernames, machine names, session IDs, and skill names or content.
Separate choices for monthly history and profile linking
Ordinary usage consent does not include these additional uses. Each stays off until you choose it separately in a participating tool. Declining either choice leaves the tool, update checks, and ordinary reporting settings available. An upgrade or a shared local profile file does not grant permission.
Monthly usage history
With your separate consent, we retain screened monthly usage counts and monthly installation and repository totals for 24 months after the month ends, to understand trends and plan maintenance. Detailed reports still expire after 90 days. Only usage from the UTC date after the service acknowledges the choice is eligible. Minimum group sizes and contribution limits can make a month unavailable; they do not guarantee anonymity. This choice does not authorize public release.
You can withdraw monthly-history consent without stopping ordinary reporting. Once acknowledged, withdrawal or deletion invalidates the affected monthly summaries. If the detailed source data has already expired, those months remain unavailable. Offline changes remain pending until acknowledged. The same processors, transfer safeguards, and rights described in this notice apply.
Optional cross-tool profile linking
With another separate consent, we link future local-use reports from participating tools to understand which tools are used together and improve them. Each tool requires its own choice. A random identifier and a separate reset credential are kept in a private local profile file; the service stores the profile identifier, a hash of its credential, tool links, and permission times. This does not identify a verified person or physical machine. Copied files represent the same profile. CI reports are excluded. Eligibility begins on the UTC date after acknowledgement; earlier reports are not linked.
You can unlink one tool or reset the shared profile for all linked tools. A reset removes links, not the tools’ independently retained reports. Deleting a tool’s reports also removes its link. Failed or offline requests remain visibly pending. Profile metadata remains while active links exist; inactive or reset metadata expires after 90 days, followed by physical cleanup within 24 hours. Linking does not extend the 90-day detail limit, enable monthly history, or authorize public release. Profile identifiers and overlap statistics are not published.
These additional choices rely on consent under Article 6(1)(a) GDPR and, for the associated device storage and access, section 25(1) TDDDG. You can withdraw each choice in the same tool settings used to give it, without affecting the lawfulness of earlier processing.
Public monthly usage totals
With a third, separate consent, monthly totals may be published through app-tracking and oss-metrics to show adoption of our tools. This requires monthly-history consent but is not included in it. Public groups contain only month, tool, reporting stream, metric, local or CI context, and counts rounded down to tens. Each group requires at least 20 installations and 20 known repositories, with no installation or repository contributing more than 10 percent. No installation, profile, or repository identifiers, unique counts, or command, version, or system breakdowns are published.
Only reports from the UTC date after acknowledgement can contribute. Published summaries expire after 24 months following month end. Anyone can access and copy public figures. Group checks and rounding reduce disclosure risks but do not guarantee anonymity or prevent matching with other knowledge. You can withdraw publication consent separately while keeping internal monthly summaries. After acknowledgement, we remove affected public summaries and recalculate only where all source data remains available. We cannot recall copies held by others. Offline withdrawal remains pending. The consent basis, processors, safeguards, and rights in this notice also apply to publication.
Processors and international transfers
Reports are sent over HTTPS to our app-tracking service. BunnyWay d.o.o. (Bunny.net), Slovenia, hosts the API and processes connection metadata such as IP addresses. PlanetScale, Inc., United States, provides the database service for reporting data. Our database region for this service is AWS Frankfurt, Germany. A database region in Germany does not mean that all support, security, or subprocessor processing takes place in the EU.
International transfers may occur through these providers and their subprocessors. PlanetScale’s data processing addendum provides for the European Commission’s standard contractual clauses for relevant transfers outside the EEA. The linked provider documents describe their processing and transfer arrangements. You can contact our privacy address above for information about applicable safeguards and a copy of them.
PlanetScale data processing addendum · PlanetScale subprocessors · Bunny processor information
Retention and backups
Usage data expires from active reporting after at most 90 days; physical cleanup follows within another 24 hours. Batch receipts expire 90 days after receipt. Active installation and consent state expire after 90 days without new accepted reports. Minimal revocation or expiry records remain for 90 days after that event, without usage or repository hashes. The unified event service also expires receipts and inactive identity state after 90 days. Expired records are physically removed within another 24 hours.
Our reporting database backup policy is at most seven days. Backups are used for recovery, not reporting. Deleting active data does not edit existing backups in place. Restoring a backup can reintroduce data deleted after its recovery point; known deletion requests must then be applied again. Provider-owned security, transport, and account records follow the applicable provider agreements and policies. The reporting retention periods are not a universal limit for those separate records.
Withdrawal, deletion, and your rights
You can withdraw consent in the tool at any time. Withdrawal stops new collection and uploads and discards unsent usage; it does not affect the lawfulness of earlier processing. Previously received reports remain until deletion or expiry. The tool can show its effective setting and preview queued data locally. Its documentation explains the available controls.
You can separately request deletion of retained reports using the credential held locally by the tool. An offline request remains pending until the service acknowledges it. Losing or explicitly removing local state can prevent automatic deletion or retries. Contact our privacy address if you need help; loss of a credential does not remove your statutory rights. Do not send credentials or private repository URLs as proof of identity. The rights and complaint options described in this policy also apply to tool reporting.
Current metric definitions · Reporting retention and recovery policy

