Privacy Policy
About this policy
This policy explains what personal data is processed when you use the node-zugferd documentation website, why it is processed, and the legal basis for that processing.
Last updated: 14 November 2026.
Who is responsible for your data?
Joél de Olivèira Solano da Silva
Neckarstr. 22, D-64283 Darmstadt, Germany
For privacy questions or requests, email service@jsolano.de.
Data we process and why
We operate a documentation website. We do not offer user accounts or process payment information through it.
| What may be processed | Why and legal basis |
|---|---|
| Technical request data, such as IP address, requested page, browser and device information, referrer, and request time | Vercel, our hosting provider, may process request and log data to deliver, secure, and troubleshoot the site. Our basis is our legitimate interest in operating and protecting the website (GDPR Article 6(1)(f)). The exact fields and retention depend on Vercel's services and configuration. |
| Sidebar preference | The site uses a sidebar_state cookie for seven days to remember whether the documentation sidebar is collapsed. It is used to provide a feature you request, and is not used for advertising. |
| Playground code and technical connection data | When you use an interactive example, the site connects to StackBlitz and CodeSandbox Sandpack. The example code and related technical requests may be sent to those providers so they can run the editor or preview. Their services may receive your IP address, browser/device data, and interaction with the embedded tool. This happens when the relevant playground is loaded. Our basis is our legitimate interest in providing the interactive developer examples (GDPR Article 6(1)(f)). |
| Feedback you submit, including your message, page URL, selected text for block feedback, and your positive or negative rating for page feedback | We use this to review and respond to feedback and improve the documentation. The message is sent to GitHub and stored in the node-zugferd repository's GitHub Discussions. Our basis is our legitimate interest in maintaining and improving the documentation (GDPR Article 6(1)(f)). Do not include sensitive or confidential information. |
| A local copy of submitted feedback | The browser may store a copy in local storage so the feedback form can remember your previous submission. This remains in your browser until it is removed by the site or you clear your browser storage. |
You can browse the documentation without submitting feedback or using an interactive playground. The examples may include publicly available project code. Do not enter personal or confidential information into the playgrounds.
Cookies and browser storage
The documentation uses the sidebar_state cookie for seven days to remember your sidebar preference. It also stores the feedback form's state in browser local storage. We do not use these items for advertising or cross-site tracking.
StackBlitz and Sandpack are third-party services. When an interactive example loads, these providers may use their own cookies or similar technologies under their privacy policies. We do not control this storage. You can avoid the associated data transfer by not opening interactive examples.
Who receives data
- Vercel hosts the website and may process visitor request data and service logs. Vercel acts as a processor for data it handles on our instructions where the DPA applies. See Vercel's Privacy Notice and Data Processing Addendum.
- StackBlitz provides the embedded online editor. See StackBlitz's Privacy Policy.
- CodeSandbox provides Sandpack, the interactive code editor and preview used in some examples. See CodeSandbox's Privacy Policy.
- GitHub receives feedback submitted through the documentation feedback feature and hosts it in GitHub Discussions. Discussions in the public node-zugferd repository can be visible to the public. See GitHub's General Privacy Statement.
We do not sell personal data or use it for targeted advertising. We do not use feedback submitted through this site to train our own AI models.
International data transfers
The operator is based in Germany, and the providers above may process data in the United States or other countries. Where Vercel processes personal data as our processor, its DPA sets out the applicable transfer safeguards, which may include Standard Contractual Clauses. StackBlitz, CodeSandbox, and GitHub handle data under their own terms and privacy commitments. Review their linked notices for details about their locations and transfer mechanisms.
How long we keep data
- Sidebar preference: up to seven days in the cookie. Browser local storage remains until cleared or removed by the site.
- Feedback: retained in GitHub Discussions until the discussion or comment is removed. You can ask us to remove feedback by emailing service@jsolano.de. Public copies, quotes, or cached versions may remain outside our control.
- Hosting and security logs: retention is controlled by Vercel's service and configuration. We do not have a separately verified retention period for these logs, so see Vercel's Privacy Notice for its practices.
- Data held by StackBlitz, CodeSandbox, or GitHub: governed by each provider's own retention practices.
Your rights
Depending on your circumstances and applicable law, you may have the right to access your personal data, request its correction or deletion, and request restrictions on its processing. You may also have the right to object to processing based on legitimate interests and to receive certain data in a portable format.
To exercise your rights, email service@jsolano.de. We may ask for information needed to verify your request. You may also lodge a complaint with a data protection supervisory authority, in particular in the EU country where you live, work, or believe a violation took place. Your rights are subject to legal conditions and exceptions.
For information processed directly by StackBlitz, CodeSandbox, GitHub, or Vercel for their own purposes, you may need to contact that provider directly.
Security
We use Vercel to host the site and take reasonable steps to protect the information we control. No website or transmission method can be guaranteed to be completely secure.
Changes to this policy
We may update this policy when the site or its data practices change. The date at the top shows when it was last updated. Material changes will be reflected on this page.
Legal sources
This policy refers to the EU General Data Protection Regulation, including Articles 6, 13, and 27. Information about storage on or access to a visitor's device is also relevant to the ePrivacy Directive, as implemented in the applicable EU country.