Your data stays on the device unless you decide otherwise.
QR-log Bridge is designed for local, camera-based file transfer through QR codes. The app reconstructs files on the iPhone or iPad itself and does not rely on developer-controlled servers, user accounts, analytics SDKs, or background data collection.
This page explains what the app handles, what it does not collect, and where responsibility shifts to iOS system features or third-party apps you choose yourself.
The policy in one screen.
QR-log Bridge is built around data minimization. In its current form the app does not require accounts, does not include analytics or advertising networks, and processes QR frames locally on the device.
No login required
The app does not use user accounts, sign-ins, or profile systems.
No analytics SDKs
No advertising identifiers, analytics frameworks, or tracking services are included.
Local processing
QR frames are decoded on-device, and reconstructed files stay in the app sandbox until you act on them.
What the app handles and what it does not handle.
1. Overview
QR-log Bridge receives data by scanning animated QR codes with the iPhone camera. The app reconstructs the original file locally on the device and allows you to open or share it after transfer.
The app is designed around data minimization. In its current form it does not use user accounts, does not require login, and does not integrate analytics or advertising networks.
2. What Data We Collect
QR-log Bridge does not collect personal data on the developer's servers. The app processes QR frames only locally on your device and stores the received file locally in the app sandbox until you open or share it.
- No account information is collected.
- No analytics or advertising IDs are used.
- No location data is collected.
- Contacts, photos, messages, and calendar data are not accessed.
- No data is transmitted to developer-controlled servers.
- Local file metadata such as file name, file size, and modification date is read only to display the in-app file library.
3. Camera Access
The app uses the camera only to scan QR codes and decode transfer frames. Camera data is processed only on the device to receive the file. The app does not record video, upload camera content, or store video recordings.
4. File Storage
After a successful transfer, the reconstructed file is stored locally on your device inside the app's documents area. The file remains there until you delete it or remove the app.
The app also keeps a local library of received files so you can open or share them later. To show this library, the app reads only local metadata such as file name, file size, and modification date from the app sandbox.
Depending on the file type, you can preview the file with Quick Look or share it through iOS system actions. The app does not upload the file to third-party services.
5. Data Security
QR-log Bridge uses local integrity checks such as CRC32, SHA-256, and FEC/parity logic to ensure the transfer completes correctly. These checks are used for error detection and are not a substitute for encryption.
The app does not provide end-to-end encryption. If confidentiality is required, the content should be encrypted before sending.
6. Third-Party Services
The app does not include analytics SDKs, advertising SDKs, or tracking services from third parties. If you share a received file with another app, that app or service may process the file according to its own privacy policy.
7. Children's Privacy
QR-log Bridge is not directed to children and does not knowingly collect personal data from children.
8. Changes to This Policy
This policy may be updated when the app changes. The current version on this page reflects the latest known behavior of the app.
9. Contact
If you have questions about this privacy policy, please contact emrich.roland@gmail.com.