Your data stays local unless you share it.
QR-log Bridge reconstructs files on device. No accounts, analytics SDKs, or developer-controlled transfer servers.
The short version.
No accounts, no analytics, local QR processing.
No login required
No accounts, sign-ins, or profiles.
No analytics SDKs
No advertising IDs, analytics, or tracking services.
Local processing
Files stay in the app sandbox until you act.
What the website and app handle locally.
1. Controller
The controller for personal data processed in connection with this website and QR-log Bridge is Roland Emrich, Schulstrasse 23, 91325 Adelsdorf, Germany. Contact: emrich.roland@gmail.com. Further imprint details are available on the Imprint page.
2. Website access and server logs
When you request a page, the hosting infrastructure necessarily processes technical connection data such as IP address, date and time, requested resource, transfer size, HTTP status, referrer information where sent, and browser and operating-system information. These data are used for technical delivery, security and troubleshooting, not for analytics or advertising. Any access or error-log retention is controlled by the hosting configuration and should be limited to the technical and security purpose.
3. Hosting and contact
The website has no application-level payload backend. If a hosting or email provider processes technical request data or messages, it receives only the data required for that service and may process it under its own legal and contractual obligations. Please do not send confidential or patient information by unencrypted email.
4. Cookies, storage and analytics
The website does not use cookies, Local Storage, IndexedDB, service workers, analytics SDKs, advertising IDs or marketing trackers. The fullscreen viewer uses a temporary sessionStorage flag only to carry a user-selected navigation state; it is removed after it is read and is not used for tracking. No consent banner is currently required for this verified functionality.
5. Browser QR Payload Encoder
The QR Payload Encoder processes the file expressly selected by you locally in the browser to generate a QR/HC2D stream or GIF. The selected file and generated payload are not uploaded to the QR-log Bridge website or to a developer-controlled server. The browser may hold the data temporarily in memory while the output is generated.
6. Contact requests
If you contact us by email, we process the information you send to handle and answer your request. Depending on the context, the legal basis is Article 6(1)(b) GDPR for contractual or pre-contractual communication or Article 6(1)(f) GDPR for general enquiries. Messages are deleted when they are no longer required, subject to applicable retention or evidence requirements.
7. QR-log Bridge app
QR-log Bridge is designed for local optical file transfer. It does not require an account or login and, under the current architecture, does not use developer-controlled transfer servers for user payloads. The developer does not receive QR frames, files, photos or videos merely because the app is used.
8. Camera, live scan and local video
The app can use the camera to detect and decode animated QR/HC2D streams. Camera frames are processed locally. For compatible fast streams, the app can create a local recording for the calculated transfer duration and process it locally through Video Decode. Captured videos remain on the device until you delete them, remove the app or take another user-initiated action. Camera frames and captured videos are not automatically uploaded to developer-controlled servers.
9. Files, photos and videos
Through a user action, the app can select local files or photos for sending. Video Decode can process a recording selected from Photos or Files. The app does not generally access the complete photo library, contacts, messages, calendar or location history. Received files and captured videos may be stored locally, opened, shared or deleted. If you select Save to Photos, the selected content is handed to the iOS/iPadOS system function for saving in the photo library.
10. Sharing with other apps
If you share a file or video through the iOS/iPadOS share sheet, the selected content is provided to the app or service you choose. That third party processes the content under its own terms and privacy policy.
11. Integrity and confidentiality
QR-log Bridge uses integrity and error-detection mechanisms such as CRC32, SHA-256 and protocol-specific recovery mechanisms. They support error detection and reconstruction but do not provide end-to-end encryption. Encrypt confidential, personal or patient-related content before optical transfer where confidentiality is required.
12. External links
The website links to external services including the Apple App Store, TestFlight, GitHub and LinkedIn. They are not embedded as tracking services when this website is loaded. When you follow a link, the destination provider's privacy rules and processing apply.
13. Retention
Website connection data are retained only according to the hosting configuration and the technical or security purpose. Contact requests are retained until they are no longer needed or a legal retention duty applies. App files and captured videos remain on the device until you delete them, use an app deletion function or remove the app.
14. Your rights
Where the legal requirements are met, you may request access, rectification, erasure, restriction of processing and data portability, and object to processing based on Article 6(1)(e) or (f) GDPR. Requests can be sent to emrich.roland@gmail.com.
15. Supervisory authority
You may lodge a complaint with a data protection supervisory authority. For a non-public controller established in Bavaria, this is generally the Bayerisches Landesamt fuer Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach, Germany: lda.bayern.de.
16. Decisions, security and changes
The website and the developer-side processing described here do not perform solely automated decisions or advertising/user-scoring profiling. Reasonable safeguards include HTTPS/TLS, access controls, security updates, limited technical logs and security headers where enabled. This policy is updated when the website, app functions, service providers or legal requirements materially change.